From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1908 invoked from network); 18 Sep 2004 13:49:33 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 18 Sep 2004 13:49:33 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1C8fap-0004QA-DS for arch-gentoo-releng@lists.gentoo.org; Sat, 18 Sep 2004 13:49:35 +0000 Received: (qmail 2050 invoked by uid 89); 18 Sep 2004 13:49:30 +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 29380 invoked from network); 18 Sep 2004 13:49:30 +0000 Message-ID: <414C3CF8.1080609@gentoo.org> Date: Sat, 18 Sep 2004 09:49:44 -0400 From: Kumba User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-releng@lists.gentoo.org References: <1094244749.22276.9.camel@sixthstreet.formanonline.com> <20040903225316.3b91aafb.gmsoft@gentoo.org> <20040904120030.GH9776@gentoo.org> <20040918122215.3afaf224.gmsoft@gentoo.org> In-Reply-To: <20040918122215.3afaf224.gmsoft@gentoo.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-releng] x86 netboot, because beejay sucks X-Archives-Salt: 03751249-68e5-4f2e-9ca5-9c304cbe1b3a X-Archives-Hash: 9aefcf31c5818f5f428efd59f4d56e81 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. Also, will this be able to use uclibc by chance? --Kumba -- "Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond -- gentoo-releng@gentoo.org mailing list