UbuntuHelp:Installation/WindowsServerNetboot

文章出处:

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

点击翻译:

English  • 中文

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

Network Installing Ubuntu Using a Windows box

This document describes how to install Ubuntu through your network without having to access to an existing linux TFTP / DHCP server. This method is especially useful for installing Ubuntu onto a machine that does not have removable drives. If you have a floppy drive, you can make a floppy that will allow you to PXE boot on a non PXE enabled network card. The etherboot based one can be found here: [1] the package is network_boot_floppy+cd+hd_540.zip Alternatively you can use the Microsoft based pxe boot floppy - which can be constructed by using the Remote Boot Floppy Generator program named "rbfg.exe" which can be found in Windows 2003 or Windows 2000 Server version under the directory \windows\system32\dllcache or \winnt\ServicePackFiles\i386 respectively.

What you will need

• A network with a windows computer
• A a network gateway to the internet (Cable/DSL Router)
• Tftpd32.exe (The windows TFTP/DHCP server program) (Tftpd32 Homepage)
• The Ubuntu Netboot Image
• 7-Zip or WinRAR to unzip the image

Netboot Files

Karmic Koala (9.10) Karmic Netboot Image (i386) Karmic Netboot Image (amd64) Jaunty Jackalope (9.04) Jaunty Netboot Image (i386) Jaunty Netboot Image (amd64) Intrepid Ibex (8.10) Intrepid Netboot Image (i386) Intrepid Netboot Image (amd64) Hardy Heron (8.04) Hardy Netboot Image (i386) Hardy Netboot Image (amd64) Dapper Drake (6.06) Dapper Netboot Image (i386) Dapper Netboot Image (amd64)

Netboot Instructions

1. On the windows box, make a folder called "UbuntuNetInstall"
2. Place tftpd32.exe in that folder
3. Extract the contents of netboot.tar.gz and place them in a folder called "netboot"

Note: Winrar may give you some errors that it couldn't create some symbolic links, just ignore it.

1. Put the netboot folder inside of the "UbuntuNetInstall" folder
2. Go To UbuntuNetInstall/netboot/ubuntu-installer/i386/ or UbuntuNetInstall/netboot/ubuntu-installer/amd64/ and copy pxelinux.cfg folder
3. Go back to the netboot folder and Paste pxelinux.cfg folder.

You may also have to copy pxelinux.0 to the netboot folder (instead of it's original home in '/netboot/ubuntu-installer/i386/'), if you get an error such as 'error 2 in system call CreateFile: The system cannot find the file specified' in TFTPD32's logs.

1. Run tftpd32.exe and click the DHCP tab

• in the default router box, put the address of your internet gateway (usually 192.168.0.1 or 192.168.1.1 for residential routers)
• in the ip pool starting address box put your gateway's address + 1 to the last number (Example: 192.168.0.2)
• Size of pool = i said about 10
• If your network is something like 192.168.0.1 then your network mask should be 255.255.255.0
• Set the Bootfile field to the address of the pxelinux.0 file (it should be "\netboot\pxelinux.0)
• Set the WINS/DNS server address to the address of your main router (192.168.0.1)
• Leave the domain name blank, unless you need to change it.

1. Hit the "Save" button and then click "settings"
2. on the settings menu Check the following items:

• PXE Compatibility
• translate unix file names
• allow / as virtual root

then uncheck 'Ping address before assignation' and leave the others how they are. 10. click "ok" and tell your target computer to look on your network for a PXE boot rom. A few bugs: When picking a apt-get source, if you select the united states, the installer tries to connect to "http://.archive.ubuntu.com" instead of "http://archive.ubuntu.com", this results in a failure to connect. you can work around this by selecting the UK mirror and then selecting "archive.ubuntu.com" when prompted. The AMD64 image for some reason installs the "edubuntu-desktop" package rather than the "ubuntu-desktop" package. My fix was to install it with a server install, and then install the ubuntu-desktop package via apt-get. Sometimes the install of the base system seems to fail, I found that just repeating the base system install WITHOUT removing the packages (installing to unclean target) means that it eventually works - must be internet connection errors or whatever - keep trying as it gets there in the end!

---