X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from chasm.ymmv.dk (unknown [193.106.164.142]) by lists.alpinelinux.org (Postfix) with ESMTP id 9F6B33617A1D for ; Wed, 6 Oct 2010 15:01:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id 710D226ABA for ; Wed, 6 Oct 2010 17:01:43 +0200 (CEST) X-Virus-Scanned: by amavisd-new at ymmv.dk Received: from chasm.ymmv.dk ([127.0.0.1]) by localhost (chasm.ymmv.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gT9tVWMtbit8 for ; Wed, 6 Oct 2010 17:01:39 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id 1423A26AC0 for ; Wed, 6 Oct 2010 17:01:39 +0200 (CEST) Received: from nx8220.ymmv.dk (unknown [10.9.8.113]) (Authenticated sender: jon@ymmv.dk) by chasm.ymmv.dk (Postfix) with ESMTPSA id 089DA26ABA for ; Wed, 6 Oct 2010 17:01:37 +0200 (CEST) Date: Wed, 6 Oct 2010 17:01:36 +0200 From: Jon Clausen To: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] i486 vserver kernel? Message-ID: <20101006150135.GB2482@nx8220.ymmv.dk> References: <20101004110235.GG2458@nx8220.ymmv.dk> <1286197843.28650.61.camel@ncopa-desktop.nor.wtbts.net> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1286197843.28650.61.camel@ncopa-desktop.nor.wtbts.net> User-Agent: Mutt/1.5.20 (2009-06-14) On Mon, 04 Oct, 2010 at 15:10:43 +0200, Natanael Copa wrote: > On Mon, 2010-10-04 at 13:02 +0200, Jon Clausen wrote: > > 1: An 'official' i486 build would be much nicer (and easier for me ;) > > hum. I think there was a reason switch to i586, but i dont remember what > it was. I wonder if it was related to better virtualization guest > support or something. > > I think it would be nice to support this kind of old hardware so I'm > switching to i486 for linux-vserver til someone comes with some good > reasons to switch back to i586. Actually I was thinking more in terms of kernel 'flavours' or 'architechtures'. People with newer HW might be better off (as in get better performance) with i586 or i686 kernels. Is it feasible to introduce multiple builds? Sort of: linux-vserver-i486-2.6.32.24-r0.apk linux-vserver-i586-2.6.32.24-r0.apk > Please try the linux-vserver kernel in edge. Well, "it boots" is about all I can say ATM - had to shuffle some stuff around, so I haven't gotten to actually running any guests yet. But thanks so far ;) > > 2: If for some reason 1: isn't feasible, what are the steps to set up a > > (semi-)automated buildsystem? > > I guess it would entail something on the order of > > * getting notified when there's a new kernel version > > * syncronizing the sources > > * generating a new 'i486 .config' > > * compile/package > > > > Hints much appreciated :) > > This should not be too hard for you to set up either. > > From the top of my head, something like: For the time being, I'll just 'coast along' with the i486 kernel from 'edge'... but thanks for 'outline'. regards, jon -- YMMV --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---