From ed6969127b0443024bc139b6b370e02e86eca9f6 Mon Sep 17 00:00:00 2001 From: Holger Wansing Date: Sun, 17 Jan 2021 23:13:12 +0100 Subject: New translation effort announced for Kabyle. Added po files (copied from templates pot files) --- po/kab/boot-new.po | 419 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 419 insertions(+) create mode 100644 po/kab/boot-new.po (limited to 'po/kab/boot-new.po') diff --git a/po/kab/boot-new.po b/po/kab/boot-new.po new file mode 100644 index 000000000..89049c99c --- /dev/null +++ b/po/kab/boot-new.po @@ -0,0 +1,419 @@ +# Translation of the Debian installation-guide into Kabyle. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: debian-installation-guide-boot-new 2021\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2020-04-02 09:22+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: boot-new.xml:5 +#, no-c-format +msgid "Booting Into Your New &debian; System" +msgstr "" + +#. Tag: title +#: boot-new.xml:7 +#, no-c-format +msgid "The Moment of Truth" +msgstr "" + +#. Tag: para +#: boot-new.xml:8 +#, no-c-format +msgid "" +"Your system's first boot on its own power is what electrical engineers call " +"the smoke test." +msgstr "" + +#. Tag: para +#: boot-new.xml:13 +#, no-c-format +msgid "" +"If you did a default installation, the first thing you should see when you " +"boot the system is the menu of the grub bootloader. " +"The first choices in the menu will be for your new &debian; system. If you " +"had any other operating systems on your computer (like Windows) that were " +"detected by the installation system, those will be listed lower down in the " +"menu." +msgstr "" + +#. Tag: para +#: boot-new.xml:23 +#, no-c-format +msgid "" +"If the system fails to start up correctly, don't panic. If the installation " +"was successful, chances are good that there is only a relatively minor " +"problem that is preventing the system from booting &debian;. In most cases " +"such problems can be fixed without having to repeat the installation. One " +"available option to fix boot problems is to use the installer's built-in " +"rescue mode (see )." +msgstr "" + +#. Tag: para +#: boot-new.xml:32 +#, no-c-format +msgid "" +"If you are new to &debian; and &arch-kernel;, you may need some help from " +"more experienced users. For direct on-line help you can " +"try the IRC channels #debian or #debian-boot on the OFTC network. " +"Alternatively you can contact the debian-" +"user mailing list. For less common " +"architectures like &arch-title;, your best option is to ask on the debian-&arch-listname; mailing list. You can also file an installation report as described in . Please make sure that you describe your problem " +"clearly and include any messages that are displayed and may help others to " +"diagnose the issue." +msgstr "" + +#. Tag: para +#: boot-new.xml:48 +#, no-c-format +msgid "" +"If you had any other operating systems on your computer that were not " +"detected or not detected correctly, please file an installation report." +msgstr "" + +#. Tag: title +#: boot-new.xml:56 +#, no-c-format +msgid "OldWorld PowerMacs" +msgstr "" + +#. Tag: para +#: boot-new.xml:57 +#, no-c-format +msgid "" +"If the machine fails to boot after completing the installation, and stops " +"with a boot: prompt, try typing Linux followed by &enterkey;. (The default boot configuration in " +"quik.conf is labeled Linux). The labels defined in " +"quik.conf will be displayed if you press the " +"Tab key at the boot: prompt. You can also " +"try booting back into the installer, and editing the /target/etc/" +"quik.conf placed there by the Install Quik on a Hard " +"Disk step. Clues for dealing with quik are " +"available at ." +msgstr "" + +#. Tag: para +#: boot-new.xml:71 +#, no-c-format +msgid "" +"To boot back into MacOS without resetting the nvram, type bye at the OpenFirmware prompt (assuming MacOS has not been removed " +"from the machine). To obtain an OpenFirmware prompt, hold down the " +" command option o f keys while cold booting the machine. " +"If you need to reset the OpenFirmware nvram changes to the MacOS default in " +"order to boot back to MacOS, hold down the command option p r keys while cold booting the machine." +msgstr "" + +#. Tag: para +#: boot-new.xml:84 +#, no-c-format +msgid "" +"If you use BootX to boot into the installed system, just " +"select your desired kernel in the Linux Kernels folder, " +"un-choose the ramdisk option, and add a root device corresponding to your " +"installation; e.g. /dev/sda8." +msgstr "" + +#. Tag: title +#: boot-new.xml:96 +#, no-c-format +msgid "NewWorld PowerMacs" +msgstr "" + +#. Tag: para +#: boot-new.xml:97 +#, no-c-format +msgid "" +"On G4 machines and iBooks, you can hold down the option key " +"and get a graphical screen with a button for each bootable OS, &debian-gnu; " +"will be a button with a small penguin icon." +msgstr "" + +#. Tag: para +#: boot-new.xml:104 +#, no-c-format +msgid "" +"If you kept MacOS and at some point it changes the OpenFirmware boot-" +"device variable you should reset OpenFirmware to its default " +"configuration. To do this hold down the command " +"option p r " +"keys while cold booting the machine." +msgstr "" + +#. Tag: para +#: boot-new.xml:112 +#, no-c-format +msgid "" +"The labels defined in yaboot.conf will be displayed if " +"you press the Tab key at the boot: prompt." +msgstr "" + +#. Tag: para +#: boot-new.xml:118 +#, no-c-format +msgid "" +"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian-" +"gnu; by default (if you correctly partitioned and placed the Apple_Bootstrap " +"partition first). If you have &debian-gnu; on a SCSI disk and MacOS on an " +"IDE disk this may not work and you will have to enter OpenFirmware and set " +"the boot-device variable, ybin normally " +"does this automatically." +msgstr "" + +#. Tag: para +#: boot-new.xml:127 +#, no-c-format +msgid "" +"After you boot &debian-gnu; for the first time you can add any additional " +"options you desire (such as dual boot options) to /etc/yaboot." +"conf and run ybin to update your boot " +"partition with the changed configuration. Please read the yaboot HOWTO for more information." +msgstr "" + +#. Tag: title +#: boot-new.xml:145 +#, no-c-format +msgid "Mounting encrypted volumes" +msgstr "" + +#. Tag: para +#: boot-new.xml:147 +#, no-c-format +msgid "" +"If you created encrypted volumes during the installation and assigned them " +"mount points, you will be asked to enter the passphrase for each of these " +"volumes during the boot." +msgstr "" + +#. Tag: para +#: boot-new.xml:155 +#, no-c-format +msgid "" +"For partitions encrypted using dm-crypt you will be shown the following " +"prompt during the boot: \n" +"Starting early crypto disks... part_crypt(starting)\n" +"Enter LUKS passphrase:\n" +" In the first line of the prompt, " +"part is the name of the underlying partition, e." +"g. sda2 or md0. You are now probably wondering for which volume you are actually entering the passphrase. Does it relate to your " +"/home? Or to /var? Of course, if " +"you have just one encrypted volume, this is easy and you can just enter the " +"passphrase you used when setting up this volume. If you set up more than one " +"encrypted volume during the installation, the notes you wrote down as the " +"last step in come in handy. If you did " +"not make a note of the mapping between part_crypt and the mount points before, you can still " +"find it in /etc/crypttab and /etc/fstab of your new system." +msgstr "" + +#. Tag: para +#: boot-new.xml:178 +#, no-c-format +msgid "" +"The prompt may look somewhat different when an encrypted root file system is " +"mounted. This depends on which initramfs generator was used to generate the " +"initrd used to boot the system. The example below is for an initrd generated " +"using initramfs-tools:" +msgstr "" + +#. Tag: screen +#: boot-new.xml:185 +#, no-c-format +msgid "" +"Begin: Mounting root file system... ...\n" +"Begin: Running /scripts/local-top ...\n" +"Enter LUKS passphrase:" +msgstr "" + +#. Tag: para +#: boot-new.xml:187 +#, no-c-format +msgid "" +"No characters (even asterisks) will be shown while entering the passphrase. " +"If you enter the wrong passphrase, you have two more tries to correct it. " +"After the third try the boot process will skip this volume and continue to " +"mount the next filesystem. Please see for further information." +msgstr "" + +#. Tag: para +#: boot-new.xml:195 +#, no-c-format +msgid "After entering all passphrases the boot should continue as usual." +msgstr "" + +#. Tag: title +#: boot-new.xml:202 +#, no-c-format +msgid "Troubleshooting" +msgstr "" + +#. Tag: para +#: boot-new.xml:204 +#, no-c-format +msgid "" +"If some of the encrypted volumes could not be mounted because a wrong " +"passphrase was entered, you will have to mount them manually after the boot. " +"There are several cases." +msgstr "" + +#. Tag: para +#: boot-new.xml:213 +#, no-c-format +msgid "" +"The first case concerns the root partition. When it is not mounted " +"correctly, the boot process will halt and you will have to reboot the " +"computer to try again." +msgstr "" + +#. Tag: para +#: boot-new.xml:220 +#, no-c-format +msgid "" +"The easiest case is for encrypted volumes holding data like /home or /srv. You can simply mount them manually " +"after the boot." +msgstr "" + +#. Tag: para +#: boot-new.xml:226 +#, no-c-format +msgid "" +"However for dm-crypt this is a bit tricky. First you need to register the " +"volumes with device mapper by running: " +"\n" +"# /etc/init.d/cryptdisks start\n" +" This will scan all volumes mentioned in " +"/etc/crypttab and will create appropriate devices under " +"the /dev directory after entering the correct " +"passphrases. (Already registered volumes will be skipped, so you can repeat " +"this command several times without worrying.) After successful registration " +"you can simply mount the volumes the usual way:" +msgstr "" + +#. Tag: screen +#: boot-new.xml:241 +#, no-c-format +msgid "" +"# mount /mount_point" +msgstr "" + +#. Tag: para +#: boot-new.xml:244 +#, no-c-format +msgid "" +"If any volume holding noncritical system files could not be mounted " +"(/usr or /var), the system should " +"still boot and you should be able to mount the volumes manually like in the " +"previous case. However, you will also need to (re)start any services usually " +"running in your default runlevel because it is very likely that they were " +"not started. The easiest way is to just reboot the computer." +msgstr "" + +#. Tag: title +#: boot-new.xml:262 +#, no-c-format +msgid "Log In" +msgstr "" + +#. Tag: para +#: boot-new.xml:264 +#, no-c-format +msgid "" +"Once your system boots, you'll be presented with the login prompt. Log in " +"using the personal login and password you selected during the installation " +"process. Your system is now ready for use." +msgstr "" + +#. Tag: para +#: boot-new.xml:270 +#, no-c-format +msgid "" +"If you are a new user, you may want to explore the documentation which is " +"already installed on your system as you start to use it. There are currently " +"several documentation systems, work is proceeding on integrating the " +"different types of documentation. Here are a few starting points." +msgstr "" + +#. Tag: para +#: boot-new.xml:278 +#, no-c-format +msgid "" +"Documentation accompanying programs you have installed can be found in " +"/usr/share/doc/, under a subdirectory named after the " +"program (or, more precise, the &debian; package that contains the program). " +"However, more extensive documentation is often packaged separately in " +"special documentation packages that are mostly not installed by default. For " +"example, documentation about the package management tool apt can be found in the packages apt-doc or " +"apt-howto." +msgstr "" + +#. Tag: para +#: boot-new.xml:289 +#, no-c-format +msgid "" +"In addition, there are some special folders within the /usr/share/" +"doc/ hierarchy. Linux HOWTOs are installed in .gz (compressed) format, in /usr/share/doc/HOWTO/en-txt/. After installing dhelp, you will find a " +"browsable index of documentation in /usr/share/doc/HTML/index." +"html." +msgstr "" + +#. Tag: para +#: boot-new.xml:298 +#, no-c-format +msgid "" +"One easy way to view these documents using a text based browser is to enter " +"the following commands: \n" +"$ cd /usr/share/doc/\n" +"$ w3m .\n" +" The dot after the w3m command " +"tells it to show the contents of the current directory." +msgstr "" + +#. Tag: para +#: boot-new.xml:308 +#, no-c-format +msgid "" +"If you have a graphical desktop environment installed, you can also use its " +"web browser. Start the web browser from the application menu and enter " +"/usr/share/doc/ in the address bar." +msgstr "" + +#. Tag: para +#: boot-new.xml:314 +#, no-c-format +msgid "" +"You can also type info command or man command " +"to see documentation on most commands available at the command prompt. " +"Typing help will display help on shell commands. And " +"typing a command followed by --help will usually " +"display a short summary of the command's usage. If a command's results " +"scroll past the top of the screen, type | more " +"after the command to cause the results to pause before scrolling past the " +"top of the screen. To see a list of all commands available which begin with " +"a certain letter, type the letter and then two tabs." +msgstr "" -- cgit v1.2.3