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 C83DEDC0166 for ; Tue, 24 Jan 2012 09:58:11 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id 50CDFAE4001; Tue, 24 Jan 2012 09:58:10 +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 ZfMinjRvdBFu; Tue, 24 Jan 2012 09:58:09 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id 43569376277; Tue, 24 Jan 2012 09:58:09 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 01110609C28C8; Tue, 24 Jan 2012 09:58:08 +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 B2702609C28C7; Tue, 24 Jan 2012 09:58:08 +0000 (UTC) Date: Tue, 24 Jan 2012 10:58:07 +0100 From: Natanael Copa To: Kevin Chadwick Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] What can we remove from our kernel? Message-ID: <20120124105807.1d958e68@ncopa-desktop.nor.wtbts.net> In-Reply-To: <20120123180555.0054696b.ma1l1ists@yahoo.co.uk> References: <20120123160339.77d895fb@ncopa-desktop.nor.wtbts.net> <20120123180555.0054696b.ma1l1ists@yahoo.co.uk> 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 18:05:55 +0000 Kevin Chadwick wrote: > On Mon, 23 Jan 2012 16:03:39 +0100 > Natanael Copa wrote: > > > I am struggling with keeping > > up with all the new stuff. > > Would the new LTS 3.0.x be easier or would it miss out required > drivers? Ideally we should do both and have a linux-lts-grsec kernel and a linux-grsec kernel. I don't have resources for that currently. I think we want the new stuff in new kernels. > I guess as you have RSBAC then you could drop RBAC, though RBAC is > easier to configure. > > I wish there was a lean and secure Kernel or even Kernel config but > then I gues it wouldn't be Linux. > > More code = more bugs Exactly. So it would be nice with some ideas what we can do to fight the kernel bloat. > I just hope the build doesn't break on you. I tried tailoring it to my > machines and disabled wireless/bluetooth and knocked 10 meg off the > size but setting the cpu type and a couple of other things broke the > build. (2.6.32.49 LTS) > > Is bluetooth required? This is exactly the kind of question I want help to come up with. I use bluetooth on my laptop. Maybe we could have a linux-grsec-bluetooth subpackage with the bluetooth stuff? How do we create such a subpackage? Can we split by a dir? There are 2 directories named bluetooth: $ du -sh drivers/bluetooth net/bluetooth/ 172.0K drivers/bluetooth 316.0K net/bluetooth Is that worth a subpackage? probably not. $ du -sh net/wireless/ drivers/net/wireless/ 220.0K net/wireless/ 5.0M drivers/net/wireless/ This might be worth a subpackage and we could probably stuff in bluetooth in there as well. Thanks! -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---