From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Q: Linux rebooting directly into linux.
Date: 11 Nov 2000 12:33:15 -0800 [thread overview]
Message-ID: <8ukaeb$eh6$1@cesium.transmeta.com> (raw)
In-Reply-To: <m17l6deey7.fsf@frodo.biederman.org> <20001109113524.C14133@animx.eu.org> <m1g0kycm0x.fsf@frodo.biederman.org>
Followup to: <m1g0kycm0x.fsf@frodo.biederman.org>
By author: ebiederm@xmission.com (Eric W. Biederman)
In newsgroup: linux.dev.kernel
> > >
> > > The interface is designed to be simple and inflexible yet very
> > > powerful. To that end the code just takes an elf binary, and a
> > > command line. The started image also takes an environment generated
> > > by the kernel of all of the unprobeable hardware details.
> >
> > Isn't this what milo does on alpha?
>
> Similar milo uses kernel drivers in it's own framework.
> This has proved to be a major maintenance problem. Milo is nearly
> a kernel fork.
>
> The design is for the long term to get this incorporated into the
> kernel, and even if not a small kernel patch should be easier to
> maintain that a harness for calling kernel drivers.
>
I'm working on something similiar in "Genesis". It pretty much is (or
rather, will be) a kernel *port*, not a fork; the port is such that it
can run on top of a simple BIOS extender and thus access the boot
media.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-11 20:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 8:18 Q: Linux rebooting directly into linux Eric W. Biederman
[not found] ` <3A0ABB0C.99075A61@holly-springs.nc.us>
2000-11-11 19:46 ` Eric W. Biederman
2000-11-11 22:46 ` Adam Lazur
2000-11-12 0:06 ` Eric W. Biederman
[not found] ` <20001109113524.C14133@animx.eu.org>
2000-11-11 20:05 ` Eric W. Biederman
2000-11-11 20:33 ` H. Peter Anvin [this message]
2000-11-12 0:09 ` Eric W. Biederman
2000-11-12 0:32 ` H. Peter Anvin
2000-11-12 6:31 ` Eric W. Biederman
2000-11-11 22:11 ` Adam Lazur
2000-11-12 0:00 ` Eric W. Biederman
2000-11-14 14:49 ` Werner Almesberger
2000-11-16 17:33 ` Eric W. Biederman
2000-11-19 2:24 ` Werner Almesberger
2000-11-19 7:20 ` Eric W. Biederman
2000-11-19 13:25 ` Werner Almesberger
2000-11-19 20:14 ` Eric W. Biederman
2001-01-18 16:18 ` Eric W. Biederman
2000-11-14 8:13 ` Erik Andersen
2000-11-14 14:59 ` Eric W. Biederman
2000-11-15 23:30 ` Erik Andersen
2000-11-16 6:19 ` Eric W. Biederman
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='8ukaeb$eh6$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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