From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: okamoto@granite.cias.osakafu-u.ac.jp
MIME-Version: 1.0
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20020712020804.559A419A1C@mail.cse.psu.edu>
Subject: [9fans] cdrom floppy tape etc, media mount point
Date: Fri, 12 Jul 2002 11:07:28 +0900
Topicbox-Message-UUID: c9c7ad7a-eaca-11e9-9e20-41e7f4b1d025

This is not so important, I know. However it annoyes me offen, particularly
when I need to explain it to newbies.  I remember some discussions
were undertaken here before, but I don't see the difference in the 
new release.  I suppose none did not pay attention so much to this.  :-)

/n is for mount points of file trees from network.   
/mnt is for mount points of user level file severs.

Then, where can we put local floppy(a:, b: etc.) or disks other than
kfs filesystem?   If we could have another directory such as /media
or just /m, we can push out all the local stuffs into it.   Even if those
are imported from network, the name of m or media will not suffer 
from unmatched naming.  Then, we don't need /mnt/cd, either.
This does not deny to have those names under /n, of course.   
However it may annoy many of newbies.

Then, /m could have directories of
9
9fat
a:
b:
c:
d:
cd
tapefs
boot
kfs

What is for a, b, c, by the way?

Kenji