| From | Sent On | Attachments |
|---|---|---|
| Kevin Oberman | Aug 8, 2008 1:04 pm | .Other |
| Mike Tancsa | Aug 8, 2008 1:33 pm | |
| Erik Trulsson | Aug 8, 2008 1:40 pm | |
| Kevin Oberman | Aug 8, 2008 2:04 pm |
| Subject: | Re: Unable to build kernel | |
|---|---|---|
| From: | Kevin Oberman (ober...@es.net) | |
| Date: | Aug 8, 2008 2:04:40 pm | |
| List: | org.freebsd.freebsd-stable | |
Date: Fri, 08 Aug 2008 16:34:01 -0400 From: Mike Tancsa <mi...@sentex.net>
At 04:04 PM 8/8/2008, Kevin Oberman wrote:
Today I was unable to build a new kernel for 7-Stable. It dies when linking the kernel, seemingly because of not finding the definitions for some nfs stuff. I don't use nfs and always exclude both server and client from my kernel. (Long config attached, if the list does not strip
nooptions NFSCLIENT # Network Filesystem Client nooptions NFSSERVER # Network Filesystem Server nooptions NFS_ROOT # NFS usable as root device, requires
Can you build generic on its own ? What if you add to your config nooptions NFSLOCKD
which recently got added to GENERIC.
Thanks, Mike (and Erik who also pointed this out) for the answer. Kernel linked just fine now that I have removed the NFS LOCKD. I should have looked at CVS for GENERIC changes. I did check UPDATING, but there was nothing there.
-- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751






.Other