9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: yoann padioleau <aryx.padator@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Porting plan9
Date: Tue,  2 Dec 2014 16:20:36 -0800	[thread overview]
Message-ID: <38B4730F-0F3D-4BF8-AF67-05ED8FFBCA48@gmail.com> (raw)
In-Reply-To: <547E3CF1.1090706@gr13.net>

I think one of the reason 9load is quite complicated is because
they wanted to boot a kernel from the network, so you need a network stack and the drivers for the ethernet card, so you really need lots of OS code in the end.

On Dec 2, 2014, at 2:28 PM, Enrico Weigelt, metux IT consult <enrico.weigelt@gr13.net> wrote:

> On 02.12.2014 23:02, Iruatã Souza wrote:
> 
>>> apropos kernel/bootloader: I just recently had a look at the code
>>> and somewhat got the impression that 9load seems to be a specially
>>> tailored plan9 kernel, which then loads the real kernel.
>>> 
>>> is that correct or am I mistaken here ?
>> 
>> Correct.
> 
> hmm, interesting.
> 
> What's the exact reason behind that ?
> 
> I'm really not an expert for bootloaders, but I always got the
> impression, that bootloaders need to be extremly minimal (eg. on
> PC you'll have only about 0.5k for the first stage) and serve an
> entirely different purpose than an OS kernel.
> 
> OTOH, having a complete OS/Kernel as preboot environment of course
> also has it's charm - allows easily adding lots of setup things,
> even rescue stuff, etc.
> 
> Can 9front also boot other operating systems, eg. Linux ?
> Could it become a replacement for other bootloaders like grub ?
> 
> 
> cu
> --
> Enrico Weigelt,
> metux IT consulting
> +49-151-27565287
> 




  parent reply	other threads:[~2014-12-03  0:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  5:14 Ramakrishnan Muthukrishnan
2014-12-01  5:44 ` erik quanstrom
2014-12-01  8:43   ` Ramakrishnan Muthukrishnan
2014-12-01 14:13     ` erik quanstrom
2014-12-01 21:54     ` Steven Stallion
2014-12-02  0:30       ` Ramakrishnan Muthukrishnan
2014-12-02  0:56       ` Kurt H Maier
2014-12-02  2:16         ` Steven Stallion
2014-12-02  2:23           ` Skip Tavakkolian
2014-12-02  4:03           ` Kurt H Maier
2014-12-02  4:05             ` erik quanstrom
2014-12-02  4:19               ` Kurt H Maier
2014-12-02  4:23                 ` erik quanstrom
2014-12-02  2:42       ` Bakul Shah
2014-12-02  3:31         ` Steven Stallion
2014-12-02  2:43       ` erik quanstrom
2014-12-02  9:32         ` Richard Miller
2014-12-02 10:12           ` Jens Staal
2014-12-02 10:48             ` mischief
2014-12-02 10:54               ` mischief
2014-12-02 14:10           ` erik quanstrom
2014-12-02 15:21             ` Steven Stallion
2014-12-02 21:57               ` Enrico Weigelt, metux IT consult
2014-12-02 22:02                 ` Iruatã Souza
2014-12-02 22:28                   ` Enrico Weigelt, metux IT consult
2014-12-02 22:55                     ` Iruatã Souza
2014-12-03  0:20                     ` yoann padioleau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-24  1:17 [9fans] porting plan9 forsyth
2002-01-24 19:13 ` Michael Grunditz
2002-01-24  0:45 jmk
2002-01-23 23:58 Michael Grunditz
2002-01-23 23:06 anothy

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=38B4730F-0F3D-4BF8-AF67-05ED8FFBCA48@gmail.com \
    --to=aryx.padator@gmail.com \
    --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).