From: Kim Shrier <kim@tinker.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Problems setting up a cpu/auth/file server
Date: Wed, 9 May 2007 08:33:04 -0600 [thread overview]
Message-ID: <9C7C2B42-4D4C-4B70-B78A-F273F75726A9@tinker.com> (raw)
In-Reply-To: <32d987d50705082154s355867e5vd1630b8a954a0c79@mail.gmail.com>
On May 8, 2007, at 10:54 PM, Federico Benavento wrote:
> not necessarly, you can drawterm to your terminal
> http://plan9.bell-labs.com/wiki/plan9/Drawterm_to_your_terminal/
>
>
Thanks. I'll look into that.
> the wiki is fine, you missed something, people always miss some
> step.
>
I.m sure that is the case.
> bootes should be in sys not kim... see below
>
Is it normal to set up a user that is a member of sys, in this
case kim, so that that user can do system maintenance?
Or, should I log in as sys when I need to do maintenance?
Should I assign passwords to sys and adm? Normally I would
think so.
>
> you didn't run /sys/lib/newuser like the adding a new user wiki says,
> that script creates a standard env for the new user when he/she
> starts the system , like binding /usr/$user/tmp to /tmp, so /tmp
> is replaced by the user's tmp dir.
>
Yes, I definitely forgot that.
>> mv: can't create /rc/bin/service.auth/il566: '/rc/bin/
>> service.auth/il566' permission denied
>> mv: can't create /rc/bin/service.auth/tcp567: '/rc/bin/
>> service.auth/tcp567' permission denied
>> mv: can't stat /rc/bin/service/il566: '/rc/bin/service/il566'
>> does not exist
>> mv: can't stat /rc/bin/service/tcp567: '/rc/bin/service/tcp567'
>> does not exist
>>
> that's why there is a if() in the standard cpurc, so you don't get
> that error
>
I do have the following lines in cpurc.
if(! test -e /rc/bin/service.auth/il566){
mv /rc/bin/service.auth/authsrv.il566 /rc/bin/service.auth/il566
mv /rc/bin/service.auth/authsrv.tcp567 /rc/bin/service.auth/tcp567
mv /rc/bin/service/il566 /rc/bin/service/_il566
mv /rc/bin/service/tcp567 /rc/bin/service/_tcp567
}
>
> bootes should be in sys, not kim
>
OK. I don't think the instructions mention that.
>
> you also need to edit your /lib/ndb/local with something like
>
> ipnet=whatever ip=someip ipmask=someipmask
> sys=bootesmachine ether=bootesmachineeaddr
> auth=bootesmachine
> ...
>
I had already done that.
> --
> Federico G. Benavento
>
Thanks,
Kim
next prev parent reply other threads:[~2007-05-09 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 4:35 Kim Shrier
2007-05-09 4:54 ` Federico Benavento
2007-05-09 14:33 ` Kim Shrier [this message]
2007-05-09 14:42 ` Skip Tavakkolian
2007-05-09 14:50 ` Federico Benavento
2007-05-09 9:03 ` Antonin
2007-05-09 14:34 ` Kim Shrier
2007-05-09 20:19 ` Claudio Leite
2007-05-09 23:35 ` David Leimbach
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=9C7C2B42-4D4C-4B70-B78A-F273F75726A9@tinker.com \
--to=kim@tinker.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).