From owner-freebsd-current@FreeBSD.ORG Sun Dec 31 14:41:01 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8888016A40F for ; Sun, 31 Dec 2006 14:41:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 160B313C465 for ; Sun, 31 Dec 2006 14:41:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.64.187.168] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1H11rv3IBc-0003CN; Sun, 31 Dec 2006 15:41:00 +0100 From: Max Laier Organization: FreeBSD To: Paolo Pisati Date: Sun, 31 Dec 2006 15:40:51 +0100 User-Agent: KMail/1.9.4 References: <20061230195219.GD64111@bunrab.catwhisker.org> <20061231024203.GA8147@tin.it> <20061231070453.GV46380@FreeBSD.org> In-Reply-To: <20061231070453.GV46380@FreeBSD.org> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1339918.rAV2WeRTfe"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200612311540.58196.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Gleb Smirnoff , freebsd-current@freebsd.org Subject: Re: Can't link kernel after recent libalias commits? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 14:41:01 -0000 --nextPart1339918.rAV2WeRTfe Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 31 December 2006 08:04, Gleb Smirnoff wrote: > On Sun, Dec 31, 2006 at 03:42:03AM +0100, Paolo Pisati wrote: > P> On Sat, Dec 30, 2006 at 11:04:33PM +0100, Max Laier wrote: > P> > On Saturday 30 December 2006 22:46, Paolo Pisati wrote: > P> > > On Sat, Dec 30, 2006 at 01:43:21PM -0800, David Wolfskill wrote: > P> > > > Note that this was for a kernel that uses ipfw, but not natd > (ref. P> > > > src/sys/conf/NOTES). > P> > > > P> > > my mistake, i'll write an entry for UPDATING. > P> > > P> > Shouldn't it still be possible to build a kernel with IPFW but > without P> > LIBALIAS? i.e. instead of a UPDATING entry you should > just wrap the P> > libalias entry points in IPFW - or am I > misunderstanding what you are P> > saying? > P> > P> with my last commit, LIBALIAS became mandatory for IPFW, and this > adds P> 40kb (-O nocona) to my kernel size. > P> > P> If it's really an issue, i can change it. > > As I said it will be very nice if it would be still possible to build > ipfw(4) w/o libalias. I think more people will share my opinion. I agree. You can either simply #ifdef-out the Libalias glue code in ipfw=20 on LIBALIAS or introduce a new option "FIREWALL_NO_ALIAS" or something to=20 have that effect. The first would not break POLA and should be=20 preferred - IMO. Having the module build default to "with LIBALIAS" is=20 okay to make this great feature available from a default installation,=20 but there certainly should be a way to disable it on a custom build. =20 Also a make.conf switch to disable it from the module could make sense. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1339918.rAV2WeRTfe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBFl8v6XyyEoT62BG0RAkrqAJ4zGGJHLLQSKqrdUTcgPYv8zxgHDQCdGwtG J9ZR5vZFK2XeEYz9eRfWEXg= =ve8t -----END PGP SIGNATURE----- --nextPart1339918.rAV2WeRTfe--