Customized Remote Install

[Polytropon]

On Tue, 21 Apr 2009 18:47:11 -0400, Jerry McAllister <jerrymc at msu.edu> wrote:
> On Tue, Apr 21, 2009 at 11:51:32PM +0200, Polytropon wrote:
> 
> > On Tue, 21 Apr 2009 14:42:32 -0600, Scott Seekamp <sseekamp at risei.net> wrote:
> > > My hope was that I could make an automated install CD/DVD that  
> > > configured all the options I want AND change some base config files so  
> > > I can actually get to the box (or install an SSH key).
> > > [...]
> > > I'm open to other options if someone has gone down this road before!
> > 
> > I'd like to advertize a method that I think is very comfortable
> > in such a setting. It's worth mentioning that this method
> > usually requires (a) modern enough PCs or (b) you to know what
> > is the hardware profile of the PC.
> > 
> > The method works as follows:
> > 
> > First create a FreeBSD as you want it to be on the clients.
> > Install and configure everything as you intend.
> > 
> > Then dump the created partitions onto a CD or DVD and create
> > a simple script that:
> > 	1. initializes the client's hard disk
> > 	2. slices the disk and newfses the partitions
> > 	3. dumps the partition images onto the disks
> > 	4. reboots the machine into operating state.
> > 
> > After this, you should be able to SSH into the client and
> > change settings that need to be changed.
> 
> This works very well. 

I just realize that I missed something: Better than dd, I think
dump & restore are the preferred tools to create the partition
images. When you're done on your "template system", umount its
partitions (in SUM) and use dump to dump them into files. These
files go to the installation DVD and are later on restored onto
the (empty) partitions using the restore command. This will
preserve any permissions and other file properties.



>  I have done essentially the same many times.
> The one thing missing is that you need to have something to set the
> network information -- hostname, IP address, gateway, netmask
> and name-server.    These will be different for each machine.
> So, your script will have to accomodate this - read console
> input for these items and plug them in to the proper places
> before rebooting.

That's correct. I always used a kind of "CHANGE THIS!" items
to do so, or, if none are given, they are automatically created
so the system boots up and runs, but then again, require service
afterwards. This can be made work this way: When the "incomplete"
system is up and running, it mails the distant administrator (or
contacts him in another way) requiring him to finish the settings.
But I think it's the best solution to propmt for these
specific settings at "installation time" (read, when the
restore job is done, the partitions can be mounted -o rw and
the files neccessary to be changed can be created or modified).

The "installation" will then continue and finish.

Of course, the dump & restore method lacks a lot of bling,
blitzen, eye candy, bells and whistles, but it honours the
abstinence to such stuff with speed and easyness of use. But
it's still neccessary to read (and understand) and press a
few keys on the keyboard. :-)



-- 
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...