From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6657 invoked from network); 18 Sep 2004 14:09:08 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 18 Sep 2004 14:09:08 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1C8ftn-0006n8-4X for arch-gentoo-releng@lists.gentoo.org; Sat, 18 Sep 2004 14:09:11 +0000 Received: (qmail 4545 invoked by uid 89); 18 Sep 2004 14:09:05 +0000 Mailing-List: contact gentoo-releng-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-releng@lists.gentoo.org X-BeenThere: gentoo-releng@gentoo.org Received: (qmail 1919 invoked from network); 18 Sep 2004 14:09:04 +0000 Date: Sat, 18 Sep 2004 16:08:55 +0200 From: Guy Martin To: gentoo-releng@lists.gentoo.org Message-Id: <20040918160855.2c4c7fe5.gmsoft@gentoo.org> In-Reply-To: <414C3CF8.1080609@gentoo.org> References: <1094244749.22276.9.camel@sixthstreet.formanonline.com> <20040903225316.3b91aafb.gmsoft@gentoo.org> <20040904120030.GH9776@gentoo.org> <20040918122215.3afaf224.gmsoft@gentoo.org> <414C3CF8.1080609@gentoo.org> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sat__18_Sep_2004_16_08_55_+0200_RZiTvEyOaClkrdbn" X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "playa.lln.tuxicoman.be", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or block similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Sat, 18 Sep 2004 09:49:44 -0400 Kumba 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. [...] Content analysis details: (0.0 points, 3.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- Subject: Re: [gentoo-releng] x86 netboot, because beejay sucks X-Archives-Salt: ab43803e-e9e3-4ab5-ad56-c3c4fdfac09d X-Archives-Hash: c9350c9be47f12bf9ae199d359574ddf --Signature=_Sat__18_Sep_2004_16_08_55_+0200_RZiTvEyOaClkrdbn Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Sat, 18 Sep 2004 09:49:44 -0400 Kumba 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) --Signature=_Sat__18_Sep_2004_16_08_55_+0200_RZiTvEyOaClkrdbn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBTEF5rpShrnoH4YYRAi9dAJ45ajCiWSRfvVnaACpmkft5yHH5nQCdGE8n bNEiQCksMElslVTQ/VKcXdM= =p+qj -----END PGP SIGNATURE----- --Signature=_Sat__18_Sep_2004_16_08_55_+0200_RZiTvEyOaClkrdbn--