You are not logged in.
Pages: 1
Hi
I want to do some exploring of our initrd.img
I found a simple command that appeared to work but it only unpacks microcode
eg all commands done as root
cp /boot/initrd.img-4.19.0-8-amd64 /tmp
cd /tmp
cpio -i -F initrd.img*
ls -al (culling older timestamps)
kernel
and the kernel has sub dirs to lead to your amd or intel or both microcodes.
I am aware that we have a file as follows
file initrd.img-4.19.0-8-amd64
initrd.img-4.19.0-8-amd64: ASCII cpio archive (SVR4 with no CRC)
I found a hit after changing my search to ask why I could only see a kernel got this
https://unix.stackexchange.com/question … ely-kernel
new root commands
mkdir /tmp/unpack
cp /boot/initrd.img-4.19.0-8-amd64 /tmp/unpack
cd /tmp/unpack
(cpio -id; zcat | cpio -id) < initrd.img-4.19.0-8-amd64
ls
bin conf cryptroot etc init initrd.img-4.19.0-8-amd64 kernel lib lib64 run sbin scripts usr
Last edited by aus9 (2020-03-30 06:28:41)
Offline
Almost easier is to use the programs found in the package "initramfs-tools-core". In particular lsinitramfs and unmkinitramfs work really well for me. I build a custom kernel and initramfs to have a router system that runs completely within memory once booted, no disk or usb stick
access.
Offline
Thanks will check out later
Offline
Pages: 1