Date: Fri, 19 Feb 2010 11:14:58 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: Kostik Belousov <kostikbel@gmail.com> Cc: marius@freebsd.org, Boris Kochergin <spawk@acm.poly.edu>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Can't load NFS server module with a custom 8.0 kernel Message-ID: <Pine.GSO.4.63.1002191112060.24826@muncher.cs.uoguelph.ca> In-Reply-To: <20100219152902.GZ50403@deviant.kiev.zoral.com.ua> References: <4B7D74A7.6010006@acm.poly.edu> <Pine.GSO.4.63.1002181455240.22960@muncher.cs.uoguelph.ca> <4B7D9C5C.1090909@acm.poly.edu> <20100218220714.GU50403@deviant.kiev.zoral.com.ua> <Pine.GSO.4.63.1002191018340.18444@muncher.cs.uoguelph.ca> <20100219152902.GZ50403@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Feb 2010, Kostik Belousov wrote: > I do not introduce new module, I added symbols from nfs_common to > nfscommon, indending to remove sys/modules/nfs_common from src, since it > is not attached to the build even without the patch. It seems that there > is no name conflicts between newnfs symbols from this combined module > and old nfs server and client. > > I did not checked possible name conflicts between this nfscommon > and fs/nfs*, that is what I mean by "not looked into ...". > Okay, I see that now. (I'm a bit slow:-) I don't think there will be any name conflicts in nfscommon, since you can build a kernel with both NFSSERVER and NFSD and they would show up multiply defined otherwise. I think that sys/nfsclient also has to be changed to use nfscommon and checked? rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1002191112060.24826>