Miles Bader wrote:
>
> Kasper Dupont <kasperd@daimi.au.dk> writes:
> > I don't think you can put all the information from /etc/mtab
> > into /proc/mounts without breaking compatibility.
>
> Why? Since the option syntax is regular, presumably programs simply
> ignore options they don't understand. No?
It is mostly the device field I had in mind.
>
> > My suggestion would be to change it from /etc/mtab to /mtab.d/mtab.
>
> Please, no. don't pollute the root (_especially_ with little one-use
> directories like that).
Unfortunately it is the best solution I can come up with.
>
> /var is clearly the right place for this;
Is it?
> if /var isn't mounted
> initially, I'd suggest that mount should simply not update any file at
> that point, and the init-script that mounts /var can be responsible from
> propagating information from /proc/mounts to /var/whatever.
Would you fsck /var while it is mounted?
I think part of the problem is that /var is used for both files
we want to keep across reboot, and files we do not want to keep
across reboot.
There are cases where it is undesirable to have mtab in /var,
but if mount expect to find mtab somewhere under /var, we can't
even use a symlink to get it out of there, because /var needs
to be mounted before the symlink can be followed.
-- Kasper Dupont -- der bruger for meget tid på usenet. For sending spam use mailto:aaarep@daimi.au.dk for(_=52;_;(_%5)||(_/=5),(_%5)&&(_-=2))putchar(_); - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Feb 28 2003 - 22:00:40 EST