From e309be1887f3b66c789fb1cf7e062bee558f42bf Mon Sep 17 00:00:00 2001 From: D-I role Date: Sun, 29 Jul 2018 08:28:03 +0000 Subject: [SILENT_COMMIT] Update of POT and PO files for the installation-guide --- po/ro/post-install.po | 213 ++++---------------------------------------------- 1 file changed, 17 insertions(+), 196 deletions(-) (limited to 'po/ro/post-install.po') diff --git a/po/ro/post-install.po b/po/ro/post-install.po index ca5014a70..1132fb3fd 100644 --- a/po/ro/post-install.po +++ b/po/ro/post-install.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: d-i-manual_post-install\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2017-07-13 22:22+0000\n" +"POT-Creation-Date: 2018-07-29 08:27+0000\n" "PO-Revision-Date: 2016-04-08 20:25+0000\n" "Last-Translator: NAME \n" "Language-Team: Romanian \n" @@ -592,208 +592,29 @@ msgstr "" #: post-install.xml:521 #, no-c-format msgid "" -"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:" +"Why would someone want to compile a new kernel? It is most probably not " +"necessary since the default kernel shipped with &debian; handles almost all " +"configurations." msgstr "" #. Tag: para -#: post-install.xml:531 +#: post-install.xml:527 #, no-c-format msgid "" -"handle special hardware needs, or hardware conflicts with the pre-supplied " -"kernels" -msgstr "" - -#. Tag: para -#: post-install.xml:537 -#, no-c-format -msgid "" -"use options of the kernel which are not supported in the pre-supplied " -"kernels (such as high memory support)" -msgstr "" - -#. Tag: para -#: post-install.xml:543 -#, no-c-format -msgid "optimize the kernel by removing useless drivers to speed up boot time" -msgstr "" - -#. Tag: para -#: post-install.xml:548 -#, no-c-format -msgid "create a monolithic instead of a modularized kernel" -msgstr "" - -#. Tag: para -#: post-install.xml:553 -#, no-c-format -msgid "run an updated or development kernel" -msgstr "" - -#. Tag: para -#: post-install.xml:558 -#, no-c-format -msgid "learn more about linux kernels" -msgstr "" - -#. Tag: title -#: post-install.xml:567 -#, no-c-format -msgid "Kernel Image Management" -msgstr "" - -#. Tag: para -#: post-install.xml:568 -#, no-c-format -msgid "Don't be afraid to try compiling the kernel. It's fun and profitable." -msgstr "" - -#. Tag: para -#: post-install.xml:572 -#, no-c-format -msgid "" -"To compile a kernel the &debian; way, you need some packages: " -"fakeroot, kernel-package, " -"linux-source-2.6 and a few others which are probably " -"already installed (see /usr/share/doc/kernel-package/README.gz for the complete list)." -msgstr "" - -#. Tag: para -#: post-install.xml:581 -#, no-c-format -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; /boot will hold the " -"kernel, the System.map, and a log of the active config file for the build." -msgstr "" - -#. Tag: para -#: post-install.xml:589 -#, no-c-format -msgid "" -"Note that you don't have to compile your kernel the " -"&debian; way; 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 linux-source-2.6, yet still use the kernel-package " -"compilation method." -msgstr "" - -#. Tag: para -#: post-install.xml:598 -#, no-c-format -msgid "" -"Note that you'll find complete documentation on using kernel-" -"package under /usr/share/doc/kernel-package. This section just contains a brief tutorial." -msgstr "" - -#. Tag: para -#: post-install.xml:605 -#, no-c-format -msgid "" -"Hereafter, we'll assume you have free rein over your machine and will " -"extract your kernel source to somewhere in your home directory " -" 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. . 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 tar xf /usr/src/" -"linux-source-&kernelversion;.tar.xz and change to the directory " -"linux-source-&kernelversion; that will have been " -"created." -msgstr "" - -#. Tag: para -#: post-install.xml:625 -#, no-c-format -msgid "" -"Now, you can configure your kernel. Run make xconfig " -"if X11 is installed, configured and being run; run make " -"menuconfig otherwise (you'll need libncurses5-dev 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 Kernel " -"module loader in Loadable module support (it is not " -"selected by default). If not included, your &debian; installation will " -"experience problems." -msgstr "" - -#. Tag: para -#: post-install.xml:640 -#, no-c-format -msgid "" -"Clean the source tree and reset the kernel-package " -"parameters. To do that, do make-kpkg clean." -msgstr "" - -#. Tag: para -#: post-install.xml:645 -#, no-c-format -msgid "" -"Now, compile the kernel: fakeroot make-kpkg --initrd --" -"revision=1.0.custom kernel_image. The version number of " -"1.0 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 custom (e.g., a host name). Kernel " -"compilation may take quite a while, depending on the power of your machine." -msgstr "" - -#. Tag: para -#: post-install.xml:655 -#, no-c-format -msgid "" -"Once the compilation is complete, you can install your custom kernel like " -"any package. As root, do dpkg -i ../&kernelpackage;-" -"&kernelversion;-subarchitecture_1.0." -"custom_&architecture;.deb. The subarchitecture part is an optional sub-architecture, " -"such as 686, depending on what kernel options you " -"set. dpkg -i will install the kernel, along with some " -"other nice supporting files. For instance, the System.map will be properly installed (helpful for debugging kernel " -"problems), and /boot/config-&kernelversion; 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." -msgstr "" - -#. Tag: para -#: post-install.xml:675 -#, no-c-format -msgid "" -"It is time to reboot the system: read carefully any warning that the above " -"step may have produced, then shutdown -r now." -msgstr "" - -#. Tag: para -#: post-install.xml:680 -#, no-c-format -msgid "" -"For more information on &debian; kernels and kernel compilation, see the " -"Debian Linux Kernel Handbook. " -"For more information on kernel-package, read the fine " -"documentation in /usr/share/doc/kernel-package." +"If you want to compile your own kernel nevertheless, this is of course " +"possible and we recommend the use of the make deb-pkg target. " +"For more information read the Debian " +"Linux Kernel Handbook." msgstr "" #. Tag: title -#: post-install.xml:696 +#: post-install.xml:542 #, no-c-format msgid "Recovering a Broken System" msgstr "" #. Tag: para -#: post-install.xml:697 +#: post-install.xml:543 #, no-c-format msgid "" "Sometimes, things go wrong, and the system you've carefully installed is no " @@ -805,7 +626,7 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:707 +#: post-install.xml:553 #, no-c-format msgid "" "To access rescue mode, select rescue from the boot " @@ -820,7 +641,7 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:724 +#: post-install.xml:570 #, no-c-format msgid "" "Instead of the partitioning tool, you should now be presented with a list of " @@ -831,7 +652,7 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:732 +#: post-install.xml:578 #, no-c-format msgid "" "If possible, the installer will now present you with a shell prompt in the " @@ -843,7 +664,7 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:744 +#: post-install.xml:590 #, no-c-format msgid "" "If the installer cannot run a usable shell in the root file system you " @@ -855,13 +676,13 @@ msgid "" msgstr "" #. Tag: para -#: post-install.xml:753 +#: post-install.xml:599 #, no-c-format msgid "In either case, after you exit the shell, the system will reboot." msgstr "" #. Tag: para -#: post-install.xml:757 +#: post-install.xml:603 #, no-c-format msgid "" "Finally, note that repairing broken systems can be difficult, and this " -- cgit v1.2.3