old-www/HOWTO/Installation-HOWTO/afterboot.html

371 lines
7.6 KiB
HTML

<HTML
><HEAD
><TITLE
>After Your First Boot</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The Linux Installation HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Booting Your New System"
HREF="firstboot.html"><LINK
REL="NEXT"
TITLE="Administrivia"
HREF="administrivia.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Linux Installation HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="firstboot.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="administrivia.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AFTERBOOT">8. After Your First Boot</H1
><P
>You should now be looking at the login prompt of a new Linux,
just booted from your hard drive. Congratulations!</P
><P
>The <A
HREF="http://algolog.tripod.com/postlnx.htm"
TARGET="_top"
>GNU/Linux
post-install procedures</A
> has some good suggestions about things you
can do just after installation to minimize problems later on.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="ADMIN">8.1. Beginning System Administratration</H2
><P
>Depending on how the installation phase went, you may need to
create accounts, change your hostname, or (re)configure X at this
stage. There are many more things you could set up and configure,
including backup devices, SLIP/PPP links to an Internet Service
Provider, etc.</P
><P
>A good book on UNIX systems administration should help. (I suggest
<I
CLASS="CITETITLE"
>Essential Systems Administration</I
> from O'Reilly and
Associates.) You will pick these things up as time goes by. You should
read various other Linux HOWTOs, such as the
<I
CLASS="CITETITLE"
>NET-3-HOWTO</I
> and
<I
CLASS="CITETITLE"
>Printing-HOWTO</I
>, for information on other
configuration tasks.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN606">8.2. Custom LILO Configuration<A
NAME="CUSTOM-LILO"
></A
></H2
><P
>LILO is a boot loader, which can be used to select either Linux,
MS-DOS, or some other operating system at boot time. Chances are
your distribution automatically configured LILO for you during the
installation phase (unless you're using OS/2, this is what you
should have done). If so, you can skip the rest of this section.</P
><P
>If you installed LILO as the <EM
>primary</EM
> boot
loader, it will handle the first-stage booting process for all operating
systems on your drive. This works well if MS-DOS is the only other
operating system that you have installed. However, you might be running
OS/2, which has its own Boot Manager. In this case, you want OS/2's Boot
Manager to be the primary boot loader, and use LILO just to boot Linux (as
the <EM
>secondary</EM
> boot loader).</P
><P
>An important gotcha for people using EIDE systems: due to a BIOS
limitation, your boot sectors for any OS have to live on one of the
first two physical disks. Otherwise LILO will hang after writing
"LI", no matter where you run it from.</P
><P
>If you have to configure LILO manually, this will involve editing the
file <TT
CLASS="FILENAME"
>/etc/lilo.conf</TT
>. Below we present an example of a
LILO configuration file, where the Linux root partition is on
<TT
CLASS="FILENAME"
>/dev/hda2</TT
>, and MS-DOS is installed on
<TT
CLASS="FILENAME"
>/dev/hdb1</TT
> (on the second hard drive).</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
># Tell LILO to install itself as the primary boot loader on /dev/hda.
boot = /dev/hda
# The boot image to install; you probably shouldn't change this
install = /boot/boot.b
# The stanza for booting Linux.
image = /vmlinuz # The kernel is in /vmlinuz
label = linux # Give it the name "linux"
root = /dev/hda2 # Use /dev/hda2 as the root filesystem
vga = ask # Prompt for VGA mode
append = "aha152x=0x340,11,7,1" # Add this to the boot options,
# for detecting the SCSI controller
# The stanza for booting MS-DOS
other = /dev/hdb1 # This is the MS-DOS partition
label = msdos # Give it the name "msdos"
table = /dev/hdb # The partition table for the second drive</PRE
></FONT
></TD
></TR
></TABLE
><P
>Once you have edited the <TT
CLASS="FILENAME"
>/etc/lilo.conf</TT
> file,
run <B
CLASS="COMMAND"
>/sbin/lilo</B
> as <EM
>root</EM
>. This will
install LILO on your drive. Note that you must rerun
<B
CLASS="COMMAND"
>/sbin/lilo</B
> anytime that you recompile your kernel in
order to point the boot loader at it properly (something that you don't
need to worry about just now, but keep it in mind).</P
><P
>Note how we use the <EM
>append</EM
> option in
<TT
CLASS="FILENAME"
>/etc/lilo.conf</TT
> to specify boot parameters as we did when
booting the bootdisk.</P
><P
>You can now reboot your system from the hard drive. By default LILO
will boot the operating system listed first in the configuration file,
which in this case is Linux. In order to bring up a boot menu, in order to
select another operating system, hold down <EM
>shift</EM
> or
<EM
>ctrl</EM
> while the system boots; you should see a prompt
such as</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>Boot:</PRE
></FONT
></TD
></TR
></TABLE
><P
>Here, enter either the name of the operating system to boot (given by
the <EM
>label</EM
> line in the configuration file; in this
case, either <EM
>linux</EM
> or <EM
>msdos</EM
>), or
press <EM
>tab</EM
> to get a list.</P
><P
>Now let's say that you want to use LILO as the secondary boot
loader; if you want to boot Linux from OS/2's Boot Manager, for
example. In order to boot a Linux partition from OS/2 Boot
Manager, unfortunately, you must create the partition using OS/2's
<B
CLASS="COMMAND"
>FDISK</B
> (not Linux's), and format the partition as FAT or
HPFS, so that OS/2 knows about it. (That's IBM for you.)</P
><P
>In order to have LILO boot Linux from OS/2 Boot Manager, you only
want to install LILO on your Linux root filesystem (in the above
example, <TT
CLASS="FILENAME"
>/dev/hda2</TT
>). In this case, your LILO config file
should look something like:</P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
>boot = /dev/hda2
install = /boot/boot.b
compact
image = /vmlinuz
label = linux
root = /dev/hda2
vga = ask</PRE
></FONT
></TD
></TR
></TABLE
><P
>Note the change in the <EM
>boot</EM
> line. After running
<B
CLASS="COMMAND"
>/sbin/lilo</B
> you should be able to add the Linux partition
to Boot Manager. This mechanism should work for boot loaders used
by other operating systems as well.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="firstboot.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="administrivia.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Booting Your New System</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Administrivia</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>