Old Hardware

[Farley Flud]

I hear a lot of ignoramus assholes talk about how GNU/Linux is
the savior of old, and obsolescent, hardware.

That certainly is true, but not how these assholes believe.

GNU/Linux can indeed accommodate any old hardware configuration,
but don't expect the average distro to do it.

Example:

Let's say that you want floppy disk access. Floppy disks have
been obsolete for many, many years, but GNU/Linux can easily
provide access.

But not through the average fucking distro!

To get floppy access, one has to go to kernel.org, which contains
ALL the kernels since the very beginning, and find the last
kernel version that has floppy drivers. Then, the kernel has
to compiled and installed.

Also, the repositories of GLIBC would have to be searched for an
appropriate, if necessary, version to support floppy access.

Again, any software that may be relevant to floppy access would
have to be acquired from the archives of said software.

In this way, a complete system that supports floppy disk access
could be built.

GNU/Linux can support ALL hardware back to 1991 but the user has
to be prepared to build the system. No distro can do it.

What about Microslop Winblows?

Ha, ha, ha, ha, ha, ha! That proprietary piece of junk can't
support anything beyond yesterday. (One of my client's scanners
suddenly failed with one of their stupid updates.)

Microslop has no archives. Such is never the way of commercial
garbage.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

[Physfitfreak]

Post by Farley Flud
I hear a lot of ignoramus assholes talk about how GNU/Linux is
the savior of old, and obsolescent, hardware.
That certainly is true, but not how these assholes believe.
GNU/Linux can indeed accommodate any old hardware configuration,
but don't expect the average distro to do it.
Let's say that you want floppy disk access. Floppy disks have
been obsolete for many, many years, but GNU/Linux can easily
provide access.
But not through the average fucking distro!
To get floppy access, one has to go to kernel.org, which contains
ALL the kernels since the very beginning, and find the last
kernel version that has floppy drivers. Then, the kernel has
to compiled and installed.
Also, the repositories of GLIBC would have to be searched for an
appropriate, if necessary, version to support floppy access.
Again, any software that may be relevant to floppy access would
have to be acquired from the archives of said software.
In this way, a complete system that supports floppy disk access
could be built.
GNU/Linux can support ALL hardware back to 1991 but the user has
to be prepared to build the system. No distro can do it.
What about Microslop Winblows?
Ha, ha, ha, ha, ha, ha! That proprietary piece of junk can't
support anything beyond yesterday. (One of my client's scanners
suddenly failed with one of their stupid updates.)
Microslop has no archives. Such is never the way of commercial
garbage.
Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

But what you say can be done with Linux can be done with Winblows
machines too. Just install an earlier version of Winblows and do not
update.

Which is simpler?

I have a Win10, a Win7, and a WinXP machine tightly stored away, but
easily accessible just for the occasions that Linux cannot do the job.
Do you know what those occasions are?... They're almost always occasions
when I'm doing something sensitive and formal that have deadlines to
them. That's when Linux fails. This is thanks to what people, Flud?
Who's responsible for this?

[CrudeSausage]

Post by Physfitfreak

Post by Farley Flud
I hear a lot of ignoramus assholes talk about how GNU/Linux is
the savior of old, and obsolescent, hardware.
That certainly is true, but not how these assholes believe.
GNU/Linux can indeed accommodate any old hardware configuration,
but don't expect the average distro to do it.
Let's say that you want floppy disk access.  Floppy disks have
been obsolete for many, many years, but GNU/Linux can easily
provide access.
But not through the average fucking distro!
To get floppy access, one has to go to kernel.org, which contains
ALL the kernels since the very beginning, and find the last
kernel version that has floppy drivers.  Then, the kernel has
to compiled and installed.
Also, the repositories of GLIBC would have to be searched for an
appropriate, if necessary, version to support floppy access.
Again, any software that may be relevant to floppy access would
have to be acquired from the archives of said software.
In this way, a complete system that supports floppy disk access
could be built.
GNU/Linux can support ALL hardware back to 1991 but the user has
to be prepared to build the system.  No distro can do it.
What about Microslop Winblows?
Ha, ha, ha, ha, ha, ha!  That proprietary piece of junk can't
support anything beyond yesterday.  (One of my client's scanners
suddenly failed with one of their stupid updates.)
Microslop has no archives.  Such is never the way of commercial
garbage.
Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

But what you say can be done with Linux can be done with Winblows
machines too. Just install an earlier version of Winblows and do not
update.
Which is simpler?
I have a Win10, a Win7, and a WinXP machine tightly stored away, but
easily accessible just for the occasions that Linux cannot do the job.
Do you know what those occasions are?... They're almost always occasions
when I'm doing something sensitive and formal that have deadlines to
them. That's when Linux fails. This is thanks to what people, Flud?
Who's responsible for this?

If anyone has an external USB floppy drive, or a floppy drive they can
put into a USB enclosure, I'll bet that Windows 10 and 11 will support
it out of the box. Larry Pietraskiewicz is usually full of shit and I
wouldn't be surprised to learn that he's wrong here too.

[Farley Flud]

Post by Physfitfreak
I have a Win10, a Win7, and a WinXP machine tightly stored away, but
easily accessible just for the occasions that Linux cannot do the job.
Do you know what those occasions are?... They're almost always occasions
when I'm doing something sensitive and formal that have deadlines to
them. That's when Linux fails. This is thanks to what people, Flud?
Who's responsible for this?

You'll have to be far more specific. Exactly what job(s) causes GNU/Linux
to fail?

I use GNU/Linux for all things, personal and paid($$$$), and have
absolutely no need for Microslop. Indeed, for me, using Microslop
would severely hamper my productivity -- and my productivity extends
into many areas.

However, I am literally forced to maintain a Microslop machine solely
because certain web sites that I need to access will fail with GNU/Linux.
The fault here is the incompetent "developers" who cannot do their
piddly-diddly coding according to standards.

[DFS]

Post by Farley Flud
I use GNU/Linux for all things, personal and paid($$$$),

You've been repeating this lie for years.

Post by Farley Flud
However, I am literally forced to maintain a Microslop machine solely
because certain web sites that I need to access will fail with GNU/Linux.

Which sites?

[Joel]

However, I am literally forced to maintain a Microslop [Windows] machine solely
because certain web sites that I need to access will fail with GNU/Linux.
The fault here is the incompetent "developers" who cannot do their
piddly-diddly coding according to standards.

I have Microsoft's Web browser, in Linux, Edge.
--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

[CrudeSausage]

Post by Joel

However, I am literally forced to maintain a Microslop [Windows] machine solely
because certain web sites that I need to access will fail with GNU/Linux.
The fault here is the incompetent "developers" who cannot do their
piddly-diddly coding according to standards.

I have Microsoft's Web browser, in Linux, Edge.

Way to stick it to Microsoft, faggot.

[Stéphane CARPENTIER]

Post by Farley Flud
You'll have to be far more specific. Exactly what job(s) causes GNU/Linux
to fail?

Your own doing.

Post by Farley Flud
However, I am literally forced to maintain a Microslop machine solely
because certain web sites that I need to access will fail with GNU/Linux.

I don't believe that. Twenty years ago using Firefox on Linux could
bring a bad experience with some websites which where clearly designed
for IE. But I can't remember the last time I was unable to access a
website with Linux. It's too long ago. And if that would happen, it
would clearly not be a needed website I would need to access.

I can believe that you are unable to access a website because you are
using too old junk believing it's modern. But it's neither the fault of
Linux or the website.

Post by Farley Flud
The fault here is the incompetent "developers" who cannot do their
piddly-diddly coding according to standards.

No, the fault is on you. The standards today are really more respected
than twenty years ago.

[Physfitfreak]

Post by Farley Flud
However, I am literally forced to maintain a Microslop machine solely
because certain web sites that I need to access will fail with GNU/Linux.
The fault here is the incompetent "developers" who cannot do their
piddly-diddly coding according to standards.

They may be comptetent but paid not to do that. Imagine that as long as
a computer is with you, there's an Al Capone standing right behind you.

Then you'll get the picture.

[candycanearter07]

Post by Physfitfreak

Post by Farley Flud
I hear a lot of ignoramus assholes talk about how GNU/Linux is
the savior of old, and obsolescent, hardware.
That certainly is true, but not how these assholes believe.
GNU/Linux can indeed accommodate any old hardware configuration,
but don't expect the average distro to do it.
Let's say that you want floppy disk access. Floppy disks have
been obsolete for many, many years, but GNU/Linux can easily
provide access.
But not through the average fucking distro!
To get floppy access, one has to go to kernel.org, which contains
ALL the kernels since the very beginning, and find the last
kernel version that has floppy drivers. Then, the kernel has
to compiled and installed.
Also, the repositories of GLIBC would have to be searched for an
appropriate, if necessary, version to support floppy access.
Again, any software that may be relevant to floppy access would
have to be acquired from the archives of said software.
In this way, a complete system that supports floppy disk access
could be built.
GNU/Linux can support ALL hardware back to 1991 but the user has
to be prepared to build the system. No distro can do it.
What about Microslop Winblows?
Ha, ha, ha, ha, ha, ha! That proprietary piece of junk can't
support anything beyond yesterday. (One of my client's scanners
suddenly failed with one of their stupid updates.)
Microslop has no archives. Such is never the way of commercial
garbage.
Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

But what you say can be done with Linux can be done with Winblows
machines too. Just install an earlier version of Winblows and do not
update.
Which is simpler?

[snip]


The thing is that it's pretty hard to avoid updates on Win10/11, and
most software isn't supported on anything older. It's not being actively
developed at all.

[vallor]

I hear a lot of ignoramus assholes talk about how GNU/Linux is the
savior of old, and obsolescent, hardware.
That certainly is true, but not how these assholes believe.
GNU/Linux can indeed accommodate any old hardware configuration, but
don't expect the average distro to do it.
Let's say that you want floppy disk access. Floppy disks have been
obsolete for many, many years, but GNU/Linux can easily provide access.
But not through the average fucking distro!

Linux Mint:

$ modinfo floppy | head -15
filename: /lib/modules/6.12.6/kernel/drivers/block/floppy.ko
alias: block-major-2-*
license: GPL
description: Normal floppy disk support
author: Alain L. Knaff
srcversion: 4E043AC02575D63C156F3CD
alias: acpi*:PNP0700:*
alias: pnp:dPNP0700*
depends:
intree: Y
name: floppy
retpoline: Y
vermagic: 6.12.6 SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
_ _ _ _ _ _ _

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

If my system had a floppy disk, it would be "plug and play".

But not on your system.

You lose. Again.

[Farley Flud]

Post by vallor
block-major-2-*
If my system had a floppy disk, it would be "plug and play".

But where are you going to plug it?

Holy moley! Your kernel must contain HUNDREDS of modules that you NEVER
have a need to use.

That's the mainstream distro strategy: build everything and build it
according to the lowest denominator specs and then heap a ton of security
on top of the mess.

[Chris Ahlstrom]

Post by Farley Flud

Post by vallor
block-major-2-*
If my system had a floppy disk, it would be "plug and play".

But where are you going to plug it?

USB.

Post by Farley Flud
Holy moley! Your kernel must contain HUNDREDS of modules that you NEVER
have a need to use.
That's the mainstream distro strategy: build everything and build it
according to the lowest denominator specs and then heap a ton of security
on top of the mess.

He got plenty of disk space, bro. On Arch /lib/modules is about 160Mb.

[Farley Flud]

Post by Chris Ahlstrom
On Arch /lib/modules is about 160Mb.

On my system /lib/modules is only 6Mb, that's SIX Mb.

I can count the Mb's on the fingers of one hand (yes, I am
a mutant).

But we have to add to that the proprietary Nvidia modules
which total 80Mb. (Nvidia is like a mini-junk-distro that
tries to support all vid cards with a single module.)

Still, my in-tree kernel modules total 6Mb and that's how
it should be. GNU/Linux is quite efficient.

The mainstream distros, however, are forced to cram 160Mb
when only 6Mb are actually necessary.

Don't keep apologizing for this lunacy.

[Stéphane CARPENTIER]

Post by Farley Flud

Post by Chris Ahlstrom
On Arch /lib/modules is about 160Mb.

On my system /lib/modules is only 6Mb, that's SIX Mb.

You should avoid to install Linux on a floppy disk. It would be way
more faster and you'd be less concerned by a few mega of disk usage.

Post by Farley Flud
I can count the Mb's on the fingers of one hand

That's probably why you can't access websites with Linux. You should
install everything needed instead. You wouldn't need to ask Windows to
do it for you.

Post by Farley Flud
Still, my in-tree kernel modules total 6Mb and that's how
it should be. GNU/Linux is quite efficient.

Yes, it's the way it gives you an excuse to use Windows.

Post by Farley Flud
The mainstream distros, however, are forced to cram 160Mb
when only 6Mb are actually necessary.

And let me access any website without the need to fall back on Windows.
You see? You are not a Linux defender, you are a Windows aficionado.

Post by Farley Flud
Don't keep apologizing for this lunacy.

I don't.

[Physfitfreak]

Post by Farley Flud
On my system /lib/modules is only 6Mb, that's SIX Mb.
I can count the Mb's on the fingers of one hand (yes, I am
a mutant).

You have six fingers?..

[Stéphane CARPENTIER]

Post by Farley Flud

Post by vallor
block-major-2-*
If my system had a floppy disk, it would be "plug and play".

But where are you going to plug it?

In your ass.

Post by Farley Flud
Holy moley! Your kernel must contain HUNDREDS of modules that you NEVER
have a need to use.

Yes, and the good part is: as Linux is modular, if a module isn't
needed, it's never loaded. So it takes only a few space on the hard
drive and nothing more. It's simplicity without inefficiency. What
do you get with your computer? From some other of your messages, it's
clear: difficulty and failure. I won't switch my efficient computer with
your brick disguised as a computer.

[Farley Flud]

Post by Stéphane CARPENTIER
Yes, and the good part is: as Linux is modular, if a module isn't
needed, it's never loaded.

That's only for modules.

There is still the core kernel which can be configured.

Post by Stéphane CARPENTIER
It's simplicity without inefficiency.

Your fucking brain is simplicity *with* inefficiency.

Post by Stéphane CARPENTIER
What do you get with your computer?

I get a kernel (without modules) that fits my hardware like
a glove -- and without choking security.

The mainstream distros (like yours) only provide a "lowest
common denominator" kernel, which is junk.

My benchmarks PROVE that I get up to 37% performance increase
over the junk distros, and to me that is quite important
because I do SIGNIFICANT WORK but you do NOTHING.

So shut your ignoramus mouth.

Idiot.

[Stéphane CARPENTIER]

Post by Farley Flud

Post by Stéphane CARPENTIER
Yes, and the good part is: as Linux is modular, if a module isn't
needed, it's never loaded.

That's only for modules.

Yes. That's the purpose of modules.

Post by Farley Flud
There is still the core kernel which can be configured.

Which is configured. To be modular. Like that, only the required stuff
is launched by default, everything else is launched only when needed.

Post by Farley Flud

Post by Stéphane CARPENTIER
It's simplicity without inefficiency.

Your fucking brain is simplicity *with* inefficiency.

Great, you improved. You see? It's not that difficult to use other words
than "idiot". I knew you could do it. Please continue.

Post by Farley Flud

Post by Stéphane CARPENTIER
What do you get with your computer?

I get a kernel (without modules) that fits my hardware like
a glove -- and without choking security.

Yes. You inability to access websites is clearly an improvement on the
security of your computer. Too bad you need Windows to compensate for
that.

Post by Farley Flud
The mainstream distros (like yours) only provide a "lowest
common denominator" kernel, which is junk.

Which is fast, efficient and let me avoid Windows at home.

Post by Farley Flud
My benchmarks PROVE that

You mostly proved you don't know how to do a benchmark.

Post by Farley Flud
I get up to 37% performance increase over the junk distros,

You would need to install other distros to be able to do it. Which you
can't.

Post by Farley Flud
and to me that is quite important because I do SIGNIFICANT WORK

The only thing you do significantly is daydreaming.

Post by Farley Flud
but you do NOTHING.

Once again, it's not relevant. You claim things about what you do. It's
unrelated with what I do.

Post by Farley Flud
So shut your ignoramus mouth.

Once again, I do what I want and it's not

Post by Farley Flud
Idiot.

Ah no. Not again. Improve. Be as you pretend: don't always fall back on
the simplicity to use the only word you know.

[Chris Ahlstrom]

Post by vallor
$ modinfo floppy | head -15
filename: /lib/modules/6.12.6/kernel/drivers/block/floppy.ko
alias: block-major-2-*

Ubuntu:

$ modinfo floppy
filename: /lib/modules/5.15.0-122-generic/kernel/drivers/block/floppy.ko
alias: block-major-2-*

Debian Sid:

$ /sbin/modinfo floppy
filename: /lib/modules/6.11.10-amd64/kernel/drivers/block/floppy.ko.xz
alias: block-major-2-*

Arch:

$ modinfo floppy
filename: /lib/modules/6.12.4-arch1-1/kernel/drivers/block/floppy.ko.zst
alias: block-major-2-*

I wonder why they are compressed in Sid and Arch.