From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] changeuser
Date: Mon, 27 Aug 2001 05:29:21 -0500 [thread overview]
Message-ID: <Pine.BSF.4.33.0108270526270.346-100000@lucifer.ducksworth.com> (raw)
In-Reply-To: <3.0.5.32.20010826000421.00dac210@mail.real.com>
i was bitten by that last week. also make sure to add
the nodummyrr to the end of the cards entry in plan9.ini.
On Sun, 26 Aug 2001, Fariborz 'Skip' Tavakkolian wrote:
> I have the auth/cpu set up now. I had missed a step (didn't create a home
> for bootes), and also there was a hardware config problem.
>
> FYI, when using Linksys Ether16 (ISA), use Linksys's utility program to
> hard assign the addr/irq on the card; In the system's BIOS setup, reserve
> that addr/irq for ISA use.
>
> At 03:01 AM 8/25/2001 -0700, I mumbled something like:
> >I've setup an auth/cpu server. changeuser rebels with:
> >
> >changeuser: can't create user bootes: access permission denied
> >
>
>
--sam
prev parent reply other threads:[~2001-08-27 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 10:01 Fariborz 'Skip' Tavakkolian
2001-08-26 7:04 ` Fariborz 'Skip' Tavakkolian
2001-08-27 10:29 ` Sam Ducksworth [this message]
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.33.0108270526270.346-100000@lucifer.ducksworth.com \
--to=sam@ducksworth.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).