9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] 9pccpu: can't open /dev/sdXX/nvram
Date: Fri, 17 Aug 2012 05:27:08 +0200	[thread overview]
Message-ID: <15702647d62958113341ea80cc9054ac@rei2.9hal> (raw)
In-Reply-To: <D57B8416-4C4B-4500-9307-C808A0E7448A@ar.aichi-u.ac.jp>

the 9front kernels use a new rc based bootstrap system. the
kernel itself uses a compressed ram filesystem image (paqfs)
that will be mounted by /boot/boot containing the required
programs like rc, srv, ifconfig and file fileservers like
9660srv and cwfs to mount the real root filesystem.

there is no special cdboot kernel or pxe boot kernel anymore.

every kernel is capable of network booting or booting from
local disk or cdrom or usb stick.

the only thing that got specialized are the bootloaders. theres
9bootiso, 9bootfat and 9bootpxe. but once they get the kernel
loaded, stuff looks exactly the same.

this also has the advantage that you can boot to a local cwfs
just using the cdrom. or boot from the cd by using a usb stick
or network boot. ect. so thats why we removed the special netboot
kernels. it also helps rescuing a unbootable/bricked system.
you can even run rc shell from these kernels (type !rc at the
bootargs prompt) so you can inspect the system even tho it might
not be able to detect the network card or disk controller ect...

for the bootloaders, i thought that a command line/console that
lets you change specific kernel parameters before boot is more
usefull than a menu with preconfigured options. especially in the
case of testing or rescuing a system. 9boot even works if theres no
plan9.ini at all.

we also want to keep the bootloaders as simple and as stupid as
possible. the less you do at the boot stage the less can go wrong.
boot enviroment is very tricky thing. we avoid interfering with
bios at all costs and do the clever parts once we took control of the
hardware and have a running kernel.

the kernel will present you with a "menu" like list of bootable
local filesystems.

--
cinap



  reply	other threads:[~2012-08-17  3:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28  3:30 arisawa
2012-07-28  8:19 ` David du Colombier
2012-07-28 13:41   ` arisawa
2012-07-28 14:33     ` David du Colombier
2012-07-29  7:30       ` arisawa
2012-07-29  9:43         ` Richard Miller
2012-07-29 11:45           ` arisawa
2012-07-29 14:16             ` Richard Miller
2012-07-29 22:49               ` arisawa
2012-07-30  9:19                 ` arisawa
2012-07-30 14:46                   ` erik quanstrom
2012-07-30 20:45                     ` cinap_lenrek
2012-08-17  2:15                       ` arisawa
2012-08-17  3:27                         ` cinap_lenrek [this message]
2013-05-13 16:37                   ` Skip Tavakkolian
2013-05-13 21:32                     ` arisawa
2013-05-13 21:53                       ` Matthew Veety
2013-05-13 23:06                       ` erik quanstrom
2013-05-15  9:56                         ` arisawa
2013-05-15 20:56                           ` arisawa
2013-05-15 21:18                             ` erik quanstrom
2013-05-16  0:16                               ` arisawa
2013-05-16  1:25                                 ` erik quanstrom
2013-05-16 13:44                                 ` kernel panic
2013-05-17 12:36                                   ` arisawa

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=15702647d62958113341ea80cc9054ac@rei2.9hal \
    --to=cinap_lenrek@gmx.de \
    --cc=9fans@9fans.net \
    /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).