From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cdrom floppy tape etc, media mount point
Date: Tue, 30 Jul 2002 07:45:18 -0400 [thread overview]
Message-ID: <40501cc48dccb5d90f0d11371bf63d48@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
> What is for a, b, c, by the way?
Sorry to prolong this, but I don't see an
answer to this part of the message.
/n/a, /n/b, and /n/c are used by a:, b:, and c:,
which now mount on both /n/_: and /n/_.
the colon-less mountpoint is easier for acme
and the plumber.
[-- Attachment #2: Type: message/rfc822, Size: 2236 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] cdrom floppy tape etc, media mount point
Date: Fri, 12 Jul 2002 11:07:28 +0900
Message-ID: <20020712020804.559A419A1C@mail.cse.psu.edu>
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
next reply other threads:[~2002-07-30 11:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 11:45 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 11:19 rog
2002-07-16 16:09 rog
2002-07-16 15:35 rog
2002-07-16 14:42 ` Sam
2002-07-16 15:39 ` Scott Schwartz
2002-07-16 13:34 rog
2002-07-16 15:19 ` Scott Schwartz
2002-07-18 9:50 ` Ben
2002-07-18 16:06 ` Jack Johnson
2002-07-16 7:39 Fco.J.Ballesteros
2002-07-15 16:45 rog
2002-07-15 16:02 ` Sam
2002-07-15 16:52 ` Lucio De Re
2002-07-15 19:21 ` Scott Schwartz
2002-07-16 12:26 ` Martin C.Atkins
2002-07-15 16:33 okamoto
2002-07-12 16:16 anothy
2002-07-12 10:44 okamoto
2002-07-12 10:37 Fco.J.Ballesteros
2002-07-12 10:32 okamoto
2002-07-12 10:20 Fco.J.Ballesteros
2002-07-15 9:30 ` Ben
2002-07-12 10:15 okamoto
2002-07-12 7:40 Fco.J.Ballesteros
2002-07-12 2:47 okamoto
2002-07-12 2:17 anothy
2002-07-12 2:07 okamoto
2002-07-12 9:03 ` Don
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40501cc48dccb5d90f0d11371bf63d48@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).