From owner-freebsd-ports@FreeBSD.ORG Thu Nov 23 21:15:54 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BCD616A40F for ; Thu, 23 Nov 2006 21:15:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F87643D75 for ; Thu, 23 Nov 2006 21:15:11 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 48C321A3C19; Thu, 23 Nov 2006 13:15:47 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 45B4651438; Thu, 23 Nov 2006 16:15:32 -0500 (EST) Date: Thu, 23 Nov 2006 16:15:32 -0500 From: Kris Kennaway To: Bakul Shah Message-ID: <20061123211532.GB83751@xor.obsecurity.org> References: <20061123191059.GA81608@xor.obsecurity.org> <20061123210728.796EE5B3E@mail.bitblocks.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GID0FwUMdk1T2AWN" Content-Disposition: inline In-Reply-To: <20061123210728.796EE5B3E@mail.bitblocks.com> User-Agent: Mutt/1.4.2.2i Cc: Anders Troback , FreeBSD Ports , Kris Kennaway Subject: Re: Qemu crash... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2006 21:15:54 -0000 --GID0FwUMdk1T2AWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 23, 2006 at 01:07:28PM -0800, Bakul Shah wrote: > > You need to include AIO support in your kernel (or as a module). The > > port should be updated to mention this. >=20 > May be it is time to add a /usr/local/etc/rc.d/qemu script > that kldload aio and kqemu (if it exists)? The problem is that kldloading a module if it's already in the kernel can cause a panic. Also if the module becomes stale with respect to the running kernel, this approach can cause a lot of confusion. Something I'd like to see is a) Fixing the kldload "double load" problems b) That optional kernel subsystems register themselves with a sysctl, so that userland can easily determine whether a feature is present in the running kernel and take appropriate action (warn user, demand load, etc) if not. compat[45]x support is another such case; there's no way for a port to tell whether the kernel supports running such binaries, and if not then the user will just get an error when they try to run it. I guess these should go on the "projects" list. The second one would be a good SoC project, for ex. Kris --GID0FwUMdk1T2AWN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFZg9zWry0BWjoQKURAsmWAKC79XoMdyI1+V7JRgvolcasREXUnQCgg0DK hsnS9IBr4yJBXjF7OiG5A6c= =m+zh -----END PGP SIGNATURE----- --GID0FwUMdk1T2AWN--