From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] a small error in /rc/bin/cpurc
Date: Tue, 6 Nov 2007 22:17:28 -0500 [thread overview]
Message-ID: <98ccc52b514dce516ff14c52ff5bbd4a@quanstro.net> (raw)
In-Reply-To: <A9533FDF-0357-40D6-BA5B-10F705FAD754@utopian.net>
> We've typically configured IP for our one standalone auth server
> from /cfg/$sysname/cpurc; I want to know if I've understood why
> you're doing it with plan9.ini bootargs instead: Is the advantage
> that you get the variables set in /net/ndb (fs, auth, etc) that I
> don't get when I call ip/ipconfig to set up a manual ip address from
> an rc script later in the boot?
we don't have any cpu servers that host their own filesystem. we use
ken's fileserver. so when the auth server boots, it must get its network
configuration from plan9.ini. there are no files at this point in the process.
and in order to get files, we need a network.
the auth server serves dhcp/tftp. so everybody else pxe boots.
i've considered building a very small fossil on a flash drive for the auth
server so it can be booted independenly of the fileserver and to have
a place to keep authentication information outside of the fs.
such a change has not yet been compelling.
- erik
next prev parent reply other threads:[~2007-11-07 3:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 3:02 Joshua Wood
2007-11-07 3:17 ` erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 5:51 Joshua Wood
2007-11-05 14:51 Joshua Wood
2007-11-05 12:59 Joshua Wood
2007-11-05 13:27 ` Antonin Vecera
2007-11-06 21:57 ` maht-9fans
2007-11-03 17:12 Antonin Vecera
2007-11-03 21:30 ` erik quanstrom
2007-11-04 11:18 ` Antonin Vecera
2007-11-04 16:48 ` erik quanstrom
2007-11-05 7:31 ` Antonin Vecera
2007-11-05 10:18 ` arisawa
2007-11-05 14:02 ` Antonin Vecera
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=98ccc52b514dce516ff14c52ff5bbd4a@quanstro.net \
--to=quanstro@quanstro.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).