1
<!-- retain these comments for translator revision tracking -->
2
<!-- $Id: network-console.xml 31173 2005-10-05 12:03:55Z holger-guest $ -->
4
<sect3 id="network-console">
5
<title>Installation Over the Network</title>
9
One of the more interesting components is
10
<firstterm>network-console</firstterm>. It allows you to do a large
11
part of the installation over the network via SSH. The use of the
12
network implies you will have to perform the first steps of the
13
installation from the console, at least to the point of setting up
14
the networking. (Although you can automate that part with
15
<xref linkend="automatic-install"/>.)
17
</para><para arch="not-s390">
19
This component is not loaded into the main installation menu by default,
20
so you have to explicitly ask for it.
22
If you are installing from CD, you need to boot with medium priority or
23
otherwise invoke the main installation menu and choose <guimenuitem>Load
24
installer components from CD</guimenuitem> and from the list of
25
additional components select <guimenuitem>network-console: Continue
26
installation remotely using SSH</guimenuitem>. Successful load is
27
indicated by a new menu entry called <guimenuitem>Continue
28
installation remotely using SSH</guimenuitem>.
30
</para><para arch="s390">
32
For installations on &arch-title;, this is the default method after
33
setting up the network.
37
<phrase arch="not-s390">After selecting this new entry, you</phrase>
38
<phrase arch="s390">You</phrase> will be asked for a new password
39
to be used for connecting to the installation system and for its
40
confirmation. That's all. Now you should see a screen which instructs
41
you to login remotely as the user <emphasis>installer</emphasis> with
42
the password you just provided. Another important detail to notice on
43
this screen is the fingerprint of this system. You need to transfer
44
the fingerprint securely to the <quote>person who will continue the
45
installation remotely</quote>.
49
Should you decide to continue with the installation locally, you
50
can always press &enterkey;, which will bring you back to
51
the main menu, where you can select another component.
55
Now let's switch to the other side of the wire. As a prerequisite, you
56
need to configure your terminal for UTF-8 encoding, because that is
57
what the installation system uses. If you do not, remote installation
58
will be still possible, but you may encounter strange display
59
artefacts like destroyed dialog borders or unreadable non-ascii
60
characters. Establishing a connection with the installation system
61
is as simple as typing:
63
<informalexample><screen>
64
<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>
65
</screen></informalexample>
67
Where <replaceable>install_host</replaceable> is either the name
68
or IP address of the computer being installed. Before the actual
69
login the fingerprint of the remote system will be displayed and
70
you will have to confirm that it is correct.
74
If you install several computers in turn and they happen to have the
75
same IP address or hostname, <command>ssh</command> will refuse to connect
76
to such host. The reason is that it will have different fingerprint, which
77
is usually a sign of a spoofing attack. If you are sure this is not the
78
case, you will need to delete the relevant line from
79
<filename>~/.ssh/known_hosts</filename> and try again.
83
After the login you will be presented with an initial screen where you
84
have two possibilities called <guimenuitem>Start menu</guimenuitem> and
85
<guimenuitem>Start shell</guimenuitem>. The former brings you to the
86
main installer menu, where you can continue with the installation as
87
usual. The latter starts a shell from which you can examine and possibly
88
fix the remote system. You should only start one SSH session for the
89
installation menu, but may start multiple sessions for shells.
91
</para><warning><para>
93
After you have started the installation remotely over SSH, you should
94
not go back to the installation session running on the local console.
95
Doing so may corrupt the database that holds the configuration of
96
the new system. This in turn may result in a failed installation or
97
problems with the installed system.
101
Also, if you are running the SSH session from an X terminal, you should
102
not resize the window as that will result in the connection being