Can I delete /boot/initrd-tree?

[R2-D2]

Hi all, I'm reading
https://ftp.slackware.com/pub/slackware/slackware-15.0/README.initrd

I'm wondering, is the directory /boot/initrd-tree used only during the creation
of /boot/initrd.gz, or is it read on every subsequent boot?

Being a little tight on my /boot partition, I'd gladly delete it. I'd save about
37MB.

[John McCue]

I just built a new initrd.gz today for the updated kernel,
I noticed it had old files plus new files. So that makes
me think it is used to build new initrd.gz files.

You can try moving /boot/initrd-tree to /initrd-tree,
create a symb link to /boot then reboot to see what
happens.

John

--
[t]csh(1) - "An elegant shell, for a more... civilized age."
- Paraphrasing Star Wars

[Giovanni]

Yes you can delete the directory and its content.

The command mkinitrd has an option to clear the tree first ( -c ) and it
is recommended.

The script /var/lib/pkgtools/setup/setup.01.mkinitrd generates during
the installation process, a command line for mkinitrd which includes the
-c option to get a fresh, clean initrd image based on the new kernel.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >

[R2-D2]

Giovanni wrote on 3/10/22 10:42:

> On 3/9/22 19:14, R2-D2 wrote:
>> Hi all, I'm reading
>> https://ftp.slackware.com/pub/slackware/slackware-15.0/README.initrd
>>
>> I'm wondering, is the directory /boot/initrd-tree used only during the
>> creation of /boot/initrd.gz, or is it read on every subsequent boot?
>>
>> Being a little tight on my /boot partition, I'd gladly delete it. I'd save
>> about 37MB.
>
> Yes you can delete the directory and its content.

Thanks, done. Rebooted flawlessly. Now I can go on with the latest kernel update.