On Fri, 04 Apr 2008 16:39:13 -0400, Jesse Keating wrote: > On Fri, 2008-04-04 at 21:41 +0200, Michael Schwendt wrote: > > What you call "trying to use F8's grub to load F9" is simple file-based > > chainloading in the GRUB shell. There's nothing forbidden in there, > > it's just that F8 GRUB doesn't understand F9's fs structure. > > > > > > It's likely that in the near future, I'll be nice again. Today, no > > new bug #s, because I've had enough bugzilla triage spam for stuff > > nobody cared to look at. > > > > > > But I plan to clone #440343 because it also affects F9 and has a > > high probability that it will still be open next year. > > Ah, the "My pet bug(s) didn't get looked at, so I'm giving up" syndrome. Nah, just stop here. That's silly. Look at the date of the bug. It's a recent discovery. Compare with when I started complaining about several different things. That started much earlier. It's the sum of it as why I'm fed up for some time. > I hope somebody else runs into your problem and files the bug so that > the maintainer and/or upstream realize that there is a problem and work > out a fix. > > As for 440343 that smells quite a lot like an upstream KDE bug, not a > kernel bug. Uh? You shouldn't ask for bug numbers if you diagnose the cause like that. With kernel-2.6.23.15-137.fc8 and earlier (Fedora 8, Fedora 7 and earlier) k3b has no trouble verifying written data. It started with the 2.6.24 kernels. So, even if k3b may really need to catch up with some device driver changes now, first there's the evidence that the kernel broke something. And btw, that's not just my observation. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
