summaryrefslogtreecommitdiff
path: root/package/aboot/src/doc/man/aboot.sgml
blob: d54d3ad8c707b7f60414428e6fcd13992bfc1707 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<!DOCTYPE RefEntry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<refentry id="aboot">

<refmeta>
<refentrytitle>aboot</refentrytitle>
<manvolnum>8</manvolnum>
<refmiscinfo>aboot</refmiscinfo>
</refmeta>

<refnamediv>
<refname>aboot</refname>
<refpurpose>The secondary boot loader for Linux/Alpha</refpurpose>
</refnamediv>

<refsect1><title>COPYRIGHT</title>
<para>
<application>aboot</application> is Copyright (C) 1996 Linus Torvalds, David Mosberger-Tang and Michael Schwingen
</para>
</refsect1>

<refsect1><title>DESCRIPTION</title>
<para>
<indexterm><primary>aboot</primary></indexterm>
<application>aboot</application> is the secondary boot loader needed if
the Linux/Alpha system is booted via SRM. It is usually installed during
system installation by <application>swriteboot</application>(8). 
</para>
<para>
To automate the booting process predefined boot configurations can be stored
in <filename>etc/aboot.conf</filename>(5). 
</para>
<para>
<application>aboot</application> can also be used interactively by issuing
</para>
<para>
<command>boot <parameter>dka0 -fl "i"</parameter></command>
</para>
<para>
at the SRM-Prompt where dka0 has to be replaced by the device used. 
</para>
<para>
In the interactive mode you can use the command l to show your current
<filename>etc/aboot.conf</filename> and then the appropriate number
(or a complete boot command as in SRM) to boot Linux.
</para>
<para>
If you do not want to use the <filename>etc/aboot.conf</filename> as set
up by <application>abootconf</application>(8) you can explicitly tell 
<application>aboot</application> where to look for <filename>etc/aboot.conf</filename> by prepending the number of the configuration with the proper
partition, i.e. if your <filename>etc/aboot.conf</filename> is on your
second partition and you want to boot the entry labeled three you would
issue
</para>
<para>
<command>boot <parameter>dqa -fl "2:3"</parameter></command>
</para>
<para>
Note that this applies to Linux booting via SRM only as
<ProductName>VMS</ProductName>, <ProductName>Tru64</ProductName>, *BSD and
<ProductName>Windows NT</ProductName> each have their own secondary boot loader.
Furthermore <application>aboot</application> is also not needed if the system is booted via
<application>milo</application>.
</para>
</refsect1>


<refsect1><title>AUTHOR</title>
<para>
This man page was written by Helge Kreutzmann
<email>debian@helgefjell.de</email> for the Debian GNU/Linux project
but may be used by others.
</para>
</refsect1>

<refsect1><title>FILES</title>
<para><filename>etc/aboot.conf</filename></para>
</refsect1>

<refsect1><title>SEE ALSO</title>
<para><application>abootconf</application>(8), <filename>aboot.conf</filename>(5),
<application>swriteboot</application>(8), HP SRM Manual (<ULink URL="http://h18002.www1.hp.com/alphaserver/download/srm_reference.pdf"></ULink>)</para>
</refsect1>
</refentry>