Date: Tue, 13 Aug 2002 13:40:50 -0400 From: Scott Lambert <lambert@lambertfam.org> To: FreeBSD-stable@freebsd.org Subject: Re: Need instructions: build kernel on one machine; install on another Message-ID: <20020813174050.GA5380@laptop.lambertfam.org> In-Reply-To: <E18F2DF2-AEC9-11D6-92E2-000502D7A780@brandeis.edu> References: <3D5915BC.30609@rsm.ru> <E18F2DF2-AEC9-11D6-92E2-000502D7A780@brandeis.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 13, 2002 at 10:35:14AM -0400, Chen Xu wrote:
>
> On Tuesday, August 13, 2002, at 10:20 AM, Dmitry Agafonov wrote:
> >
> >We have compiled kernels (make buildkernel KERNCONF=LALALA) on one machine,
> > and then after nfs-mounting /usr/src and /usr/obj to target machine -
> >make installkernel KERNCONF=LALALA
> >This works fine and is very good for poor-cpu/ram machines :)
> >
> >The question still remains - can one build a number of kernels and
> >then install them? This will save some time on updating a number
> >of machines: 3 steps (cvsup'ing and world and kernel(s) building)
> >may be fully automated.
>
> I don't see why you cann't do it for many machines. One can just
> make buildkernel KERNCONF=LALALA
> ...
> make buildkernel KERNCONF=ZAZAZA
>
> then nfs mount to each machine to installkernel. Only problem is
> that you have to do `installkernel KERNCONF=$cornel_config`
> on each target boxes, which makes fully auto a problem. \
From my buildeverything script:
THIS_HOSTS_KERNEL=`uname -a | sed 's|.*/sys/||' | awk '{print $1}'`
make installkernel KERNCONF=$THIS_HOSTS_KERNEL
There is probably a less expensive way to gather the installed kernel's
config file name, but I just threw this together and ran it.
--
Scott Lambert KC5MLE Unix SysAdmin
lambert@lambertfam.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020813174050.GA5380>