diff options
Diffstat (limited to 'po/pot/post-install.pot')
| -rw-r--r-- | po/pot/post-install.pot | 46 |
1 files changed, 23 insertions, 23 deletions
diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 378d5423f..5378e5a82 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -236,118 +236,118 @@ msgstr "" #: post-install.xml:328 #, no-c-format #. Tag: para -msgid "To compile a kernel the Debian way, you need some packages: <classname>kernel-package</classname>, <classname>kernel-source-&kernelversion;</classname> (the most recent version at the time of this writing), <classname>fakeroot</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)." +msgid "To compile a kernel the Debian way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname> (the most recent version at the time of this writing)</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></phrase> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list)." msgstr "" -#: post-install.xml:338 +#: post-install.xml:339 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:346 +#: post-install.xml:347 #, no-c-format #. Tag: para -msgid "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>kernel-source-&kernelversion;</classname>, yet still use the <classname>kernel-package</classname> compilation method." +msgid "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 <phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> yet still use the <classname>kernel-package</classname> compilation method." msgstr "" -#: post-install.xml:355 +#: post-install.xml:357 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:362 +#: post-install.xml:364 #, no-c-format #. Tag: para -msgid "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/kernel-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>kernel-source-&kernelversion;</filename> that will have been created." +msgid "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 <phrase condition=\"classic-kpkg\">/usr/src/kernel-source-&kernelversion;.tar.bz2</phrase> <phrase condition=\"common-kpkg\">/usr/src/linux-source-&kernelversion;.tar.bz2</phrase></userinput> and change to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg\"><filename>linux-source-&kernelversion;</filename></phrase> that will have been created." msgstr "" -#: post-install.xml:382 +#: post-install.xml:387 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:397 +#: post-install.xml:402 #, no-c-format #. Tag: para msgid "Clean the source tree and reset the <classname>kernel-package</classname> parameters. To do that, do <userinput>make-kpkg clean</userinput>." msgstr "" -#: post-install.xml:402 +#: post-install.xml:407 #, no-c-format #. Tag: para msgid "Now, compile the kernel: <userinput>fakeroot make-kpkg --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." msgstr "" -#: post-install.xml:412 +#: post-install.xml:417 #, no-c-format #. Tag: para msgid "If you require PCMCIA support, you'll also need to install the <classname>pcmcia-source</classname> package. Unpack the gzipped tar file as root in the directory <filename>/usr/src</filename> (it's important that modules are found where they are expected to be found, namely, <filename>/usr/src/modules</filename>). Then, as root, do <userinput>make-kpkg modules_image</userinput>." msgstr "" -#: post-install.xml:421 +#: post-install.xml:426 #, no-c-format #. Tag: para msgid "Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../kernel-image-&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>i586</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i kernel-image...</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 <classname>kernel-image-&kernelversion;</classname> package is also clever enough to automatically use your platform's boot-loader to run an update on the booting, allowing you to boot without re-running the boot loader. If you have created a modules package, e.g., if you have PCMCIA, you'll need to install that package as well." msgstr "" -#: post-install.xml:442 +#: post-install.xml:447 #, no-c-format #. Tag: para msgid "It is time to reboot the system: read carefully any warning that the above step may have produced, then <userinput>shutdown -r now</userinput>." msgstr "" -#: post-install.xml:447 +#: post-install.xml:452 #, no-c-format #. Tag: para -msgid "For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>." +msgid "<phrase condition=\"etch\">For more information on Debian kernels and kernel compilation, see the <ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>.</phrase> For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>." msgstr "" -#: post-install.xml:461 +#: post-install.xml:469 #, no-c-format #. Tag: title msgid "Recovering a Broken System" msgstr "" -#: post-install.xml:462 +#: post-install.xml:470 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:472 +#: post-install.xml:480 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:487 +#: post-install.xml:495 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:495 +#: post-install.xml:503 #, no-c-format #. Tag: para msgid "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=\"i386\"> 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>" msgstr "" -#: post-install.xml:507 +#: post-install.xml:515 #, no-c-format #. Tag: para msgid "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." msgstr "" -#: post-install.xml:516 +#: post-install.xml:524 #, no-c-format #. Tag: para msgid "In either case, after you exit the shell, the system will reboot." msgstr "" -#: post-install.xml:520 +#: post-install.xml:528 #, no-c-format #. Tag: para msgid "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." |