support /var as a mount #855
Labels
Comments
|
Related PR: #856 |
|
PR in #859 |
|
Closed by #859 |
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
May 17, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc.
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
May 23, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc.
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
Jun 2, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc.
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
Jun 6, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc. Related: rhbz#1098303
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
Jun 8, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc. Resolves: rhbz#1459623
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
Jul 12, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc.
cgwalters
added a commit
to cgwalters/anaconda
that referenced
this issue
Jul 24, 2017
See: ostreedev/ostree#855 Basically, if `/var` is in the user specified mounts, don't override it with the "default ostree" `var`. This allows people to easily keep all of their local state (apart from `/etc`) in a single partition with potentially different quotas etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Downstream: https://bugzilla.redhat.com/show_bug.cgi?id=1098303
The DISA STIG specifies for Red Hat Enterprise Linux that
/varshould be a mount point.Right now that doesn't quite work with libostree on Fedora-derived (likely more generally systemd-using) OSes since systemd notices
var.mountalready exists as a unit, and the fstab generator hence skips whatever is in fstab.I think we can fix this by doing the "sysroot var" mount after the switchroot. My rough plan here is basically:
/etc/fstab, and if a mount for/varis not found, generates a unit for the ostree "sysroot var" mountThe text was updated successfully, but these errors were encountered: