Re: Some of the parameters used in my genisoimage command don't produce a bootable ISO image
I wrote this a few days ago, but then you posted a follow-up to the
same post that used a different method, and so I never bothered to
send this.
I don't know how other people's tolerance compares with mine, but
I tried to follow some of what you did and was frustrated by what
seemed to be inconsistencies, so I gave up.
Anyway, seeing that others are lost, for one reason or another,
I just thought I'd let you see my criticisms, in case they're
of any help. They're easily dealt with and will make your postings
more robust and easier to understand, for some at least.
I haven't used cpio myself since the turn of the millenium, when
I used to frequently clone one system from another (I had a number
of identical machines). So on reading about your duplicate filenames,
the first thing I did was confirm my understanding by checking with
a toy example (posted earlier). I would suggest you play with toys
likewise, concentrating on one aspect with each toy, before you
put it all together.
On Sat 22 Oct 2022 at 22:45:20 (+0200), Mario Marietto wrote:
> Il giorno sab 22 ott 2022 alle ore 18:02 Andrew M.A. Cater ha scritto:
> > On Sat, Oct 22, 2022 at 05:13:18PM +0200, Thomas Schmitt wrote:
> > > Mario Marietto wrote:
> > > > I'm trying to change the pictures inside the /live/initrd.gz file.
> > >
> > > I really wonder where this file comes from.
> > >
> > > > 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.
> > >
> > > Prime suspect would be Cubic. The "u" in in its name means "Ubuntu".
> > > So it probably makes assumptions which the Debian Live ISO does not
> > > fulfill. Did you follow the advise of "Cubic PPA (cubic-wizard)" in
> > > https://answers.launchpad.net/cubic/+question/703422
> > > to ask your question on the "official web site" ?
> >
> > Further to this: if you are dealing with Debian-live images as your base,
> > use Debian tools. If you're dealing with Ubuntu images use Ubuntu-based
> > PPAs. In general, they really don't mix - to the extent that there's
> > a whole section on the Debian wiki to this effect.
> >
> > https://wiki.debian.org/DontBreakDebian
> >
> > The number of people working on Debian-live images at any one time is
> > small: if you can't raise anyone, then I might also suggest having
> > a chat with Roland Clobus who is working on making live images
> > work reproducibly with the Reproducible build project.
> >
> > https://wiki.debian.org/DebianLive
> >
> > I see you're already contributing on the debian-live mailing list
> > so should find the appropriate people there. highvoltage, of course,
> > is also the Debian Project leader so is very busy with everything
> > else and not necessarily debian-live build problems.
> >
> > > > So. What's my problem ?
> > >
> > > It could be that you try to squeeze the square block into the round hole.
> > > Either eliminate Cubic from your proceedings or ask its developer via
> > > https://github.com/PJ-Singh-001/Cubic/issues
> >
> This is what I did. I gone into this folder :
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/ and I
> have renamed the file "initrd.gz" into "initrd_.gz" and I've burnt a new
> ISO image. I have soon realized that that file has been regenerated. The
> initrd_.gz file disappeared and a new initrd.gz file appeared when,in
> CUBIC,I have chosen which kernel bootstrap,as you can see here :
> https://ibb.co/Xy0nKtL ; So. I suppose that the file that I should alter is
> called "initrd.img-5.10.0-19-amd64" because I have chosen that kernel
> version on the Cubic tab. And this is what I tried to do,but it didn't
> work. This is the commands that I have issued :
I don't know why you don't cut and paste the output of your commands,
instead of just writing a narrative. And if you put a timestamp and
$PWD into your prompt, and listed the files in directories as you
generated them, then you and we both could audit what you've done.
> cd /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot
I don't think you ever move higher than /home/ziomario/Scrivania/PassT-Cubic/Debian-new/
so there's no need to clutter the post by typing it over and over.
$PWD = custom-disk/boot/
> gunzip initrd.img-5.10.0-19-amd64.gz : has been produced a cpio file called
> : initrd.img-5.10.0-19-amd64
Hmm. Well that's the first oddity. Where did the gzipped initrd.img
come from?
> mv initrd.img-5.10.0-19-amd64 initrd.img-5.10.0-19-amd64_
A .cpio custom-disk/boot/initrd.img-5.10.0-19-amd64_
> cpio -idv < initrd.img-5.10.0-19-amd64_ : it has been unpacked and then
> I've copied the files inside a folder called initrd.img-5.10.0-19-amd64
I'd like to see your copy command. Anyway …
$PWD = custom-disk/boot/
A .cpio custom-disk/boot/initrd.img-5.10.0-19-amd64_
A tree rooted at custom-disk/boot/initrd.img-5.10.0-19-amd64
> cd
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64/
In the tree rooted at custom-disk/boot/initrd.img-5.10.0-19-amd64,
$PWD = custom-disk/boot/initrd.img-5.10.0-19-amd64/
> cp /usr/share/plymouth/debian-logo.png
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64/usr/share/plymouth/
>
> cp /usr/share/plymouth/themes/homeworld/debian.png
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64/usr/share/plymouth/themes/homeworld
>
> cp /usr/share/plymouth/themes/homeworld/logo.png
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64/usr/share/plymouth/themes/homeworld
In the tree rooted at custom-disk/boot/initrd.img-5.10.0-19-amd64,
$PWD = custom-disk/boot/initrd.img-5.10.0-19-amd64/
in which there is a directory called usr/share/plymouth/
> mv initrd.img-5.10.0-19-amd64 initrd.img-5.10.0-19-amd64-
$PWD = custom-disk/boot/initrd.img-5.10.0-19-amd64/
This suggests that as well as usr/share/plymouth/, there was something called
initrd.img-5.10.0-19-amd64, now called initrd.img-5.10.0-19-amd64-
at the same level as usr/…
Where did that file come from?
> cd
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64-
Now, has initrd.img-5.10.0-19-amd64- popped up a level?
Presumably there was a missed cd command.
> find . -print -depth | cpio -ov > ../initrd.img-5.10.0-19-amd64 : generated
> the cpio file called initrd.img-5.10.0-19-amd64
>
> cd ..
>
> gzip initrd.img-5.10.0-19-amd64 : generated the gzip file called "
> initrd.img-5.10.0-19-amd64"
So you gzipped foo and it gave you foo, not foo.gz?
> cd /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-root/boot/
>
> mv initrd.img-5.10.0-19-amd64 initrd.img-5.10.0-19-amd64_
So is this the old one? Is that what you started this post with?
We were never shown what custom-disk/boot/initrd.img-5.10.0-19-amd64.gz
was, nor whether it originated from somewhere in custom-root/boot/.
> cp /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/initrd.img-5.10.0-19-amd64.gz
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-root/boot/
Now, custom-disk/boot/initrd.img-5.10.0-19-amd64.gz has got its .gz
extension. That was presumably a transcribing error?
> size of the new (initrd.img-5.10.0-19-amd64) file is 178.4 MiB (187,099,720
Is this file ↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑ the gzipped one, or the
uncompressed one, or do the two files initrd.img-5.10.0-19-amd64 and
initrd.img-5.10.0-19-amd64.gz represent the same contents?
> byte),of the old one is : 78.8 MiB (82,661,551 byte) ; so probably there is
> something not good if the sizes are so different ?
Well, all my comments might seem like nitpicking, but the trouble is
that without the actual output, I don't have a clue what you /really/
did, only what you thought you did. There may be any amount of difference.
> Anyway,I've burned a new ISO image with cubic and I've tried to boot it,but
> I've got the following error : https://ibb.co/GCBFcpK
I see you've written another post, in which you say it worked.
That's good. But you will forgive me if I don't check it, because
again it's just a transcript, not the actual output. The only reason
I looked through this one was because it started with that strange
initrd.img-5.10.0-19-amd64.gz filename. My understanding is that
initrd files are /either/ .img or .gz but not both.
Cheers,
David.
Reply to: