SystemV 18 August 2004 Summary  I removed hotplug from SysV and added modules with modconf -- likely needs tweaking. Software and Guides main packages (the system itself) sysv-rc sysvinit configuration tools sysv-rc-conf (to see start only) sysv-rc-conf -p  (to see both start and kill, with priorities) ksysv (use this to save a configuration, for safety and comparison) sysvconfig (not as useful) Installation history 18 August 2004: the move away from hotplug Far too many modules were loaded automatically, and I couldn't figure out why. firewire, wireless, and other modules were loading unasked you should keep a full list of modules loaded automatically pick from them when you now switch to a manual system It turns out the hotplug utility is responsible for the autoloading Hotplugging is enabled in the 2.6.7-1 kernel (that's fine) The daemon is turned on at boot in SysV, which runs /etc/init.d/hotplug I turned it off in runlevel S in sysv -- that's the only place it was on For details see man hotplug and /etc/hotplug/ sysv-rc-conf -- check spello for reasonable values runlevel 1 is for single-user mode -- keep a minimum of other stuff there use runlevel 2 at home, default runlevel use runlevel 3 at work, add telinit 3 to /usr/bin/office script runlevel 4 not used runlevel 5 normall X11 runlevel 6 reboot runlevel 0 halt runlevel S may be useful for booting up? Not sure After booting the kernel without hotplug, add modules manually run modconf and pick those you need they get added to /etc/modules some file systems didn't get loaded soon enough (vfat and ntfs) the partitions didn't mount automatically try placing the SysV scripts in runlevel S -- that worked Somehow my SysV changes blocked non-root login, creating the file /etc/nologin /etc/init.d/bootmisc.sh is responsible for this /etc/init.d/rmnologin removes it, so keep that in runlevel 2 (or maybe S?) Alsa was having problems restoring -- that's alsactl restore I tried placing alsa in runlevel S -- not yet tested I set /etc/default/bootlogd to yes to enable bootlogging, activate it in runlevel S in sysv-rc-conf You can run sys-rc-conf in two modes simple -- just issue sys-rc-conf complex -- issue sys-rc-conf -p A different set of modules are needed for different circumstances use the /usr/bin/office script to load and unload modules for the office let the default boot into the /home values (at least for how) Power management issues Some change I made in SysV made Sigillo power off again on its own! all functionality is now restored -- modem working great, headphones fantastic (but mono), wireless worked in Berlin booting now no longer loads extra modules, and you can have module loading and unloading in the context scripts (home, class, office) power management still imperfect -- lots of components (cpufreq, cpu voltage scaling, spinning down harddrive, acpi, suspend to ram, suspend to disk -- it's not worth messing with and they're working on it on balance, the laptop is now well supported, and my understanding of Linux on Sigillo has translated extremely well to Tord's Dell laptop there's the powermanagement stuff left, but it's too complicated to bother learning -- just leave it write up some of the ideas in your conversation with mor Laptop mode for disk and CPU: conf files need more tweaking worked on power management -- tentative configurations: installed and configured cpufreqd installed and configured laptop-mode-tools I then disabled laptop mode in SysV runlevel 2, it stops the disk too much! This needs tweaking