[Mario 'BitKoenig' Holbe] > Sorry, but this is a very strange argumentation and hard to follow.
OK. Lack of time cause me to not include the complete background. > Shouldn't the reason for something to happen in runlevel S be functional > rather than non-functional? Maintainability, useability, and concurrency > are all pure non-functional properties. Sure. > The functional reason for something belonging to runlevel S is > hardware setup and configuration, and initial system setup. This is > why things like hwclock, hdparm, ifupdown, keyboard-setup, etc., as > well as mount* reside there. These are not really the reasons to putting stuff in rcS.d (which is not the same as runlevel S). Scripts should be put in rcS.d/ if they have to run before the machine enter runlevel S at boot. runlevel S is the runlevel running only one process, /sbin/sulogin. rcS.d/ is more accurately called rc.boot in other distributions, and they often require all hooks to go into the real runlevels (0-6). Most of hardware setup and configuration and initial system setup can be and should be placed in runlevels 2-6 to ensure that runlevel 1 and single user become more useful when needing to recover a problematic machine. Do not have time to for now. :) Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
