From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] Re: M device?
Date: Tue, 16 Mar 1999 11:38:33 -0500 [thread overview]
Message-ID: <19990316163833.J4bgl9t03LBxNslK1gYC3wBLQsHLqZ787Vgp8L4pS9o@z> (raw)
Trivial question, but I can't find the answer anywhere I'd expect to see
it; what's the M device? It comes up in an ls -l listing of my root
directory (single machine, 386, standard install from the Plan 9 CDROM).
d-rwxrwxr-x M 3 sys sys 0 Jun 22 1997 /3210
d-rwxrwxr-x M 3 sys sys 0 Jun 22 1997 /386
d-rwxrwxr-x M 3 sys sys 0 Jun 22 1997 /68020
d-rwxrwxr-x M 3 sys sys 0 Jun 22 1997 /960
--r--r--r-- M 3 sys sys 63707 Apr 5 1995 /_conform.map
d-rwxrwxr-x M 3 sys sys 0 Jun 22 1997 /acme
d-rwxrwxrwx M 3 adm adm 0 Jun 22 1997 /adm
d-rwxrwxrwx / 0 cwr cwr 0 Apr 4 1995 /bin
d-rwxrwxr-x M 3 sys sys 0 Apr 5 1995 /bin
--r-xr-xr-x / 0 cwr cwr 34080 Apr 4 1995 /boot
--r-xr-xr-x / 0 cwr cwr 38432 Apr 4 1995 /cfs
etc.
The sys-owned stuff is the ordinary root fs, so M must be some sort
of server, but I can't find the relevant letter in man(3).
Will
cwr@crash.cts.com
Brazil has the '#c/drivers' file to make finding out which drivers are loaded
with the kernel a bit easier. The devtab table changed from being an array of
Dev to an array of pointers to Dev and Dev acquired a couple of new elements to
describe the entry; devchar went away.
% tail -20 /sys/src/brazil/port/devmnt.c
Dev mntdevtab = {
'M',
"mnt",
mntreset,
devinit,
mntattach,
mntclone,
mntwalk,
mntstat,
mntopen,
mntcreate,
mntclose,
mntread,
devbread,
mntwrite,
devbwrite,
mntremove,
mntwstat,
};
% cat /dev/drivers
#/ root
#c cons
#e env
#| pipe
#p proc
#M mnt
#s srv
#d dup
#r rtc
#D ssl
#z mntstats
#l ether
#I ip
#i draw
#m mouse
#v vga
#S scsi
#W cd
#w sd
#H ata
#f floppy
#A audio
#y i82365
#L lpt
#t ns16552
%
next reply other threads:[~1999-03-16 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 16:38 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-15 21:29 Will
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=19990316163833.J4bgl9t03LBxNslK1gYC3wBLQsHLqZ787Vgp8L4pS9o@z \
--to=jmk@plan9.bell-labs.com \
/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).