| Previous | Table of Contents | Next |
Configuring the Modem
If you’re planning on using a modem for connecting to online systems or to a TCP/IP network via SLIP or PPP, you need to configure the modem. Essentially, this involves just telling Linux exactly what serial port the modem is connected to. The first serial port on a PC is called com1, and under Linux parlance this becomes cua0; the second serial port on a PC is called com2, and under Linux parlance this becomes cua1; and so on. (Note the numbering difference; UNIX likes to start things at 0, and PCs prefer to start things at 1.)
After you set up the mouse, you’ll be asked to set the speed for the modem. The choices (38400, 19200, et al.) are pretty clear.
NOTE: If you’re using a modem and the speed isn’t represented on the menu, use the next-fastest speed. For example, to properly configure a 28800-bps modem, you’d choose 38400.
Configuring the Mouse
You’ll want to use a mouse if you’re using the X Window System, and this menu allows you to set up the proper mouse. For newer PCs, setting up a mouse isn’t a hassle at all because they usually contain a serial port for that purpose. All you need to do is tell Linux what kind of mouse you’re using and its location (if you’re using a serial mouse, you’ll need to specify where the mouse is connected), and then move on from there.
Configuring LILO
LILO is the Linux Loader, and it’s used to boot Linux from the hard disk. It can also be used to boot additional operating systems (like OS/2 and MS-DOS) from the hard disk.
NOTE: LILO is a tool best left to Linux veterans. If you’ve used LILO before, go ahead and follow these directions to install it. However, if you’re a Linux newbie and don’t feel up to the task of a challenging configuration, it’s best for you to skip LILO.
LILO works with a configuration file that’s generated automatically through this Setup program. Your first move will be to start the process, then mark any operating systems you want to appear in this configuration file. Because you want Linux to be able to boot, you’ll want to begin by specifying Linux. After that, you can designate another operating system (MS-DOS or OS/2) as a possible boot option. You’ll want to specify Linux first, however, so it appears first in the configuration file. When you’re finished running through these queries, you’ll end up with a file that looks like this:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 50
vga = normal # force sane state
ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
root = /dev/hda2
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for
checking
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = DOS
table = /dev/hda
# DOS bootable partition config ends
This file is stored as /etc/lilo.conf.
You’ll also be asked about how long to wait before loading Linux. LILO is pretty handy, in that it lets you specify a period of time (5 seconds or 30 seconds) between when LILO loads and when the first operating system is loaded. (In the /etc/lilo.conf file, this appears as the numeral 50 if you chose 5 seconds, and 300 if you chose 30 seconds.) This gives you time to specify another operating system to boot, should you want to boot DOS or OS/2 instead of Linux. This is done by pressing the left Shift key after LILO loads; you will see the following prompt:
boot:
If you specify DOS, DOS will boot from the DOS partition (provided, of course, that you’ve marked this partition as a boot partition). Pressing the Tab key gives you a list of options.
NOTE: If you’re using OS/2’s Boot Manager, you may want to use that for the primary boot loader and use LILO to boot Linux.
Miscellaneous Installation Notes
At this time you can configure your Linux box for use on the network. However, because this is an advanced subject, we’ll skip it for now and revisit it in Chapter 8.
There might be other configuration options presented to you, depending on what you installed (for example, if you installed sendmail, there will be a query regarding its installation). Again, these tend to be advanced topics, so we’ll revisit them throughout the course of this book.
Now that the installation is finished, it’s time to actually run Linux. Before we get to that point, however, we’ll discuss some alternate installation methods.
You may run into situations where you are able to access a CD-ROM drive from DOS but not from Linux’s installation process. (This will happen if a SCSI card is not supported by Linux but there are drivers available for DOS or OS/2.) If this occurs, you can still use the accompanying CD-ROM for installation, but you’ll need to copy the files to your hard drive, floppy disks, or a tape drive. All three types of installation are explained here.
This installation method involves moving installation files from the CD-ROM to a DOS hard disk partition and installing from there. This must be a straight DOS partition, not altered via a disk-doubling technology such as the disk doubler in MS-DOS 6.x or Stacker.
You’ll need to replicate the file structure from the CD-ROM on the DOS partition, keeping intact the many subdirectories (A1, A2, and so on).
When you run the setup program and specify the source of the installation files, you’ll choose a hard disk partition instead of a CD-ROM.
The disk sets contained on the CD-ROM can be copied directly to DOS-formatted diskettes. (You’ll end up with a slew of diskettes, of course.) For each disk, make an MS-DOS format disk and copy the proper files to it. Then, when you run the setup program, you can specify that you’re installing from diskettes and not from another source.
The 00index.txt files are added by the FTP server; you don’t need those.
| Previous | Table of Contents | Next |