That is bad for so many reasons...
1. New users won't know to do that. Old users with new hardware
might have a bit of trouble.
2. You get a file that must be hacked. The syntax looks like a
cross between /bin/sh and LISP.
3. There is no connection between that file and the kernel.
Any changes must be matched with module parameters and/or
boot parameters. Even if all this were documented, it would
be difficult. Module parameter systax is not consistent with
boot parameter syntax and drivers vary greatly.
4. If the hardware changes, such a config file may cause conflicts.
The system might not even boot after a hardware or Windows upgrade.
(Windows is known to change BIOS PnP settings!)
5. This is not PnP. It is software jumpers. PnP exists because it
is moronic to make the user tell the computer about the computer.
Computers ought to be able to determine their own innards.
6. This won't let us reallocate devices. If I have n IRQs available
for the ISA bus and cards that need n+2 IRQs, I ought to be able
to use all but 2 devices at the same time without deciding that
2 particular devices just won't ever function. The kernel needs
to move IRQs as needed so that I can freely use my hardware.
Userspace can't handle this at all.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/