>Didn't you strive for manipulating the initrd in /d-i/gtk/initrd.gz of the
ISO ?
I have already changed the pictures inside the /d-i/gtk/initrd.gz file,now
I'm trying to change the pictures inside the /live/initrd.gz file. The
initrd.img-5.10.0-18-amd64 file is in the /custom-root/boot folder,but I
never changed the images inside of this file. Despite this,at some point of
debian booting,I see the old picture that I have added inside the
/live/initrd.gz file and I know that the image that I should change is
inside there. I have followed your suggestions,doing something like this :
gunzip /live/initrd.gz
cpio -idv < /live/initrd
cd initrd
find . -print -depth | cpio -ov > ../initrd
gzip initrd
BUT after having "burned" another ISO image using Cubic,I've seen that it
still uses the old images that I have previously added inside the
/live/initrd file. I don't understand why ? It seems that this file is
re-generated taking the files from somewhere else.
>Are you still with debian-live-11.5.0-amd64-xfce.iso , where I see no
/live/initrd.gz but /live/initrd.img-5.10.0-18-amd64 ?
Inside the "live" folder I have the following files :
config-5.10.0-18-amd64
filesystem.size
initrd-unpacked
initrd.gz
vmlinuz
filesystem.manifest
filesystem.squashfs
initrd
System.map-5.10.0-18-amd64
There isn't any "initrd.img-5.10.0-18-amd64" file in that folder. BUT on
the custom-root/boot folder I have these files :
config-5.10.0-18-amd64 initrd.img-5.10.0-19-amd64
vmlinuz-5.10.0-18-amd64
config-5.10.0-19-amd64 initrd.img-5.19.0-15.2-liquorix-amd64
vmlinuz-5.10.0-19-amd64
config-5.19.0-15.2-liquorix-amd64 System.map-5.10.0-18-amd64
vmlinuz-5.19.0-15.2-liquorix-amd64
initrd.img-5.10.0-18-amd64 System.map-5.10.0-19-amd64
initrd.img-5.10.0-18-amd64-sos System.map-5.19.0-15.2-liquorix-amd64
and on the custom-disk/boot folder I have these files :
config-5.10.0-18-amd64 initrd.img-5.10.0-19-amd64
vmlinuz-5.10.0-18-amd64
config-5.10.0-19-amd64 initrd.img-5.19.0-15.2-liquorix-amd64
vmlinuz-5.10.0-19-amd64
config-5.19.0-15.2-liquorix-amd64 System.map-5.10.0-18-amd64
vmlinuz-5.19.0-15.2-liquorix-amd64
grub System.map-5.10.0-19-amd64
initrd.img-5.10.0-18-amd64 System.map-5.19.0-15.2-liquorix-amd64
So. What's my problem ? I hope you understood,because I'm getting tired of
getting the same wrong result. I have burned the ISO image thousands of
times.
Il giorno sab 22 ott 2022 alle ore 09:09 Thomas Schmitt <scdbac...@gmx.net>
ha scritto:
> Hi,
>
> Mario Marietto wrote:
> > echo /usr/share/plymouth/themes/homeworld/logo.png | cpio -H newc -o -A
> -F
> > /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/live/initrd
>
> Didn't you strive for manipulating the initrd in /d-i/gtk/initrd.gz of
> the ISO ?
> (Are you still with debian-live-11.5.0-amd64-xfce.iso , where i see
> no /live/initrd.gz but /live/initrd.img-5.10.0-18-amd64 ?)
>
>
> > echo /usr/share/plymouth/debian-logo.png | cpio -H newc -o -A -F initrd
>
> I see in both initrds only relative paths.
> In /live/initrd.img-5.10.0-18-amd64 :
> .
> bin
> conf
> conf/arch.conf
>
> In /d-i/gtk/initrd.gz :
> bin
> bin/anna
> bin/anna-install
>
> So i would strive for such a path with the appended file:
>
> cd / ; echo usr/share/plymouth/debian-logo.png | cpio ...
>
>
> > Furthermore,I would like to know how to remove a file that's stored
> inside a
> > cpio archive
>
> For that you have to unpack the cpio archive, do the desired manipulations,
> and pack up the archive from the manipulated tree.
> (This will also avoid multiple occurences of the same file path, of which
> the last one survives when unpacking the archive.)
>
> So it's about time you read
> https://www.gnu.org/software/cpio/manual/cpio.html
> which proposes for unpacking:
>
> cpio -idv < tree.cpio
>
> Do this in some playground directory. "tree.cpio" is the placeholder name
> for your decompressed archive. If you have absolute paths in the archive
> you need option --no-absolute-filenames.
>
> The manual proposes for packing up the manipulated archive:
>
> find . -print -depth | cpio -ov > tree.cpio
>
> Option -v will cause both operations to report all file paths.
> You might want to omit it.
>
>
> Have a nice day :)
>
> Thomas
>
>
--
Mario.
