Date: Thu, 28 Feb 2002 00:11:02 -0800 From: Danny Howard <dannyman@toldme.com> To: "Thomas P. Holmes [ Systems ]" <tholmes@thebiz.net> Cc: Koroush Saraf <koroush.saraf@lmco.com>, freebsd-cluster@freebsd.org Subject: Re: Mass Upgrade and Maintenance questions Message-ID: <20020228001102.K3896@pianosa.catch22.org> In-Reply-To: <Pine.BSF.4.21.0202272233350.11349-100000@staff.noc.thebiz.net>; from tholmes@thebiz.net on Wed, Feb 27, 2002 at 10:45:00PM -0500 References: <20020227095221.F3896@pianosa.catch22.org> <Pine.BSF.4.21.0202272233350.11349-100000@staff.noc.thebiz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 27, 2002 at 10:45:00PM -0500, Thomas P. Holmes [ Systems ] wrote: > > NFS? I'd mount 4.5-RELEASE /usr/src on all these machines, make > > buildworld and buildkernel, then write a script that goes to each in > > turn installs both. Maybe put the procedure in an install.sh and do > > like this: > > Are you saying to buildworld on each seperate machine with having just > the src code nfs mounted? Or build on 1 machine and then installworld > on each machine? If it is the latter, I've had problems the 2 times > I've tried that. It could be differences in the machines I guess. It > always seems to bomb with something like "command install not found" > halfway through. Sh!t happens. Measure twice, cut once. I'd have a couple of boxes reserved for guinea pig testing, myself. I've found that installworld from multiple machines over NFS works, but there's danger any time you're upgrading the OS. > In our production work environment we have a set of master servers and > everything else are diskless clients of the masterservers. Services > are "sandboxed" so that too makes life easier :) Yes, network booting is da bomb, and that is how I'd prefer to maintain 34 workstations. :) -danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-cluster" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020228001102.K3896>