Date: Fri, 17 Mar 2000 07:51:28 -0500 From: Forrest Aldrich <forrie@forrie.com> To: freebsd-current@freebsd.org Subject: Streamlining FreeBSD Installations Message-ID: <4.3.1.2.20000317074445.00b60d90@216.67.12.69>
next in thread | raw e-mail | index | archive | help
There was mentioned that someone was "appointed" (perhaps unwillingly :) to look into this one... who? I was also curious about what people do to keep a fleet of FreeBSD machines up-to-date with CVSup and buildworld. I can't imagine manually going to more than 100 machines and doing the same thing manually... how time consuming. To summarize again, we are deploying status monitoring machines into POPs, across the US. Those machines are identical in terms of hardware, et al. We were hoping to find a means by which to streamline the installation process, such that we could create (say) custom boot floppies where you'd input minimum information (IP address, hostname, domain, etc.) and it would then go off and perform the installation (from fdisk, newfs... to editing packet filters appropriately, which make require a "template" of sorts). The idea of doing all of this manually makes carpal tunnel syndrome sound like a vacation, compared to what condition one might be in afterward :) Anyone got some ingenious hack to perform this? Someone made a comment about one procedure we were doing which involved using "dd" to mirror a base installation onto another disk. As far as I know, there haven't been any gotchyas with that method. The disks are WD "pluggable" drives. So, we have a master machine that we simply do our mirror from. It's hacky as hell. Someone mentioned that sysinstall could be scripted... is this the way to go, then? TIA... _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.1.2.20000317074445.00b60d90>