Root directory
It's important to keep the / directory free of more mounts points (FHS)
Backward compatability
/mnt/floppy, etc... still works as expected (you could link /floppy)
Multiple devices
This allows for multiple CD-ROMs, floppies, etc... while still
having easy access to most common (first) device of each type
(Re)Writable CD
As far as most applications are concerned this is just another CD-ROM
If in the future there is a way to write to CD-R(W)s "directly", w/out
creating an image first (ala Adaptec DirectCD for Windows:
http://www.adaptec.com/products/overview/dcdwin.html)
it may be usefull to create a /mnt/removable/cdrom/N to point
to matching /mnt/removable/cdrw/N
Names
This also makes it possible to address media by volume name (if exists)
i.e.: /mnt/removable/cdrom.d/install-cd -> 1
Remote
There is no need for /mnt/remote type structure, since you can either
use /mnt/tmp/N or integrate it into your normal tree
It may be usefull to have a per user $HOME/mnt/remote for private
NFS and/or SMB mounts (ala Network Neighborhood)
i.e.
$HOME/mnt/remote/<hostname>/<volume name>
Possibly without "remote/"
Possibly adding "<domain>/" before "<hostname">
Functionality
This functionlity is NOT provided by fstab or mtab, since that
would be platform dependand (which entry is the CD-ROM?, some
systems use vold/mediad -- not in fstab)
/mnt/
tmp/ -> tmp.d/0
tmp.d/
0/
1/
floppy/ -> removable/floppy.d/0
zip/ -> removable/zip.d/0
cdrom/ -> removable/cdrom.d/0
dvd/ -> removable/dvd.d/0
removable/
floppy/ -> floppy.d/0
floppy.d/
0/
1/
zip/ -> zip.d/0
zip.d/
0/
1/
cdrom/ -> cdrom.d/0
cdrom.d/
0/
<volume name 0>/ -> 0
1/
<volume name 1>/ -> 1
dvd/ -> dvd.d/0
dvd.d/
0/
<volume name 0>/ -> 0
1/
<volume name 1>/ -> 1
fixed/
windows/ -> windows.d/0
windows.d/
0/
c/ -> 0
<fat label 0>/ -> 0
1/
d/ -> 1
<fat label 1>/ -> 1
macos/ -> macos.d/0
macos.d/
0/
<hfs label>/ -> 0
<other os>/ -> <other os>.d/0
<other os>/.d
0/
1/
> On Tue, 20 Jun 2000, Johannes Poehlmann wrote:
>
> <snip>
>
> > It is recommended (not required !) that /mounts is structured this way:
> >
> > /mounts--+
> > +-cdrom0
> > +-cdrom1
> > +-cdrom...
> > |
> > +-cdburner0
> > +-cdburner1
> > +-cdburner..
> > |
> > +-dvd0
> > +-dvd1
> > +-dvd.....
> > |
> > +-floppy0
> > +-floppy1
> > +-floppy...
> > |
> > +-other removable media.....
> > |
> > +-dos-+
> > | +--c
> > | +--d
> > | +--etc....
> > |
> > +--nt-+
> > | +--c
> > | +--d
> > | +--etc....
> > |
> > +--other classes of alien partitions........
> >
> > All theses items are optional especially for non existing drives/
> > partitions.
>
> Hmm... It would seem logical that *permanent* mount points should be
> segregated from *temporary* ones...
>
> A physical hard disk can become a working part of the filesystem, in
> essence a seamless part of the whole.
>
> A removable drive, whatever the media, is of a different nature, and
> exists at points where the file system intersects with the wider
> world... iyswim.
>
> I'd have thought real partitions are going to be rarely changed, and
> fairly stable - say you dual boot with windows, you're likely to have a
> set, stable place where the disk is linked, and it won't change.
>
> Why can't something like:
>
> /mount
> |
> +-local-+
> | +--dos_c or whatever
> | +--etc...
> |
> +-net-+
> | +--remote sites - nfs, smb, etc
> |
> +-removable-+
> +-floppy[0-n]
> +-cdrom[0-n]
> +-dvd[0-n]
>
> and so on?
>
> This way, actual *fixed* mount points get proper names, and floppy drives
> are "visibly" external.
