Commit 23b8bdb1 authored by Leigh B. Stoller's avatar Leigh B. Stoller
Browse files

Add CVSUP discussion. Add route commands to the part about bringing up

the network to copy the image off.
parent a0b25ab9
......@@ -18,6 +18,11 @@ messages about installing ports).
A. Linux:
0. Update /etc/rc.d/testbed/supfile from the source (tmcd/linux)
directory. With each new image, the sup release needs to be bumped
and the checkouts file removed. See below for a more detailed
explaination of this.
1. Update whatever files necessary.
2. Reboot to single-user. To do this, reboot and when you get the
......@@ -70,14 +75,21 @@ A. Linux:
B. FreeBSD:
0. Update /etc/testbed/supfile from the source (tmcd/freebsd) directory.
With each new image, the sup release needs to be bumped and the
checkouts file removed. See below for a more detailed explaination of
this.
1. Update whatever files necessary.
2. Reboot to single-user. To do this, reboot and when you get the
FreeBSD boot prompt:
Hit [Enter] to boot immediately, or any other key for command prompt.
>> FreeBSD/i386 BOOT
Default: 0:ad(0,a)kernel
boot:
Hit the space bar and type "boot -s".
Type "kernel -s" at the boot prompt and type return.
3. Mount the root filesystem RW:
mount -u /
......@@ -85,7 +97,10 @@ B. FreeBSD:
4. Remove /etc/ssh/ssh_host_key and /etc/ssh/ssh_host_dsa_key. This will
cause /etc/rc.network to create new host keys when the machine reboots
multiuser. So make sure you don't go multiuser before you cut the image.
multiuser. So make sure you don't go multiuser before you cut the
image.
rm /etc/ssh/ssh_host_key /etc/ssh/ssh_host_dsa_key
5. Zero out as much of the filesystem free space as possible. I do this by
creating a big, zero-filled file in each filesystem and then removing it:
......@@ -119,7 +134,10 @@ C. Cutting the image:
1. Boot up FreeBSD in single-user (you may already be there.
2. Fire up the control net:
ifconfig fxp4 inet 155.99.214.xxx netmask 0xffffff00
ifconfig fxp4 inet 155.101.132.xxx netmask 0xfffffc00
route add -net 155.101.132 -interface fxp4
route add default 155.101.132.1
3. DD a disk image over to plastic. Do this however you want but I prefer
good ole rsh. I temporarily stick the machine in question into
......@@ -142,3 +160,49 @@ C. Cutting the image:
put the little magic header at the beginning).
CVSUP:
Each time we cut a new image, we need to bump the sup release since its
entirely possible that different versions of the image will be running on
different nodes. Older images will still need the sup release that they
were built with so that they continue to get updates, while new images
need a different (newer) sup release. Fortunately, this is pretty easy to
do.
* Before you cut a new image, make sure that both freebsd and linux are
booted to multiuser mode so that they pick up all the updates in their
sup release.
* Bump the sup release in the supfile. This file is CVS'ed in the tmcd
directory as linux/supfile and freebsd/supfile. The section of this
file that matters is:
release=20000221
Change this to the current date and install the new supfile. On freebsd
this is /etc/testbed/supfile. On linux its /etc/rc.d/testbed/supfile.
* Unfortunately, cvsup on the client side has a minor bug in how it
handles a new release. The work around is to remove the "checkouts"
file that tells sup which files it has picked up:
Linux: rm /etc/rc.d/testbed/sup/sup/RHL62-STD/checkouts
Freebsd: rm /etc/testbed/sup/sup/FBSD40-STD/checkouts
* Now for the server side (before you boot the new image!). You need to
create the new "release" that is referenced in the supfile you modified
above. To do this, go to
paper:/usr/testbed/sup/sup/{FBSD40-STD,RHL62-STD} and edit the
"releases" file in each. You need to *add* a line like this:
20000221 list=list prefix=/usr/testbed/sup/sup/FBSD40-STD/root-20000221 norcs
where 20000221 is the name of the new release you put in the supfile
above. You also need to create the new root directory (the prefix
argument):
mkdir /usr/testbed/sup/sup/FBSD40-STD/root-20000221
Do this for both the freebsd and linux sup subdirs.
* Thats it! Easy as cake.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment