Void linux locale ru

Настройка русской локали в Linux

Чтобы изменить установленную по умолчанию локализацию в системе на русскую, необходимо выполнить несколько не сложных шагов.

Подготовка к настройке

• Подключаемся к VPS по SSH с правами root.
• Проверяем, доступна ли русская локаль в системе и её корректное название:

• В результате, при наличии локали, будет получен примерно следующий вывод:

• В нашем случае, интересует вариант ru_RU.utf8. Его мы и будем использовать далее. Поэтому скопируйте это значение в блокнот для дальнейшей вставки.

Настройка локали в CentOS, Fedora

• Создадим файл i18n, в котором затем сохраним параметры новой локали:

• В открывшемся редакторе вносим следующую информацию:

• Сохраняем изменения сочетанием клавиш CTRL+O и затем Enter.
• На этом всё, локаль изменена и теперь необходимо переподключиться в консоль, чтобы увидеть изменения. Если вы использовали VNC или другое удаленное подключение к рабочему столу, то рекомендуется и в нём произвести переподключение для применения изменений.

Настройка локали в Debian, Ubuntu

Если в шаге подготовки команда locale -a | grep ru дала пустой результат, значит русская локаль отсутствует в системе и её можно установить следующими способами:

Способ 1:

• Перенастраиваем пакет locales командой:

• В появившейся форме ищем локаль ru_RU.UTF-8 и отмечаем её нажатием пробелом, в результате перед этой локалью появится звёздочка, как показано на изображении ниже. Затем нажимаем Enter и переходим к следующему шагу.
• Следующий шаг – выбор локали по умолчанию. Выбераем русскую локаль из списка и нажмаем Enter.
• В результате будет завершена перенастройка локали и теперь необходимо только выполнить повторное подключение к консоли и к удаленному рабочему столу (если таковое используется).

Способ 2:

• Устанавливаем языковой пакет:

• Открываем текстовым редактором файл /etc/default/locale:

• Заменяем его содержимое на:

• Сохраняем изменения сочетанием клавиш CTRL+O и затем Enter.
• Выходим из консоли, а также закрываем соединение с удаленным рабочим столом (если такое соединение было) и подключаемся к этим сервисам повторно.
• На этом настройка завершена.

Источник

Installation

This section includes general information about the process of installing Void. For specific guides, see the «Advanced Installation» section.

Base system requirements

Void can be installed on very minimalist hardware, though we recommend the following minimums for most installations:

Architecture	CPU	RAM	Storage
x86_64-glibc	x86_64	96MB	700MB
x86_64-musl	x86_64	96MB	600MB
i686-glibc	Pentium 4 (SSE2)	96MB	700MB

Note that flavor installations require more resources; how much more depends on the flavor.

Void is not available for the i386, i486, or i586 architectures.

Before installing musl Void, please read the «musl» section of this Handbook, so that you are aware of software incompatibilities.

It is highly recommended to have a network connection available during install to download updates, but this is not required. ISO images contain installation data on-disk and can be installed without network connectivity.

Downloading installation media

The most recent live images and rootfs tarballs can be downloaded from https://alpha.de.repo.voidlinux.org/live/current/. They can also be downloaded from other mirrors. Previous releases can be found under https://alpha.de.repo.voidlinux.org/live/, organized by date.

Verifying images

Each image release’s directory contains two files used to verify the image(s) you download. First, there is a sha256sum.txt file containing image checksums to verify the integrity of the downloaded images. Second is the sha256sum.sig file, used to verify the authenticity of the checksums.

It is necessary to verify both the image’s integrity and authenticity. It is, therefore, recommended that you download both files.

Verifying image integrity

You can verify the integrity of a downloaded file using sha256sum(1) with the sha256sum.txt file downloaded above. The following command will check the integrity of only the image(s) you have downloaded:

This verifies that the image is not corrupt.

Verifying digital signature

Prior to using any image you’re strongly encouraged to validate the signatures on the image to ensure they haven’t been tampered with.

Current images are signed using a signify key that is specific to the release. If you’re on Void already, you can obtain the keys from the void-release-keys package, which will be downloaded using your existing XBPS trust relationship with your mirror. You will also need a copy of signify(1); on Void this is provided by the outils package.

To obtain signify when using a Linux distribution or operating system other than Void Linux:

• Install the signify package in Arch Linux and Arch-based distros.
• Install the signify-openbsd package in Debian and Debian-based distros.
• Install the package listed here for your distribution.
• Install signify-osx with homebrew in macOS.

If you can’t obtain signify for some reason (e.g. you are on Windows and can’t use WSL or MinGW), you can use minisign(1) to verify the file.

If you are not currently using Void Linux, it will also be necessary to obtain the appropriate signing key from our Git repository here.

Once you’ve obtained the key, you can verify your image with the sha256sum.sig file. The following example demonstrates the verification of the GCP musl filesystem from the 20191109 release:

If the verification process does not produce the expected «OK» status, do not use it! Please alert the Void Linux team of where you got the image and how you verified it, and we will follow up on it.

For verification with minisign , it is necessary to rename the sha256sum.sig file to sha256sum.txt.minisig and remove the first line from the .pub release key. The following example demonstrates the verification of the sha256sum.txt file from the 20191109 release:

The same warning as above applies. If the verification process isn’t successful, do not use the file — warn the Void Linux team about it.

Источник

Frequently Asked Questions

Contents

The basics

Is Void an Arch Linux fork?

Is there a ‘Stable’ version of Void?

There are linux distros that release to a periodic cycle, Void does not, instead provides a continual steam of updates, which makes it a rolling release. On the other hand there are bleeding edge distros, that gives the latest software as soon as possible after its release. This is not what Void does and although some software is updated frequently, it is by no means as soon as possible or come what may.

As a rolling release distribution, there are no «stable» freezes. You may choose what to update and when, and you may put packages on hold (refuse upgrades for specific packages, see XBPS), but bear in mind that upgrading some packages will occasionally require their dependencies be upgraded as well.

Void Linux name origin

Void comes from the C literal «void». It started as a testbed for xbps, so the name was choosen rather randomly and has no deeper meaning. See [1]

Installation and configuration

How should I partition my disk?

Note that Void (on x86/x86_64) keeps old kernels around, this takes about 20 MB per kernel version, so plan /boot accordingly. 20-30 GB for / is probably a good fit for an expansive desktop installation.

The installer sucks, how can I do $SPECIALTHING on installation?

You can install Void manually if you wish, there are many guides on the Void wiki for alternate installation scenarios. see for example Install LVM LUKS, or the Macbook page.

How can I change my users default shell?

Use chsh -l to list available shells and change it with chsh for the current user or chsh root for root or another specific user.

How do I remove old kernels?

Void Linux provides the vkpurge tool for the sole purpose of listing and removing old kernels. To list the old kernels in your system:

To remove a specific version:

To remove all kernels except the latest one:

How can I load kernel modules at boot?

To load kernel modules at boot time, a .conf file must be created in /etc/modules-load.d :

Multiple modules can be specified separated by newlines:

How do I blacklist kernel modules?

There are two ways of accomplishing this. The first one involves creating a .conf file in /etc/modprobe.d :

If the module being blacklisted is also available in the initramfs , don’t forget to omit the module from dracut creating a file in /etc/dracut.conf.d , then rebuild the initramfs:

The second method involves using the modprobe.blacklist variable in the kernel command line, like this:

How to get rid of «ataN: softreset failed (device not ready)» ?

Add libata.force=norst to your kernel parameters or compile your kernel with CONFIG_SATA_PMP=n .

How do I set up/start/stop services?

To list current running services:

To enable a service to be started at boot time and start it in less than 5 seconds:

To start a service (must be symlinked first):

To stop a service:

To setup a service but not run it at boot time, create a file named down in the service directory:

The service can still be started manually.

Packages

Which package contains XYZ?

If you need this more often, xlocate from the xtools package provides a caching database:

Use man xtools after installation for more info about the commands provided by xtools .

How do I get a list of installed packages?

An example command line to get a list of all installed package names without their version is:

This list can be used to e.g. install your package selection on another machine.

I want to downgrade a package!

You can try using the xdowngrade script from the xtools package, like

In case you don’t have xtools installed, and are unable to install for whatever reason, you may manually downgrade this way (source)

I installed $PKGNAME and it’s not in my $PATH!

Packages like openjdk-jre provide a file located at /etc/profile.d/10_openjdk.sh that sets up the right environment variables. It’s necessary to re login or source your profile again after installing a package that needs environment variables set.

A ‘Transaction aborted due to unresolved shlibs’ error is preventing me from updating!

This is most often caused because a large build is occurring, and it will take some time for the packages to become available in the repo. You will have to wait for the packages to finish being built before they can be updated.

You can view the build’s progress at the Build Server Status Site and some particularly long builds may be announced on Twitter

Development

Valgrind needs glibc-dbg, which cannot be found. Help?

How do I check template files for common errors?

Use xlint from the xtools package.

. doesn’t $MANWIDTH change the man pages’ width?

That’s because Void Linux uses Mandoc (formerly known as mdocml) by default instead of man-db. Users who wish to use man-db can install the man-db package through XBPS.

To change the default width of man pages, open the file /etc/man.conf in your editor of choice and append this line to the end of the file:

You can substitute 200 with the maximum number of columns a line should be long. 200 is a good value for 1080p displays; the default is 78. Save the file and test the changes with man man .

If you want to preview your changes without changing man.conf , just execute the following command: man man | fmt -w 200 . Change 200 to your preferred value.

. is tar/Engrampa/XYZ unable to unpack *tar.xz archives?

If you keep getting

while trying to unpack a *tar.xz archive with tar or your favourite unpacker fails to open these archives, that’s because you need to install xz , the package with the xz compression utilities. A simple

will sort this out for you.

. isn’t my gamepad detected by some apps (e.g. supertux2)?

Make sure you are in the input group by executing the command getent group . If you’re not in the group, execute the command usermod -a -G input user replacing user with your username. This isn’t necessary on systems using elogind.

. isn’t a newly packaged kernel immediately offered by XBPS for installation?

Void Linux developers wait usually a bit until it is set as the new default for the linux meta package, and this usually depends on dkms modules and stability. It’s up to the package maintainer to decide when the update becomes the new default, but you are free to install it by explicitely telling XBPS about the package. You are doing that at your own risk, though.

. do I install a newer kernel manually?

As stated previously, newer kernels aren’t offered until all DKMS modules build correctly with it. Nonetheless, installing a newer kernel is fairly easy. Simply specify the version after «linux», like so:

You may also need to install linux5.0-headers, if you have any DKMS modules that you need to build. If you install linux5.0-headers after installing linux5.0 and need to build the DKMS modules manually, run the command:

. do I add an user account?

Besides root, an user account with access to sudo (and thus able to gain root privileges) is created as part of the installation process when you use the installer. However, if you installed Void Linux manually or you fiddled with the default groups assigned to this account in the installer (which includes wheel ) you might need to create another account. In fact, some Void software might run into problems if only the root account exists.

To create another user account using the console you do this as root:

See the man pages for useradd , usermod and passwd for more info.

Some DEs like Cinnamon or MATE come with a suitable GUI based application for this task so you don’t have to use the console if you don’t like to.

. do I set up my locale?

If your DE of choice doesn’t come with an editor for this job, you can always use the console. To see a listing of available locales:

To set up a locale for your system:

If your locale is not available in the locale -a output, edit /etc/default/libc-locales and uncomment the one you need. After that, rebuild the GNU libc locales:

. do I set the timezone?

Again some DEs come with an editor for this job, but in case you need/want to use the console, you can set your timezone like this:

To set up RTC to be in local time rather than UTC:

See hwclock(8) for more information.

. do I suspend/hibernate/shutdown/reboot the system using the console?

Use zzz to suspend your system to RAM, or ZZZ to suspend to disk (hibernation). To shut down (power off) the system use shutdown -h now . To reboot, use shutdown -r now or just reboot . All these commands require root privileges.

. do I make my NTFS partitions writable?

By default, NTFS partitions are mounted as read-only in Void Linux. This may lead to problems if you have e.g. a VirtualBox disk image stored in such a partition; VirtualBox will complain that the image is read only and will refuse to open it.

The simplest way to solve this matter is to install the ntfs-3g package, like thus:

Источник