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] Permissions, again
Date: Wed, 15 May 2002 17:22:32 +0200	[thread overview]
Message-ID: <20020515172231.Y1584@cackle.proxima.alt.za> (raw)

I'm obviously too off-tune to understand Plan 9's permission scheme,
it keeps catching me out.  I suppose the lack of "root" to solve
all problems does require a clearer understanding and I'm notoriously
slow.

I haven't yet installed 4ed but I've been having a good look at
the distribution and especially the man pages.  There's a lot of
exciting stuff in there.

In my exuberance, I thought I'd install the ISO image as a file
and access it using 9660srv(1) which is a very handy way indeed to
read the various documents etc.

Where I failed, was when I thought I'd alter something (I forget
what) on the image.  Now, I have no idea how complicated it is to
manage an ISO image (specially one with multiplicates :-) but it
would have been so nice to be able to do it that I really regretted
receiving a "permission denied" or somesuch.

Naturally, I did attempt to tidy up all the permissions (I see Rob
owns more or less all the image contents) as well as the underlying
ones (I was using disk/kfs at the time) but that was quite
unsuccessful.

I presume that the ISO image was generated in some fashion and I
haven't yet found out how, so please illuminate me, but mostly I'd
be very excited to discover that 9660srv can modify an ISO image
and retain its structure successfully, if it needs some work and
someone wants to guide me, I'll happily help.  I did note that the
4ed version has some undeployed code for "removing" files where
the 3ed version has just the "not supported" message.

Back to permissions, it may be just something in the way I set
things up that blocked my use of 9660srv, so a short lesson on
layered permissions would be welcome:

	% cd /dist/Plan9/4ed
	% bunzip2 < plan9.iso.bz2 > plan9.iso
	% 9660srv
	% mount -c /srv/9660srv /n/kremvax plan9.iso
	% cd /n/kremvax/sys/src/cmd

this is from memory.  What would it take to allow me to edit a file
or create a directory at this point?

++L


             reply	other threads:[~2002-05-15 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 15:22 Lucio De Re [this message]
2002-05-15 18:20 rsc
2002-05-15 18:23 ` Scott Schwartz
2002-05-15 18:25 rob pike, esq.
2002-05-15 18:31 ` Sam
2002-05-16  9:06   ` Don
2002-05-15 20:50 ` Dan Cross
2002-05-15 21:01   ` Chris Hollis-Locke
2002-05-15 21:20     ` Dan Cross
2002-05-16 19:00       ` Matt H
2002-05-15 20:56 rob pike, esq.
     [not found] <20020516192637.3C3F33408A@bolivar.ugcs.caltech.edu>
2002-05-16 21:49 ` matt
2002-05-17  9:10   ` 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=20020515172231.Y1584@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).