linux-kernel - Re: 2.6.22-rc4-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070607085200.f8d6e2d3.akpm@linux-foundation.org>
Date:	Thu, 7 Jun 2007 08:52:00 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Greg KH <gregkh@...e.de>
Cc:	Peter Jones <pjones@...hat.com>,
	Kay Sievers <kay.sievers@...y.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22-rc4-mm1

On Thu, 7 Jun 2007 08:43:42 -0700 Greg KH <gregkh@...e.de> wrote:

> >  Fixed in mkinitrd-6.0.9-6 , which I'll build now and push to 
> >  updates-testing.  Thanks for getting my attention here.
> 
> Great, Andrew, can you please reenable the block-device patch that is in
> my tree now that the problem has been solved?

I think we're screwed, aren't we?  Everyone needs to upgrade mkinitrd to be
able to boot the kernel?  Not viable :(

For example, what about my two-year-old yellowdog machine?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/