-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 27 March 2003 07:32 pm, Jack Bowling wrote:
> ** Reply to message from Michael Fratoni
> on Thu, 27 Mar 2003 18:58:14 -0500
> > I used to think so as well. And I'm sure I had to do both in the past
> > at some point. However on the Pheobe
** Reply to message from Michael Fratoni <[EMAIL PROTECTED]> on Thu, 27 Mar 2003
18:58:14 -0500
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thursday 27 March 2003 03:05 am, Jack Bowling wrote:
> > ** Reply to message from Michael Fratoni
> > on Wed, 26 Mar 2003 23:08:22 -0500
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 27 March 2003 03:05 am, Jack Bowling wrote:
> ** Reply to message from Michael Fratoni
> on Wed, 26 Mar 2003 23:08:22 -0500
> > On Wednesday 26 March 2003 04:14 pm, Robert P. J. Day wrote:
[...]
> > > so, before i spend a lot of time on
** Reply to message from Michael Fratoni <[EMAIL PROTECTED]> on Wed, 26 Mar 2003
23:08:22 -0500
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wednesday 26 March 2003 04:14 pm, Robert P. J. Day wrote:
> > in a fit of poor judgment, i tried to test the new 2.5.66 kernel
> > on my RH 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 26 March 2003 04:14 pm, Robert P. J. Day wrote:
> in a fit of poor judgment, i tried to test the new 2.5.66 kernel
> on my RH 8.0 box, and not only did it explode in glorious ways,
> it made a mess of my nvidia setup.
>
> in recovering
in a fit of poor judgment, i tried to test the new 2.5.66 kernel
on my RH 8.0 box, and not only did it explode in glorious ways,
it made a mess of my nvidia setup.
in recovering to an older, working kernel, i now find i can't
rebuild the NVIDIA kernel src rpms (loads of parse errors from
/usr
