]] rleigh | 2) Currently, it's the responsibility of initscripts | (/etc/init.d/mtab.sh) to create the initial mtab. Presumably | systemd does something similar to "replay" the mount commands | run prior to this point to create it.
No, we just assume it's a symlink to /proc/mounts. | 3) util-linux would be a logical place for it, given that it's | associated with mount. But since it needs doing at boot time and | mtab.sh already contains the logic to create it, mtab is probably | the best choice--it's just a couple of lines to add to an already | existing script that's dedicated to the job. mtab.sh is masked by systemd, but it seems like systemd needs a «boot-time fixup» list. (We might want to do this on shutdown rather than bootup, not entirely sure about that.) | Another consideration is that we probably only want to make the switch | to a symlink if we're running a sufficiently recent kernel (2.6.26). This isn't a concern for systemd, but otherwise, yes. | I think this is way lower than the minimum supported kernel version, | in squeeze, so probably safe to do it unconditionally. However, in the | case that we can't link to /proc/mounts, are there any situations where | we would want to retain the old mtab.sh behaviour as a fallback? I'm | thinking of upgrade scenarios with old kernel versions, missing /proc | or any other circumstance which could result in a broken system? I can't really think of any, even chroots and such wouldn't have a correct mtab anyway. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
