From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] One last check of steps for bootstrapping fs
Date: Fri, 6 Dec 2002 00:45:12 -0800 [thread overview]
Message-ID: <8ae2d39b36508ece093fd11facc5bc43@collyer.net> (raw)
That sounds mostly right. Don't worry about authdisable. If you need
to use it (and I've never used it yet), it's now a file server console
command, so you can turn auth on and off at will. I think in step 3,
you want to copy /adm over and then type "users" on the file server
console. You may need to type "allow" on either file server
beforehand and "disallow" after; just try the plain copy first and
see.
I'm not sure that step 5 is needed, but just to clarify, "ream" and
"recover" (and a few other config commands, like "copyworm") are
one-time commands, not configuration state. They are not remembered.
So you don't need to change your configuration just to avoid a second
reaming.
next reply other threads:[~2002-12-06 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 8:45 Geoff Collyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 6:37 Skip Tavakkolian
2002-12-06 17:32 ` Dan Cross
2002-12-06 5:50 Skip Tavakkolian
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=8ae2d39b36508ece093fd11facc5bc43@collyer.net \
--to=geoff@collyer.net \
--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).