[systemd-devel] Is there a reason to forcefully create /etc/mtab?

[Leonid Isaev]

Hi,

	I have a read-only / filesystem and /etc/mtab points to
/proc/self/mounts as it should.
	So, in systemd-215 tmpfile.d fails to create a symbolic link /etc/mtab
because /usr/lib/tmpfiles.d/etc.conf contains is a line "L+ /etc/mtab - - - -
../proc/self/mounts". 
	Is this intentional? Besides failing on ro /, it is also confusing
because /etc/mtab can be supplied by a package (in archlinux, the 'filesystem'
package), so why tmpfiles instead of including this symlink with systemd?
	The same question applies to the entire etc.conf: why does tmpfiles
touch /etc at all, especially if /etc is already properly set up?

Thanks,
-- 
Leonid Isaev
GPG fingerprints: DA92 034D B4A8 EC51 7EA6  20DF 9291 EE8A 043C B8C4
                  C0DF 20D0 C075 C3F1 E1BE  775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140706/ef8d9f56/attachment.sig>