On Thu, Jul 20, 2006 at 09:11:21AM -0700, Chris Wedgwood wrote:
> On Thu, Jul 20, 2006 at 02:28:32PM +0100, David Greaves wrote:
>
> > Does this problem exist in 2.16.6.x??
>
> The change was merged after 2.6.16.x was branched, I was mistaken
> in how long I thought the bug has been about.
>
> > I hope so because I assumed there simply wasn't a patch for 2.6.16 and
> > applied this 'best guess' to my servers and rebooted/remounted successfully.
>
> Doing the correct change to 2.6.16.x won't hurt, but it's not
> necessary.
Yep. As Chris said, 2.6.17 is the only affected kernel. I've
fixed up the whacky html formatting and my merge error (thanks
to all for reporting those) so its a bit more readable now.
cheers.
--
Nathan
-
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/
[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]
