Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
emulab
emulab-devel
Commits
86c458b3
Commit
86c458b3
authored
Oct 24, 2003
by
Mike Hibler
Browse files
More notes I added at some point
parent
c6bc9b95
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/uk-image.txt
View file @
86c458b3
...
...
@@ -56,16 +56,20 @@ B. While running Linux (single user):
Copy the correct file over from /usr/share/zoneinfo
* /etc/ssh/ssh_host*
Generate new host keys. Actually, copy from an existing image.
Generate new host keys. Actually, copy from an existing image if
available (i.e., we use a single host key across all images and OSes
within a testbed).
* /etc/testbed/shadow
Change the root password, this file will get installed by prepare.
* /etc/testbed/{client,emulab}.pem
Generate a new one. From Leigh:
Just need to cd into the ssl directory and do a gmake
(on their boss of course!) then a gmake boss-installX.
The images need emulab.pem and client.pem from that directory.
Generate new ones. This needs to be done on the site's boss node.
Go into the build tree "ssl" subdirectory and edit the *.cnf.in files
to update the "[ req_distinguished_name ]" section with the appropriate
country, state, city, etc. Then do a "gmake boss-installX" which generates
the certs and installs the server-side. Grab the emulab.pem and client.pem
from that directory to put in the images.
* Remount root filesystem read-only (IMPORTANT!)
cd /
...
...
Write
Preview
Supports
Markdown
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