TheRudy
14th July 2006, 12:48
Yes, the title is scary :D
http://www.debian.org/News/2006/20060713
Anyways, since i'm using kernel 2.6.14-2-686-smp and there it says that this is one of the versions that has this bug in it, i was kinda thinking of upgrading kernel untill i rememberd that this was the only kernel that recognized my SATA disks. Probably upgrading it and rebooting will result in non-bootable error or am i wrong?
If i get new kernel, won't it put it into grub loader and ask me which kernel to load? So even if the newest version of kernel doesn't work, i can simply boot from current kernel.
Not sure here, that's why i'm asking about this but i do remember that when ubuntu kernel was upgraded on my desktop that i had 2 entries at grub boot to choose from. Will this be the same deal?
Basically, just a precaution questions before i go messing on the live server :)
On the other hand, debians server was hacked cause attacker got 1 of the users account info.. so..
http://www.debian.org/News/2006/20060713
Anyways, since i'm using kernel 2.6.14-2-686-smp and there it says that this is one of the versions that has this bug in it, i was kinda thinking of upgrading kernel untill i rememberd that this was the only kernel that recognized my SATA disks. Probably upgrading it and rebooting will result in non-bootable error or am i wrong?
If i get new kernel, won't it put it into grub loader and ask me which kernel to load? So even if the newest version of kernel doesn't work, i can simply boot from current kernel.
Not sure here, that's why i'm asking about this but i do remember that when ubuntu kernel was upgraded on my desktop that i had 2 entries at grub boot to choose from. Will this be the same deal?
Basically, just a precaution questions before i go messing on the live server :)
On the other hand, debians server was hacked cause attacker got 1 of the users account info.. so..