个人工具

UbuntuHelp:Installation/OnNFSDrive

来自Ubuntu中文

Oneleaf讨论 | 贡献2007年5月13日 (日) 10:58的版本 (New page: {{From|https://help.ubuntu.com/community/Installation/OnNFSDrive}} {{Languages|php5}} ==== Introduction & warning ==== This page describes installing Ubuntu on a NFS server. The client(s)...)

(差异) ←上一版本 | 最后版本 (差异) | 下一版本→ (差异)
跳转至: 导航, 搜索

Introduction & warning

This page describes installing Ubuntu on a NFS server. The client(s) running Ubuntu don't need anything wroten on the harddisk. This configuration has some extra requirements:

  • A pre-configured NFS-server. GNU/Linux on a 500MHz/512MB computer will do fine.
  • 100Mbit/s network. System will work very slowly with 10MBit/s.
  • Client with atleast 256MB RAM, preferrably 512MB OR a harddisk for a swap partition.
  • Some Linux experience and ability to compile your own kernel.

Set up the install directory

Create a directory for Ubuntu on the NFS server. This directory will be the root for storing all files needed by the clients. I will use /ubuntu in this tutorial.

$ su
Password:

# mkdir /ubuntu
</code>

==== Get debootstrap scripts ====

 1. Grab the latest debootstrap_*.tar.gz from http://archive.ubuntulinux.org/ubuntu/pool/main/d/debootstrap/  Save the archive into the /tmp directory.

 2. Uncompress and extract the archive, then cd into the newly created directory and build the program:
<pre>
# cd /tmp
# tar zxvf debootstrap_0.2.39ubuntu22.tar.gz
# cd debootstrap-0.2.39ubuntu22
# make
</code>

==== Run debootstrap ====

You should run the debootstrap you just built, which requires a slightly odd invocation:

<pre>
# DEBOOTSTRAP_DIR=`pwd` ./debootstrap --arch i386 hoary /ubuntu http://archive.ubuntulinux.org/ubuntu hoary
</code>

(JonathanLozinski notes that this did not seem to work on edgy-server, however simply "DEBOOTSTRAP_DIR=`pwd` ./debootstrap --arch i386 edgy /ubuntu" did seem to do as intended. )

The Ubuntu debootstrap will now run the warty scripts.  If your network is unreliable, you may need to run debootstrap multiple times to get all the files.  It resumes where it left off.

Near the end of debootstrap's copious output, you should see "Base system installed successfully". If not, remove everything in /mnt/ubuntu apart from the lost+found directory and try again.

==== Set up the host name ====

Of course, you should replace HOSTNAME in the command below with the desired name for your machine.

<pre>
# echo HOSTNAME > /ubuntu/etc/hostname
</code>

==== Set up fstab ====

Create your fstab. It should include procfs, sysfs and possibly cdrom and fd0. Root is not included.

<pre>
# nano /ubuntu/etc/fstab
</code>

Here is a decent fstab to get started with:

<pre>
/proc    /proc    proc    defaults   0 0
/sys     /sys     sysfs   defaults   0 0

/dev/fd0  /mnt/floppy auto user,noauto,sync,exec,umask=000 0 0
/dev/cdrom /mnt/cdrom auto user,noauto,exec,ro   0 0
</code>

==== Enter the install environment ====

<pre>
# chroot /ubuntu
# mount /proc
</code>

Set the root password:

<pre>
# passwd
Enter new UNIX password:
Retype new UNIX password:
</code>

==== Compile kernel for your system ====

This step is not described fully here. I used kernel 2.6.10 with gentoo patches, just because I had it compiled for my system already. There are some important settings you have to make:

 1. Compile your network card driver in the kernel, not as a module.
 2. Enable "IP: kernel level autoconfiguration" in Device Drivers -> Networking support -> Networking options
 3. Enable NFS in Filesystems -> Network file systems: Enable "NFS File system support" and "Root file system on NFS"

If you get "Warning: Unable to open initial console" on the boot and it hangs, try to also:

 1. Enable "Preliminary device filesystem" in Filesystems -> Pseudo filesystems
 2. Enable "Mount devfs automatically on boot"

===== kernel UPDATE: dapper & later users =====

Since dapper, it is not necessary to recompile the kernel, since initramfs is used on the initial ramdisk. Go to /etc/mkinitramfs/initramfs.conf (in the chroot) and change "BOOT=local" to "BOOT=nfs". Then install any linux-image, the initrd generated will be nfs-bootable. Alternatively, call update-initrd to regenerate initrd if you have kernel already installed.

Make sure to send '''both''' kernel image ("/boot/vmliunuz-VERSION") '''and''' initrd ("/boot/initrd.img-VERSION") when netbooting, in the next step. 

===== Getting out of chroot =====

In chrooted enviroment umount /proc and then exit:
<pre>
# umount /proc
# exit
</code>

==== Get PXELinux, dhcpd and tftpd ====

This step is not described fully here. You need PXELinux from http://syslinux.zytor.com/pxe.php , a TFTPD or other tftp server and DHCPD or other dhcp server. 
* Alternatively you can download the Netboot image for Dapper from http://archive.ubuntu.com/ubuntu/dists/dapper/main/installer-i386/current/images/netboot/netboot.tar.gz extract it, copy the pxelinux.0 file and the pxelinux.cfg directory to your tftpd root (mine is /ubuntu) and edit the pxelinux.cfg/default file as described as follows.

Configure PXELinux. A decent configuration file would be like:
<pre>
TIMEOUT 50

DEFAULT kernel-2.6.10
APPEND root=/dev/nfs nfsroot=192.168.0.150:/ubuntu ip=dhcp
</code>

You should atleast replace the server address. It is the address of the NFS server. Put pxelinux.0 and kernel-2.6.10 in the tftp server root directory. Put the configuration file "default" in directory "pxelinux.cfg".

Configure dhcpd to provide the boot image. A decent configuration would be like:
<pre>
 host netbooted {
  hardware ethernet 00:0C:F1:98:1B:A6;
  fixed-address 192.168.0.204;
  filename "/pxelinux.0";
 }
</code>

I give a fixed address for this to set NFS exports more securitely. You should replace the IP and the MAC address of the client. The MAC address can be seen with "ifconfig" on computers running Linux. Restart dhcp server to apply the changes.

==== Configure NFS exports ====

Add a suitable line in /etc/exports:
<pre>
/ubuntu                     192.168.0.204(rw,no_root_squash,async)
</code>

Restart NFS-server to apply the changes.

==== Boot ====

Configure the client to "Boot from network". It should load PXELinux and in 5 seconds start loading Ubuntu.

==== How To Setup The Ubuntu Desktop on this System ====
(ToDo !!) - this means how to setup the above system to be exactly like a Ubuntu Desktop Installation on the Client machine as the above only installs a similar system without the xserver/gnome/etc. and apt-get install ubuntu-desktop does not work out of the box.
workaroud for the time beeing :
* Setup NFS Server create the directory /ubuntu and export it described as above
* Install Ubuntu Desktop via NetbootImage/CD on Client machine
* Boot into it mount the /ubuntu directory via NFS
* get a root shell and copy the entire / to the mounted NFS directory
* chroot into the NFS dir, mount proc and uninstall all linux-image-...
* edit /etc/mkinitramfs/initramfs.conf and /etc/fstab as described above
* install linux-image
* configure pxelinux
* reboot via pxe
----
CategoryDocumentation

[[category:UbuntuHelp]]