Date: Sat, 30 Dec 2006 13:43:21 -0800 From: David Wolfskill <david@catwhisker.org> To: Paolo Pisati <piso@freebsd.org> Cc: current@freebsd.org Subject: Re: Can't link kernel after recent libalias commits? Message-ID: <20061230214321.GG64111@bunrab.catwhisker.org> In-Reply-To: <20061230205153.GB5902@tin.it> References: <20061230195219.GD64111@bunrab.catwhisker.org> <20061230205153.GB5902@tin.it>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, Dec 30, 2006 at 09:51:53PM +0100, Paolo Pisati wrote: > On Sat, Dec 30, 2006 at 11:52:19AM -0800, David Wolfskill wrote: > > Running: > > g1-18(7.0-C)[1] uname -a > > FreeBSD g1-18.catwhisker.org. 7.0-CURRENT FreeBSD 7.0-CURRENT #279: Fri Dec 29 09:33:05 PST 2006 root@g1-18.catwhisker.org.:/common/S4/obj/usr/src/sys/LAPTOP_30W i386 > > g1-18(7.0-C)[2] > > i guess you have IPFIREWALL in you kernel config, but > no LIBALIAS? Adding "option LIBALIAS" to the kernel config fixed my problem: g1-18(7.0-C)[1] uname -a FreeBSD g1-18.catwhisker.org. 7.0-CURRENT FreeBSD 7.0-CURRENT #281: Sat Dec 30 13:11:47 PST 2006 root@g1-18.catwhisker.org.:/common/S4/obj/usr/src/sys/LAPTOP_30W i386 g1-18(7.0-C)[2] Note that this was for a kernel that uses ipfw, but not natd (ref. src/sys/conf/NOTES). Peace, david -- David H. Wolfskill david@catwhisker.org Believe SORBS at your own risk: 63.193.123.122 has been static since Aug 1999. See http://www.catwhisker.org/~david/publickey.gpg for my public key. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkWW3XcACgkQmprOCmdXAD3a6wCfRnHjCKghQj4+QuegBRq7pZJI WhIAmwRAg+Tznha/0LTsDCxB0lp1FL08 =LpWD -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061230214321.GG64111>