On Tue, Oct 01, 2013 at 04:15:16AM +0200, Lennart Poettering wrote:
On Tue, 24.09.13 13:53, Kelly Anderson (ke...@xilka.com) wrote:
Hello,
If I'm not mistaken, the intent way back in the early stages of systemd was
to
eliminate /etc/fstab and use .mount files exclusively. Since it
Am 01.10.2013 15:26, schrieb Karel Zak:
2. If /etc/fstab is missing, systemd must create a valid fstab (in this
case
/run/fstab) so that fsck runs properly.
Not following on this one really... If fsck fails if it doesn't find any
fstab, then this is really something to fix in util-linux I
On Tue, Oct 01, 2013 at 03:40:00PM +0200, Thomas Bächler wrote:
Am 01.10.2013 15:26, schrieb Karel Zak:
2. If /etc/fstab is missing, systemd must create a valid fstab (in this
case
/run/fstab) so that fsck runs properly.
Not following on this one really... If fsck fails if it doesn't
Am 24.09.2013 21:53, schrieb Kelly Anderson:
If I'm not mistaken, the intent way back in the early stages of systemd was
to
eliminate /etc/fstab and use .mount files exclusively. Since it was never
fully implemented I took the prerogative to make it work on my systems.
I've been using the
On Tue, 01.10.13 16:09, Karel Zak (k...@redhat.com) wrote:
Why does it even print that warning? It's annoying and I don't see its
purpose. Unless you run fsck with the -A option, it doesn't even need
the fstab file.
OK, fixed (will be in util-linux v2.24-rc2).
Thanks a lot for this
On Tue, 24.09.13 13:53, Kelly Anderson (ke...@xilka.com) wrote:
Hello,
If I'm not mistaken, the intent way back in the early stages of systemd was
to
eliminate /etc/fstab and use .mount files exclusively. Since it was never
fully implemented I took the prerogative to make it work on my
Hello,
If I'm not mistaken, the intent way back in the early stages of systemd was to
eliminate /etc/fstab and use .mount files exclusively. Since it was never
fully implemented I took the prerogative to make it work on my systems.
I've been using the setup for quite some time and it works
