X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail.wtbts.no (mail.wtbts.no [213.234.126.131]) by mail.alpinelinux.org (Postfix) with ESMTP id A4137DC0166 for ; Tue, 24 Jan 2012 10:39:20 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id B3EA4AE4001; Tue, 24 Jan 2012 10:39:19 +0000 (UTC) X-Virus-Scanned: Yes Received: from mail.wtbts.no ([127.0.0.1]) by localhost (bsna.nor.wtbts.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXyCfuBCjCa2; Tue, 24 Jan 2012 10:39:19 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id E7243376277; Tue, 24 Jan 2012 10:39:18 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 9BE4C609C28C7; Tue, 24 Jan 2012 10:39:18 +0000 (UTC) Received: from ncopa-desktop.nor.wtbts.net (ncopa-desktop.nor.wtbts.net [10.65.65.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@ytre.org) by mail.ytre.org (Postfix) with ESMTPSA id 75AAF60A70426; Tue, 24 Jan 2012 10:39:18 +0000 (UTC) Date: Tue, 24 Jan 2012 11:39:18 +0100 From: Natanael Copa To: Florian Heigl Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] What can we remove from our kernel? Message-ID: <20120124113918.3cfa2b94@ncopa-desktop.nor.wtbts.net> In-Reply-To: References: <20120123160339.77d895fb@ncopa-desktop.nor.wtbts.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; x86_64-unknown-linux-gnu) 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-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP On Mon, 23 Jan 2012 22:09:21 +0100 Florian Heigl wrote: > Hi, > > 2012/1/23 Natanael Copa : > > Hi, > > > > I have been looking at upgrading the kernel to 3.2 and I realize > > that configuring kernel is a pretty big job. I am struggling with > > keeping up with all the new stuff. > > I'll try to list the kinds of odd stuff that I commonly use or > definitely know be using in advance to keep it in... > (but of course I could also be building my own kernel, it being odd > stuff) This is the kind of feedback I wanted. > - infiniband (and mellanox drivers), rdma stuff, ipoib CONFIG_RDS_RDMA is not set Do you want me enable it? > - solarflare nics (don't actually have one yet) Are they enabled? > - scst (generic scsi target) Yes, I know there are many that use iscsi. I think we want follow upstream and use linux-iscsi.org if possible. (meaning linux-scst goes away in the long run) > - ceph filesystem client > - dmvpn / l2tpv3 DMVPN is one of the reasons Alpine Linux exists in first place and will not go away. Please let me know if anything of the above is missing in current kernel. > Another idea more in the spirit of AlpineLinux might be to start by > ticking off all items that are on the Carrier Grade Linux requirements > list, as these will probably apply to many users, and then look into > what else is "nice to have". Yes. I would need help with something like that. I think it would be nice if we could split the kernel package in 2. -base and -extra. All the "nice to have" things goes into extra and what the majority use is in -base. That'd be a start at least. Thanks! -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---