Translations by Ofir Klinger

. Arabic

# Armenian

# Cyrillic - KOI8-R and KOI8-U

# Cyrillic - non-Slavic languages

# Cyrillic - Slavic languages (also Bosnian and Serbian Latin)

. Ethiopic

# Georgian

# Greek

# Hebrew

# Lao

# Latin1 and Latin5 - western Europe and Turkic languages

# Latin2 - central Europe and Romanian

# Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh

# Latin7 - Lithuanian; Latvian; Maori and Marshallese

. Latin - Vietnamese

# Thai

. Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic

. Combined - Latin; Slavic Cyrillic; Greek

. Combined - Latin; Slavic and non-Slavic Cyrillic

Caps Lock

Right Control

Right Shift

Right Logo key

Menu key

Alt+Shift

Control+Shift

Control+Alt

Left Alt

Left Control

Left Shift

Left Logo key

No toggling

No temporary switch

Both Logo keys

No AltGr key

No compose key

Compose key:

If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk.

The partition ${PARTITION} assigned to ${MOUNTPOINT} starts at an offset of ${OFFSET} bytes from the minimum alignment for this disk, which may lead to very poor performance.

Since you are formatting this partition, you should correct this problem now by realigning the partition, as it will be difficult to change later. To do this, go back to the main partitioning menu, delete the partition, and recreate it in the same position with the same settings. This will cause the partition to start at a point best suited for this disk.

The device should be specified as a device in /dev. Below are some examples: - "/dev/sda" will install GRUB to the master boot record of your first hard drive; - "/dev/sda2" will use the second partition of your first hard drive; - "/dev/sdc5" will use the first extended partition of your third hard drive; - "/dev/fd0" will install GRUB to a floppy.

Logical Volume Management

A common situation for system administrators is to find that some disk partition (usually the most important one) is short on space, while some other partition is underused. The Logical Volume Manager (LVM) can help with this.

LVM allows combining disk or partition devices ("physical volumes") to form a virtual disk ("volume group"), which can then be divided into virtual partitions ("logical volumes"). Volume groups and logical volumes may span several physical disks. New physical volumes may be added to a volume group at any time, and logical volumes can be resized up to the amount of unallocated space in the volume group.

The items on the LVM configuration menu can be used to edit volume groups and logical volumes. After you return to the main partition manager screen, logical volumes will be displayed in the same way as ordinary partitions, and should be treated as such.

Checking the u-boot file system in partition #${PARTITION} of ${DEVICE}...

The test of the file system with type u-boot in partition #${PARTITION} of ${DEVICE} found uncorrected errors.

The u-boot file system creation in partition #${PARTITION} of ${DEVICE} failed.

No mount point is assigned for the u-boot file system in partition #${PARTITION} of ${DEVICE}.

uboot