Customized Remote Install
odhiambo at gmail.com
Wed Apr 22 08:18:56 UTC 2009
On Tue, Apr 21, 2009 at 11:42 PM, Scott Seekamp <sseekamp at risei.net> wrote:
> I've done a lot of searching and maybe this capability doesn't exist, but I
> am looking to do this:
> I am at my company's HQ, we have a new field office that I am setting up a
> FreeBSD server. The technical knowledge at the site windows only, so I
> basically have someone I can have put a CD in a drive and power a machine
> My problem is that the default install of FreeBSD has password
> authentication turned off, and root SSH disabled. Being a small office, they
> don't have a IP KVM or some way for me to get to the box to configure it.
> 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 know I can do the scripted sysinstall, but from what I could find I would
> need a floppy or additional CD to put the answer file on.
> I'm open to other options if someone has gone down this road before!
All you need is that the guy at the field office knows something about PC
hardware and can type a few commands on any command line. Then there should
be a phone.
FreeBSD is not as silly as Linux when you move a disk from one box to
another. If it is a "server" box (which requires no GUI) then the only
changes you are likely to make are on the network configurations (ifconfig_*
in rc.conf and resolv.conf) and the rest will remain pretty much the same.
What I have done is that I have a prototype, which is a SATA disk. I am
pretty much okay of the next machine I want to install has a SATA disk, but
I am also not worried if it has PATA disk as I know I will only need a
change in /etc/fstab.
So what I normally do is this:
Attach my prototype disk as master on the machine to install, while slaving
the disk that the machine had.
I enter sysinstall and disklable/newfs the slave disk. I make the disk
bootable, enable softupdates on it and I normally create the root mount
point (/). Once done, I change the mount point again to, say, /newdisk, so
the slave disk is now mounted on /newdisk.
dump L0af - / | (cd /newdisk/; restore -rf -) # BTW, I have the habit of
creating only / and swap!
So now I have a duplicate system on the slave disk.
cd /newdisk; ee etc/rc.conf ; ee etc/fstab; ee etc/resol.conf
Here I change the ifconfig_ line for the network device (as seen from
dmesg.boot), ensure that fstab refers to the correct device names and voila!
I save, shutdown, remove my prototype disk, restore the slave disk to master
position and reboot and I have a system identical to the proto. Once
connected to a live network, I can ssh to it from anywhere I want using my
own account and the su to root if needed, though I always prefer sudo.
Now, if only you can follow my way, you only need to ship your prototype
disk to the field office and get the windows lunnie to do the disk
connections, type the commands, etc and you have a server running at the
field office in no time!
Of course tell him to pack your prototype disk safely and return it to you.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"Clothes make the man. Naked people have little or no influence on
-- Mark Twain
More information about the freebsd-questions