I can validate that this works - one way you can automate this is to
put the KERNCONF definition in /etc/make.conf. We used this to bulk
update a farm of SMP and uniprocessor systems, the SMP kernel was
different for us.
One thing that can bite you is _other_ things in /etc/make.conf - like
if you use NO_SENDMAIL=yes in the base system - if /etc/make.conf
doesn't have the same options in the install systems the install will
fail. Likewise for kerberos. I don't know what can be done about CPU
variants unless you have a relatively homogenous setup.
What worked best for us was to keep /etc/make.conf as short as
possible, even if all of the systems ended up getting the games
directory installed...
- Mike H.
Date: Tue, 13 Aug 2002 10:35:14 -0400
Cc: [EMAIL PROTECTED]
From: Chen Xu <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
X-Loop: FreeBSD.ORG
X-Spam-Status: No, hits=-2.3 required=5.0
tests=IN_REP_TO,DOUBLE_CAPSWORD
version=2.31
X-Spam-Level:
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. \
Chen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
