MSGID: 1:153/757.0 01c3b9e0   
   REPLY: 1:261/38.0 af859e28   
   TZUTC: -0800   
   CHRS: LATIN-1 2   
   > Anyone else have a problem with the LFS section on creating an initrd? Me   
   > and a friend tried the mkinitramfs from   
   > https://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html   
      
   > When we ran it, we wound up with a 770Mb file. When we extracted it with   
   > cpio, it only extracted about 64K bytes. We tried a few times and the   
   > results were consistent.   
      
   > It only contained a few files, related to microcode (I don't have access to   
   > his computer right now so I can't be more specific).   
      
   That sounds like the microcode bits were prepended to the initrd file.   
      
   If that is the case then it's hard to inspect the rest of the contents of that   
   file, at least in the usual way.   
      
   I don't normally use an initramfs but I had one with a gentoo install and I   
   found the same thing. Gentoo's initramfs tool (i forget what it called now)   
   created a huge initramfs but I was only able to see the intel-ucode bits of it   
   when I tried to look inside of it.   
      
   It must have contained a lot of modules but it did boot up just fine.   
      
   --- BBBS/Li6 v4.10 Toy-6   
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/709 123/131 124/5016   
   SEEN-BY: 129/305 134/100 153/135 141 143 757 6809 7001 7715 154/10   
   SEEN-BY: 203/0 218/700 221/0 1 6 226/30 227/114 229/111 112 113 206   
   SEEN-BY: 229/307 317 400 424 426 428 452 470 550 616 664 700 240/1120   
   SEEN-BY: 240/5832 266/512 280/464 5003 282/1038 292/789 854 8125 301/1   
   SEEN-BY: 310/31 317/3 320/219 322/757 335/364 341/66 234 342/200 396/45   
   SEEN-BY: 410/9 423/120 460/58 633/280 712/848 770/1 5020/545   
   PATH: 153/757 280/464 292/854 229/426