diff options
Diffstat (limited to 'nl/post-install')
| -rw-r--r-- | nl/post-install/further-reading.xml | 49 | ||||
| -rw-r--r-- | nl/post-install/kernel-baking.xml | 173 | ||||
| -rw-r--r-- | nl/post-install/mail-setup.xml | 263 | ||||
| -rw-r--r-- | nl/post-install/new-to-unix.xml | 29 | ||||
| -rw-r--r-- | nl/post-install/orientation.xml | 109 | ||||
| -rw-r--r-- | nl/post-install/post-install.xml | 15 | ||||
| -rw-r--r-- | nl/post-install/rescue.xml | 71 | ||||
| -rw-r--r-- | nl/post-install/shutdown.xml | 31 |
8 files changed, 0 insertions, 740 deletions
diff --git a/nl/post-install/further-reading.xml b/nl/post-install/further-reading.xml deleted file mode 100644 index 357e3dd7e..000000000 --- a/nl/post-install/further-reading.xml +++ /dev/null @@ -1,49 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 30719 untranslated --> - - <sect1 id="further-reading"><title>Further Reading and Information</title> -<para> - -If you need information about a particular program, you should first -try <userinput>man <replaceable>program</replaceable></userinput>, or -<userinput>info <replaceable>program</replaceable></userinput>. - -</para><para> - -There is lots of useful documentation in -<filename>/usr/share/doc</filename> as well. In particular, -<filename>/usr/share/doc/HOWTO</filename> and -<filename>/usr/share/doc/FAQ</filename> contain lots of interesting -information. To submit bugs, look at -<filename>/usr/share/doc/debian/bug*</filename>. To read about -&debian;-specific issues for particular programs, look at -<filename>/usr/share/doc/(package name)/README.Debian</filename>. - -</para><para> - -The -<ulink url="http://www.debian.org/">Debian web site</ulink> -contains a large quantity of documentation about Debian. In -particular, see the -<ulink url="http://www.debian.org/doc/FAQ/">Debian GNU/Linux FAQ</ulink> and the -<ulink url="http://www.debian.org/doc/user-manuals#quick-reference">Debian -Reference</ulink>. -An index of more Debian documentation is available from the -<ulink url="http://www.debian.org/doc/ddp">Debian Documentation Project</ulink>. -The Debian community is self-supporting; to subscribe to -one or more of the Debian mailing lists, see the -<ulink url="http://www.debian.org/MailingLists/subscribe"> -Mail List Subscription</ulink> page. -Last, but not least, the <ulink url="http://lists.debian.org/">Debian Mailing -List Archives</ulink> contain a wealth of information on Debian. - -</para><para arch="linux-any"> - -A general source of information on GNU/Linux is the -<ulink url="http://www.tldp.org/">Linux Documentation Project</ulink>. -There you will find the HOWTOs and pointers to other very valuable -information on parts of a GNU/Linux system. - -</para> - - </sect1> diff --git a/nl/post-install/kernel-baking.xml b/nl/post-install/kernel-baking.xml deleted file mode 100644 index 5420f102c..000000000 --- a/nl/post-install/kernel-baking.xml +++ /dev/null @@ -1,173 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 40980 untranslated --> - - <sect1 arch="linux-any" id="kernel-baking"><title>Compiling a New Kernel</title> -<para> - -Why would someone want to compile a new kernel? It is often not -necessary since the default kernel shipped with &debian; handles most -configurations. Also, &debian; often offers several alternative kernels. -So you may want to check first if there is an alternative kernel image -package that better corresponds to your hardware. However, it can be -useful to compile a new kernel in order to: - -<itemizedlist> -<listitem><para> - -handle special hardware needs, or hardware conflicts with the -pre-supplied kernels - -</para></listitem> -<listitem><para> - -use options of the kernel which are not supported in the pre-supplied -kernels (such as high memory support) - -</para></listitem> -<listitem><para> - -optimize the kernel by removing useless drivers to speed up boot time - -</para></listitem> -<listitem><para> - -create a monolithic instead of a modularized kernel - -</para></listitem> -<listitem><para> - -run an updated or development kernel - -</para></listitem> -<listitem><para> - -learn more about linux kernels - -</para></listitem> -</itemizedlist> - -</para> - - <sect2><title>Kernel Image Management</title> -<para> - -Don't be afraid to try compiling the kernel. It's fun and profitable. - -</para><para> - -To compile a kernel the &debian; way, you need some packages: -<classname>fakeroot</classname>, <classname>kernel-package</classname>, -<classname>linux-source-2.6</classname> -and a few others which are probably already installed (see -<filename>/usr/share/doc/kernel-package/README.gz</filename> for the -complete list). - -</para><para> - -This method will make a .deb of your kernel source, and, if you have -non-standard modules, make a synchronized dependent .deb of those -too. It's a better way to manage kernel images; -<filename>/boot</filename> will hold the kernel, the System.map, and a -log of the active config file for the build. - -</para><para> - -Note that you don't <emphasis>have</emphasis> to compile your kernel -the <quote>Debian way</quote>; but we find that using the packaging system -to manage your kernel is actually safer and easier. In fact, you can get -your kernel sources right from Linus instead of -<classname>linux-source-2.6</classname>, -yet still use the <classname>kernel-package</classname> compilation method. - -</para><para> - -Note that you'll find complete documentation on using -<classname>kernel-package</classname> under -<filename>/usr/share/doc/kernel-package</filename>. This section just -contains a brief tutorial. - -</para><para> - -Hereafter, we'll assume you have free rein over your machine and will -extract your kernel source to somewhere in your home directory<footnote> - -<para> - -There are other locations where you can extract kernel sources and build -your custom kernel, but this is easiest as it does not require special -permissions. - -</para> - -</footnote>. We'll also assume that your kernel version is -&kernelversion;. Make sure you are in the directory to where you want to -unpack the kernel sources, extract them using -<userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> -and change to the directory <filename>linux-source-&kernelversion;</filename> -that will have been created. - -</para><para> - -Now, you can configure your kernel. Run <userinput>make -xconfig</userinput> if X11 is installed, configured and being run; run -<userinput>make menuconfig</userinput> otherwise (you'll need -<classname>libncurses5-dev</classname> installed). Take the time to read -the online help and choose carefully. When in doubt, it is typically -better to include the device driver (the software which manages -hardware peripherals, such as Ethernet cards, SCSI controllers, and so -on) you are unsure about. Be careful: other options, not related to a -specific hardware, should be left at the default value if you do not -understand them. Do not forget to select <quote>Kernel module loader</quote> -in <quote>Loadable module support</quote> (it is not selected by default). -If not included, your &debian; installation will experience problems. - -</para><para> - -Clean the source tree and reset the <classname>kernel-package</classname> -parameters. To do that, do <userinput>make-kpkg clean</userinput>. - -</para><para> - -Now, compile the kernel: -<userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. -The version number of <quote>1.0</quote> can be changed at will; this is just -a version number that you will use to track your kernel builds. -Likewise, you can put any word you like in place of <quote>custom</quote> -(e.g., a host name). Kernel compilation may take quite a while, depending on -the power of your machine. - -</para><para> - -Once the compilation is complete, you can install your custom kernel -like any package. As root, do -<userinput>dpkg -i -../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. -The <replaceable>subarchitecture</replaceable> part is an optional -sub-architecture, -<phrase arch="i386"> such as <quote>686</quote>, </phrase> -depending on what kernel options you set. -<userinput>dpkg -i</userinput> will install the -kernel, along with some other nice supporting files. For instance, -the <filename>System.map</filename> will be properly installed -(helpful for debugging kernel problems), and -<filename>/boot/config-&kernelversion;</filename> will be installed, -containing your current configuration set. Your new -kernel package is also clever enough to automatically update your boot -loader to use the new kernel. If you have created a modules package, -you'll need to install that package as well. - -</para><para> - -It is time to reboot the system: read carefully any warning that the -above step may have produced, then <userinput>shutdown -r now</userinput>. - -</para><para> - -For more information on &debian; kernels and kernel compilation, see the -<ulink url="&url-kernel-handbook;">Debian Linux Kernel Handbook</ulink>. -For more information on <classname>kernel-package</classname>, read -the fine documentation in <filename>/usr/share/doc/kernel-package</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/mail-setup.xml b/nl/post-install/mail-setup.xml deleted file mode 100644 index 103d06059..000000000 --- a/nl/post-install/mail-setup.xml +++ /dev/null @@ -1,263 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 48595 untranslated --> - - <sect1 id="mail-setup"> - <title>Setting Up Your System To Use E-Mail</title> -<para> - -Today, email is an important part of many people's life. As there are -many options as to how to set it up, and as having it set up correctly is -important for some &debian; utilities, we will try to cover the basics in -this section. - -</para><para> - -There are three main functions that make up an e-mail system. First there is -the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user -actually uses to compose and read mails. Then there is the <firstterm>Mail -Transfer Agent</firstterm> (MTA) that takes care of transferring messages -from one computer to another. And last there is the <firstterm>Mail -Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail -to the user's inbox. - -</para><para> - -These three functions can be performed by separate programs, but they can -also be combined in one or two programs. It is also possible to have -different programs handle these functions for different types of mail. - -</para><para> - -On Linux and Unix systems <command>mutt</command> is historically a very -popular MUA. Like most traditional Linux programs it is text based. It is -often used in combination with <command>exim</command> or -<command>sendmail</command> as MTA and <command>procmail</command> as MDA. - -</para><para> - -With the increasing popularity of graphical desktop systems, the use of -graphical e-mail programs like GNOME's <command>evolution</command>, -KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> -(in &debian; available as <command>icedove</command><footnote> - -<para> -The reason that <command>thunderbird</command> has been renamed to -<command>icedove</command> in &debian; has to do with licensing issues. -Details are outside the scope of this manual. -</para> - -</footnote>) is becoming more popular. These programs combine the function -of a MUA, MTA and MDA, but can — and often are — also be used -in combination with the traditional Linux tools. - -</para> - - <sect2 id="mail-default"> - <title>Default E-Mail Configuration</title> -<para> - -Even if you are planning to use a graphical mail program, it is important -that a traditional MTA/MDA is also installed and correctly set up on your -&debian-gnu; system. Reason is that various utilities running on the -system<footnote> - -<para> -Examples are: <command>cron</command>, <command>quota</command>, -<command>logcheck</command>, <command>aide</command>, … -</para> - -</footnote> can send important notices by e-mail to inform the system -administrator of (potential) problems or changes. - -</para><para> - -For this reason the packages <classname>exim4</classname> and -<classname>mutt</classname> will be installed by default (provided you -did not unselect the <quote>standard</quote> task during the installation). -<classname>exim4</classname> is a combination MTA/MDA that is relatively -small but very flexible. By default it will be configured to only handle -e-mail local to the system itself and e-mails addressed to the system -administrator (root account) will be delivered to the regular user account -created during the installation<footnote> - -<para> -The forwarding of mail for root to the regular user account is configured -in <filename>/etc/aliases</filename>. If no regular user account was created, -the mail will of course be delivered to the root account itself. -</para> - -</footnote>. - -</para><para> - -When system e-mails are delivered they are added to a file in -<filename>/var/mail/<replaceable>account_name</replaceable></filename>. -The e-mails can be read using <command>mutt</command>. - -</para> - </sect2> - - <sect2 id="mail-outgoing"> - <title>Sending E-Mails Outside The System</title> -<para> - -As mentioned earlier, the installed &debian; system is only set up to handle -e-mail local to the system, not for sending mail to others nor for -receiving mail from others. - -</para><para> - -If you would like <classname>exim4</classname> to handle external e-mail, -please refer to the next subsection for the basic available configuration -options. Make sure to test that mail can be sent and received correctly. - -</para><para> - -If you intend to use a graphical mail program and use a mail server of -your Internet Service Provider (ISP) or your company, there is not really -any need to configure <classname>exim4</classname> for handling external -e-mail. Just configure your favorite graphical mail program to use the -correct servers to send and receive e-mail (how is outside the scope of -this manual). - -</para><para> - -However, in that case you may need to configure individual utilities to -correctly send e-mails. One such utility is <command>reportbug</command>, -a program that facilitates submitting bug reports against &debian; packages. -By default it expects to be able to use <classname>exim4</classname> to -submit bug reports. - -</para><para> - -To correctly set up <command>reportbug</command> to use an external mail -server, please run the command <command>reportbug --configure</command> -and answer <quote>no</quote> to the question if an MTA is available. You -will then be asked for the SMTP server to be used for submitting bug reports. - -</para> - </sect2> - - <sect2 id="config-mta"> - <title>Configuring the Exim4 Mail Transport Agent</title> -<para> - -If you would like your system to also handle external e-mail, you will -need to reconfigure the <classname>exim4</classname> package<footnote> - -<para> -You can of course also remove <classname>exim4</classname> and replace -it with an alternative MTA/MDA. -</para> - -</footnote>: - -<informalexample><screen> -# dpkg-reconfigure exim4-config -</screen></informalexample> - -</para><para> - -After entering that command (as root), you will be asked if you want split -the configuration into small files. If you are unsure, select the default -option. - -</para><para> - -Next you will be presented with several common mail scenarios. Choose the -one that most closely resembles your needs. - -</para> - -<variablelist> -<varlistentry> -<term>internet site</term> -<listitem><para> - -Your system is connected to a network and your mail is sent and -received directly using SMTP. On the following screens you will be -asked a few basic questions, like your machine's mail name, or a list of -domains for which you accept or relay mail. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>mail sent by smarthost</term> -<listitem><para> - -In this scenario your outgoing mail is forwarded to another machine, -called a <quote>smarthost</quote>, which takes care of sending the message -on to its destination. -The smarthost also usually stores incoming mail addressed to your -computer, so you don't need to be permanently online. That also means -you have to download your mail from the smarthost via programs like -fetchmail. - -</para><para> - -In a lot of cases the smarthost will be your ISP's mail server, which -makes this option very suitable for dial-up users. It can also be a -company mail server, or even another system on your own network. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>mail sent by smarthost; no local mail</term> -<listitem><para> - -This option is basically the same as the previous one except that the -system will not be set up to handle mail for a local e-mail domain. Mail -on the system itself (e.g. for the system administrator) will still be -handled. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>local delivery only</term> -<listitem><para> - -This is the option your system is configured for by default. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>no configuration at this time</term> -<listitem><para> - -Choose this if you are absolutely convinced you know what you are -doing. This will leave you with an unconfigured mail system — -until you configure it, you won't be able to send or receive any mail -and you may miss some important messages from your system utilities. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -If none of these scenarios suits your needs, or if you need a finer -grained setup, you will need to edit configuration files under the -<filename>/etc/exim4</filename> directory after the installation is -complete. More information about <classname>exim4</classname> may be -found under <filename>/usr/share/doc/exim4</filename>; the file -<filename>README.Debian.gz</filename> has further details about -configuring <classname>exim4</classname> and explains where to find -additional documentation. - -</para><para> - -Note that sending mail directly to the Internet when you don't have an -official domain name, can result in your mail being rejected because of -anti-spam measures on receiving servers. Using your ISP's mail server is -preferred. If you still do want to send out mail directly, you may want to -use a different e-mail address than is generated by default. If you use -<classname>exim4</classname> as your MTA, this is possible by adding an -entry in <filename>/etc/email-addresses</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/new-to-unix.xml b/nl/post-install/new-to-unix.xml deleted file mode 100644 index e235f3757..000000000 --- a/nl/post-install/new-to-unix.xml +++ /dev/null @@ -1,29 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - - - <sect1 id="unix-intro"> - <title>If You Are New to Unix</title> -<para> - -If you are new to Unix, you probably should go out and buy some books -and do some reading. A lot of valuable information can also be found -in the <ulink url="&url-debian-reference;">Debian Reference</ulink>. -This <ulink url="&url-unix-faq;">list of Unix FAQs</ulink> contains a -number of UseNet documents which provide a nice historical reference. - -</para><para arch="linux-any"> - -Linux is an implementation of Unix. The -<ulink url="&url-ldp;">Linux Documentation Project (LDP)</ulink> -collects a number of HOWTOs and online books -relating to Linux. Most of these documents can be installed locally; -just install the <classname>doc-linux-html</classname> package (HTML -versions) or the <classname>doc-linux-text</classname> package (ASCII -versions), then look in <filename>/usr/share/doc/HOWTO</filename>. -International versions of the LDP HOWTOs are also available as &debian; -packages. - -</para> - - </sect1> diff --git a/nl/post-install/orientation.xml b/nl/post-install/orientation.xml deleted file mode 100644 index 50283724b..000000000 --- a/nl/post-install/orientation.xml +++ /dev/null @@ -1,109 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43576 untranslated --> - - - <sect1 id="debian-orientation"><title>Orienting Yourself to &debian;</title> -<para> - -&debian; is a little different from other distributions. Even if you're -familiar with Linux in other distributions, there are things you -should know about &debian; to help you to keep your system in a good, -clean state. This chapter contains material to help you get oriented; -it is not intended to be a tutorial for how to use &debian;, but just a -very brief glimpse of the system for the very rushed. - -</para> - - <sect2><title>&debian; Packaging System</title> -<para> - -The most important concept to grasp is the &debian; packaging system. -In essence, large parts of your system should be considered under the -control of the packaging system. These include: - -<itemizedlist> -<listitem><para> - -<filename>/usr</filename> (excluding <filename>/usr/local</filename>) - -</para></listitem> -<listitem><para> - -<filename>/var</filename> (you could make -<filename>/var/local</filename> and be safe in there) - -</para></listitem> -<listitem><para> - -<filename>/bin</filename> - -</para></listitem> -<listitem><para> - -<filename>/sbin</filename> - -</para></listitem> -<listitem><para> - -<filename>/lib</filename> - -</para></listitem> -</itemizedlist> - -For instance, if you replace <filename>/usr/bin/perl</filename>, that -will work, but then if you upgrade your <classname>perl</classname> -package, the file you put there will be replaced. Experts can get -around this by putting packages on <quote>hold</quote> in -<command>aptitude</command>. - -</para><para> - -One of the best installation methods is apt. You can use the command -line version <command>apt-get</command> or full-screen text version -<application>aptitude</application>. Note apt will also let you merge -main, contrib, and non-free so you can have export-restricted packages -as well as standard versions. - -</para> - </sect2> - - <sect2><title>Application Version Management</title> -<para> - - -Alternative versions of applications are managed by update-alternatives. If -you are maintaining multiple versions of your applications, read the -update-alternatives man page. - -</para> - </sect2> - - <sect2><title>Cron Job Management</title> -<para> - -Any jobs under the purview of the system administrator should be in -<filename>/etc</filename>, since they are configuration files. If you -have a root cron job for daily, weekly, or monthly runs, put them in -<filename>/etc/cron.{daily,weekly,monthly}</filename>. These are -invoked from <filename>/etc/crontab</filename>, and will run in -alphabetic order, which serializes them. - -</para><para> - -On the other hand, if you have a cron job that (a) needs to run as a -special user, or (b) needs to run at a special time or frequency, you -can use either <filename>/etc/crontab</filename>, or, better yet, -<filename>/etc/cron.d/whatever</filename>. These particular files -also have an extra field that allows you to stipulate the user account -under which the cron job runs. - -</para><para> - -In either case, you just edit the files and cron will notice them -automatically. There is no need to run a special command. For more -information see cron(8), crontab(5), and -<filename>/usr/share/doc/cron/README.Debian</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/post-install.xml b/nl/post-install/post-install.xml deleted file mode 100644 index 95eca7933..000000000 --- a/nl/post-install/post-install.xml +++ /dev/null @@ -1,15 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43623 untranslated --> - -<chapter id="post-install"> - <title>Next Steps and Where to Go From Here</title> - -&shutdown.xml; -&new-to-unix.xml; -&orientation.xml; -&further-reading.xml; -&mail-setup.xml; -&kernel-baking.xml; -&rescue.xml; - -</chapter> diff --git a/nl/post-install/rescue.xml b/nl/post-install/rescue.xml deleted file mode 100644 index 5517b5e2d..000000000 --- a/nl/post-install/rescue.xml +++ /dev/null @@ -1,71 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - - <sect1 id="rescue"> - <title>Recovering a Broken System</title> -<para> - -Sometimes, things go wrong, and the system you've carefully installed is no -longer bootable. Perhaps the boot loader configuration broke while trying -out a change, or perhaps a new kernel you installed won't boot, or perhaps -cosmic rays hit your disk and flipped a bit in -<filename>/sbin/init</filename>. Regardless of the cause, you'll need to -have a system to work from while you fix it, and rescue mode can be useful -for this. - -</para><para> - -<!-- TODO: describe what to do on arches where this isn't set up in the - bootloader --> - -To access rescue mode, type <userinput>rescue</userinput> at the -<prompt>boot:</prompt> prompt, or boot with the -<userinput>rescue/enable=true</userinput> boot parameter. You'll be shown -the first few screens of the installer, with a note in the corner of the -display to indicate that this is rescue mode, not a full installation. Don't -worry, your system is not about to be overwritten! Rescue mode simply takes -advantage of the hardware detection facilities available in the installer to -ensure that your disks, network devices, and so on are available to you -while repairing your system. - -</para><para> - -Instead of the partitioning tool, you should now be presented with a list of -the partitions on your system, and asked to select one of them. Normally, -you should select the partition containing the root file system that you -need to repair. You may select partitions on RAID and LVM devices as well as -those created directly on disks. - -</para><para> - -If possible, the installer will now present you with a shell prompt in the -file system you selected, which you can use to perform any necessary -repairs. - -<phrase arch="any-x86"> -For example, if you need to reinstall the GRUB boot loader into the master -boot record of the first hard disk, you could enter the command -<userinput>grub-install '(hd0)'</userinput> to do so. -</phrase> - -</para><para> - -If the installer cannot run a usable shell in the root file system you -selected, perhaps because the file system is corrupt, then it will issue a -warning and offer to give you a shell in the installer environment instead. -You may not have as many tools available in this environment, but they will -often be enough to repair your system anyway. The root file system you -selected will be mounted on the <filename>/target</filename> directory. - -</para><para> - -In either case, after you exit the shell, the system will reboot. - -</para><para> - -Finally, note that repairing broken systems can be difficult, and this -manual does not attempt to go into all the things that might have gone wrong -or how to fix them. If you have problems, consult an expert. - -</para> - </sect1> diff --git a/nl/post-install/shutdown.xml b/nl/post-install/shutdown.xml deleted file mode 100644 index e71db46d4..000000000 --- a/nl/post-install/shutdown.xml +++ /dev/null @@ -1,31 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - - <sect1 id="shutdown"> - <title>Shutting down the system</title> - -<para> - -To shut down a running &debian-gnu; system, you must not reboot with the -reset switch on the front or back of your computer, or just turn off -the computer. &debian-gnu; should be shut down in a controlled manner, -otherwise files might get lost and/or disk damage might occur. If you run a -desktop environment, there is usually an option to <quote>log out</quote> -available from the application menu that allows you to shutdown (or reboot) -the system. - -</para><para> - -Alternatively you can press the key combination <keycombo> -<keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> -<phrase arch="powerpc"> or <keycombo> <keycap>Control</keycap> -<keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh -systems</phrase>. A last option is to log in as root and type one of the -commands <command>poweroff</command>, <command>halt</command> or -<command>shutdown -h now</command> if either of the key combinations do not -work or you prefer to type commands; use <command>reboot</command> to reboot -the system. - -</para> - </sect1> |