9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] fossil permission checking
Date: Wed,  6 Aug 2008 18:24:59 -0600	[thread overview]
Message-ID: <14ec7b180808061724v3c86c27dh4643fbb4ab402ab1@mail.gmail.com> (raw)
In-Reply-To: <621112A569DAE948AD25CCDCF1C075331AB323@dolly.ntdom.cupdx>

/ is indeed mounted without -c. if you want to create a directory in /
use /root. see 'nm' for how the namespace is constructed.

i believe new directories in / are frowned upon (even if created in
/root). i can't find the relevant message in the archives.

On Wed, Aug 6, 2008 at 6:10 PM, Benjamin Huntsman
<BHuntsman@mail2.cu-portland.edu> wrote:
> I'm having some trouble setting up a terminal (which will become a cpu/auth server).
> I've gotten the 9pccpuf kernel booted, and is running as the user bootes, but even from the server's console, if I type something as simple as "echo hi > /foo" I receive the message:
>
> mounted directory forbids creation
>
> I've basically followed the wiki pages on setting up a standalone auth/cpu server, though it's not getting me very far on the fossil side of things...  I chose all of the defaults during the install process,
>
> Can someone give me a quick tip as to how to set up a new cpu/fossil user that can actually write to something other than their home directory?
>
> Also, there's not exactly a command like UNIX's sudo, is there?
>
> Thanks in advance!
>
>



  reply	other threads:[~2008-08-07  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07  0:10 Benjamin Huntsman
2008-08-07  0:24 ` andrey mirtchovski [this message]
2008-08-07  1:01   ` Benjamin Huntsman
2008-08-07  1:36     ` Uriel
2008-08-07  2:18     ` andrey mirtchovski
2008-08-07  3:07     ` erik quanstrom

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=14ec7b180808061724v3c86c27dh4643fbb4ab402ab1@mail.gmail.com \
    --to=mirtchovski@gmail.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).