9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jason Gurtz" <jason@tommyk.com>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] new bootstrap structure
Date: Wed, 14 Nov 2001 11:33:55 -0500	[thread overview]
Message-ID: <HBEEKNPPKIMFLJHGHNHMGEAHCGAA.jason@tommyk.com> (raw)
In-Reply-To: <20011113234030.E5B8319A4A@mail.cse.psu.edu>



> what to do for people without CD drives is a
> seperate question.

  I'm not sure how many people around here have played much with the grub bootloader.  It supports quite a few "standardish" Ethernet adapters as well as built in support for reading FAT and other file systems.  This comes in handy as grub features a built in (very) mini shell not entirely unlike what the PROM offers in a RISC box.  The hapless admin can hand boot an OS from any of the recognized file systems. The version I've built for booting GNU/Linux weighs in <115K.  It might be a bit more than Plan 9 needs but it could be a good source of ideas.  Find it here:  http://www.gnu.org/software/grub/ 

  I few days ago I did an ftp install of FreeBSD 4.4-RELEASE.  It's pretty smooth; one downloads 2 1.44 Meg floppy images, dd them to disks (gah, 5 out of 7 were ready for the bin) and boot.  The rest of it was fairly intuitive to me save for that it's not immediately clear when you are done.  There was no wording to suggest that indeed all tasks were complete and I should reboot now.  Other than that I had my cake and ate it too  :)  I would consider it close to a model install process.

P.S.  Don't be afraid of the GNU people calling it alpha software.  It has yet to fail me in several situations.  But maybe better programmers like yourselves would have a clearer view of whether to be afraid or not  ;)

Cheers,

~Jason

-- 



  parent reply	other threads:[~2001-11-14 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 23:40 anothy
2001-11-13 23:48 ` George Michaelson
2001-11-14 16:33 ` Jason Gurtz [this message]
2001-11-14 19:40   ` plan9

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=HBEEKNPPKIMFLJHGHNHMGEAHCGAA.jason@tommyk.com \
    --to=jason@tommyk.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).