Index: trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_copyhowto.po =================================================================== --- trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_copyhowto.po (nonexistent) +++ trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_copyhowto.po (revision 1540364) @@ -0,0 +1,108 @@ +# +# Alexander Potashev , 2019. +msgid "" +msgstr "" +"Project-Id-Version: \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2014-04-28 02:12+0000\n" +"PO-Revision-Date: 2019-04-22 13:45+0300\n" +"Last-Translator: Alexander Potashev \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"X-Generator: Lokalize 18.12.2\n" + +#. Tag: title +#: copyhowto.docbook:2 +#, no-c-format +msgid "How-To: Copying a Partition" +msgstr "Инструкция: копирование раздела" + +#. Tag: para +#: copyhowto.docbook:4 +#, no-c-format +msgid "" +"This how-to describes copying a partition. We will assume the intention is to " +"copy a partition from one device to another and overwriting an existing" +" target " +"partition, but the general procedure would not be much different when copying " +"to the same device or to some unallocated area." +msgstr "" + +#. Tag: para +#: copyhowto.docbook:8 +#, no-c-format +msgid "The following screenshot shows how the source device looks like:" +msgstr "" + +#. Tag: phrase +#: copyhowto.docbook:16 +#, no-c-format +msgid "Main window with source device" +msgstr "" + +#. Tag: para +#: copyhowto.docbook:21 +#, no-c-format +msgid "" +"The source partition in our example will be sdb1 " +"which is currently mounted, indicated by the lock-icon next to the mount" +" point " +"name in the screen shot. A mounted partition can not be copied, thus you" +" first " +"need to unmount it: Click on it then select ." +msgstr "" + +#. Tag: para +#: copyhowto.docbook:25 +#, no-c-format +msgid "" +"After unmounting the partition the lock icon has gone and it is now possible" +" to " +"select . This puts sdb1 " +"in &partman;'s clipboard; in other words: sdb1 " +"is now the partition that will be inserted when you select ." +msgstr "" + +#. Tag: para +#: copyhowto.docbook:29 +#, no-c-format +msgid "" +"The destination device for copying in this how-to is /dev/sdc" +". Click on it in the Devices panel. This is how the device looks like before " +"copying:" +msgstr "" + +#. Tag: phrase +#: copyhowto.docbook:37 +#, no-c-format +msgid "Main window with destination device before copying" +msgstr "" + +#. Tag: para +#: copyhowto.docbook:42 +#, no-c-format +msgid "" +"The partition to overwrite is sdc5. To paste the copied " +"partition into it, click on it and select . You will see the operation to copy the " +"partition has been added to the list of pending operations. Note that there" +" is " +"no dialog box required to insert the partition as would be the case if you " +"pasted into an unallocated area: Beginning and end of the pasted partition" +" are " +"determined by the overwritten partition." +msgstr "" + +#. Tag: para +#: copyhowto.docbook:46 +#, no-c-format +msgid "" +"Now select and the partition will be " +"copied. See the " +"how-to on resizing partitions for details about applying operations." +msgstr "" Index: trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_faq.po =================================================================== --- trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_faq.po (nonexistent) +++ trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_faq.po (revision 1540364) @@ -0,0 +1,321 @@ +# +# Alexander Potashev , 2019. +msgid "" +msgstr "" +"Project-Id-Version: \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2016-12-04 02:03+0000\n" +"PO-Revision-Date: 2019-04-22 13:45+0300\n" +"Last-Translator: Alexander Potashev \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"X-Generator: Lokalize 18.12.2\n" + +#. Tag: title +#: faq.docbook:2 +#, no-c-format +msgid "Questions and Answers" +msgstr "Вопросы и ответы" + +#. Tag: para +#: faq.docbook:7 +#, no-c-format +msgid "How dangerous is &partman; for my data?" +msgstr "" + +#. Tag: para +#: faq.docbook:10 +#, no-c-format +msgid "" +"First of all, you should never perform any destructive operations (delete, " +"move, resize) without first making a complete backup of everything affected." +msgstr "" + +#. Tag: para +#: faq.docbook:13 +#, no-c-format +msgid "" +"Having said that, &partman; is safe to use. It performs extensive checks" +" before " +"and after every operation. It calls external tools written and supported by" +" the " +"file system authors. And it has been tested extensively." +msgstr "" + +#. Tag: para +#: faq.docbook:16 +#, no-c-format +msgid "" +"There is always the risk of data loss due to an unknown bug. &partman;'s " +"authors try to minimize this risk, but there are of course no guarantees." +msgstr "" + +#. Tag: para +#: faq.docbook:23 +#, no-c-format +msgid "" +"I have installed all recommended external file system support packages and " +"still do not get support for all operations on all file systems." +msgstr "" + +#. Tag: para +#: faq.docbook:26 +#, no-c-format +msgid "" +"Not everything &partman; can do in principle can be done with all file" +" systems." +msgstr "" + +#. Tag: para +#: faq.docbook:29 +#, no-c-format +msgid "" +"One example is performing a file system check on linuxswap: It is just not " +"possible. There are other limitations like that inherent in some file" +" systems. " +"You cannot shrink JFS or XFS file systems because neither of the two supports " +"shrinking at all, with or without &partman;." +msgstr "" + +#. Tag: para +#: faq.docbook:36 +#, no-c-format +msgid "" +"Why can't I see any meaningful progress information when resizing a partition?" +msgstr "" + +#. Tag: para +#: faq.docbook:39 +#, no-c-format +msgid "" +"&partman; can only show progress information when it knows how long the jobs" +" in " +"an operation will take. Unfortunately this is usually not the case when " +"resizing partitions because the by far longest job when doing so is resizing " +"the file system on the partition. Resizing file systems is in most cases " +"something an external tool will do on behalf of &partman; and these external " +"tools do not provide useful progress information to &partman;, so there's " +"nothing to report while they are running." +msgstr "" + +#. Tag: para +#: faq.docbook:46 +#, no-c-format +msgid "" +"Why can't I resize the root partition? How can I resize the partition /home" +" is " +"on?" +msgstr "" + +#. Tag: para +#: faq.docbook:49 +#, no-c-format +msgid "" +"To modify a partition it must not be mounted. You can however not unmount the " +"root partition. Neither will you be able to unmount the home partition if the " +"home directory of the currently logged in user is on it." +msgstr "" + +#. Tag: para +#: faq.docbook:52 +#, no-c-format +msgid "" +"The solution for this problem is to boot from a Linux Live CD that comes with " +"&partman; and modify these partitions from there." +msgstr "" + +#. Tag: para +#: faq.docbook:59 +#, no-c-format +msgid "" +"I'm getting a warning message in the log output about something that a " +"partition cannot be created with the size I requested and that it will" +" instead " +"be smaller. What happened?" +msgstr "" + +#. Tag: para +#: faq.docbook:62 +#, no-c-format +msgid "" +"On MS-DOS partition tables, partitions have to begin and end on cylinder " +"boundaries. This is mainly for historical reasons. &partman; will deal with " +"this internally and try not to bother the user with that limitation." +msgstr "" + +#. Tag: para +#: faq.docbook:65 +#, no-c-format +msgid "" +"Under rare circumstances, &partman; will however not be able to set up an " +"operation in the way the user requested it due to this limitation. For" +" example, " +"if one cylinder on a device is 8 MiB large and you try to resize a partition" +" by " +"6 MiB, this will not work." +msgstr "" + +#. Tag: para +#: faq.docbook:68 +#, no-c-format +msgid "" +"You might also encounter this message if you have a device and partition" +" table " +"where the partitions are, for whatever reason, not correctly snapped to " +"cylinder boundaries and you try to move or copy these partitions for the" +" first " +"time." +msgstr "" + +#. Tag: para +#: faq.docbook:71 +#, no-c-format +msgid "" +"The message itself is harmless and only exists to inform the user that " +"something can not be done quite exactly the way the user expects. Your " +"partitions and data will not be negatively affected in any way if you see" +" this " +"message." +msgstr "" + +#. Tag: para +#: faq.docbook:78 +#, no-c-format +msgid "How many operations can I add to the list of pending operations?" +msgstr "" + +#. Tag: para +#: faq.docbook:81 +#, no-c-format +msgid "There is no limit." +msgstr "" + +#. Tag: para +#: faq.docbook:84 +#, no-c-format +msgid "" +"It is however not recommended to add too many operations to the list. There" +" is " +"always a small chance an operation might fail with an error, in which case " +"&partman; will stop executing operations. In that case it is a lot easier to " +"find out what happened (and to re-add all the operations that could not be " +"executed) if the list of pending operations was not exceedingly long." +msgstr "" + +#. Tag: para +#: faq.docbook:91 +#, no-c-format +msgid "" +"Resizing an ext2 or ext3 file system failed with something in the report" +" about " +"no space left on device. What happened? Is my data corrupted " +"now?" +msgstr "" + +#. Tag: para +#: faq.docbook:94 +#, no-c-format +msgid "" +"This is a problem of the e2resize " +"command and the underlying ext2/3/4 file system. If a file system is nearly " +"full, e2resize cannot make it any smaller even though that " +"should be possible from the number of free sectors left. &partman; can " +"unfortunately not know beforehand if e2resize " +"will abort with this error for a given file system or not. If it happens " +"nothing will be done at all and your data will not be negatively affected." +msgstr "" + +#. Tag: para +#: faq.docbook:97 +#, no-c-format +msgid "There is no real workaround for this problem right now." +msgstr "" + +#. Tag: para +#: faq.docbook:104 +#, no-c-format +msgid "" +"Why can't I format my floppy disk with &partman;? Why is there no support for " +"CD writing or DVD burning?" +msgstr "" + +#. Tag: para +#: faq.docbook:107 +#, no-c-format +msgid "" +"None of this is what &partman; has been designed to do: It is an application " +"that deals with partitions and the file systems on these partitions. Floppy " +"disks, CDs or DVDs do not need or use partitions." +msgstr "" + +#. Tag: para +#: faq.docbook:114 +#, no-c-format +msgid "" +"Why can't I modify partitions on a device with an amiga or bsd partition" +" table?" +msgstr "" + +#. Tag: para +#: faq.docbook:117 +#, no-c-format +msgid "" +"&partman; currently only allows read-only access to any other partition table " +"type than MS-DOS. This is for safety reasons: Support in &partman; for this " +"partition table types is not really there and what is there (or just " +"incidentally works) has not been tested enough to use it with confidence." +msgstr "" + +#. Tag: para +#: faq.docbook:120 +#, no-c-format +msgid "" +"Of course you can still create a new MS-DOS partition table on the device in " +"question, but that is probably not what you want." +msgstr "" + +#. Tag: para +#: faq.docbook:127 +#, no-c-format +msgid "" +"On startup, &partman; hangs for a couple of minutes while it apparently tries " +"to scan the floppy drive on my computer." +msgstr "" + +#. Tag: para +#: faq.docbook:130 +#, no-c-format +msgid "" +"This happens if you have a floppy drive configured in your computer's BIOS " +"settings but have not actually connected one. If you do not have a floppy" +" drive " +"check your BIOS settings and disable any floppy drives configured there to" +" see " +"if this makes the problem go away." +msgstr "" + +#. Tag: para +#: faq.docbook:137 +#, no-c-format +msgid "" +"During startup, &partman; prints some message about probing devices and that" +" it " +"might even crash or at least take a long time." +msgstr "" + +#. Tag: para +#: faq.docbook:140 +#, no-c-format +msgid "" +"LibParted, a backend library &partman; uses, has problems with systems where " +"the Linux Device Mapper is used in a way it doesn't understand. Unfortunately " +"it reacts to some of these situations with segmentation faults, i.e. crashes. " +"&partman; therefore tries to avoid these situations by using an alternative" +" way " +"to scan your computer for disks. If it cannot do that, however, and therefore " +"has to rely on LibParted, it will print a message like the one mentioned. If " +"the scanning for disks works, you can safely disregard the message." +msgstr "" Index: trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_glossary.po =================================================================== --- trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_glossary.po (nonexistent) +++ trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_glossary.po (revision 1540364) @@ -0,0 +1,574 @@ +# +# Alexander Potashev , 2019. +msgid "" +msgstr "" +"Project-Id-Version: \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2016-12-04 02:03+0000\n" +"PO-Revision-Date: 2019-04-22 13:43+0300\n" +"Last-Translator: Alexander Potashev \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"X-Generator: Lokalize 18.12.2\n" + +#. Tag: glossterm +#: glossary.docbook:4 +#, no-c-format +msgid "Command" +msgstr "" + +#. Tag: para +#: glossary.docbook:6 +#, no-c-format +msgid "" +"In &partman; commands are what jobs " +"are made up of. These are very low level steps being taken, often executed by " +"an external tool, and only visible in the detailed progress report." +msgstr "" + +#. Tag: para +#: glossary.docbook:9 +#, no-c-format +msgid "The user normally does not have to bother with commands at all." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:11 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:18 +#, no-c-format +msgid "Cylinder" +msgstr "" + +#. Tag: para +#: glossary.docbook:20 +#, no-c-format +msgid "" +"A unit used to divide up a device" +". Some operating systems and many disk tools require partitions to begin and end on a " +"cylinder. &partman; therefore automatically snaps partitions to cylinder " +"boundaries when changing their start or end." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:22 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:29 +#, no-c-format +msgid "Cylinder Size" +msgstr "" + +#. Tag: para +#: glossary.docbook:31 +#, no-c-format +msgid "" +"The number of sectors " +"per cylinder " +"on a device" +". Calculated as the number of heads " +"multiplied by the number of sectors " +"per track." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:38 +#, no-c-format +msgid "Device" +msgstr "" + +#. Tag: para +#: glossary.docbook:40 +#, no-c-format +msgid "" +"A physical disk device. Physical disk devices are divided into logical" +" sections " +"called partitions " +"with the use of " +"partition tables." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:47 +#, no-c-format +msgid "Disk Label" +msgstr "" + +#. Tag: para +#: glossary.docbook:49 +#, no-c-format +msgid "" +"Another name for a " +"partition table stemming from the SUN/BSD world." +msgstr "" + +#. Tag: para +#: glossary.docbook:54 +#, no-c-format +msgid "" +"They are easy to mix up, but a disk label has nothing to do with a file system label." +msgstr "" + +#. Tag: para +#: glossary.docbook:57 +#, no-c-format +msgid "" +"See " +"this Wikipedia entry for details on the name." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:67 +#, no-c-format +msgid "Extended Partition" +msgstr "" + +#. Tag: para +#: glossary.docbook:69 +#, no-c-format +msgid "" +"A partition " +"that contains other partitions. Extended partitions can only be primary partitions " +"themselves. Whether extended partitions are available or not depends on the " +"partition table " +"type used. MS-DOS partition tables allow one extended partition per device." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:71 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:78 +#, no-c-format +msgid "File System" +msgstr "" + +#. Tag: para +#: glossary.docbook:80 +#, no-c-format +msgid "" +"A file system defines how the storage of data (files with their metadata, " +"folders and their metadata, free space) is organized within a partition. There are various different " +"types of file systems, some coming originally from the Unix/Linux world, some " +"not. Examples for commonly used file systems on Unix/Linux are Btrfs, ext4" +" and " +"XFS." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:87 +#, no-c-format +msgid "File System Label" +msgstr "" + +#. Tag: para +#: glossary.docbook:89 +#, no-c-format +msgid "" +"A title of a file system. Some file systems (among them Btrfs, ext2/3/4, " +"FAT16/32 and NTFS) support setting a label for the file system so it can be " +"identified in tools like &partman; or other applications." +msgstr "" + +#. Tag: para +#: glossary.docbook:94 +#, no-c-format +msgid "" +"They are easy to mix up, but a file system label has nothing to do with a <" +"link " +"linkend=\"glossary-disklabel\">disk label." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:101 +#, no-c-format +msgid "Flag" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:106 +#, no-c-format +msgid "GPT" +msgstr "" + +#. Tag: para +#: glossary.docbook:108 +#, no-c-format +msgid "" +"A modern partition table format supported by most modern computers and " +"operating systems. It supports more than 4 primary partitions " +"unlike older MS-DOS partition table." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:114 +#, no-c-format +msgid "Head" +msgstr "" + +#. Tag: para +#: glossary.docbook:116 +#, no-c-format +msgid "" +"A unit used to divide up a device." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:118 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:125 +#, no-c-format +msgid "Job" +msgstr "" + +#. Tag: para +#: glossary.docbook:127 +#, no-c-format +msgid "" +"In &partman; a number of jobs is what " +"operations are made up of. You normally do not have to bother with" +" jobs " +"at all; it only becomes apparent when applying the list of pending" +" operations: " +"&partman; will then show a progress dialog that is made up of all operations " +"and their jobs and show which operation and which job is currently being " +"executed." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:129 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:136 +#, no-c-format +msgid "Label" +msgstr "" + +#. Tag: para +#: glossary.docbook:138 +#, no-c-format +msgid "" +"Either a disk label " +"or a file system label." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:140 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:147 +#, no-c-format +msgid "Logical Partition" +msgstr "" + +#. Tag: para +#: glossary.docbook:149 +#, no-c-format +msgid "" +"A partition " +"inside an extended partition<" +"/link>" +"." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:151 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:158 +#, no-c-format +msgid "LUKS" +msgstr "LUKS" + +#. Tag: para +#: glossary.docbook:160 +#, no-c-format +msgid "Linux Unified Key Setup is the standard encryption format for Linux." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:166 +#, no-c-format +msgid "LVM" +msgstr "" + +#. Tag: para +#: glossary.docbook:168 +#, no-c-format +msgid "" +"LVM is a system for managing logical partitions that is more flexible than " +"normal partitions. It consists of three main components:" +msgstr "" + +#. Tag: member +#: glossary.docbook:170 +#, no-c-format +msgid "" +"LVM physical volumes are partitions on the disk whose space is managed by LVM." +msgstr "" + +#. Tag: member +#: glossary.docbook:171 +#, no-c-format +msgid "" +"LVM volume group is a collection of LVM physical volumes that can be " +"partitioned into logical partitions. It might be used to create file systems " +"spanning over multiple devices or to split encrypted LUKS volume into smaller partitions." +msgstr "" + +#. Tag: member +#: glossary.docbook:172 +#, no-c-format +msgid "" +"LVM logical volumes are similar to normal partitions except that they reside" +" on " +"LVM volume group. Also, the location of LVM logical partitions does not" +" matter " +"and they do not have to be physically contiguous. Therefore, &partman; does" +" not " +"allow to move LVM logical volumes and displays the remaining free space at" +" the " +"end of the device." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:178 +#, no-c-format +msgid "Operation" +msgstr "" + +#. Tag: para +#: glossary.docbook:180 +#, no-c-format +msgid "" +"&partman; divides the work it does up in operations, jobs and " +"commands." +msgstr "" + +#. Tag: para +#: glossary.docbook:183 +#, no-c-format +msgid "" +"Operations are the most visible of the three. If you pick an action in the " +"graphical user interface, this will likely result in a new operation being " +"added to the list of pending operations. The idea behind that is: You will" +" most " +"probably want to set up quite a number of steps to transform the current" +" state " +"of your disk devices to the state you have in mind. Some of these steps may " +"take quite a long time to execute (like copying a large file system or" +" resizing " +"a file system that is nearly full). To save you from having to sit in front" +" of " +"your computer for a long time waiting for one step to finish and then" +" starting " +"the next one, operations allow you to exactly specify how the computer's " +"devices should look like once everything is finished, then let &partman;" +" apply " +"the operations and come back when it has executed all of them." +msgstr "" + +#. Tag: para +#: glossary.docbook:186 +#, no-c-format +msgid "" +"Operations are kept in a list of pending operations. As long as an operation " +"has not been applied it can still be " +"taken back easily and nothing will have been modified." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:188 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:195 +#, no-c-format +msgid "Partition" +msgstr "" + +#. Tag: para +#: glossary.docbook:197 +#, no-c-format +msgid "" +"A section of a hard disk device " +"that can hold a file system " +"or other partitions. Without at least one valid partition, a disk can not be " +"used." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:199 +#, no-c-format +msgid "" +" " +" " +" " +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:209 +#, no-c-format +msgid "Partition Flag" +msgstr "" + +#. Tag: para +#: glossary.docbook:211 +#, no-c-format +msgid "" +"A marker for a partition" +". The availability of these flags depends on the type of partition table used." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:218 +#, no-c-format +msgid "Partition Table" +msgstr "" + +#. Tag: para +#: glossary.docbook:220 +#, no-c-format +msgid "" +"A small section at the beginning of a " +"device used to store information about the layout of the device's <" +"link " +"linkend=\"glossary-partition\">partitions. There are different types" +" of " +"partition tables, each with their own limitations." +msgstr "" + +#. Tag: para +#: glossary.docbook:223 +#, no-c-format +msgid "Sometimes also referred to as disk label." +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:230 +#, no-c-format +msgid "Primary Partition" +msgstr "" + +#. Tag: para +#: glossary.docbook:232 +#, no-c-format +msgid "" +"A partition " +"directly inside a " +"partition table, as opposed to logical partitions" +", which are in " +"extended partitions." +msgstr "" + +#. Tag: para +#: glossary.docbook:235 +#, no-c-format +msgid "" +"Partition tables " +"usually impose restrictions on the maximum number of primary partitions that " +"can be created on a device" +". For MS-DOS type partition tables, for example, this maximum number is four." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:237 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:244 +#, no-c-format +msgid "Sector" +msgstr "" + +#. Tag: para +#: glossary.docbook:246 +#, no-c-format +msgid "" +"A unit used to divide up a device" +". Partitions " +"must always begin and end on a sector." +msgstr "" + +#. Tag: glossdef +#: glossary.docbook:248 +#, no-c-format +msgid "" +" " +"" +msgstr "" + +#. Tag: glossterm +#: glossary.docbook:255 +#, no-c-format +msgid "Sector Size" +msgstr "" + +#. Tag: para +#: glossary.docbook:257 +#, no-c-format +msgid "" +"The number of bytes per sector " +"on a device" +". The sector size of most devices in use today is 512 bytes." +msgstr "" Index: trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_installoshowto.po =================================================================== --- trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_installoshowto.po (nonexistent) +++ trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_installoshowto.po (revision 1540364) @@ -0,0 +1,221 @@ +# +# Alexander Potashev , 2019. +msgid "" +msgstr "" +"Project-Id-Version: \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2014-04-28 02:12+0000\n" +"PO-Revision-Date: 2019-04-22 13:45+0300\n" +"Last-Translator: Alexander Potashev \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"X-Generator: Lokalize 18.12.2\n" + +#. Tag: title +#: installoshowto.docbook:2 +#, no-c-format +msgid "How-To: Installing a New Operating System" +msgstr "Инструкция: установка новой операционной системы" + +#. Tag: para +#: installoshowto.docbook:4 +#, no-c-format +msgid "" +"This how-to describes the preparation of a new hard disk device for an OS " +"installation: Suppose you bought a new hard disk and now intend to use it as" +" a " +"replacement for the old one that currently holds your OS and data partitions. " +"You would also like to take this opportunity to install a new operation" +" system. " +"Several steps will have to be taken to make the transition from the old to" +" the " +"new system and drive." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:8 +#, no-c-format +msgid "" +"In the following, /dev/sdb is the old hard disk and " +"/dev/sdc is the new one. This screenshot shows the situation on the " +"source device:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:16 +#, no-c-format +msgid "Main window with source device" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:21 +#, no-c-format +msgid "" +"The new device will look like this. Note that it doesn't yet have valid " +"partition table, thus the first step to take is to create one by selecting " +":" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:29 +#, no-c-format +msgid "Main window with destination device" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:34 +#, no-c-format +msgid "" +"After confirming the warning dialog you can begin creating partitions on the " +"new device by clicking the extended partition and selecting . Begin with an extended partition at the end " +"of the device to later hold the home and swap partitions:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:42 +#, no-c-format +msgid "Creating an extended partition" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:47 +#, no-c-format +msgid "" +"Click OK and the operation to create this extended " +"partition is added to the list." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:51 +#, no-c-format +msgid "" +"Now create a primary partition on the rest of the device where the new OS" +" will " +"be installed. Make it as large as the unallocated area in front of the" +" extended " +"partition:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:59 +#, no-c-format +msgid "Creating a primary partition" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:64 +#, no-c-format +msgid "" +"Click OK in the dialog to accept your choice. The " +"operation to create the new primary partition is then added to the operation " +"list." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:68 +#, no-c-format +msgid "" +"Now it is time to copy the home partition from the old device to the extended " +"partition on the new device. Select the old device in the Device List panel, " +"click on partition sdb5 and pick ." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:72 +#, no-c-format +msgid "" +"Then go back to the new device and click the extended partition. Select . The following dialog will come up:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:80 +#, no-c-format +msgid "Pasting the home partition" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:85 +#, no-c-format +msgid "" +"This already looks mostly okay but you already know that you will not need" +" that " +"much free space after the home partition because you will later create a swap " +"partition there." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:89 +#, no-c-format +msgid "" +"So grab the right resize handle in the dialog's resizer widget and move it to " +"the right until the free space after the pasted partition has a size more " +"suitable for a swap partition:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:97 +#, no-c-format +msgid "Resizing a pasted partition" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:102 +#, no-c-format +msgid "" +"This looks fine. Click OK to accept and close the " +"dialog. A new operation to paste the copied partition to the extended" +" partition " +"on sdc is added to the operation list. Note that this" +" operation " +"will also set the new size." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:106 +#, no-c-format +msgid "" +"Finally you will want to create a new swap partition at the end of the" +" extended " +"partition on sdc. There is no need to copy the existing swap " +"partition from sdb because swap does not hold any permanent " +"information worth keeping. Simply create a new partition with type linuxswap " +"that fills the whole of the unallocated area after the new home partition." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:110 +#, no-c-format +msgid "" +"The main window with all operations and the preview of how sdc " +"will look like once they are applied now looks like this:" +msgstr "" + +#. Tag: phrase +#: installoshowto.docbook:118 +#, no-c-format +msgid "Main window after setting up all operations" +msgstr "" + +#. Tag: para +#: installoshowto.docbook:123 +#, no-c-format +msgid "" +"This looks great so select " +", confirm the warning dialog and wait until the operations have all been " +"executed. For details on executing operations see the how-to on resizing partitions." +msgstr "" + +#. Tag: para +#: installoshowto.docbook:127 +#, no-c-format +msgid "" +"Your new hard disk device is now ready for the installation of your new " +"operation system." +msgstr "" Index: trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_resizehowto.po =================================================================== --- trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_resizehowto.po (nonexistent) +++ trunk/l10n-kf5/ru/docmessages/extragear-sysadmin/partitionmanager_resizehowto.po (revision 1540364) @@ -0,0 +1,301 @@ +# +# Alexander Potashev , 2019. +msgid "" +msgstr "" +"Project-Id-Version: \n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2014-04-28 02:12+0000\n" +"PO-Revision-Date: 2019-04-22 13:44+0300\n" +"Last-Translator: Alexander Potashev \n" +"Language-Team: Russian \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: ru\n" +"X-Generator: Lokalize 18.12.2\n" + +#. Tag: title +#: resizehowto.docbook:2 +#, no-c-format +msgid "How-To: Resizing a Partition" +msgstr "Инструкция: изменение размера раздела" + +#. Tag: para +#: resizehowto.docbook:4 +#, no-c-format +msgid "" +"This how-to explains the resizing of a partition " +"that is becoming too full. See the following screenshot for the initial " +"situation before resizing:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:12 +#, no-c-format +msgid "Main window before resizing partitions" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:17 +#, no-c-format +msgid "" +"On device " +"/dev/sdb, partition sdb2 has only little free space" +" left " +"while the other partition, sdb1, is far from being full. For " +"that reason it seems advisable to make the first partition a little smaller" +" and " +"grow sdb2 so it has more free space available." +msgstr "" + +#. Tag: title +#: resizehowto.docbook:22 +#, no-c-format +msgid "Note: You cannot modify mounted partitions." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:23 +#, no-c-format +msgid "" +"In the screenshot above both partitions are not currently mounted. If one or " +"both of them were mounted you would have to unmount them first using ." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:26 +#, no-c-format +msgid "" +"The first step is to make more room for the partition to grow, so start by " +"shrinking sdb1. Click on the partition and choose . The following dialog comes up:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:34 +#, no-c-format +msgid "Resize dialog before resizing /dev/sdb1" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:39 +#, no-c-format +msgid "" +"The dialog allows you to resize the partition in multiple ways. You can" +" either " +"drag the right handle to the left until the partition has the desired size or " +"simply enter the size in the Size " +"text field. Another possibility would be to adjust the size by clicking on" +" the " +"little arrows next to the text field, but that is a little tedious for larger " +"changes." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:43 +#, no-c-format +msgid "" +"Whichever way you prefer for setting the new size, the dialog should now look " +"like this:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:51 +#, no-c-format +msgid "Resize dialog after resizing /dev/sdb1" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:56 +#, no-c-format +msgid "" +"After you click on OK, a new operation is added to the " +"pending operations list and the graphical view and tree view of the device" +" are " +"updated to reflect the new situation:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:64 +#, no-c-format +msgid "Main window after resizing /dev/sdb1" +msgstr "" + +#. Tag: title +#: resizehowto.docbook:70 +#, no-c-format +msgid "Note: Operations are previewed first before applying them." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:71 +#, no-c-format +msgid "" +"Although the main window reflects the device's state how it will be after " +"applying the new operation, the operation has in fact not been applied yet: " +"While operations are pending you can still undo them (one by one using or " +"to undo all of them) or quit &partman;, and nothing will have been modified" +" at " +"all." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:74 +#, no-c-format +msgid "" +"Now that there is some free space between the two partitions you can move and " +"grow partition sdb2. First, click on sdb2 " +"and choose " +"again. The resize dialog comes up once more, this time for the second " +"partition. Drag its left handle to the leftmost end so that the dialog looks " +"like this:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:82 +#, no-c-format +msgid "Resize dialog after resizing /dev/sdb2" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:87 +#, no-c-format +msgid "" +"Be careful to make sure that the Free space before " +"text field really does show 0 MiB because otherwise there will " +"be a little free space left between the partitions that will then be wasted." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:91 +#, no-c-format +msgid "" +"Now click OK again. In the main window things now look " +"like this:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:99 +#, no-c-format +msgid "Main window after resizing /dev/sdb2" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:104 +#, no-c-format +msgid "" +"This already looks like what you wanted, so choose . A dialog box will come up and ask you if you" +" are " +"sure to apply the pending operations. Confirm this dialog box and &partman; " +"will begin executing operations:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:112 +#, no-c-format +msgid "&partman; is applying operations" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:117 +#, no-c-format +msgid "" +"While operations are being executed you can click on the plus-sign next to" +" each " +"operation in the list to find out the jobs it is made up of and see which job " +"is currently being run." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:121 +#, no-c-format +msgid "" +"Resizing a partition in the way you resized /dev/sdb2 " +"above always means it has to be moved to the left first before it can be" +" grown " +"because partitions can never be grown to the left directly. Unfortunately, " +"moving such a large partition will take quite some time. It is not unusual" +" for " +"an operation like this to take several minutes or even more." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:125 +#, no-c-format +msgid "Finally, all operations will have been successfully completed:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:133 +#, no-c-format +msgid "Progress dialog after successfully applying operations" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:138 +#, no-c-format +msgid "" +"By clicking on OK you can now close the progress" +" dialog " +"and return to the main window. &partman; will rescan your devices at this" +" point " +"so that might take a few seconds." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:142 +#, no-c-format +msgid "" +"If you are interested in some more details about the operations that were" +" just " +"run click on Details. You will see the detailed report " +"that is always generated (and updated on the fly) while &partman; executes " +"operations:" +msgstr "" + +#. Tag: phrase +#: resizehowto.docbook:150 +#, no-c-format +msgid "Progress dialog details" +msgstr "" + +#. Tag: para +#: resizehowto.docbook:155 +#, no-c-format +msgid "" +"This report is particularly of interest if an error occurs while executing " +"operations. A report shows each operation, each job and each external command " +"that is being run and is thus very helpful when trying to track down problems." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:159 +#, no-c-format +msgid "" +"You can save the report as HTML or view it in an external " +"web browser." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:164 +#, no-c-format +msgid "" +"Always save the detailed report as HTML " +"when executing the operations fails with errors or warnings for later " +"reference. You might also want to include it in a bug report you submit to" +" the " +"&kde; bug tracking system at " +"bugs.kde.org." +msgstr "" + +#. Tag: para +#: resizehowto.docbook:169 +#, no-c-format +msgid "" +"To hide the details again click on Details " +"and to finally close the progress dialog click on OK." +msgstr ""