From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] booting term kernel over the net
Date: Wed, 11 Dec 2002 08:59:33 -0500 [thread overview]
Message-ID: <21317b9382d83885fbd6edd9f9d885d7@plan9.bell-labs.com> (raw)
If you're talking about booting from kfs (rather
than a real fs, in which case IL will cause problems),
it's not hard. You can't fetch the kernel over the
wide-area network, but that's the only problem.
If you have the kernel on a floppy and put the
auth and fs info into plan9.ini, that's enough to
get going. I've done this for booting terminals
from a standalone kfs/auth across campus and
it worked reasonably well.
Russ
next reply other threads:[~2002-12-11 13:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 13:59 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 0:16 Geoff Collyer
2002-12-11 18:04 Russ Cox
2002-12-11 18:03 Fco.J.Ballesteros
2002-12-11 17:26 Fco.J.Ballesteros
2002-12-11 17:12 a
2002-12-11 17:51 ` Axel Belinfante
2002-12-11 15:14 Skip Tavakkolian
2002-12-11 11:17 Fco.J.Ballesteros
2002-12-11 8:37 Fco.J.Ballesteros
2002-12-11 8:11 Skip Tavakkolian
2002-12-11 1:23 Skip Tavakkolian
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=21317b9382d83885fbd6edd9f9d885d7@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).