Re: [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16

On 21 Jun 2006, [email protected] stipulated:
> It didn't take long to work out that this was because my initramfs's
> contents were being included twice in the cpio image.

Ping? Anyone?

-- 
`NB: Anyone suggesting that we should say "Tibibytes" instead of
 Terabytes there will be hunted down and brutally slain.
 That is all.' --- Matthew Wilcox
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16
    • From: Sam Ravnborg <[email protected]>

• References:
  • [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16
    • From: Nix <[email protected]>

• Prev by Date: Re: PATCH: SC1200 debug printk
• Next by Date: Re: [Fastboot] [RFC] [PATCH 2/2] kdump: cciss driver initialization issue fix
• Previous by thread: [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16
• Next by thread: Re: [PATCH] Fix 100% initramfs bloat in 2.6.17 versus 2.6.16
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]