This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
docs:man:installing_pld_linux_based_on_rescue_cd [2019-01-21 20:15] arekm [Packages installation] |
docs:man:installing_pld_linux_based_on_rescue_cd [2019-01-21 20:20] arekm [Kernel installation] |
||
---|---|---|---|
Line 164: | Line 164: | ||
By default kernel installation also generates initrd based on mounted /proc, /sys, /dev files and configured fstab, modprobe.conf and few others configuration files. generated initrd (which by default is initramfs cpio image) is saved in /boot. | By default kernel installation also generates initrd based on mounted /proc, /sys, /dev files and configured fstab, modprobe.conf and few others configuration files. generated initrd (which by default is initramfs cpio image) is saved in /boot. | ||
+ | |||
+ | There are two initrd generators used in PLD: geninitrd and dracut. Choose one. | ||
+ | |||
+ | === geninitrd === | ||
If something fails or you want to regenerate initrd manually you can do it using: | If something fails or you want to regenerate initrd manually you can do it using: | ||
Line 174: | Line 178: | ||
//-v// option causes geninitrd to write additional information, so you can see if proper kernel modules are being installed into initrd. | //-v// option causes geninitrd to write additional information, so you can see if proper kernel modules are being installed into initrd. | ||
+ | |||
+ | === dracut === | ||
+ | |||
- | PLD supports systemd and non-systemd installations. In case of systemd installation you need to install | + | PLD supports systemd and non-systemd installations. In case of systemd installation you need to install package |
<file>systemd</file> | <file>systemd</file> |