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 2F03F3617A23 for ; Mon, 4 Oct 2010 11:02:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id 7A80C26A0C for ; Mon, 4 Oct 2010 13:02:41 +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 GLtcYWJqKjVD for ; Mon, 4 Oct 2010 13:02:38 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by chasm.ymmv.dk (Postfix) with ESMTP id 70CBD26A39 for ; Mon, 4 Oct 2010 13:02:38 +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 673E726A0C for ; Mon, 4 Oct 2010 13:02:37 +0200 (CEST) Date: Mon, 4 Oct 2010 13:02:35 +0200 From: Jon Clausen To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] i486 vserver kernel? Message-ID: <20101004110235.GG2458@nx8220.ymmv.dk> 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 User-Agent: Mutt/1.5.20 (2009-06-14) Hi I have these old, underpowered, resource starved singleboard machines. (VIA Samuel 2 CPU, 512 MB RAM) I'd like to extend their life a little longer, and one way of doing that would be using them for 'pet projects'. 'vserver' seems a likely way of getting the most out of the hardware, except that the CPU doesn't support instructions that the i686 kernel needs (CMOV) I managed to get a proof of concept system running by recompiling a vserver kernel configured for i486, but... 1: An 'official' i486 build would be much nicer (and easier for me ;) 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 :) /jon -- YMMV --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---