[systemd-devel] howto migrate some things to systemd

Michael Olbrich m.olbrich at pengutronix.de
Tue Apr 19 04:52:49 PDT 2011


On Tue, Apr 19, 2011 at 12:15:01PM +0200, Mirco Tischler wrote:
> 2011/4/19 Michael Olbrich <m.olbrich at pengutronix.de>:
> > Hi,
> >
> > On Tue, Apr 19, 2011 at 09:02:47AM +0200, Robert Schwebel wrote:
> >> On Mon, Apr 18, 2011 at 11:57:46PM +0200, Mirco Tischler wrote:
> >> > How about pointing the default.target symlink at your custom unit that
> >> > pulls in only a very basic system and executes your custom setup
> >> > script.
> >>
> >> That sounds pretty good, we'll try that!
> >
> > Unfortunately not. This is far too late. udev is already running and
> > sockets are up too. At that point it's rather difficult to ensure that
> > nothing else is executed.
> > And there is already stuff confused by the ro/rw filesystem:
> > -------------------------
> > systemd-user-sessions[430]: Failed to remove /etc/nologin file: Read-only file system
> > -------------------------
> >
> > Regards,
> > Michael Olbrich
> setup.service:
> DefaultDependencies=off
> Requires=local-fs.target
> After=local-fs.target
> 
> With such a service file as default target you should end up with only
> the fs mounted
> and not much else.

Ok, now I'm starting with "systemd.unit=setup.service". There are some
issues however:

[...]
Starting Debug File System...
Starting /tmp...
Starting /var/log...
Starting Runtime Directory...
Starting Lock Directory...
Starting /var/tmp...
Starting Remount API VFS...
Starting File System Check on Root Device...
Starting Media Directory...
Starting Stdio Syslog Bridge...
<27>systemd-logger[234]: Failed to connect log socket to /dev/log: No such file or directory
<29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=1
<29>systemd[1]: Unit systemd-logger.service entered failed state.
Starting Stdio Syslog Bridge...
<27>systemd-logger[246]: Failed to connect log socket to /dev/log: No such file or directory
<29>systemd[1]: systemd-logger.service: main process exited, code=exited, status=1
<29>systemd[1]: Unit systemd-logger.service entered failed state.
[...]

This looks like there is a dependency missing for systemd-logger.service,
right?

Regards,
Michael Olbrich

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


More information about the systemd-devel mailing list