On Mon, Apr 12, 2010 at 09:51:20PM +0200, Hans de Goede wrote:
Wrong, except for laptops until very recently every single standard
machine sold
came with a floppy drive. In the university where I used to work all new machines
came with a ... floppy. That is all 2000 of them.
Where are your numbers, statements like EVERYONE and NOBODY really are quite
meaningless without some solid numbers to back them up.
Alright, whatever. I have no interest in arguing this.
> PNP only reports the presence of the controller, not
> the drive.
>
Wrong again, on most machines the presence of the PNP0700 id in the PNP data
depends on the setting of the floppy drive type in the BIOS, set it to None
and PNP0700 id goes away.
No, it's just like everything else. This is how the BIOS /should/ work,
theory and practice are seldom similar. This bit Dave, and it bit me on
all my machines, across a variety of vendors.
Erm, you *completely* failed to respond to my upstream argument, if
this is
as clear cut a decision as you make it, why don't you take it upstream ?
This whole discussion really is quite simply, there are 3 options here:
1) floppy driver autoloading on pnp info is a bad idea ->
take it upstream
2) this is a gray area ->
let not deviate from upstream, discuss upstream
Upstream is irrelevant. They don't make an OS, we do.
3) floppy driver autoloading is fine, people with problems need
to be educated to properly configure their BIOS
This is ridiculous.
Also note that anaconda is autoloading the floppy driver on every
install,
so if it would really be the cause of a lot of problems, we (the anaconda
team) would have been overwhelmed by bug reports about this by now, which
surprise, surprise we are not.
The issue is that probing the controller with no drives attached causes
extremely long boot delays. That's why we removed the module aliases.
regards, Kyle