“UbuntuHelp:Installation/LocalNet”的版本间的差异

2007年11月22日 (四) 13:10的版本

文章出处:

https://help.ubuntu.com/community/Installation/LocalNet

点击翻译:

English

请不要直接编辑翻译本页，本页将定期与来源同步。

1 Feisty Desktop Edition Install
- 1.1 Set up the servers
- 1.2 Net-boot your client machine.
  - 1.2.1 Technical Note: About Casper
2 Basic: Hands-On Interactive Network Server Edition Install
3 Advanced: Hands-Off, Preseeded Network Server Install
4 Advanced: Network install using apt-mirror
5 Related Links

Feisty Desktop Edition Install

This section (and perhaps this page) was correct for Feisty. It does not work for Gutsy.

The following describes how you can boot a machine into the Ubuntu Desktop Edition, using just its network card to "PXE netboot", via a tftp and nfs server. This means you can use the machine to run a LiveCD system, without actually needing any CD drive nor hard disk in the machine. The machine is effectively a diskless workstation at this point. You can then install Ubuntu onto its hard drive just as if you had a CD in its CD drive.

The way this works, in summary is: you do some configuring of some servers, so that your client machine will 'netboot' via pxe/bootp, get an ip address, get passed a boot kernel via tftp, will boot into that kernel, and it will display a menu screen to run a 'live-(pseudoCD)-install' on your client machine. You will have defined the menu item(s) for this menu, those being how to boot into a 'Live CD/install'. When you select the menu item, it boots a second kernel which takes you into the 'Live CD'.

Actually, to be precise, the boot kernel is a linux kernel and it is accompanied by the initial ramdisk image (initrd...). Each is a single file. Inside the initrd is the entire initial ramdisk including an init script. This script does the actual bootup and install. When we refer to a boot kernel on this page we should more precisely refer to the kernel and its partner initrd. They are a set that should be kept together.

Set up the servers

0. Ensure that you have a dhcp server (or a bootp server), a tftp (eg tftp-hpa) server, and an nfs server available on your network. If not, install them onto a machine (or over a set of machines if you want to complicate things). 0. Configure the dhcp server: Set the following options in dhcpd.conf on your DHCP server:

next-server 10.20.1.2; # this is your TFTP server
filename "pxelinux.0"; # put this in verbatim

or:

0. Configure a bootp server. If your router already provides dhcp, you might install and use a bootp server. The client machine's ip address will be assigned by the router. The ip address you try to assign with your bootp server will be ignored. Either way, your client machine will ask via pxe for an ip address, and will then be passed over to the tftpserver. 0. Install bootpd with Synaptic (package name = bootp) 0. Edit /etc/bootptab. Here is an example.

client:\
	td=/var/lib/tftpboot: hd=/: bf=pxelinux.0:\
	ip=192.168.1.4:\
	ha="00:1B:FC:58:69:69":\
	gw=192.168.1.1:\
	sm=255.255.255.0:
client:\
	td=/var/lib/tftpboot: hd=/: bf=pxelinux.0:\
	ip=192.168.1.42:\
	ha="00:00:39:2B:54:B5":\
	gw=192.168.1.1:\
	sm=255.255.255.0:

For further help: man bootpd; man bootptab and also found in the etc/bootptab file itself as comments.

If you don't know the hardware address, or which ip address dhcp will assign, start bootp and/or dhcp/router, get the hardware address from the client's startup screen and the ip address assigned by the router by browsing into the router after the first startup. Update /etc/bootptab with these good values, then restart bootpd.

0. Starting bootp: Here is a wrapper to start and stop bootpd from the command line.

#!/bin/bash
vDaemon=bootpd

Start () {
	/usr/sbin/$vDaemon -d 4 -c /var/lib/tftpboot >/tmp/$vDaemon.log 2>/tmp/$vDaemon.err &
}

Stop () {
	kill `pidof $vDaemon`
}

Status () {
	vPid="`pidof $vDaemon`"
	if [ "$vPid" ] ; then
		echo "$vDaemon running, pid=$vPid"
	else
		echo "$vDaemon not running"
	fi
}

case "$1" in
	start)	Start ;;
	stop)	Stop ;;
	restart) Stop ; sleep 2; Start ;;
	status) Status ;;
	""|*) echo `basename $0` parameter: start stop status or restart ;;
esac

Preparing Files for TFTP Net Booting, Section "Setting up BOOTP server" has more info on bootp, including instructions for starting bootp using the inetd alternative.

0. Configure the nfs server: 0. Download the Ubuntu Desktop .iso. 0. Mount the .iso and copy its contents to a directory on your nfs server. Eg if you use /home/ftp/..., you can also make the distro available via vs-ftpd, set for anonymous ftp. (This could include installing using an ftp server instead: another type of install, not covered here.) 0. Nfs-export the directory, (or one somewhere above it,) in /etc/exports so this directory is accessible via nfs. 0. Reload or restart the nfs server.

0. Configure the tftp server: 0. Download this tarfile from the Ubuntu Archives, and extract its contents into the tftpboot directory on your tftp server. 0. Copy vmlinuz and initrd.gz from the /casper directory of the Ubuntu Desktop .iso to the tftpboot directory. Rename them if you wish, eg vmlinuz.fromUbuntu704DesktopCd, initrd.gz.fromUbuntu704DesktopCd. This is the kernel and initrd that you will select to load as your 'live CD' session. Eg

cp -a /home/ftp/ubuntu704DesktopCd/casper/vmlinuz /var/lib/ftfpboot/vmlinuz.fromUbuntu704DesktopCd
cp -a /home/ftp/ubuntu704DesktopCd/casper/initrd.gz /var/lib/ftfpboot/initrd.gz.fromUbuntu704DesktopCd

Note the use of -a so you preserve the timestamp. This helps clarify later which version kernel you are using.

0. Edit a menu LABEL entry in pxelinux.cfg/default to point to the kernel and initrd from the previous step. Also edit in options to tell casper to mount to it via NFS, eg as per the following 5 lines:

1 DEFAULT LiveDesktopCD
2
3 LABEL LiveDesktopCD
4 kernel vmlinuz.fromUbuntu704DesktopCd
5 append initrd=initrd.gz.fromUbuntu704DesktopCd boot=casper netboot=nfs nfsroot=192.168.1.40:/home/ftp/ubuntu704DesktopCd --

(The 5th line is long and might appear split here. Join them in your pxelinux.cfg/default.) nfsroot points to your NFS server and the path to the directory where you copied all the contents of the CD. 0. Its useful to also edit the boot-screens/boot.txt to make the startup menu look different to the standard installation startup, and boot-screens/F3 file to document your use of the casper kernel.

(More background info is at Preparing Files for TFTP Net Booting).

Net-boot your client machine.

0. The tftpboot server passes the client the boot kernel, as described in the intro. The boot kernel presents an installation screen, or menu, which looks similar to the first pre-installation screen of the Desktop live CD. You will be presented with the installation startup menu described above. If you have set up the LABEL lines correctly, simply hit [Enter].

0. The installation kernel does a simple install to RAM and starts Gnome. You get a desktop with an icon to Install to hard disk. If you start this icon, the full hard disk install proceeds. If not, you simply run a 'Live Cd' session in RAM (without the actual CD).

Technical Note: About Casper

"Casper is a hook for initramfs-tools used to generate an initramfs capable to boot live systems as those created by make-live. This includes the Debian-Live isos, netboot tarballs, and usb stick images and Ubuntu live cds. At boot time it will look for a (read-only) media containing a "/casper" directory where a root filesystems (often a compressed squashfs) is stored. If found, it will create a writable environment, using unionfs, for debian-like systems to boot from." man casper for more information.

Basic: Hands-On Interactive Network Server Edition Install

These steps allow you to install an Ubuntu distro from over your network, as if you had booted and installed it from the Ubuntu installation CD. This is almost a rewrite of the above, except its using http via Apache instead of nfs. Moreover, it does not use Casper so it does not result in a live system. Instead the client boots into an installer.)

Services needed, on a server (or servers) : 0. dhcp or bootp: to provide netboot server support, 0. tftp: to feed the first boot image to the netboot client machine, when requested by the netboot server, 0. http, ftp or nfs: to supply the Ubuntu distro to the client machine during the installation process. 0. The client machine must be able to boot from its network card, else from a diskette that you built to 'netboot'.

This page focusses on the combination of dhcp, tftp, and http. In the examples below 'myserver' is the server for these 3 services. (Each of these can be run on a separate server if desired.)

0.#1 Install and configure the dhcp server. Eg to install:

root@myserver:~ # apt-get install dhcp3-server

Configure the dhcp server to tell the clients what to boot. I added a default host name, you don't need it but it comes in handy for other things.

root@myserver:~ # cat /etc/dhcp3/dhcpd.conf
subnet 192.168.1.0  netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.254;
}
# put your DNS IP's here:
option domain-name-servers 192.168.1.7, 68.87.66.196 ;
filename="ubuntu/feisty/alternate/install/netboot/pxelinux.0";

root@myserver:~ # /etc/init.d/dhcp3-server restart
Stopping DHCP server: dhcpd3.
Starting DHCP server: dhcpd3.

0.#2 Install and configure the Trivial File Transfer Protocol server. The tftpd-hpa package is recommended. Install it. It is enabled via /etc/default/tftpd-hpa,

RUN_DAEMON="yes"
OPTIONS="-l -s /var/lib/tftpboot"

Also note its base directory. The default setting is shown above.

Mount the CD (media or image) under the tftpboot base directory found above,eg

root@myserver:/var/lib/tftpboot/ubuntu/feisty$ mount -o loop feisty-alternate-i386.iso alternate/

or, you can instead copy the contents of the CD into that location, instead of leaving the ISO mounted.

See Preparing Files for TFTP Net Booting for detailed information.

0.#3 Install and configure Apache, eg:

root@myserver:~ # apt-get install apache2

Make a symlink from apache's doc Root to the CD

root@myserver:/var/www # ln -s /var/lib/tftpboot/ubuntu/

Or copy the /ubuntu directory from the CD into here.

To use a pure ftp server like the vs-ftp server instead of Apache, install the ftp server, and configure it for anonymous ftp access. Then copy the /ubuntu directory from the CD into the anonymous ftp home. With vs-ftpd, this is set to /home/ftp. (Check /etc/passwd to confirm the anonymous ftp home.) Next test that anonymous ftp works and finds the installation stuff. eg via 'ftp localhost' on that machine. The install needs to be done in 'expert' mode, so you can select the ftp protocol instead of the default 'http'. 0.#4 Boot up the client machine, set its bios to net boot and you should get the Ubuntu screen and Boot: prompt. Yippee!

Advanced: Hands-Off, Preseeded Network Server Install

The above is for an interactive install, just as if you booted from CD. The following addresses preseeding, which enables a Hands Off Install where all the questions have been answered and fed to the installer. In addition, the following does not pull anything from the Internet.

A handful of preseed options need to be passed via kernel options. The kernel only supports 255 chars, so things are cramped. To accommodate this, I dumped some of the paths and made symlinks. That gave me just enough space for now. Note that the path/name of the kernel gets appended, so even trimming that helped.

root@sahara:/var/lib/tftpboot # ln -s ubuntu-installer/i386/initrd.gz
root@sahara:/var/lib/tftpboot # ln -s ubuntu-installer/i386/linux

/var/lib/tftpboot/pxelinux.cfg/default

# pxelinux.cfg/default

# display u0buntu-installer/i386/boot-screens/syslinux.txt

default menu
prompt 1
timeout 150
ontimeout boothd

label menu
# makes a menu out of this file, allows editing the options on the client
kernel menu.c32

label boothd
# boot from the first HD
# (this is what happens if nothing is pressed for 15 seconds)
localboot 0

label ubuntu-feisty-normal
# ubuntu installer
kernel ubuntu-feisty/linux
append vga=normal initrd=ubuntu-feisty/initrd.gz ramdisk_size=14984 root=/dev/rd/0 rw  --

label ubuntu-feisty-hands-off
# ubuntu installer
# The 'kernel' and 'initrd' paths must identify files under tftpboot.
# For example, on my system I have /var/lib/tftpboot/ubuntu-feisty/linux and /var/lib/tftpboot/ubuntu-feisty/initrd.gz.
kernel ubuntu-feisty/linux
append initrd=ubuntu-feisty/initrd.gz ramdisk_size=14984 root=/dev/rd/0 rw preseed/locale=en_US kbd-chooser/method=us netcfg/wireless_wep= netcfg/choose_interface=eth0 netcfg/get_hostname= preseed/url=http://192.168.1.7/preseed-feisty.cfg vga=6 --

netcfg/get_hostname= Is blank so that it will pick up the host-name supplied by the DHCP server.

netcfg/choose_interface=eth0 - You may wish to specify eth1 or wlan0 for laptops if you want it to setup the wifi card, not the wired port.

Note for client-specific PXE configurations: The DHCP server can't pass it, but pretending that the MAC address of your wireless card is 12 : CD : 56 : AB : 78 : EF you can specify a custom pxelinux.cfg/01-12-dc-56-ab-78-ef (lowercase) instead. If you are using static dhcp, you can also use the IP address in hex for a per-machine or per-subnet or per-network configuration. See http://syslinux.zytor.com/pxe.php#config for more information. Basically, say you have three wireless cards where the IP in hex translated to caf12d5e, caf12d6b, caf124ea, you could specify pxelinux.cfg/caf12d and pxelinux.cfg/caf12. The first two would match to the first config file and the third would match to the second config file.

See http://www.debian.org/releases/etch/example-preseed.txt for an example preseed file, and be sure to note the debconf-get-selections example commands. Here are the important changes for using the copy of the install CD on your server instead of the Internet repositories during the install:

d-i	mirror/country		string enter information manually
d-i	mirror/http/hostname	string sahara # This is whatever HTTP server you have set up
d-i	mirror/http/directory	string /ubuntu # This is the /ubuntu directory from the install CD copied (or linked) under the webroot of your HTTP server
d-i	mirror/suite		string feisty # Name your ubuntu version here
d-i	mirror/http/proxy	string

Here is my current dhcpd.conf

ping-check = 1;
log-facility local7;

option domain-name "sahara.net";
option time-servers  192.168.1.1;
option broadcast-address 192.168.1.255;

option domain-name-servers 63.240.76.4, 204.127.198.4;
option routers  192.168.1.1;

subnet 192.168.1.0  netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.254;
}

# Hoary test boxes
group {
	filename="pxelinux.0" ;

	# You need a next-server option if TFTP and DHCPd aren't on the same system.
	next-server sahara;
	
	# 192.168.1.2 does not exist on my lan.
	# I am setting it like this to make sure the box doesn't find
	# a repo on the net to pull sources from.
	# It would be good I can figure out how to i
	#  limit these setting to the install phase 
	#  (including the 2nd part after the reboot )
	
	option domain-name-servers 192.168.1.2 ;
	option routers 192.168.1.2 ;

	host dwl650p { 
		hardware ethernet 00:05:5d:5a:81:f0 ; 
		option host-name "dwl650p" ; }
	
	# tsp2 6100 - a=wired, b=wifi
	host tsp2a { 
		hardware ethernet 00:00:39:fa:ff:f3 ;
		option host-name "tsp2a" ; }
	
	host tsp2b { 
		hardware ethernet 00:02:2d:b0:c8:6c ;
		option host-name "tsp2b" ; }

	host tsp1 { 
		hardware ethernet 00:00:39:88:31:a6 ; 
		option host-name "tsp1" ; }

host e400 { 

		hardware ethernet 00:60:08:b0:62:0d ; 
		# fixed-address 192.168.1.181 ;
		option host-name "e400" ; }

}

If your box doesn't have the option to boot from lan (like one of mine) you can make a boot disk that will do that part.

http://etherboot.sourceforge.net

http://rom-o-matic.net

I am pleased to say that I was able to read, download, build, run, make the floppy in under 30 min.

"Etherboot does not (yet) offer support for PCMCIA cards." so the older laptops will have to wait.

Advanced: Network install using apt-mirror

apt-mirror is a Perl script for maintaining a mirror of the Debian or Ubuntu installation sets. It is often set up as a cron job to download updates to the mirror automatically. Updates are downloaded incrementally using parallel threads. Contents of the mirror are typically served via a web server to the local network.

apt-mirror can be installed on most Unix machine from the tarball. On Debian or Ubuntu, the apt-mirror package can usually be installed by apt-get with the appropriate addition to sources.list. See the apt-mirror project home page for details.

For basic instructions pertaining to Ubuntu, see How To Create A Local Debian/Ubuntu Mirror With apt-mirror. Some modifications are required to the mirror configuration to work in conjunction with netboot. Netboot requires debian-installer. The following snippet from an example configuration is reported to work:

deb http://mirrors.kernel.org/ubuntu feisty main main/debian-installer restricted restricted/debian-installer
deb http://mirrors.kernel.org/ubuntu feisty-updates main restricted
deb http://mirrors.kernel.org/ubuntu feisty-security main restricted

clean http://mirrors.kernel.org/ubuntu

You will need to modify your apt-mirror configuration file accordingly. Often this file is located at /etc/apt/mirrors.list. Note that not everyone chooses to mirror the security files unless the mirror updates regularly.

If your mirror is configured to support netboot, the following directories should be present:

/ubuntu/dists/feisty/restricted/debian-installer/
/ubuntu/dists/feisty/main/debian-installer/

If these portions of the file tree are not present on your mirror, the Feisty netboot installer displays a generic error screen beginning with the text "The installer failed to download a file from the mirror."

Surprisingly, my netboot installation of the Feisty server release set did not install openssh-server by default. After all this work setting up netboot, it was back to the console again for a couple of minutes.

个人工具

“UbuntuHelp:Installation/LocalNet”的版本间的差异 - Ubuntu中文

搜索

导航

编辑

工具