Aha, I don't think so, Slackware 9.1 is already 2.6 ready, I upgraded to 2.6.0-test9 without any pain at all.
Having say that, I'm running Debian on my Evo1015 which 2.6.0 kernels constantly hang up the whole machine, and only accepts a hard reset. I can only pray that test10 patches the problem!
The installer will change the chrome directory's files ( and its subdirectories' content) into 400 unto the user who installed it! it causes us 20 mins to track down the bug!
if you see a warning msg regarding chrome://something/something/*.xul not found, you know where to solve it now.......
Slashdot Mirror
Aha, I don't think so, Slackware 9.1 is already 2.6 ready, I upgraded to 2.6.0-test9 without any pain at all.
Having say that, I'm running Debian on my Evo1015 which 2.6.0 kernels constantly hang up the whole machine, and only accepts a hard reset. I can only pray that test10 patches the problem!
The installer will change the chrome directory's files ( and its subdirectories' content) into 400 unto the user who installed it! it causes us 20 mins to track down the bug!
.......
if you see a warning msg regarding chrome://something/something/*.xul not found, you know where to solve it now