From: "Federico Benavento" <benavento@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Broken auth after replica/pull
Date: Sat, 12 May 2007 09:36:01 +0200 [thread overview]
Message-ID: <32d987d50705120036g5c9eeabfn269df7735efd27be@mail.gmail.com> (raw)
In-Reply-To: <56EDE421-11DA-446A-9A1C-C13CC9F9979C@telus.net>
> plalonde@paulhome.net password. I've been unable to find this string
> anywhere in my config files anymore, and have rebooted the cpu server
> and restarted the drawterm. Could this (instead of plalonde@p9cpu)
> be the source of my grief? Is there a way to fix it?
IIRC that's set in your nvram, remember "authdom:" after you
echoed jflda > /dev/sdC0/nvram and rebooted?
--
Federico G. Benavento
next prev parent reply other threads:[~2007-05-12 7:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 7:24 Paul Lalonde
2007-05-12 7:36 ` Federico Benavento [this message]
2007-05-12 16:02 ` Paul Lalonde
2007-05-12 16:25 ` lucio
2007-05-12 7:37 ` Skip Tavakkolian
2007-05-12 16:46 ` Paul Lalonde
2007-05-12 19:52 ` Paul Lalonde
2007-05-12 10:19 ` Martin Neubauer
2007-05-12 16:44 ` Paul Lalonde
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=32d987d50705120036g5c9eeabfn269df7735efd27be@mail.gmail.com \
--to=benavento@gmail.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).