bug-cpio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-cpio] Fw: How come the initrd cpio archives are so large?


From: Shlomi Fish
Subject: Re: [Bug-cpio] Fw: How come the initrd cpio archives are so large?
Date: Tue, 22 Jan 2019 10:18:21 +0200

Hi,

On Mon, 21 Jan 2019 18:47:43 +0100
Reuti <address@hidden> wrote:

> Hi,
> 
> > Am 21.01.2019 um 14:59 schrieb Shlomi Fish <address@hidden>:
> > 
> > Hi all!
> > 
> > Can anyone address my concern?
> > 
> > Begin forwarded message:
> > 
> > Date: Mon, 21 Jan 2019 12:47:21 +0200
> > From: Shlomi Fish <address@hidden>
> > To: Linux-IL <address@hidden>
> > Subject: How come the initrd cpio archives are so large?
> > 
> > 
> > Hi all!
> > 
> > address@hidden:~/initrd/good/unpack # ls -l ../img
> > -rw------- 1 root root 11419609 Jan 21 11:42 ../img
> > address@hidden:~/initrd/good/unpack # cpio -i  < ../img
> > 26 blocks
> > address@hidden:~/initrd/good/unpack # du .
> > 16K     ./kernel/x86/microcode
> > 20K     ./kernel/x86
> > 24K     ./kernel
> > 32K     .
> > address@hidden:~/initrd/good/unpack #
> > 
> >   
> > ==> why is the initrd cpio image so large in comparison to its contents?    
> 
> Because it contains more than a single file, i.e. a compressed directory tree
> is attached:
> 
> https://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel
> 

Thanks!

Yes, as I discovered one should use dracut's lsinitrd -
http://man7.org/linux/man-pages/man1/lsinitrd.1.html - possibly with "--unpack"
to extract an initrd.

> -- Reuti
> 




-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
NSA Factoids - http://www.shlomifish.org/humour/bits/facts/NSA/

Objective Visual Turbo Global jIronOpenPerl++.NET™ Enterprise Edition♭
Professional Home Premium Ultimate 64-bit Single-user.
    — based on a Freenode #perl conversation ( http://is.gd/cCUBY2 )

Please reply to list if it's a mailing list post - http://shlom.in/reply .



reply via email to

[Prev in Thread] Current Thread [Next in Thread]