On Sat, 29 Jul 2000, Marcus Meissner wrote:
> Please do it right and use something like a directory per mount:
>
> /proc/xmounts/<nr>/
> mountpoint (file with content of the mount target
> directory)
> device (whatever is in the device value)
> fstype (you get the drift)
> options
> ...
>
> Iterate <nr> for all mounts.
>
> Most clean way, easy to parse, unambigous.
... and ugly enough to make one barf. WTF is "device"? Makes no sense for
procfs, for NFS, as the matter of fact for most of filesystems. How would
you like your "options", sliced or in one piece? Why? WTF is "/proc/xmounts"?
If it's an fs of its own - don't put it under procfs. Yodda, yodda..
Now, what's wrong with having 1 (.o.n.e.) text file instead of all that
hierarchy? \0 can't happen inside the names, so we can trivially use it
for separator. Dunno about you, but I _hate_ this braindamage with
replacing plain files with a metric buttload of little cute one-line
turdlets. And here you don't even have a pseudo-excuse that tends to be
uttered when it is done to something like /etc/inetd.conf (lusers who
package k3WlcR4pIRCd and can't be arsed to learn sed(1) or use the
standard script that should be provided by distribution). IOW, __please__
don't do that.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:28 EST