Posted by: Anonymous Coward
on July 23, 2006 03:39 AM
Why are you checking for every piece of hardware, or device known to man on every BOOT anyway! Your boot sequence thought proccess is seriously flawed. Your treating even a completed HDD install of Linux as if you are booting a "LIVE CD". Only Boot to what is known, and configured previously on HDD installed systems. Add a "Scan For Hardware" (changes) menu option to Lilo/Grub. Then pass the "Scan For Hardware" app/script, on to the Desktop GUI people. They could then add to that, a graphical way to scan-for-hardware, and load/unload kernel modules. That way, you see, the Linux Desktop GUI's can come up to speed with Windows 95 in this regard. Currently, users who can't/won't use the command line, are painted into a corner when devices aren't found at boot. This method fixes both problems, and should net you wildly quicker boots!
Cleaning up the wacky calls in the code is great work to do. But adding some real-world "common sense" to the boot proccess couldn't hurt either.
Learn about Linux
Download Linux
Get Linux help
Why userspace sucks? Boot Up Only What's Known!
Posted by: Anonymous Coward on July 23, 2006 03:39 AMThat way, you see, the Linux Desktop GUI's can come up to speed with Windows 95 in this regard. Currently, users who can't/won't use the command line, are painted into a corner when devices aren't found at boot. This method fixes both problems, and should net you wildly quicker boots!
Cleaning up the wacky calls in the code is great work to do. But adding some real-world "common sense" to the boot proccess couldn't hurt either.
#