Subject: Re: [alpine-devel] i486 vserver kernel?
From: Natanael Copa <ncopa@alpinelinux.org>
To: Jon Clausen <alpine@ymmv.dk>
Cc: alpine-devel@lists.alpinelinux.org
In-Reply-To: <20101006150135.GB2482@nx8220.ymmv.dk>
References: <20101004110235.GG2458@nx8220.ymmv.dk>
	 <1286197843.28650.61.camel@ncopa-desktop.nor.wtbts.net>
	 <20101006150135.GB2482@nx8220.ymmv.dk>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 07 Oct 2010 10:25:53 +0200
Message-ID: <1286439953.1540.12.camel@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Wed, 2010-10-06 at 17:01 +0200, Jon Clausen wrote:
> 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: 
...
> 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.

we use the term "flavor" for the patchsets. linux-grsec, linux-vserver.

> 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

This would be the best, yes. Unfortunally it would require some extra
maintenence work. How about 3rd party modules? dahdli-linux-vserver for
instance. I also does a quick test to verify that the kernel actually
boot in a virtual machine before I push the change. Should I test both
i486 and i586? The biggest issue is that those things are not a one-time
job and currently I'm pretty much at the limit of what I can maintain.

I am also planning to do alpine x86_64 soonish and I think most high-end
vserver hosts will be using that, so I'm not that keen on start with
linux-vserver-i486, linux-vserver-i586, linux-vserver-i686 for the time
beeing.

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---