From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Network booting
Date: Thu, 01 Aug 2013 09:35:08 +0100 [thread overview]
Message-ID: <3556481.TFZYk16CGl@helios> (raw)
In-Reply-To: <FDB39166-46D6-451C-9681-89E214958BF3@keylevel.com>
Hi Chris,
On Wednesday 31 July 2013 22:25:42 Chris Tapp wrote:
> On 31 Jul 2013, at 21:30, Chris Tapp wrote:
> > Is there an easy way to have a system boot and load the rootfs from a
> > network server?
> >
> > I'm using an x86 system and can have the kernel and an initrd on it. I
> > would use bootp, but a lot of end users either don't have this or will
> > not allow it to be used. I think it needs to go something like:
> >
> > 1) Kernel loads the initrd and bring the network up (static or DHCP);
> > 2) The rootfs image can then be download;
> > 3) Some magic then makes this run...
> >
> > This would allow easy update of the rootfs and makes it non-volatile
> > (which is good for this project).
> >
> > Does this make sense, or is there a better / easier way to do it?
>
> Looks like http://ipxe.org/ could be what's needed.
FWIW, a couple of years ago I did write a recipe for ipxe which I successfully
used for over-the-network booting with atom-pc. I never found a proper home
for it though so it's still sitting in one of my poky-contrib branches:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/tree/meta/recipes-bsp/ipxe?h=paule/ipxe
Feel free to make use of it if it helps you. (I can't promise it hasn't
bitrotted in the time since I wrote it, so it may need tweaking; I notice
I didn't even specify a SRCREV which really should be specified, and
I'm not sure if it's cross-compiling properly either).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-08-01 8:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 20:30 Network booting Chris Tapp
2013-07-31 21:25 ` Chris Tapp
2013-08-01 8:35 ` Paul Eggleton [this message]
2013-08-01 18:50 ` Chris Tapp
2013-07-31 21:29 ` Rudolf Streif
2013-07-31 21:36 ` Chris Tapp
2013-08-01 8:08 ` Tomas Frydrych
2013-08-01 14:06 ` Tomas Frydrych
2013-08-01 18:53 ` Chris Tapp
2013-08-02 7:22 ` Tomas Frydrych
2013-08-02 7:35 ` Chris Tapp
2013-08-02 8:09 ` Tomas Frydrych
-- strict thread matches above, loose matches on Subject: below --
2002-02-20 8:43 network booting nimeesh
2002-02-20 11:19 ` Chris Chabot
2002-02-20 11:38 ` Wakko Warner
2002-02-20 13:53 ` Chris Chabot
1999-11-17 4:14 Network Booting Chris McKillop
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=3556481.TFZYk16CGl@helios \
--to=paul.eggleton@linux.intel.com \
--cc=opensource@keylevel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.