2008/4/25 David Broadfoot <[EMAIL PROTECTED]>:
> I concur with Ken. The way I do it is I keep my orogional kernel and add
> the new one as a non default option to the botloader. Then, you can play
> with the kernel until U get it working perfectly with your system. Then,
> change the default to the
I concur with Ken. The way I do it is I keep my orogional kernel and add
the new one as a non default option to the botloader. Then, you can play
with the kernel until U get it working perfectly with your system. Then,
change the default to the new kernel. Keep the old kernel available in
case
On Fri, Apr 25, 2008 at 07:05:17AM -0400, Alonso Graterol wrote:
> Hello,
>
> I'm thinking on update my current 2.6.22.15 kernel to one more
> recent if not the latest. I'm running a x86-64 pure 64 bit CBLFS
> system.
> Should I expect any trouble? Should I also update the kernel
> headers? Un
Hello,
I'm thinking on update my current 2.6.22.15 kernel to one more
recent if not the latest. I'm running a x86-64 pure 64 bit CBLFS
system.
Should I expect any trouble? Should I also update the kernel
headers? Unless it is strictly necessary I don't want to build another
system from scratch
