From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] u9fs
Date: Tue, 18 Feb 2003 10:12:04 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0302181006420.16254-100000@carotid.ccs.lanl.gov> (raw)
In-Reply-To: <a11d6b7b1fa0b31171c34bf3625cc9e5@plan9.bell-labs.com>
On Tue, 18 Feb 2003, Russ Cox wrote:
> The only use of the attach spec in u9fs is that if you attach
> to the name "device" then you can access devices
> on the system. Otherwise you're not allowed, so as
> to avoid blocking the (single-threaded) server.
ah, that is interesting. This is what happens when you re-do an
implementation from the man pages.
We actually make different use of the attach spec here. It lets you
restrict the domain of the server by basically making a fid for the attach
lower in the tree than '/'.
I guess I'll get the same effect by chroot'ing the server.
It's interesting seeing how much I did the same as Plan 9 from the man
pages, and how many little differences like this have crept in. I've been
using that attach spec for years (and truth to tell, I still like it, but
I'm going to stick with stock u9fs).
I ran into this just now for this reason: I am running v9fs2k (linux vfs
client for 9p2000) on the same laptop as u9fs. I am getting readdir
working. The mount point for v9fs2k is /mnt. Things got messy when the
server walked over /mnt ... as in deadlock. I never had this type of thing
with my old 9p server that I wrote, since the attaches were always below
root.
Anyway, an easy workaround.
thanks
ron
next prev parent reply other threads:[~2003-02-18 17:12 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 16:38 Ronald G. Minnich
2003-02-18 16:42 ` Russ Cox
2003-02-18 17:12 ` Ronald G. Minnich [this message]
2003-02-18 17:18 ` Russ Cox
2003-02-18 16:49 ` nigel
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 11:36 arisawa
2008-03-30 12:25 ` arisawa
2003-10-09 14:24 [9fans] U9FS Lucio De Re
2003-01-28 15:50 [9fans] u9fs Russ Cox
2003-01-31 15:35 ` Axel Belinfante
2003-01-31 16:07 ` Nigel Roles
2003-01-31 16:39 ` Russ Cox
2003-01-31 18:23 ` Axel Belinfante
2003-01-31 18:45 ` Russ Cox
2003-01-31 22:54 ` Axel Belinfante
2002-12-09 8:09 Russ Cox
2002-12-09 7:51 YAMANASHI Takeshi
2002-12-05 17:49 David Swasey
2002-05-05 23:24 [9fans] Bug report Russ Cox
2002-05-05 23:33 ` arisawa
2002-05-05 23:39 ` [9fans] u9fs arisawa
2002-03-24 6:42 Russ Cox
2002-03-23 18:45 nigel
2002-03-23 18:12 Russ Cox
2002-03-24 5:44 ` Martin C.Atkins
2002-03-26 10:45 ` Christopher Nielsen
2002-03-23 10:43 nigel
2002-03-22 13:42 Jean Mehat
2002-03-21 16:19 Russ Cox
2002-03-23 0:40 ` Christopher Nielsen
2002-03-20 22:00 forsyth
2002-03-20 19:31 Russ Cox
2002-03-20 19:31 markp
2002-03-20 19:05 Russ Cox
2002-03-20 19:42 ` skipt
2002-03-21 11:02 ` Peter Canning
2002-03-20 18:40 markp
2002-03-20 9:27 Fco.J.Ballesteros
2002-03-20 7:10 Geoff Collyer
2002-03-20 7:23 ` Lucio De Re
2002-03-20 8:10 ` Dean Prichard
2002-03-20 7:01 forsyth
2002-03-20 5:15 Russ Cox
2002-03-19 22:33 Russ Cox
2002-03-19 17:19 Russ Cox
2002-03-19 16:39 forsyth
2002-03-19 16:18 anothy
2002-03-19 16:46 ` Dharani Vilwanathan
2002-03-19 22:00 ` Dharani Vilwanathan
2002-03-19 14:03 [9fans] long long warning nigel
2002-03-19 16:07 ` [9fans] u9fs Dharani Vilwanathan
2002-03-19 16:15 ` William Josephson
2002-03-20 4:46 ` Steve Kotsopoulos
2001-01-07 6:08 rob pike
2001-01-07 5:54 rob pike
2001-01-07 6:00 ` Boyd Roberts
2000-07-07 16:16 ianb
2000-07-07 14:46 Ish Rattan
2000-07-07 15:26 ` Steve Kotsopoulos
1999-04-23 11:05 [9fans] U9FS
1999-04-22 16:31 Russ
1999-04-22 8:32
1999-03-18 11:30 Jean
1999-03-17 23:47 Ed
1999-03-17 19:48 Markus
1999-03-17 19:16 Scott
1999-03-17 16:26
1999-03-17 15:07
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=Pine.LNX.4.44.0302181006420.16254-100000@carotid.ccs.lanl.gov \
--to=rminnich@lanl.gov \
--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).