compiling kernel for another machine then installing - how?

Paul Jansen vlaero at
Mon Apr 21 21:03:37 PDT 2003

Thanks Mike.

replaced the kernel as you described and it works
I'm hoping someone can describe how I can set up NFS 
- and then mount remotely - in such a way so that I
can do an install if modules are required that aren't
on the remote system.  I need some clarification as to
how to set up the '/etc/exports' file appropriately. 
just to confirm I'm using freebsd 4.8 and teh remote
systems will be freebsd 4.8 also.  I'm wanting to use
the 'new' kernel compilation method.

Thanks in advance for any clarification on this.

 --- Mike Meyer <mwm at> wrote: > In
<20030419053455.63747.qmail at>,
> Paul Jansen <vlaero at> typed:
> > I've also looked in the handbook but it doesn't
> > discuss this issue.
> > Basically I've got a slow machine and a much
> faster
> > machine.  I wanted to compile the kernel for the
> > slower machine on the faster one to save a lot of
> > time.  I've followed the directions in the
> handbook to
> > compile a kernel as normal but I'm not sure
> exactly
> > what I need to copy and where.  Is it easier to
> > mount to do this?  I tried and ran into some
> pathing
> > issues.
> > Can anyone help?
> What you need to copy depends on which version of
> FreeBSD you are
> running. With 4.x, you need to get /kernel and the
> contents of
> /modules into place. With 5-whatever, you just need
> the contents of
> /boot/kernel.
> For 4.x, if you are just building a custom kernel
> for a system that is
> already running from the sources you started with,
> you can copy either
> /usr/src/sys/compile/CONFIGNAME/kernel (traditional
> kernel build
> methodology) or
> /usr/obj/usr/src/sys/CONFIGNAME/kernel (make
> buildkernele methodology) over, and use the /modules
> that is already
> installed.
> If you need to install /modules, it's probably
> easiest to NFS-mount
> the /usr/src and /usr/obj on the target system and
> do a "make
> install". The trick here is that you have to mount
> /usr/src with the
> same path name as it has on the fast system, as that
> path name is used
> in the object tree. So if it's really /usr/src on
> your fast system,
> mount it as /usr/src on the slow one. If it's really
> in
> /my/scratch/disk/freebsd/src and /usr/src is a
> symlink to that, you
> have to mount it as /my/scratch/disk/freebsd/src on
> the slow system,
> and create the symlink if you want. /usr/obj doesn't
> have that
> requirement, but I do it the same way anyway.
> The only way I know of to do this for 5.0 is the
> NFS-mount and
> install, but I haven't really gotten into 5.0.
> 	<mike
> -- 
> Mike Meyer <mwm at>	
> Independent Network/Unix/Perforce consultant, email
> for more information. - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.

More information about the freebsd-questions mailing list