Date: Thu, 6 Nov 2008 15:58:58 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: FreeBSD current mailing list <current@freebsd.org> Cc: src-committers@freebsd.org, FreeBSD net mailing list <net@freebsd.org> Subject: Kernel without INET Message-ID: <20081106153035.R16105@maildrop.int.zabbadoz.net>
next in thread | raw e-mail | index | archive | help
Hi, some might have wondered about lots of small commits I have done the last two days. I had been trying to compile a kernel without any networking a few weeks ago and that failed; I had needed to add (I think it was) INET, ether and loop. So I had been trying to get rid of that requirement the last days. As a partial victory it seems to be possible again to build a kernel without any networking now. I'll have to check with my original setup but I have a stripped down LINT file I tested with. Obviously the long term goal is to be able to build a kernel without INET support (again?). As an intermediate step that will mean without INET and INET6 and once that works and IPX only would compile *cough*, then work on a (LINT) kernel with nooption INET. It'll be a long long way to go and this is nothing to finish within a week or two. Do not think about doing a quick sweep over the rest of the tree. You would wonder what depends on INET these days. I have more patches mailed out or pending here. While we had been trying to make it possible to build without INET6 most of the time, someone doing review on my code told me that if compaining about 'kernel needs INET' I should put some code under #ifdef INET. I did. The bottom line is that I now ask you to consider this for all new code as well. I am very well aware that some code, as is, would already require a maze of #ifdefs (I have a sample of that) so we need to be careful and apply the checks sensibly. Regards, Bjoern PS: please obey Reply-To: -- Bjoern A. Zeeb Stop bit received. Insert coin for new game.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081106153035.R16105>