X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by lists.alpinelinux.org (Postfix) with ESMTP id B2BF11EB598 for ; Wed, 31 Mar 2010 11:28:34 +0000 (UTC) Received: by bwz22 with SMTP id 22so12098803bwz.25 for ; Wed, 31 Mar 2010 04:28:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BjXEQLKQ9W0fdRUI8RsAGAqGsQyBw3HsGs/fy+QtQQc=; b=lGy88N/sgo5smHS+U6iOPFUT8TxOXXqJMTtkKXV0FmrYpgFN2XVSaozDo2vlwzMjEp 5NH2akrE/jI4QTwhzmEUmD+ApLQd/HRCcOwdZzQdI4nw/2MlZs3uv3PjVvyx5GYCTu8P GlNQ2V/FT3WpQUMQYQeDM/F8A2rIOJ7zXlGb8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vxE53Q/sjkYvdM4Sx9rBBlT5Izd0yzl0V4+O8rLnee5Pe3MSae0FB7eiPkwa1OmFKE +wBqGj08EakUidGyY3hMUSQaK3SUb/1l7wbVkUI22VYnb/3zKT82InAcu4X5McB+dp6s GMcxN3JyDIHebdlKM4O7xdBjxzfQCkT9PbraQ= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.204.54.147 with HTTP; Wed, 31 Mar 2010 04:28:32 -0700 (PDT) In-Reply-To: References: Date: Wed, 31 Mar 2010 13:28:32 +0200 Received: by 10.204.33.194 with SMTP id i2mr4617406bkd.140.1270034912844; Wed, 31 Mar 2010 04:28:32 -0700 (PDT) Message-ID: Subject: Re: [alpine-devel] Alpine Linux Xen support From: Natanael Copa To: cschieli@gmail.com Cc: alpine-devel@lists.alpinelinux.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Mar 30, 2010 at 11:25 AM, wrote: > Hello, > > > I've been working on bringing paravirtualized Xen support to Alpine Linux > for a few weeks, and the result is running fine here. > > Here is the current state of my work for review : > > > Small fixes (not Xen specific) needed for patch #6 : > 0001-main-dahdi-linux-vserver-install-modules.patch > 0002-main-iscsitarget-grsec-set-ksrc-in-package.patch applied. > > PV guest additions provided by Citrix for better integration in XenServer > 5.5 : > 0003-main-xe-guest-utilities-new-aport.patch The Maintainer comment is supposed to tell who is responsible for making the updates etc in alpine. (I need to clarify that in the docs) I applied the patch anyway. Would you like to take care of this package? When there are updates in future it'll be you to do those. If there are bugs in this package I'll send those in your direction. > Create a /dev/cdrom for virtual cdrom device > 0004-main-busybox-initscripts-add-xen-stuff-to-mdev.patch -pkgver=3D2.0 -pkgrel=3D10 +pkgver=3D2.0_git1 +pkgrel=3D0 why? Applied anyway. btw, I am thinking of switching to udev. (and are interested in feedback on reasons to do so or not do so) > CONFIG_586TSC and CONFIG_X86_PAE are needed to enable pvops Xen in mainli= ne > kernel, so I created a new kernel flavor aport : linux-pae > Grsecurity doesn't play nice with 2.6.32 32bits Xen code for the moment (= see > http://forums.grsecurity.net/viewtopic.php?f=3D1&t=3D2063&start=3D75#p965= 3) so > this patch is not enabled. The remaining is taken from the grsec flavor : > 0005-main-linux-pae-new-aport.patch makes sense. I wonder if we should provide this kernel as an option for paravirtualized vmware guests too? They also have problems with PaX. Since it does not have any special patches (vserver, grsec etc) would it be an idea to call this kernel "vanilla"? applied anyway. > Re-use existing aports to build dahdi-linux-pae and iscsitarget-pae (as > already done in xtables-addons-grsec) > 0006-main-dahdi-linux-vserver-iscsitarget-grsec-multi-fla.patch applied. > Note I've put the linux-pae aport in main as it is easier to build > dahdi-linux-pae, iscsitarget-pae and xtables-addons-pae from there. Maybe > some hacking can be done to enable building them from testing. Yes. What I'd like to do is remove the build dependency resolving from abuild shell script to an external lua script. I have the basics there. Related to that, I'm also working on splitting apk-tools into apk (binary) and libapk and then make lua bindings to libapk. The first reason to do so is so the lua script can use the version compare code with the real apk-tools. > I also worked on creating a bootable iso (by patching mkinitfs and > alpine-iso), but this is not quite finished, so I'll post that part later= . Nice! Thanks alot! > Regards, > C=E9dric Schieli > --=20 Natanael Copa --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---