From ab277998bd4cbe6b970cd8981bea4900b20fafde Mon Sep 17 00:00:00 2001 From: Mike Hibler Date: Thu, 26 Jun 2008 17:52:23 +0000 Subject: [PATCH] Last minute tweaks --- doc/cisco-voodoo.txt | 4 ++-- doc/create-generic-image.txt | 2 +- doc/customize-image.txt | 15 ++++++++++----- doc/customize-mfs.txt | 10 +++++++--- 4 files changed, 20 insertions(+), 11 deletions(-) diff --git a/doc/cisco-voodoo.txt b/doc/cisco-voodoo.txt index d827d7535..372e281fb 100644 --- a/doc/cisco-voodoo.txt +++ b/doc/cisco-voodoo.txt @@ -199,8 +199,8 @@ ID Name Members of VLAN To stop cloning: Console> (enable) set span disable - NOTE: as of 10/11/07 bge0 on oboss has been taken over. You could use - 2/1, which is 100Mb fxp0 on oboss. + NOTE: as of 10/11/07 bge0 on oboss has been taken over and oboss is now + nslow.flux.utah.edu. You can use 2/17, which is 100Mb fxp0 on nslow. NOTE: as of 12/14/06 we have bge0 on oboss attached to the control net switch (cisco2) so that it can be used for spanning. Its cisco2 port is 9/13, use that for . Also note that you will have to have diff --git a/doc/create-generic-image.txt b/doc/create-generic-image.txt index b7ade0d34..eb10ee006 100644 --- a/doc/create-generic-image.txt +++ b/doc/create-generic-image.txt @@ -113,7 +113,7 @@ How to make a generic image from a Utah one: 3h. Reboot into the admin MFS 4. Minor admin stuff. - Once in the admin MFS, I run fsck on the filesystesm just to be safe: + Once in the admin MFS, I run fsck on the filesystems just to be safe: fsck /dev/ad0s1[aef] e2fsck -f -y /dev/ad0s2 diff --git a/doc/customize-image.txt b/doc/customize-image.txt index b7502b54f..8fe3c3153 100644 --- a/doc/customize-image.txt +++ b/doc/customize-image.txt @@ -11,15 +11,20 @@ provided by Utah. The basic procedure is: - save customized image We will provide you with a generic disk image tarball. This tarball will -include a multi-OS "full disk" image and one or more auxilliary "single +include a multi-OS "full disk" image and one or more auxiliary "single partition" images. The combo image is one which has both a FreeBSD partition and a Linux partition. You will need to customize both. By convention FreeBSD is in DOS partition #1 and Linux in DOS partition #2. First you need to decide which image to use. The combo image choices are: - FBSD62+FC6-GENERIC.ndz # FreeBSD6.2 + Fedora6 - generic-image.tar - FBSD410+RHL90-GENERIC.ndz # FreeBSD4.10 + RedHat9 - generic-image-old.tar + * FBSD62+FC6-GENERIC.ndz + Includes FreeBSD 6.2 and Fedora 6. + Download http://www.emulab.net/downloads/generic-image.tar for this. + + * FBSD410+RHL90-GENERIC.ndz + Includes FreeBSD 4.10 and RedHat 9. + Download http://www.emulab.net/downloads/generic-image-old.tar for this. Generally, you will want to use the former as your default image that disks are loaded with. The reason the second image is included at all is that it @@ -27,7 +32,7 @@ must be used for "virtual node" support, which right now is only available in our modified FreeBSD 4.10 kernel. Unfortunately, the 4.10 kernel, being more than 5 years old, doesn't run on all modern hardware. So you may be stuck without vnodes for awhile if your hardware is in the unsupported -catagory. +category. You will need to have the Emulab network-booted, memory-filesystem-based, FreeBSD systems (hereafter known as the MFSes). If you have not done this @@ -418,7 +423,7 @@ I. Dealing with SCSI disks (or RAID) and unrecognized hardware. * For FreeBSD, we have five different FreeBSD 4.10 kernels that are used for various purposes. All of them are based on the GENERIC configuration. If the default kernel ("/kernel" aka "/kernel.100HZ") does not boot on your - machine or your disk or ethernet interfaces are not recognized, you will + machine or your disk or Ethernet interfaces are not recognized, you will have to move to the FreeBSD 6.2 based solution above. * For Linux, it is even more of a PITA. We currently don't even have a diff --git a/doc/customize-mfs.txt b/doc/customize-mfs.txt index c34ea8b49..37943b7b1 100644 --- a/doc/customize-mfs.txt +++ b/doc/customize-mfs.txt @@ -2,7 +2,6 @@ These are the files/directories needed for PXE booting. - 2. CONTENTS: README @@ -47,7 +46,12 @@ do that now, I'll wait... ...ok. First, you have to choose between using FreeBSD 4.7 or FreeBSD 6.2 MFSes. You almost certainly want to use the 6.2 versions since 6.2 supports -more hardware. If you have any problems with those, then try the 4.7 versions. +more hardware. In fact, the "6.2 version" actually has a 6.3-STABLE kernel +built on 6/26/2008, so it is the lastest available for the 6.x series. + +If you have any problem with the 6.2 versions *and* you have older hardware, +then try the 4.7 versions. If the 6.2 version don't work because it appears +that your hardware is not supported, then contact Utah for more help. In summary, I recommend: pxeboot62/pxeboot.emu-{sio,vga} (pick one and rename to "pxeboot.emu") @@ -70,4 +74,4 @@ loader to drop into interactive mode. Make sure you replace the loader.conf file in the three subdirectories with the -null version as well. [ This file is a copy of doc/customize-mfs.txt in the Emulab source tree. ] -[ Last updated 03/02/07 ] +[ Last updated 06/26/08 ] -- GitLab