On 03/12/2018 20.22, L A Walsh wrote:
On 12/3/2018 1:51 AM, Carlos E. R. wrote:
On 03/12/2018 06.00, George from the tribe wrote:
Is there another way to read the initrd file? It is not a file, it is an archive....
Have you tried this:
table of contents (I don't remember cpio invocation for ToC)
star -t <initrd.img
or to extract
mkdir img && cd img && gunzip <initrd.img |cpio -i
If you want to create devices, w/cpio, you'll need to be root.
Is that what you were wanting?
That's what I explained, yes. But it is not that trivial, because the cpio part is preceded by a cpu firmware update part, that has to be bypassed first. That's what the "skipcpio" command does. Once you obtain the real tree contained in the archive, the second part is to grep all the files in it to find out which file contains the reference to the wrong uuid. Once this is found, the next step would be finding out why it is created and correct it. I have been saying this since the first message, in less words. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)