On Saturday 22 November 2003 8:18, Charles Swiger wrote:
> /mnt should be reserved as a default temporary mount point-- it's silly
> to risk breaking existing tools or procedures. Anyway, I suggest you
> solicit feedback from Solaris users and possibly MacOS X people as
> well. Solaris features vold (implied by wanting to use /vol), and the
> latter OS places temporary removable mountpoints under /Volumes.
The point that /mnt should be left alone is pretty clear, but I'm glad to be
able to say "Folks on the FreeBSD questions list agree."
As for Mac OS X, they have no intention of being FHS-compliant, so while we
may learn some lessons from them, they won't worrz about what we have to say.
> I happen to think that OS X handles things well from a user interface
> standpoint-- the Finder in Panther with Miller column display and an
> eject symbol next to the volume name, but I'm not sure how relevant
> that is. Frank, is your group's standard concerned about physical
> volume names, logical volume names intended for human
> identification/access, or both?
> Physical device names ought to have unit numbers or even be part of a
> tree-like device hierarchy-- for instance, what does /cdrom refer to in
> a machine with two CD-ROM devices?
In the current version of the standard (2.2), nothing. But in the next
revision, /foo/cdrom will be a symlink to /foo/cdrom0, and /foo/cdrom1 won't
have a link. Managing these links is not the scope of the standard (yet). The
priority for the next revision is to define what "/foo" should be.
> Human-readable names also run the risk of two removable devices having
> the same name; people are happy seeing a list containing duplicate
> names (eg, particularly if one name has a CDROM icon next to it, and
> the other has a floppy or USB pen icon :-), but that doesn't tell you
> what to do with your filesystem hierarchy layout.
The actual names of the directories will be undefined, but there will be some
suggestions (cdrom, floppy, etc.)
> Obviously, a standard that says "place mount points anywhere you want"
> isn't very useful. But if you did come up with a standard, who should
> follow it and what would they gain?
As for who should follow it, Linux distributions (Debian, Red Hat, SuSE) as
well as the *BSDs (though I'm not sure exaclty what that means in the BSD
world). What would be gained is more for application support. Basically, xmms
and xcdroast could configure a /foo/cdrom as a default location, and it will
be correct for all FHS-compliant systems.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"