Re: [Cooker] Re: Cooker filesystem vs FHS 2.3

[Claudio Matsuoka]

On Tue, 24 May 2005, David Walser wrote:

> By default /mnt is empty.  Things are only added there when certain
> things are detected (floppy drives, optical drives, and some other things)
>
> The fact that the installer automates adding some mount points for you
> (which you'd need to do anyway) doesn't seem like a violation.

It is, as I see it, system usage of /mnt (i.e. the system chooses or
assumes mount points under /mnt, which should be kept free for temporary
mounts). If something else is mounted on /mnt, it is likely that certain
subsystems may stop working.

If, after the installation, the admin decides to use /mnt/xxx for floppies,
cdrom or other filesystems, that's ok, but the system can't assume that
by default.

A valid concern was raised on nonstandard, non-removable media that's
mounted by default, such as windows filesystems. I'm not sure where these
should be mounted to be both practical and standards-compliant.

One possible location would be straight in the root fs, but there are
objections on overpopulating it.

I've been thinking about keeping /mnt/win_[cde] and declare it as site-
specific, since it's a nonstandard directory that would not be available
in all machines and no other system tool uses this path. Seems to be the
best choice so far...

In machines with no windows filesystems on it, which would be the case
of servers, /mnt would stay clear.

In home desktops with dual-boot, the installer gives a hand to the local
admin and places the nonstandard directory there, as a local configuration.