9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] identity/ownership
Date: Tue,  6 Nov 2001 15:00:20 +0200	[thread overview]
Message-ID: <20011106150020.E25942@cackle.proxima.alt.za> (raw)

My Plan 9 network is a bit of a jumble:  I have a 2ed fileserver
with the 2ed system on "main" and the 3ed system on "other".  The
status of both these filesystems is a bit dated, but it is workable.

I have a second fileserver, running a 3ed kernel, possibly not as
recent as it could be.  This serves only a 3ed filesystem as "main"
(and "dump" which I haven't quite come to grips with properly yet).
The filesystem itself is pretty much up to date.

I then have a 2ed compute server which also provides authentication
and naturally uses the 2ed filesystem.

A 3ed compute server used to mount the 3ed filesystem ("other") on
the 2ed fileserver, but now uses the second fileserver.

My workstation is even more messy: it mounts the 3ed filesystem
from the 2ed fileserver and runs as a somewhat dated 3ed workstation.

Where things become obscure is when I connect from the workstation
to the 3ed CPU server and gain access to the 3ed filesystem but
don't seem to have write permissions even in my home directory
there.

Mounting the same filesystem onto the workstation doesn't have such
a problem.

The same entry for "lucio" has at least the same numeric index in
all three /adm/users files and it would seem that I am "lucio" in
all instances, so what should I inspect to find out why I have no
permissions in this particular instance?  Am I being surreptitiously
replaced by "none"?  How do I find out?  /dev/user contains "lucio"
and so does /dev/hostowner.  I see that /dev/hostdomain, if relevant,
is empty.  What else would be worth checking?

I haven't been able to coax the 2ed CPU server to let me connect
to it from the 3ed workstation (ocpu notwithstanding, the devs
don't fit - more's the pity, 'cause I'd like to use art, catclock,
etc.), so I can't tell what type of access I would have from there.

++L


             reply	other threads:[~2001-11-06 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 13:00 Lucio De Re [this message]
2001-11-06 13:44 forsyth
2001-11-06 13:45 ` Lucio De Re
2001-11-06 14:15   ` Lucio De Re
2001-11-06 14:52 forsyth
2001-11-06 15:33 presotto
2001-11-07  5:27 ` Lucio De Re
2001-11-07  9:03 Fco.J.Ballesteros
2001-11-07  9:12 ` Lucio De Re
2001-11-07 13:36 presotto
2001-11-07 14:22 presotto

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=20011106150020.E25942@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).