3.5. Preparing for a Network Installation
Make sure an installation CD (or any other type of CD) is not in your system's CD/DVD drive if you are performing a network-based installation. Having a CD in the drive may cause unexpected errors.
The Fedora installation media must be available for either a network installation (via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if you are performing an NFS, FTP, or HTTP installation.
The NFS, FTP, or HTTP server to be used for installation over the network must be a separate machine which can provide the complete contents of the installation DVD-ROM or the installation CD-ROMs.
The Fedora installation program has the ability to test the integrity of the installation media. It works with the CD / DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type the following command at the boot:
In the following examples, the directory on the installation staging server that will contain the installation files will be specified as
. The directory that will be made publicly available via FTP, NFS, or HTTP will be specified as
. For example,
may be a directory you create called /var/isos
might be /var/www/html/f11
, for an HTTP install.
To copy the files from the installation DVD or CD-ROMs to a Linux machine which acts as an installation staging server, perform the following steps:
Create an iso image from the installation disk(s) using the following command (for DVDs):
refers to your DVD drive device.
For instructions on how to prepare a network installation using CD-ROMs, refer to the instructions on the README-en
file in disk1
3.5.1. Preparing for FTP and HTTP installation
Extract the files from the iso image of the installation DVD or the iso images of the installation CDs and place them in a directory that is shared over FTP or HTTP.
Next, make sure that the directory is shared via FTP or HTTP, and verify client access. You can check to see whether the directory is accessible from the server itself, and then from another machine on the same subnet that you will be installing to.