9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] AMD A68-N5000 kabini mother
Date: Sat,  2 Aug 2014 04:35:10 +0200	[thread overview]
Message-ID: <4918b51ec46123f7121ed282a4acfd6e@felloff.net> (raw)
In-Reply-To: <af7eb948e40867ec77a84ab0371547b1@ladd.quanstro.net>

the bootfs.paq with all the binaries is 1.5mb. and it
has support for all the fileservers and network booting.

we just reuse the rc scripts and binaries that are already
there and not trying to make up special solutions just for
booting to save a bit of memory. and having self contained
rc environment in the kernel is great as it lets you debug
the hardware before you have a working driver. (or you can
instruct someone to run some rc commands to troubleshoot a
system without him having the capability of building a
new kernel (because theres no driver yet)).

instead of having half broken smarts in the bootloader
(like passing half the partitions from loader to kernel)
which needs to duplicate all the drivers, we can just do
that with the kernels drivers and rc scrips. the kernel
doesnt care how it got loaded. it gets to the same environment
every time regardless of who loaded it. i can boot terminal
that mounts the root filesystem over wpa encrypted wifi
network and there are no hacks there. it just runs the same
programs early that you would normally run from termrc.

if you want to make a specialized low memory overhead
kernel that will only work on your machines then you still
can by specifying different files and /boot/boot
in your kernel configuration.

--
cinap



      reply	other threads:[~2014-08-02  2:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  5:18 [9fans] (no subject) kokamoto
2014-07-31  5:28 ` [9fans] AMD A68-N5000 kabini mother kokamoto
2014-07-31  7:59   ` cinap_lenrek
2014-07-31  8:23     ` kokamoto
2014-07-31  9:30       ` cinap_lenrek
2014-07-31 12:54         ` kokamoto
2014-07-31 13:35           ` cinap_lenrek
2014-08-01  0:45             ` kokamoto
2014-08-01  1:07               ` kokamoto
2014-08-02  1:25             ` erik quanstrom
2014-08-02  2:35               ` cinap_lenrek [this message]

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=4918b51ec46123f7121ed282a4acfd6e@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --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).