"Dmitry A. Bondareff" wrote:
>
> How to minimize traffic for upgrading remote host ?
The best upgrade process I have come up with so far for
remote hosts (or rach mount systems withoout CDROM drives
in them) is to:
1) Create a new directory on the CDROM before you
burn it called "upgrade".
2) Put the CDROM copy of /stand/sysinstall in that
directory as "sysinstall". This is a lot harder
than it looks.
3) Put copies of the /dev/MAKEDEV and /dev/MAKEDEV.local
scripts in the directory, too (ignore this step for
5.x or other mandatory use of devfs).
Then:
A) Mount the CDROM on a system and export it via NFS.
B) NFS mount the exported CDROM onto the target system.
C) Run "sysinstall" off the mounted CDROM (this only
works because you manually copied it into the
magic directory).
D) Do the upgrade; tell it to use "local media", and
then point it to the NFS mounted directory.
E) Manually copy the MAKEDEV and MAKEDEV.local to the
target system, prior to the "reboot".
F) disklabel -B to install the new bootblocks (if any);
this is reallly important if you have a FreeBSD that
was in flux for the switchover debacle.
G) Install the source package to overwrite /usr/src, if
you care. Note that this is an overwrite, so if you
have local changes, move the directory out of the way,
or back them up.
H) cd /dev; sh MAKEDEV all
Other than the /etc/pam.conf crap because of the gratuitous
ssh changes, where you might have to manually add lines to
it so that you can ssh back in, this pretty much covers the
upgrade process.
This should probably be automated as part of sysinstall. I
have no idea why doing it without booting to the new version
doesn't do the MAKEDEV stuff correctly.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
