[systemd-devel] use /run instead of /dev/.run

Ludwig Nussel ludwig.nussel at suse.de
Mon Mar 28 07:25:32 PDT 2011


Kay Sievers wrote:
> On Mon, Mar 28, 2011 at 13:28, Ludwig Nussel <ludwig.nussel at suse.de> wrote:
> > Bill Nottingham wrote:
> >> Andrey Borzenkov (arvidjaar at gmail.com) said:
> >> > On Fri, Mar 25, 2011 at 7:07 AM, Kay Sievers <kay.sievers at vrfy.org> wrote:
> >> > > Instead of the /dev/.run trick we have currently implemented, we decided
> >> > > to move the early-boot runtime dir to /run.
> >> > >
> >> >
> >> > What is the benefit? /var/run is well known and established; what is
> >> > the reason to move it in another place?
> >>
> >> /var/run depends on /var, which is allowed to be a separate filesystem, and
> >> therefore not available during all portions of the boot process or shutdown.
> >
> > mount --bind /var/run /mnt
> > mount /var
> > mount -M /mnt /var/run
> 
> We would need to make sure that /var/run exists on the rootfs then. We
> could probably do that on shutdown, but it's not really fun to rely on
> such things.

If it's not there and / is ro you can put /var on tmpfs temporarily too (or
even reuse the one for /var/run via bind mount or symlink).

cu
Ludwig

-- 
 (o_   Ludwig Nussel
 //\
 V_/_  http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)


More information about the systemd-devel mailing list