mirror of
git://slackware.nl/current.git
synced 2025-02-15 08:50:09 +01:00
d569bae77f
a/kernel-firmware-20250208_4ccb15a-noarch-1.txz: Upgraded.
a/kernel-generic-6.12.13-x86_64-1.txz: Upgraded.
a/pkgtools-15.1-noarch-27.txz: Rebuilt.
installpkg: --terse remains the same, default output drops the huge amount
of debugging output such as the file/link/dir lists, and --verbose is added
as an option in case you actually want to see that stuff. New --save-cookies
option added for upgradepkg to use. This lets us preserve some data from the
first pass so that we don't have to redo some expensive operations.
removepkg: default to --terse, but add a --verbose option.
Change sed delimiter from / to | to fix using ROOT=. Thanks to USUARIONUEVO.
upgradepkg: export a global MCOOKIE, and call installpkg with --save-cookies
for the first pass. Pass along the --verbose option to installpkg/removepkg
if upgradepkg is called with it. Render the banner with a little more care.
I think we're done improving these tools -- hopefully Dijkstra would be a
little less embarrassed for me now. ;-)
a/sysvinit-3.14-x86_64-1.txz: Upgraded.
d/kernel-headers-6.12.13-x86-1.txz: Upgraded.
k/kernel-source-6.12.13-noarch-1.txz: Upgraded.
l/SDL2_image-2.8.5-x86_64-1.txz: Upgraded.
l/SDL2_mixer-2.8.1-x86_64-1.txz: Upgraded.
l/wireplumber-0.5.8-x86_64-1.txz: Upgraded.
n/gnutls-3.8.9-x86_64-1.txz: Upgraded.
libgnutls: Fix potential DoS in handling certificates with numerous name
constraints, as a follow-up of CVE-2024-12133 in libtasn1. The bundled
copy of libtasn1 has also been updated to the latest 4.20.0 release to
complete the fix. Reported by Bing Shi.
For more information, see:
https://www.cve.org/CVERecord?id=CVE-2024-12243
(* Security fix *)
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
testing/packages/kernel-generic-6.13.2-x86_64-1.txz: Upgraded.
testing/packages/kernel-headers-6.13.2-x86-1.txz: Upgraded.
testing/packages/kernel-source-6.13.2-noarch-1.txz: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
74 lines
2.6 KiB
Text
74 lines
2.6 KiB
Text
|
|
Slackware initrd mini HOWTO
|
|
by Patrick Volkerding, volkerdi@slackware.com
|
|
Sat Feb 8 23:25:27 UTC 2025
|
|
|
|
This document describes how to create and install an initrd.
|
|
Also see "man mkinitrd".
|
|
|
|
1. What is an initrd?
|
|
2. Why to I need an initrd?
|
|
3. How do I build the initrd?
|
|
4. Now that I've built an initrd, how do I use it?
|
|
|
|
|
|
1. What is an initrd?
|
|
|
|
Initrd stands for "initial ramdisk". An initial ramdisk is a very small
|
|
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
|
|
and before the main root filesystem is mounted.
|
|
|
|
2. Why do I need an initrd?
|
|
|
|
The usual reason to use an initrd is because you need to load kernel
|
|
modules before mounting the root partition, or because you need additional
|
|
userspace support for doing so (as with LVM). Modern Linux is practically
|
|
expected to be using an initrd, so even in cases where it *works* to boot
|
|
without one, you're probably less likely to run into bugs by using one.
|
|
|
|
3. How do I build the initrd?
|
|
|
|
Just installing the kernel package will automatically run the geninitrd
|
|
script to produce an initrd, so normally you won't need to build one --
|
|
it will be done for you. However, if you need to generate an initrd you
|
|
can do so by just running "geninitrd" which will build an initrd for the
|
|
newest kernel in /boot. You can also specify the kernel to build an initrd
|
|
for on the command line, like this:
|
|
|
|
geninitrd /boot/vmlinuz-6.11.7
|
|
|
|
If you need specific modules, or you'd like to use a different initrd
|
|
generator than Slackware's mkinitrd, or to make other adjustments, see
|
|
the /etc/default/geninitrd configuration file. You can also disable
|
|
automatic initrd generation if you don't want it.
|
|
|
|
4. Now that I've built an initrd, how do I use it?
|
|
|
|
Now that you've got an initrd (/boot/initrd.gz), you'll want to load
|
|
it along with the kernel at boot time. If you use LILO for your boot
|
|
loader you'll need to edit /etc/lilo.conf and add a line to load the
|
|
initrd. Here's an example section of lilo.conf showing how this is
|
|
done:
|
|
|
|
# Linux bootable partition config begins
|
|
image = /boot/vmlinuz-generic
|
|
initrd = /boot/initrd-generic.img
|
|
root = /dev/sda6
|
|
label = Slackware
|
|
read-only
|
|
# Linux bootable partition config ends
|
|
|
|
The initrd is loaded by the "initrd = /boot/initrd-generic.img" line.
|
|
Just add the line right below the line for the kernel image you use.
|
|
Save the file, and then run LILO again ('lilo' at the command line).
|
|
You'll need to run lilo every time you edit lilo.conf or rebuild the
|
|
initrd.
|
|
|
|
Other bootloaders also support the use of an initrd.
|
|
See the documentation for those programs for details on using an
|
|
initrd with them.
|
|
|
|
|
|
---------
|
|
|
|
Have fun!
|