From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] P9P on Solaris
Date: Wed, 28 May 2008 16:00:59 -0400 [thread overview]
Message-ID: <20080528195945.79EF81E8C71@holo.morphisms.net> (raw)
In-Reply-To: <052820081934.14135.483DB3BA0007BF150000373722230647029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
> I know it's been a while, but that got me farther. The
> odd thing is that I had already played with the magic
> define, but it seems that __sun__ wasn't getting set.
Bug in 9c. Fixed and pushed.
> - There's also a discrepancy between the V1 inode
> defined in ffs.h and the one defined in the Solaris
> header files. It ends up messing up the UID and
> GID fields.
Please compare against the BSD sources if you get
a chance -- I hope I just misread the data structure.
> the inodes and the directory entries. It basically
> looks at the magic number and if it would be correct
> swapped, we take that as good enough and set a flag
> to swap everything.
Great, thanks.
> - Because I'm introducing venti into a UNIX environment
> instead of putting a UNIX machine in a Plan 9 environment,
> I need to at least have the option of traditional
> superuser behavior. So I added an insecure (-i) flag
> to vnfs. It turns off the mapping from UID/GID 0 to
> -1. Then in ffs.c, I allowed the traditional uid 0
> gets all access.
It's interesting you view that as Plan 9-specific.
I was just mimicking the usual Unix NFS behavior.
Russ
next prev parent reply other threads:[~2008-05-28 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 20:43 Brian L. Stuart
2008-05-14 0:17 ` Russ Cox
2008-05-15 21:04 ` Brian L. Stuart
2008-05-15 22:29 ` Russ Cox
2008-05-28 19:34 ` Brian L. Stuart
2008-05-28 20:00 ` Russ Cox [this message]
2008-05-28 20:25 ` Brian L. Stuart
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=20080528195945.79EF81E8C71@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
/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).