From: Wes <anomaly256@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Error booting from latest plan9.iso download
Date: Tue, 8 May 2007 10:10:18 +1000 [thread overview]
Message-ID: <2899e2610705071710i47125c9dl22727abfe13233c3@mail.gmail.com> (raw)
In-Reply-To: <32d987d50705070311j1ebf0379od50947ae03d456cd@mail.gmail.com>
I did add it to termrc, but when I rebooted I forgot to do an fshalt
first so it didn't take. All good now, thanks. I'll set it up the
proper way now.
Wes
On 5/7/07, Federico Benavento <benavento@gmail.com> wrote:
> I thought we were talking about booting the live CD...
> after the installation add an entry to /lib/ndb/local
>
> sys=mymachine ether=macaddres
>
> you can find nic's macaddres by catting /net/ether0/addr
> ah, and it has to be in lower case
>
> On 5/7/07, Martin Neubauer <m.ne@gmx.net> wrote:
> > * Wes (anomaly256@gmail.com) wrote:
> > > hmm, echoing machinename to /dev/sysname doesn't seem to be persistent
> > > across reboots and adding it to termrc also doesn't seem to take.
> > > Will I have to do this every bootup?
> >
> > The ``right'' solution would be to specify your network configuration in
> > /lib/ndb/local. If you have only a single plan9 machine you can get away
> > with ``echo hostname > /dev/sysname'' in termrc (or, rather, termrc.local).
> >
> > Martin
> >
> >
>
>
> --
> Federico G. Benavento
>
next prev parent reply other threads:[~2007-05-08 0:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 5:57 Wes
2007-05-07 6:02 ` Federico Benavento
2007-05-07 6:04 ` Wes
2007-05-07 6:53 ` Wes
2007-05-07 8:35 ` Martin Neubauer
2007-05-07 10:11 ` Federico Benavento
2007-05-08 0:10 ` Wes [this message]
2007-05-08 5:02 ` [9fans] Sam: m and "changes not in sequence" Yard Ape
2007-05-08 19:18 ` Micah Stetson
2007-05-09 15:18 ` rog
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=2899e2610705071710i47125c9dl22727abfe13233c3@mail.gmail.com \
--to=anomaly256@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).