| 1 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
<!-- $Id: boot-new.xml 12840 2004-04-07 21:44:06Z fjpop-guest $ -->
|
| 3 |
|
| 4 |
<chapter id="boot-new">
|
| 5 |
<title>Booting Into Your New Debian System</title>
|
| 6 |
|
| 7 |
<sect1><title>Make System Bootable</title>
|
| 8 |
<para>
|
| 9 |
|
| 10 |
Note that multiple operating systems booting on a single machine is
|
| 11 |
still something of a black art. This document does not even attempt
|
| 12 |
to document the various boot managers, which vary by architecture and
|
| 13 |
even by subarchitecture. You should see your boot manager's
|
| 14 |
documentation for more information.
|
| 15 |
|
| 16 |
</para>
|
| 17 |
|
| 18 |
&bootloader-i386.xml;
|
| 19 |
&bootloader-m68k.xml;
|
| 20 |
&bootloader-alpha.xml;
|
| 21 |
&bootloader-sparc.xml;
|
| 22 |
&bootloader-powerpc.xml;
|
| 23 |
&bootloader-hppa.xml;
|
| 24 |
&bootloader-s390.xml;
|
| 25 |
&bootloader-arm.xml;
|
| 26 |
&bootloader-mipsel.xml;
|
| 27 |
|
| 28 |
<sect2 condition="supports-nfsroot"><title>Diskless Workstations</title>
|
| 29 |
<para>
|
| 30 |
|
| 31 |
If you are installing a diskless workstation, obviously, booting off
|
| 32 |
the local disk isn't a meaningful option, and this step will be
|
| 33 |
skipped. <phrase arch="sparc">You may wish to set the OpenBoot to boot
|
| 34 |
from the network by default; see <xref
|
| 35 |
linkend="boot-dev-select-sun"/>.</phrase>
|
| 36 |
|
| 37 |
</para>
|
| 38 |
|
| 39 |
</sect2>
|
| 40 |
</sect1>
|
| 41 |
|
| 42 |
<sect1 id="make-boot-floppy"><title>Making a Boot Floppy</title>
|
| 43 |
<para>
|
| 44 |
|
| 45 |
You may wish to make a boot floppy even if you intend to boot the
|
| 46 |
system from the hard disk. The reason for this is that it's possible
|
| 47 |
for the hard disk bootstrap to be mis-installed, but a boot floppy
|
| 48 |
will almost always work.
|
| 49 |
|
| 50 |
</para><para>
|
| 51 |
|
| 52 |
Feed the system a blank floppy as directed. Make sure the floppy isn't
|
| 53 |
write-protected, as the software will format and write it. Mark this
|
| 54 |
the <quote>Custom Boot</quote> floppy and write-protect it once it has
|
| 55 |
been written.
|
| 56 |
|
| 57 |
</para><para>
|
| 58 |
|
| 59 |
This floppy will contain a kernel and a simple file system, with a
|
| 60 |
directive to use your new root file system.
|
| 61 |
|
| 62 |
</para><para arch="alpha">
|
| 63 |
|
| 64 |
Unfortunately, a boot floppy can only be made for SRM systems, since
|
| 65 |
<command>MILO</command> won't fit together with a kernel on a single
|
| 66 |
floppy.
|
| 67 |
|
| 68 |
</para>
|
| 69 |
</sect1>
|
| 70 |
|
| 71 |
|
| 72 |
<sect1 id="base-boot"><title>The Moment of Truth</title>
|
| 73 |
<para>
|
| 74 |
|
| 75 |
You system's first boot on its own power is what electrical engineers
|
| 76 |
call the <quote>smoke test</quote>.
|
| 77 |
|
| 78 |
</para><para arch="s390">
|
| 79 |
|
| 80 |
Select the ``Reboot the System'' menu item which will halt the system
|
| 81 |
because rebooting is not supported on &arch-title; in this case. You
|
| 82 |
then need to IPL GNU/Linux from the DASD which you selected for the
|
| 83 |
root filesystem during the first steps of the installation.
|
| 84 |
|
| 85 |
</para><para>
|
| 86 |
|
| 87 |
If you are booting directly into Debian, and the system doesn't start
|
| 88 |
up, either use your original installation boot media (for instance,
|
| 89 |
the rescue floppy), or insert the custom boot floppy if you created
|
| 90 |
one, and reset your system. If you are <emphasis>not</emphasis> using
|
| 91 |
the custom boot floppy, you will probably need to add some boot
|
| 92 |
arguments. If booting with the rescue floppy or similar technique,
|
| 93 |
you need to specify
|
| 94 |
<userinput>rescue root=<replaceable>root</replaceable></userinput>,
|
| 95 |
where <replaceable>root</replaceable> is your root partition, such as
|
| 96 |
<filename>/dev/sda1</filename>.
|
| 97 |
|
| 98 |
</para>
|
| 99 |
|
| 100 |
<sect2 arch="m68k"><title>VME6000 Booting</title>
|
| 101 |
<para>
|
| 102 |
|
| 103 |
If you have just performed a diskless install on a BVM or Motorola
|
| 104 |
VMEbus machine: once the system has loaded the
|
| 105 |
<command>tftplilo</command> program from the TFTP server, from the
|
| 106 |
<prompt>LILO Boot:</prompt> prompt enter one of:
|
| 107 |
|
| 108 |
<itemizedlist>
|
| 109 |
<listitem><para>
|
| 110 |
|
| 111 |
<userinput>b6000</userinput> followed by &enterkey;
|
| 112 |
to boot a BVME4000/6000
|
| 113 |
|
| 114 |
</para></listitem><listitem><para>
|
| 115 |
|
| 116 |
<userinput>b162</userinput> followed by &enterkey;
|
| 117 |
to boot an MVME162
|
| 118 |
|
| 119 |
</para></listitem><listitem><para>
|
| 120 |
|
| 121 |
<userinput>b167</userinput> followed by &enterkey;
|
| 122 |
to boot an MVME166/167
|
| 123 |
|
| 124 |
</para></listitem>
|
| 125 |
</itemizedlist>
|
| 126 |
|
| 127 |
</para>
|
| 128 |
|
| 129 |
</sect2>
|
| 130 |
|
| 131 |
<sect2 arch="m68k"><title>Macintosh Booting</title>
|
| 132 |
|
| 133 |
<para>
|
| 134 |
|
| 135 |
Go to the directory containing the installation files and start up the
|
| 136 |
<command>Penguin</command> booter, holding down the
|
| 137 |
<keycap>command</keycap> key. Go to the
|
| 138 |
<userinput>Settings</userinput> dialogue (<keycombo>
|
| 139 |
<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate
|
| 140 |
the kernel options line which should look like
|
| 141 |
<userinput>root=/dev/ram video=font:VGA8x16</userinput> or similar.
|
| 142 |
|
| 143 |
</para><para>
|
| 144 |
|
| 145 |
You need to change the entry to
|
| 146 |
<userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>.
|
| 147 |
Replace the <replaceable>yyyy</replaceable> with the Linux name of the
|
| 148 |
partition onto which you installed the system
|
| 149 |
(e.g. <filename>/dev/sda1</filename>); you wrote this down earlier.
|
| 150 |
The <userinput>video=font:VGA8x8</userinput> is recommended especially
|
| 151 |
for users with tiny screens. The kernel would pick a prettier (6x11)
|
| 152 |
font but the console driver for this font can hang the machine, so
|
| 153 |
using 8x16 or 8x8 is safer at this stage. You can change this at any
|
| 154 |
time.
|
| 155 |
|
| 156 |
</para><para>
|
| 157 |
|
| 158 |
If you don't want to start GNU/Linux immediately each time you start,
|
| 159 |
uncheck the <userinput>Auto Boot</userinput> option. Save your
|
| 160 |
settings in the <filename>Prefs</filename> file using the
|
| 161 |
<userinput>Save Settings As Default</userinput> option.
|
| 162 |
|
| 163 |
</para><para>
|
| 164 |
|
| 165 |
Now select <userinput>Boot Now</userinput> (<keycombo>
|
| 166 |
<keycap>command</keycap> <keycap>B</keycap> </keycombo>) to start your
|
| 167 |
freshly installed GNU/Linux instead of the RAMdisk installer system.
|
| 168 |
|
| 169 |
</para><para>
|
| 170 |
|
| 171 |
Debian should boot, and you should see the same messages as
|
| 172 |
when you first booted the installation system, followed by some new
|
| 173 |
messages.
|
| 174 |
|
| 175 |
</para>
|
| 176 |
|
| 177 |
</sect2>
|
| 178 |
</sect1>
|
| 179 |
|
| 180 |
<sect1 id="base-config">
|
| 181 |
<title>Debian Post-Boot (Base) Configuration</title>
|
| 182 |
|
| 183 |
<para>
|
| 184 |
|
| 185 |
After booting, you will be prompted to complete the configuration of
|
| 186 |
your basic system, and then to select what additional packages you
|
| 187 |
wish to install. The application which guides you through this
|
| 188 |
process is called <classname>base-config</classname>. Its concept is
|
| 189 |
very similar to the &d-i; from the first stage. Indeed,
|
| 190 |
<classname>base-config</classname> consists of a number of specialized
|
| 191 |
components, where each component handles one configuration task,
|
| 192 |
contains <quote>hidden menu in the background</quote> and also uses
|
| 193 |
the same navigation system.
|
| 194 |
|
| 195 |
</para><para>
|
| 196 |
|
| 197 |
If you wish to re-run the <classname>base-config</classname> at any
|
| 198 |
point after installation is complete, as root run
|
| 199 |
<userinput>base-config</userinput>.
|
| 200 |
|
| 201 |
</para>
|
| 202 |
|
| 203 |
&module-bc-timezone.xml;
|
| 204 |
&module-bc-shadow.xml;
|
| 205 |
&module-bc-ppp.xml;
|
| 206 |
&module-bc-apt.xml;
|
| 207 |
&module-bc-packages.xml;
|
| 208 |
&module-bc-install.xml;
|
| 209 |
&module-bc-mta.xml;
|
| 210 |
|
| 211 |
</sect1>
|
| 212 |
|
| 213 |
<sect1 id="login">
|
| 214 |
<title>Log In</title>
|
| 215 |
|
| 216 |
<para>
|
| 217 |
|
| 218 |
After you've installed packages, you'll be presented with the login
|
| 219 |
prompt. Log in using the personal login and password you
|
| 220 |
selected. Your system is now ready to use.
|
| 221 |
|
| 222 |
</para><para>
|
| 223 |
|
| 224 |
If you are a new user, you may want to explore the documentation which
|
| 225 |
is already installed on your system as you start to use it. There are
|
| 226 |
currently several documentation systems, work is proceeding on
|
| 227 |
integrating the different types of documentation. Here are a few
|
| 228 |
starting points.
|
| 229 |
|
| 230 |
</para><para>
|
| 231 |
|
| 232 |
Documentation accompanying programs you have installed is in
|
| 233 |
<filename>/usr/share/doc/</filename>, under a subdirectory named after
|
| 234 |
the program. For example, the APT User's Guide for using
|
| 235 |
<command>apt</command> to install other programs on your system, is
|
| 236 |
located in
|
| 237 |
<filename>/usr/share/doc/apt/guide.html/index.html</filename>.
|
| 238 |
|
| 239 |
</para><para>
|
| 240 |
|
| 241 |
|
| 242 |
In addition, there are some special folders within the
|
| 243 |
<filename>/usr/share/doc/</filename> hierarchy. Linux HOWTOs are
|
| 244 |
installed in <emphasis>.gz</emphasis> format, in
|
| 245 |
<filename>/usr/share/doc/HOWTO/en-txt/</filename> and
|
| 246 |
<filename>/usr/share/doc/HOWTO/en-txt/mini/</filename>. The
|
| 247 |
<filename>/usr/share/doc/HTML/index.html</filename> contains
|
| 248 |
browse-able indexes of documentation installed by
|
| 249 |
<command>dhelp</command>.
|
| 250 |
|
| 251 |
</para><para>
|
| 252 |
|
| 253 |
One easy way to view these documents is to <userinput>cd
|
| 254 |
/usr/share/doc/</userinput>, and type <userinput>lynx</userinput>
|
| 255 |
followed by a space and a dot (the dot stands for the current
|
| 256 |
directory).
|
| 257 |
|
| 258 |
</para><para>
|
| 259 |
|
| 260 |
You can also type <userinput>info
|
| 261 |
<replaceable>command</replaceable></userinput> or <userinput>man
|
| 262 |
<replaceable>command</replaceable></userinput> to see documentation on
|
| 263 |
most commands available at the command prompt. Typing
|
| 264 |
<userinput>help</userinput> will display help on shell commands. And
|
| 265 |
typing a command followed by <userinput>--help</userinput> will
|
| 266 |
usually display a short summary of the command's usage. If a command's
|
| 267 |
results scroll past the top of the screen, type <userinput>|
|
| 268 |
more</userinput> after the command to cause the results to pause
|
| 269 |
before scrolling past the top of the screen. To see a list of all
|
| 270 |
commands available which begin with a certain letter, type the letter
|
| 271 |
and then two tabs.
|
| 272 |
|
| 273 |
</para><para>
|
| 274 |
|
| 275 |
For a more complete introduction to Debian and GNU/Linux, see
|
| 276 |
<filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>.
|
| 277 |
|
| 278 |
</para>
|
| 279 |
|
| 280 |
</sect1>
|
| 281 |
</chapter>
|
Parent Directory
| 
Revision Log