Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
emulab-stable
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
emulab
emulab-stable
Commits
ab277998
Commit
ab277998
authored
Jun 26, 2008
by
Mike Hibler
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Last minute tweaks
parent
9d2aef7d
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
20 additions
and
11 deletions
+20
-11
doc/cisco-voodoo.txt
doc/cisco-voodoo.txt
+2
-2
doc/create-generic-image.txt
doc/create-generic-image.txt
+1
-1
doc/customize-image.txt
doc/customize-image.txt
+10
-5
doc/customize-mfs.txt
doc/customize-mfs.txt
+7
-3
No files found.
doc/cisco-voodoo.txt
View file @
ab277998
...
...
@@ -199,8 +199,8 @@ ID Name Members of VLAN
To stop cloning:
Console> (enable) set span disable <monitor>
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 <monitor>. Also note that you will have to have
...
...
doc/create-generic-image.txt
View file @
ab277998
...
...
@@ -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 filesyste
sm
just to be safe:
Once in the admin MFS, I run fsck on the filesyste
ms
just to be safe:
fsck /dev/ad0s1[aef]
e2fsck -f -y /dev/ad0s2
...
...
doc/customize-image.txt
View file @
ab277998
...
...
@@ -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 auxil
l
iary "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
cat
a
gory.
cat
e
gory.
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
e
thernet interfaces are not recognized, you will
machine or your disk or
E
thernet 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
...
...
doc/customize-mfs.txt
View file @
ab277998
...
...
@@ -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 0
3/02/07
]
[ Last updated 0
6/26/08
]
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment