On Mon, Jan 10, 2011 at 8:17 PM, Kurt Roeckx <k...@roeckx.be> wrote: >> + method guaranteed to be supported by all init implementations. An >> + exception to this rule is scripts or jobs provided by the init >> + implementation itself; such jobs may be required for an >> + implementation-specific equivalent of the <file>/etc/rcS.d/</file> >> + scripts and may not have a one-to-one correspondence with the init >> + scripts. >> + </p> > > A lot of the scripts currently in /etc/rcS.d/ come from the > initscripts package. Is the alternative supposed to implement > all the functionality by those scripts? Or do we expect them > to run the scripts from /etc/rcS.d/ as 9.3.4. seems to suggest? > Well, in the systemd case, all the things those scripts used to do are built in and hardcoded in systemd itself. And in the Upstart case, there is a separate implementation of those as well.
So yes, I think an init system should deal with "core" boot by itself, as sysvinit does with the initscripts package. I guess this means policy needs to specify what needs to be done ;-) (otherwise people may find they get a shock if systemd's hardcoded mounting doesn't match what they expected) Scott -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinrow2gp8og01bbxgripgb0rhyn4cphs6pcs...@mail.gmail.com
