On Thu, Feb 13, 2014 at 4:00 AM, Scott Ferguson <scott.ferguson.debian.u...@gmail.com> wrote: > On 13/02/14 19:12, Gian Uberto Lauri wrote:
>> let's assume that I have to execute a script after S10checkfs/ >> S11mountall and before S13networking. > > My experience with systemd is limited, but so far (Wheezy) everything > "just worked". I haven't been using it long enough to consider employing > it in production environments - but Jessie is a long way from stable so > I'm not overly concerned, just mildly curious. So far I'm impressed with > the increased configurability, and especially, the faster boot-times > (SLA goodness!). > Make the script S12whatever and then install systemd(?) > > # apt-get install systemd systemd-sysv;reboot There's no need to install "systemd-sysv", especially since it won't allow you to boot using both (not simultaneously) sysvinit and systemd. >> Do I find a clear, reliable set of instructions to achieve this goal? > > Do "man system" and "man systemd.conf" not suffice? "man system" or man systemd"? "man -k systemd" will be better because there are many systemd-related man pages and the above two (especially "man systemd.conf") won't help you write a systemd unit. "man systemd-directives" for example will list and explain the various directives (before the "=" in the .ini files) that you can use in a unit. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxMm=AaFnLy6M3OHQZsfEqGuoB7OqgrqX91d=naqo+...@mail.gmail.com
