[systemd-devel] [PATCH 1/2] fstab-generator: initrd - mount the entries in /etc/fstab.sys from the initramfs

Lennart Poettering lennart at poettering.net
Fri Mar 1 11:57:27 PST 2013

On Fri, 01.03.13 19:42, Harald Hoyer (harald.hoyer at gmail.com) wrote:

> > If we only want to support / and /usr, and don't care about stuff like
> > /usr/local or /usr/share on separate mounts, then going with usr=
> > makes sense to me. It would also make everything else much simpler (no
> > need to reload settings after mounting sysroot). I already wrote the
> > patch for usr=, so I'll send it out soon.
> >
> > Harald, what do you think?
> "x-initrd" or "x-initrd.mount" sounds good, but I would imply "x-initrd"
> for "/usr" if "noauto" is not set.

Given that we might end up adding other options in the x-initrd
namespace later on we should stick to "x-initrd.mount" here I think. And
yes, I too would imply this for /usr.

> /etc/fstab.sys could just be copied to /etc/fstab in the initramfs. For the
> rest "x-initrd" can be used easily.

Hmm, but the mount destination paths in the initrd would be very
different in the initrd (where everything would be prefixed with
/sysroot), then in the host? Not following? I'd actually like fstab.sys
to go away or at least stay something dracut specific...

> Main usage is for things, which get mounted in the initramfs, survive the
> switch-root and cannot be remounted with different options, because they
> are busy.
> /dev/shm and /run come to my mind.

On the final systemd, we already remount /run with the options in
/etc/fstab, and this can be done while the mount is active, fine, for
all options I am aware off, which one do you expect to break with

/dev/shm is a different case, if this comes pre-mounted from the initrd,
then we currently won't update it at all, and we have no good story
about it so far...


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list