[systemd-devel] [PATCH] tmpfiles: move legacy flag-files handling to legacy.conf

[Colin Guthrie]

'Twas brillig, and Reindl Harald at 06/01/13 00:17 did gyre and gimble:
> 
> 
> Am 06.01.2013 01:13, schrieb Tom Gundersen:
>> On Sun, Jan 6, 2013 at 12:59 AM, Reindl Harald <h.reindl at thelounge.net> wrote:
>>> on a running system the rootfs is not readonly
>>
>> It may be (i.e., systemd supports that setup if the rest of your
>> software does), so it cannot be that a reboot always causes writes to
>> the rootfs.
> 
> please do not reply off-list and do not cut most of
> the previous post, i explained why "touch /forcefsck"
> is a godd idea and why deprecate anything which existed
> before systemd is a bad attitude


You have a very odd way of expressing yourself here. As Lennart
explained this is still *supported*. Putting it in a file called
legacy.conf means very little in all practice, especially as this is a
very simple tidyup routine, which is completely separate from the actual
checking part itself (which would typically remove the file itself after
the check anyway - this is just belt and braces).

Even on systems with rw root, if I get some strange behaviour the first
thing I'll do (if the kernel doesn't do it for me automatically) is
mount -o remount,ro /. If I want to check the root fs, then the initrd
will likely be the thing that actually does the check for me, not
anything on the drive itself, so it's still isolated from the partition
being checked.

So I fully support the rationale that "touch /forcefsck" is a *bad* idea
generally and any sysadmins that regularly use it should really try to
use something with less impact going forward and try not to pass on bad
habits. But there is no need to post sarcastic and unhelpful comments
about something that actually *is* still supported (even if it is, for
good reasons already mentioned, termed legacy).

Of course the question of whether it is or is not supported in the
future is more appropriate for the dracut mailing list (or
$initrd_generator of your choosing), not here in systemd - because
again, this is just a trivial tidy up routine to cleanup left over cruft
and nothing to do with any actual execution of the check itself.


Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/