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

On Mon, Jun 26, 2006 at 06:57:45PM +0100, Nix wrote:
> 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?
It is included in kbuild.git - and Linus has been asked to pull that
tree. It is also forwarded to [email protected] for inclusion in next
stable release.

	Sam
-
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: Nix <[email protected]>

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

• Prev by Date: Re: [Suspend2][ 2/2] [Suspend2] Freezer upgrade.
• Next by Date: Re: [patch 2/6] [Network namespace] Network device sharing by view
• Previous by thread: Re: [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]