In case anyone has been annoyed by the floppy drive light always being on. I finally found that if I loaded the floppy module, it would go out as it should. I have no idea why the drive was being continuously polled without the module being loaded. Nor do I know why the module wasn't loaded automatically by udev. Hopefully this will help someone else.
Most of that comes from hwdetect --modules, minus the stuff I don't want.Code:MODULES=(cdrom agpgart intel-agp evdev psmouse serio_raw pci_hotplug rtc-cmos rtc-core rtc-lib ac97_bus snd-page-alloc snd-pcm snd-timer snd snd-ac97-codec snd-maestro3 soundcore ata_generic sd_mod ata_piix e100 mii usbcore usb-storage uhci-hcd)
Last edited by K.Mandla; January 12th, 2008 at 01:54 PM. Reason: For some reason, it appears I was typing in another language.
Ubuntu user #7247 :: Linux user #409907
Static? Are you serious? That's what I meant by being "sane". One would want something like udev if hotplugging occurs regularly. So of course, if you have no hotplugging devices, there is no concern over plugging in something and the module not being inserted into the kernel.
But with udev, hotplug, devfs, you have only the nodes for devices that are actually plugged in. That's what these utilities are for, to make life easier and keep things neat And a sane kernel, will have modules, not everything built in. But yeah, I do have an insane K6 and I don't use any kind of initrd.
Actually, most of the problems faced usually are direct results of manually loading modules in rc.conf
The ultimate "boot-up time" tweak: suspend and hibernate
My favorite method at the moment is uswsusp's "s2both" which saves the current state to disk and then suspends to ram -- it uses what was saved to disk only in case something happens to power while the computer is asleep. It works great.
You can also use it on desktop computers, of course, which is what I do on mine -- my computer starts up in about 2-3 seconds...
BTW - those of you who don't really use the Arch website all that often should go and check out the awesome new look and logo
That will get you all of the standard device nodes. For any that get missed, read the kernel documentation for the module/driver. They generally list the names and major/minor numbers of the related device nodes. (/usr/src/linux/Documentation is an interesting read)Code:/dev/.static/dev
yabbadaboop: hmm i have to say you are somewhat correct!