Re: Can't link kernel after recent libalias commits?
- From: David Wolfskill <david@xxxxxxxxxxxxxx>
- Date: Sat, 30 Dec 2006 13:43:21 -0800
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@xxxxxxxxxxxxxxxxxxxxx:/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@xxxxxxxxxxxxxxxxxxxxx:/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@xxxxxxxxxxxxxx
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:
pgpzgF0EqIAfn.pgp
Description: PGP signature
- Follow-Ups:
- Re: Can't link kernel after recent libalias commits?
- From: Paolo Pisati
- Re: Can't link kernel after recent libalias commits?
- References:
- Can't link kernel after recent libalias commits?
- From: David Wolfskill
- Re: Can't link kernel after recent libalias commits?
- From: Paolo Pisati
- Can't link kernel after recent libalias commits?
- Prev by Date: Re: Can't link kernel after recent libalias commits?
- Next by Date: Re: Can't link kernel after recent libalias commits?
- Previous by thread: Re: Can't link kernel after recent libalias commits?
- Next by thread: Re: Can't link kernel after recent libalias commits?
- Index(es):
Relevant Pages
|
|