From: Guy Martin <gmsoft@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] x86 netboot, because beejay sucks
Date: Sat, 18 Sep 2004 16:08:55 +0200 [thread overview]
Message-ID: <20040918160855.2c4c7fe5.gmsoft@gentoo.org> (raw)
In-Reply-To: <414C3CF8.1080609@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Sat, 18 Sep 2004 09:49:44 -0400
Kumba <kumba@gentoo.org> wrote:
> Guy Martin wrote:
>
> > I'm working on this atm.
> >
> > My catalyst patch starts from a stage3, compile all the stuff you
> > specified in the spec file, copy the file you specified for each pkg
> > in the chroot, handle required libs and co. It also compiles busybox
> > and let you specify your config file for it.
> > I still have to write support for the kernel compilation and the
> > final netboot image generation.
> >
> > Btw, I need info about generating such image for x86. I know how to
> > do it for hppa but nfi for x86. :)
>
> Can one possibility for this be to just generate the
> loopback-mountable ramdisk as the final catalyst product along with a
> tar.bz2 of the same data (i.e., skip kernel compiliation)? In the
> case of mips netboots, systems whose kernels can be built w/ ramdisks
> will use the loopback image, while the others will use the tar.bz2 for
> nfsroot.
For now, I was planning somehting simple. The catalyst script would just
create a kernel and the ramdisk which would be a simple ext2 filesystem.
The final image would be created by a third-part script like the iso
generation script for the livecd.
Do you absolutely need to not build a kernel or the kernel build will
always be required ?
> Also, will this be able to use uclibc by chance?
I'm not familiar with uclibc. If simply copying the uclibc's libc.so
file in the ramdisk instead of the glibc's one works then I can
implement it quickly.
If all apps really needs to be linked against uclibc, I guess it can be
doable too but I'll have to look at it.
I should be able to have somehting running and useable today. I just
finished the kernel generation part. I just need to pack all of the
files. If you want to test, I'm on irc :)
> --Kumba
>
--
Guy Martin
Gentoo Linux - HPPA port Lead / IPv6 team
Lug Charleroi (Belgium)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-18 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 20:52 [gentoo-releng] x86 netboot, because beejay sucks Jeffrey Forman
2004-09-03 20:53 ` Guy Martin
2004-09-04 12:00 ` Sven Vermeulen
2004-09-04 18:05 ` John Davis
2004-09-18 10:22 ` Guy Martin
2004-09-18 13:49 ` Kumba
2004-09-18 14:08 ` Guy Martin [this message]
2004-09-04 23:24 ` Ciaran McCreesh
2004-09-05 5:09 ` John Davis
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=20040918160855.2c4c7fe5.gmsoft@gentoo.org \
--to=gmsoft@gentoo.org \
--cc=gentoo-releng@lists.gentoo.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