Re: Streamlining FreeBSD installations across many machines
Nik Clayton wrote: > > On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote: > > I'm wondering if there might not be a way to streamline this install > > process, such that a boot floopy and script could be created to take a > > minimum amount of information, and then "do the right thing" as for the > > install. Things like putting in the packet filters, the kernel, IP > > config, etc. > > See sysinstall(8); you can script sysinstall. See > > src/release/sysinstall/install.cfg I built a pico floppy under 3.2 that uses sysinstall to do most of this. a search of my name in the pico mailing list should turn it up. Pete -- Peter McKenna U S WEST !NTERPRISE [EMAIL PROTECTED] http://www.interprise.com/ Main 612-664-4000 FAX 612-664-4770 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD installations across many machines
On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote: > I'm wondering if there might not be a way to streamline this install > process, such that a boot floopy and script could be created to take a > minimum amount of information, and then "do the right thing" as for the > install. Things like putting in the packet filters, the kernel, IP > config, etc. See sysinstall(8); you can script sysinstall. See src/release/sysinstall/install.cfg for an example. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD installations across many machines
> In article <[EMAIL PROTECTED]>, Rodney W. Grimes > <[EMAIL PROTECTED]> wrote: > > > A much faster way to do this is to just dd the first few megabytes > > of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use > > dump | restore to populate the disk. > > Do you run newfs on the receiving disk before the dump|restore? It > seems like if you didn't then the free block bitmaps in the cylinder > groups would contain garbage. Ooopsss.. left a step out... yes.. we newfs the disk after the dd operations. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD installations across many machines
In article <[EMAIL PROTECTED]>, Rodney W. Grimes <[EMAIL PROTECTED]> wrote: > A much faster way to do this is to just dd the first few megabytes > of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use > dump | restore to populate the disk. Do you run newfs on the receiving disk before the dump|restore? It seems like if you didn't then the free block bitmaps in the cylinder groups would contain garbage. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD installations across many machines
> Perhaps this would be of interest in CURRENT issues: > > > We have several servers that we plan on deploying across the US. Their > purpose in life is network status and monitoring. The hardware profiles > are exactly the same... > > Currently, we're using DD to mirror a disk image onto a new installation, > and them nanually tweaking all the necessary configurations. It's > tedious, and is going to get hellish with the amount we plan on deploying. A much faster way to do this is to just dd the first few megabytes of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use dump | restore to populate the disk. (We actually have 3.x and 4.x recent build filesystems that are built weekly on a master loading machine just for this purpose.) We mass produce system disk this way and it is much faster than a whole disk image operation especially when dealing with drives much larger than 2G bytes. > I'm wondering if there might not be a way to streamline this install > process, such that a boot floopy and script could be created to take a > minimum amount of information, and then "do the right thing" as for the > install. Things like putting in the packet filters, the kernel, IP > config, etc. > > Surely someone has done this before...? We do it on a weekly basis, 4 to 32 disks at a time... > Any pointers would be greatly appreciated. Hope this gives you some ideas... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Streamlining FreeBSD installations across many machines
In message <[EMAIL PROTECTED]>, Forrest Aldrich writes : >Perhaps this would be of interest in CURRENT issues: > > >We have several servers that we plan on deploying across the US. Their >purpose in life is network status and monitoring. The hardware profiles >are exactly the same... > >Currently, we're using DD to mirror a disk image onto a new installation, >and them nanually tweaking all the necessary configurations. It's >tedious, and is going to get hellish with the amount we plan on deploying. There was actually a good deal of interest in this at FreeBSDcon'99, and I belive we managed to bully^H^H^H^H^H^Hpersuade Wes Peters to take an active role in coordinating efforts in this area ? -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Streamlining FreeBSD installations across many machines
Perhaps this would be of interest in CURRENT issues: We have several servers that we plan on deploying across the US. Their purpose in life is network status and monitoring. The hardware profiles are exactly the same... Currently, we're using DD to mirror a disk image onto a new installation, and them nanually tweaking all the necessary configurations. It's tedious, and is going to get hellish with the amount we plan on deploying. I'm wondering if there might not be a way to streamline this install process, such that a boot floopy and script could be created to take a minimum amount of information, and then "do the right thing" as for the install. Things like putting in the packet filters, the kernel, IP config, etc. Surely someone has done this before...? Any pointers would be greatly appreciated. Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
