For all you Linux fans, new version of Linux has been relesed (v2.6.13).
Article: http://lkml.org/lkml/2006/3/20/9
Full changelog: http://www.kernel.org/pub/linux/kern...angeLog-2.6.16
For all you Linux fans, new version of Linux has been relesed (v2.6.13).
Article: http://lkml.org/lkml/2006/3/20/9
Full changelog: http://www.kernel.org/pub/linux/kern...angeLog-2.6.16
Last edited by nixdude; 03-20-2006 at 12:45 PM.
I'm using 2.6.16-rc6 and I'll probably just wait for a couple of point releases (e.g. 2.6.16.2) now to get on the stable track again. It's more of a pain for me nowadays, because I have to compile and install it, then reboot and compile vmware kernel modules (and patch if new kernel breaks them). Then I have to copy the new kernel, source and modules tree to my gaming setup and fix up lilo and stuff, then boot there and redo the Nvidia drivers to compile kernel module (again, patch if necessary). I keep those two setups in sync, so I don't have to compile software twice.
I used to play with my kernel nearly every day but now I tend to keep a kernel for a week or two![]()
heheh, well, since making that post I bit the bullet and stopped procrastinating. Everything seems to be good.
I'm still on 2.6.12.2. Gonna stay with it for a long time. At least until I either buy or build another computer. Gonna stay away from slack current as well. That just caused too many problems.
I knew you was spittin' into cyberspace Sensei - just had to do it, didn't ya!!!
Originally Posted by mlangdn
funny you should mention slack current M..just upgraded xorg(some sort of security fix)..well it sure fixed something..i can no longer log in as user..but works fine as root...
..luckely i have pclos,and also a spare slack install(which i happen to be typing this post from) just in case of crazy shit like what just happened..i guess i'll wait and see how i can fix it..probably will roll back to previuos xorg,if he doesn't make a fix soon..
just part of playing with development shit![]()
:ROFLMAO:Originally Posted by labatts
Now that's the best fix out there. think in the lines of a developer writing for a realtime linux system server, etc. The onlyone who should really have roo access is the sys admin. Who breaks the setup the most? the user. Therfore to make a truly secure system, get rid of that troublesome pest!
VODKA : IT'S NOT JUST A BREAKFAST DRINK!
9-11.......... ALL GAVE SOME..............SOME GAVE ALL ................NEVER FORGET !!
yep makes perfect sense..turns out that xorg wasn't set suid in these packages..so i chmoded the bitch,and my troublesome user is allowed access to x again...He'll probably release new packages with this problem fixed..
Bookmarks