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 5868A3617A1E
	for <alpine-devel@lists.alpinelinux.org>; Sun, 10 Oct 2010 08:33:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by chasm.ymmv.dk (Postfix) with ESMTP id CF25327392
	for <alpine-devel@lists.alpinelinux.org>; Sun, 10 Oct 2010 10:33:29 +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 MNp+jAkvF-xm for <alpine-devel@lists.alpinelinux.org>;
	Sun, 10 Oct 2010 10:33:26 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by chasm.ymmv.dk (Postfix) with ESMTP id 96AB527397
	for <alpine-devel@lists.alpinelinux.org>; Sun, 10 Oct 2010 10:33:25 +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 8E4CE27392
	for <alpine-devel@lists.alpinelinux.org>; Sun, 10 Oct 2010 10:33:24 +0200 (CEST)
Date: Sun, 10 Oct 2010 10:33:17 +0200
From: Jon Clausen <alpine@ymmv.dk>
To: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] i486 vserver kernel?
Message-ID: <20101010083317.GA2445@nx8220.ymmv.dk>
References: <20101004110235.GG2458@nx8220.ymmv.dk>
 <1286197843.28650.61.camel@ncopa-desktop.nor.wtbts.net>
 <20101006150135.GB2482@nx8220.ymmv.dk>
 <1286439953.1540.12.camel@ncopa-desktop.nor.wtbts.net>
 <20101007090257.GA2467@nx8220.ymmv.dk>
 <4CAD9782.3050207@iki.fi>
 <1286463256.1540.23.camel@ncopa-desktop.nor.wtbts.net>
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1286463256.1540.23.camel@ncopa-desktop.nor.wtbts.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, 07 Oct, 2010 at 16:54:16 +0200, Natanael Copa wrote:
> On Thu, 2010-10-07 at 12:48 +0300, Timo Ter=E4s wrote:

> > I wonder if we could automate the "does the
> > kernel boot test". I think it should be doable with qemu + a script to
> > monitor console output (e.g to check that we get getty prompt).
>=20
> It is infact half automated already. I run a script that builds iso with
> specified kernel (vserver or grsec), installs qemu and boots it up with
> ncurses interface. Then i just log in and do 'poweroff'.

Is it possible to add networking/sshd to this test-setup?

If it is, then key-based auth might provide a way to automate the post build
test process without 'expect' (?)

> If the boot iso had serial boot, then I could use something like
> 'expect' ur lua-pty to wait for login: and send 'root<enter>' and
> 'poweroff' and if success, then push the commit...
>=20
> hum...
>=20
> Does anyone have any objections to enable serial login by default?

Personally, no - but this;

> The
> only reason I havent it enabled by default is that you never know what
> devices are connected to computers serial interface (UPS? sms gateway?)
> and once its enabled, it cannot be turned off from default iso.

may be a pretty good reason not to enable serial by default.

regards,
jon
--=20
YMMV


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---