Preparing for a Network Installation

If you are performing a network installation and have booted from a boot disk with the bootnet.img
image, the Configure TCP/IP dialog appears; for an explanation of this dialog, go to the Section called
Network Configuration, and then return here.

Setting Up the Server

Because the Red Hat Linux 7.3 installation program is capable of installing Red Hat Linux from multiple
CD-ROMs, if you intend to support NFS, FTP, or HTTP installations you must copy the RedHat directory
from each CD-ROM comprising Red Hat Linux 7.3 onto a disk drive:

 Insert CD-ROM 1 and execute the following commands:

o mount /mnt/cdrom
o cp -var /mnt/cdrom/RedHat /location/of/disk/space

Where /location/of/disk/space is a directory you create such as /export/7.3/.

o umount /mnt/cdrom
 Insert CD-ROM 2 and execute the following commands:
o mount /mnt/cdrom
o cp -var /mnt/cdrom/RedHat /location/of/disk/space

Where /location/of/disk/space is a directory you create such as /export/7.3/.

o umount /mnt/cdrom
 Next, make /location/of/disk/space accessible to the installation program (for example,
exporting it for NFS installations) by editing the /etc/exports file and adding the line:

/location/of/disk/space *(ro)

 Finally, run the following command to make /location/of/disk/space available as read-

only to each system to mount:

/sbin/service nfs reload

If you are not sure how to do this, refer to the Official Red Hat Linux Customization Guide and the Official
Red Hat Linux Reference Guide for more information.

Using ISO Images for NFS Installs

NFS installations can use ISO (or CD-ROM) images rather than copying an entire installation tree. After
placing the required ISO images (the binary Red Hat Linux CD-ROMs) in a directory, choose to install via
NFS. You will then point the installation program at that directory to perform the installation.

Verifying that the ISO images are intact before you attempt an installation will help to avoid problems that
are often encountered during an NFS installation. To verify the ISO images are intact prior to performing
an installation, use an md5sum program (many md5sum programs are available for various operating
systems). An md5sum program should be available on the same server as the ISO images.
Installing via NFS
The NFS dialog (Figure 3-4) applies only if you are installing from an NFS server (if you booted from a
network or PCMCIA boot disks and selected NFS Image in the Installation Method dialog).

Enter the fully-qualified domain name or IP address of your NFS server. For example, if you are installing
from a host named eastcoast in the domain redhat.com, enter eastcoast.redhat.com in the NFS
Server field.

Next, enter the name of the exported directory. If you followed the setup described in the Section called
Preparing for a Network Installation, you would enter the directory /location/of/disk/space/ which
contains the RedHat directory.

If the NFS server is exporting a mirror of the Red Hat Linux installation tree, enter the directory which
contains the RedHat directory. (If you do not know this directory path, ask your system administrator.) For
example, if your NFS server contains the directory /mirrors/redhat/i386/RedHat, enter
/mirrors/redhat/i386.

If the NFS server is exporting the ISO images of the Red Hat Linux CD-ROMs, enter the directory which
contains the ISO images.

Next you will see the Welcome dialog.

Installing via FTP

The FTP dialog (Figure 3-5) applies only if you are installing from an FTP server (if you selected FTP in
the Installation Method dialog). This dialog allows you to identify the FTP server from which you are
installing Red Hat Linux.

Enter the name or IP address of the FTP site you are installing from, and the name of the directory
containing the RedHat installation files for your architecture. For example, if the FTP site contains the
directory /mirrors/redhat/i386/RedHat, enter /mirrors/redhat/i386.

If everything has been specified properly, a message box appears indicating that base/hdlist is being
retrieved.

Next you will see the Welcome dialog.

Installing via HTTP

The HTTP dialog (Figure 3-6) applies only if you are installing from an HTTP server (if you selected HTTP
in the Installation Method dialog). This dialog prompts you for information about the HTTP server from
which you are installing Red Hat Linux.

Enter the name or IP address of the HTTP site you are installing from, and the name of the directory there
containing the RedHat installation files for your architecture. For example, if the HTTP site contains the
directory /mirrors/redhat/i386/RedHat, enter /mirrors/redhat/i386.
If everything has been specified properly, a message box appears indicating that base/hdlist is being
retrieved.

Next you will see the Welcome dialog.

Welcome to Red Hat Linux

The Welcome screen does not prompt you for any input. Please read over the help text in the left panel
for additional instructions and information on where to register your Official Red Hat Linux product.

Please notice the Hide Help button at the bottom left corner of the screen. The help screen is open by
default. If you do not want to view the help information, click on Hide Help to minimize the help portion of
the screen.

Click on the Next button to continue.

Language Selection
Using your mouse, select the language you would prefer to use for the installation and as the system
default (see Figure 3-7).

Selecting the appropriate language will also help target your time zone configuration later in the
installation. The installation program will try to define the appropriate time zone based on what you
specify on this screen.

Once you select the appropriate language, click Next to continue.

Network Configuration
Firewall Configuration
IF u do not hve a netwrk device,then configure firewall

Red Hat Linux offers firewall protection for enhanced system security. A firewall exists between your
computer and the network, and determines which resources on your computer remote users on the
network can access. A properly configured firewall can greatly increase the security of your system.

Choose the appropriate security level for your system.

High

If you choose High, your system will not accept connections (other than the default settings) that
are not explicitly defined by you. By default, only the following connections are allowed:

 DNS replies
 DHCP — so any network interfaces that use DHCP can be properly configured

If you choose High, your firewall will not allow the following:
  Active mode FTP (passive mode FTP, used by default in most clients, should still work)
 IRC DCC file transfers
 RealAudioTM
 Remote X Window System clients

If you are connecting your system to the Internet, but do not plan to run a server, this is the safest
choice. If additional services are needed, you can choose Customize to allow specific services
through the firewall.

If you have a network device and you have not already configured your networking (such as booting from
a network boot disk you created and entering in your network information as prompted), you now have the
opportunity (as shown in Figure 3-17) to do so.

If you have multiple devices, you will see a tab for each device. You may switch between devices (for
example, between eth0 and eth1) and the information you provide on each tab will be specific to each
device.

Indicate if you would like to configure your IP address using DHCP (Dynamic Host Configuration
Protocol). If you select Activate on boot, your network interface will be started when you boot. If you do
not have DHCP client access or you are unsure what to provide here, please contact your network
administrator.

Next enter, where applicable, the IP Address, Netmask, Network, and Broadcast addresses. If you are
unsure about any of these, please contact your network administrator.

If you have a fully qualified domain name for the network device, enter it in the Hostname field.

Finally, enter the Gateway and Primary DNS (and if applicable the Secondary DNS and Ternary DNS)
addresses.

Allow Incoming

Enabling these options allow the specified services to pass through the firewall. Note, during a
workstation installation, the majority of these services are not installed on the system.

DHCP

If you allow incoming DHCP queries and replies, you allow any network interface that uses DHCP
to determine its IP address. DHCP is normally enabled. If DHCP is not enabled, your computer
can no longer get an IP address.

SSH

Secure SHell (SSH) is a suite of tools for logging into and executing commands on a remote
machine. If you plan to use SSH tools to access your machine through a firewall, enable this
option. You need to have the openssh-server package installed in order to access your
machine remotely, using SSH tools.

Telnet
Telnet is a protocol for logging into remote machines. Telnet communications are unencrypted
and provide no security from network snooping. Allowing incoming Telnet access is not
recommended. If you do want to allow inbound Telnet access, you will need to install the
telnet-server package.

WWW (HTTP)

The HTTP protocol is used by Apache (and by other Web servers) to serve webpages. If you plan
on making your Web server publicly available, enable this option. This option is not required for
viewing pages locally or for developing webpages. You will need to install the apache package if
you want to serve webpages.

Enabling WWW (HTTP) will not open a port for HTTPS. To enable HTTPS, specify it in the Other
ports field.

Mail (SMTP)

If you want to allow incoming mail delivery through your firewall, so that remote hosts can connect
directly to your machine to deliver mail, enable this option. You do not need to enable this if you
collect your mail from your ISP's server using POP3 or IMAP, or if you use a tool such as
fetchmail. Note that an improperly configured SMTP server can allow remote machines to use
your server to send spam.

FTP

The FTP protocol is used to transfer files between machines on a network. If you plan on making
your FTP server publicly available, enable this option. You need to install the wu-ftpd (and
possibly the anonftp) package for this option to be useful.

Other ports

You can allow access to ports which are not listed here, by listing them in the Other ports field.
Use the following format: port:protocol. For example, if you want to allow IMAP access
through your firewall, you can specify imap:tcp. You can also explicitly specify numeric ports; to
allow UDP packets on port 1234 through the firewall, enter 1234:udp. To specify multiple ports,
separate them with commas.