This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
cs:archlinux_installation [2019/05/03 14:02] paolo_bolzoni typo |
cs:archlinux_installation [2021/05/02 14:08] (current) paolo_bolzoni |
||
---|---|---|---|
Line 104: | Line 104: | ||
This will create a different hook for each disk, to configure each just do the same you would do for a single disk but add ''0'', ''1'', ... to each variable name. | This will create a different hook for each disk, to configure each just do the same you would do for a single disk but add ''0'', ''1'', ... to each variable name. | ||
- | To avoid to have to type the password many times you can consider to add a filekey to the first disk and set up the next hooks to use it. The ''-s'' option is not necessary, but to see the detected partitions can help debugging. | + | To avoid to have to type the password many times you can consider to add a filekey to the first disk and set up the next hooks to use it. |
Line 112: | Line 112: | ||
''parted'') to inform the OS of the new partitions. | ''parted'') to inform the OS of the new partitions. | ||
- | In the hook file look up for lines with ''if [ -e "/dev/mapper/${cryptname}" ]; then'' two of those ifs check if the text-plain abstraction has been properly created. Just add ''partprobe -s "/dev/mapper/${cryptname}"'' in a line below. At time of writing the two lines are the 91st and the 129th. | + | In the hook file look up for lines with ''if [ -e "/dev/mapper/${cryptname}" ]; then'' two of those ifs check if the text-plain abstraction has been properly created. Just add ''partprobe -s "/dev/mapper/${cryptname}"'' in a line below (The ''-s'' option is not necessary, but to see the detected partitions can help debugging.) At time of writing the two lines are the 91st and the 129th. |
Example: | Example: | ||
Line 153: | Line 153: | ||
=== Wifi menu === | === Wifi menu === | ||
- | The installation media has ''wifi-menu'' to easily connect to wireless networks; unfortunately the ''base'' group **does not** has it. So when boot strapping the new environment I use: | + | The installation media has ''wifi-menu'' to easily connect to wireless networks; unfortunately the ''base'' group **does not** has it. |
- | + | ||
- | # pacstrap /mnt base base-devel netctl dialog dhcpcd wpa_supplicant | + | |
The ''netctl'', ''dialog'', ''dhcpcd'', and ''wpa_supplicant'' packages just use few megabytes of space, but they ensure you have a easy and quick way to connect to wireless networks after the reboot. | The ''netctl'', ''dialog'', ''dhcpcd'', and ''wpa_supplicant'' packages just use few megabytes of space, but they ensure you have a easy and quick way to connect to wireless networks after the reboot. | ||
+ | |||
+ | In addition many useful packages are in the AUR and to install with easy one needs ''pikaur,'' to be installed it needs few deps: ''git'', ''pyalpm'', and ''python-commonmark''. So to kickstart the system, a good line is: | ||
+ | |||
+ | # pacstrap /mnt linux linux-firmware base base-devel netctl dialog dhcpcd wpa_supplicant git pyalpm python-commonmark | ||
+ | |||
+ | ''pikaur'' will need to be installed manually. | ||
If using ZFS, add to ''pacstrap'' also the ''zfs-dkms'' and ''linux-headers'' packages. | If using ZFS, add to ''pacstrap'' also the ''zfs-dkms'' and ''linux-headers'' packages. | ||
+ | |||
+ | |||
=== Wifi card driver === | === Wifi card driver === | ||
Line 178: | Line 184: | ||
Once found the kernel driver look it up in the ''/usr/lib/firmware'' directory to check if the package needs to be installed. | Once found the kernel driver look it up in the ''/usr/lib/firmware'' directory to check if the package needs to be installed. | ||
+ | |||
+ | ====== Post-installation ====== | ||
+ | |||
+ | Once started the X (Wayland) server the font configuration will be horible. Often the spacing between the characters will be totally messed up. Here are the instructions to set up the fonts properly ([[https://www.reddit.com/r/archlinux/comments/5r5ep8/make_your_arch_fonts_beautiful_easily/|Original post]].) | ||
+ | |||
+ | First of all install the liberation fonts, it indirectly sets up the correct characters positions. | ||
+ | |||
+ | # pacman -S ttf-liberation | ||
+ | |||
+ | Secondly install a bit more fonts. | ||
+ | |||
+ | # pacman -S ttf-ibm-plex ttf-dejavu noto-fonts | ||
+ | |||
+ | Enable font presets: | ||
+ | |||
+ | # ln -s /etc/fonts/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d | ||
+ | # ln -s /etc/fonts/conf.avail/10-sub-pixel-rgb.conf /etc/fonts/conf.d | ||
+ | # ln -s /etc/fonts/conf.avail/11-lcdfilter-default.conf /etc/fonts/conf.d | ||
+ | |||
+ | In the ''/etc/profile.d/freetype2.sh'' file uncomment the ''FREETYPE_PROPERTIES'' line. | ||
+ | |||
+ | |||
+ | Finally create the ''/etc/fonts/local.conf'' file with the following content. The file tells the system what you mean with //serif//, //sans//, or //monospace//. | ||
+ | |||
+ | <?xml version="1.0"?> | ||
+ | <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> | ||
+ | <fontconfig> | ||
+ | <match> | ||
+ | <edit mode="prepend" name="family"><string>Liberation Sans</string></edit> | ||
+ | </match> | ||
+ | <match target="pattern"> | ||
+ | <test qual="any" name="family"><string>serif</string></test> | ||
+ | <edit name="family" mode="assign" binding="same"><string>Liberation Serif</string></edit> | ||
+ | </match> | ||
+ | <match target="pattern"> | ||
+ | <test qual="any" name="family"><string>sans-serif</string></test> | ||
+ | <edit name="family" mode="assign" binding="same"><string>Liberation Sans</string></edit> | ||
+ | </match> | ||
+ | <match target="pattern"> | ||
+ | <test qual="any" name="family"><string>monospace</string></test> | ||
+ | <edit name="family" mode="assign" binding="same"><string>IBM Plex Mono</string></edit> | ||
+ | </match> | ||
+ | </fontconfig> |