9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Fileserver Initialisation
Date: Sat, 28 Oct 2000 05:04:37 -0700	[thread overview]
Message-ID: <Pine.BSF.4.21.0010280427300.10391-100000@cassandra.foobarbaz.net> (raw)

Ok. I'm feeling a little silly asking this because from what
I've read in the archives, this is well documented there.
However, I can't seem to get it to work.

I have my fileserver up and running, and I am trying to
intialise it with the recent plan9.9gz from my cpu/auth
server.

I have issued the 'allow' command in config mode, and then
mounted the filesystem on the cpu/auth server with '9fs fs'
to extract the distribution. However, when I issue the
command

wrap/inst -ovr /n/fs plan9.9gz

I get the following error repeatedly during the extraction

mkdir /n/fs/<directory>: mounted directory forbids creation

Here is the directory listing (lc -ld /n/fs) from the
cpu/auth server

d-r-xr-xr-x M 112 adm adm 0 Oct 28 04:14 /

I recognise that the directory doesn't permit writing, but I
can't seem to figure out how to change the permissions such
that I can extract the distribution. The worm cartridges are
rewritable media, and they do not have write protection
enabled.

The filesystem 'main' is a MO jukebox with a pair of SCSI
discs as cache setup with the following filsys command

filsys main c[w0.<0-1>.0]j(w1.6.0w1.5.0w1.4.0)(l1.<0-37>.0l1.<38-75>.0)

What am I doing wrong?

--
Christopher Nielsen
(enkhyl|cnielsen)@pobox.com
"Not only is UNIX dead, it's starting to smell really bad." --rob pike




             reply	other threads:[~2000-10-28 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-28 12:04 Christopher Nielsen [this message]
2000-10-28 13:26 nigel

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.BSF.4.21.0010280427300.10391-100000@cassandra.foobarbaz.net \
    --to=cnielsen@pobox.com \
    --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).