The Linux distributors detail their plans on when they’ll be introducing Linux 2.6 into their commercial releases, while the analysts consider what 2.6 will mean to Microsoft and users. Fedora already has some test 2.6 kernels and Slackware now too in its -Current tree.
Getting Linux 2.6 Into The Enterprise
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
“Slackware now too in its -Current tree.”
gentoo too: emerge -p development-sources
it runs smooth altought i cant bind nvidia module
I’m sure they will bring out a better installer
soon. The beta looks good
http://www.minion.de/
i’ve had it running nicely for a while on slackware with gnome and i must say that its the slickest desktop i’ve ever used. Although i never had the chance really to try beos before. so i’m likely starved of a experiance.
The SCO Group director of public relations, Blake Stowell, stated, “To our knowledge, 2.6 builds upon the intellectual property violations that continue to be in 2.4. JFS, NUMA, XFS, RCU, and a host of other code violations have not been removed. SCO’s position remains unchanged.”
I’ve been using one of those test kernels and it seems to be working quite well. Only problems encountered were switching over from OSS to ALSA. Took me about 2 hours before I realizing ALSA mixer needed to be set.
2.6.0 handles my music to much better than the highly patched 2.4 series I had been using before. The kernel build process is far more polished.
With kde 3.2b2 (after fixing Redhat’s damage) and 2.6.0, Fedora is by far the slickest distro in my own opinion.
Mandrake 9.2 was nice, but not what I’ve been looking for.
“Slackware now too in its -Current tree.”
All Pat did was adding the source to the testing dir so slack users still have to compile 2.6 for themselves (whereas Fedora, MDK, … already have installable binary kernels).
Am I the only one who thinks that this article was pretty useless? Nothing I haven’t heard before or anyone reads osnews once a week has heard before.
Mandrake released a cooker snapshot iso with kernel 2.6.0dayortwobeforefinal, and 2.6.0final is in the cooker mirrors now. Seems to be quite solid and enjoyable to use.
Hope they are aware of the Memory Corruption problem introduced by Linus around 2.6.0-pre9 and upwards and by many other people on the lkm.
What year is this? Is that you, Picard?
I’m running Fedora and also like it very much. However, my sound does not work with the 2.6.0 kernel. What did you do to get your sound working?
actualy, Capt. Picard says in the second to finaly episode
“counselor, what is the date”
Spike TV just had it on 🙂
Hey,
Mandrake has had 2.6 in cooker for a few days now. It works quite good. Mdk really deserves more publicity than it receives. I belive most of their kernels are 2.6 now.
Taras
I guess that it would make sense to have a standard set of libraries that all of the distributions would be able to meet so that it would be easier to deploy software on Linux. Is that what OSDL is going to establish?
Not bad!
I’m not using a 2.6 kernel on the box I’m running Fedora on, so I haven’t run into the problem personally. But have you checked that all of the volume settings are un-muted (master and PCM especially)? A lot of people seem to run into this when using ALSA for the first time. Also, did you compile the kernel yourself or did you download a binary? If you compiled yourself, did you compile the module for your sound card? If you didn’t compile yourself, have you checked and made sure that the module corresponding to your soundcard is actually up and running? (For a list of cards and modules, go to
http://www.alsa-project.org/alsa-doc/index.php3?vendor=All#matrix
and find your soundcard, and click on “details” in the drivers and docs column.)
if you have problems installing your nvidia drivers in gentoo, it’s probably because you haven’t relinked /usr/src/linux to the correct directory. relink it and emerge nividia drivers
To get it on the enterpise, Linux would need warp core drivers, more robust shield modulation among other things.
I think 2.6 will be a big boost to enterprise Linux. After all, 2.4 didn’t quite do it at the high end, unless massively patched. But when you think how far Linux has gone under 2.4, just wait until 2.6 is solid and widely deployed.
Personally, I’m very excited about 2.6, but I’m waiting a little longer before switching on my machine. There’s a huge amount of fairly important stuff queued for the first few patch releases, and I’m going to wait until that settles down a bit. Oh, and for nvidia to release an official 2.6 driver!
“To get it on the enterpise, Linux would need warp core drivers, more robust shield modulation among other things.”
True, but at least it won’t BSOD and cause embarrasing situations like the one that occured in Star Nebula V. Pretty hard discribing to the brass that everyone on board died when the StarShip Liberty Oxygen generation Unit blue screened. Of course, Microsoft was protected by it’s EULA.
Well I have an Audigy and I have to manually load the emu10kl module. Apparently module.conf is deprecated. No ALSA here.
(MDK10)
IMHO, this is going to be yet another 2.4 release. Released too early with too many bugs. PPP problems, memory corruption and I am sure there are lots of other “features” people can point out, like the 24GB limit.
The fact remains that it should been more rigolously tested before it was released.
br: modules.conf is indeed deprecated. If you installed the right Cooker packages, though, you should have got an auto-generated version of its replacement, modprobe.conf, including all your old modules.
Anyone else find 2.6.0 still crashes every so often under heavy disk load on nforce2? It’s nowhere near as bad as it was in the 2.5 and 2.6-test stages, but the problem’s still there.
Am I the only one who thinks that this article was pretty useless? Nothing I haven’t heard before or anyone reads osnews once a week has heard before.
Perhaps, but the same could be said for all the “useless” Longhorn articles too. I’m just glad for something new to read every now and then.
Can you link to the memory corruption problem–other than with preempt enabled? And what about this 24GB limit? It’s 16TB, not 24GB. Link to PPP problems?
It has been extensively tested; for the past five months I have been running it, and it’s extremely stable and fairly issue-free.
I run debian stable on a server. If this server breaks down or is compromised, me and several other people are screwed. There are applications on this server that should better run reliably 24/7, otherwise some customers might get really annoyed and choose somebody else.
To be completely buzzword compliant, I would have to refer to the above server as a mission critical enterprise backend application server or something.
But for me it is just a server. It does what it is supposed to do and its uptime is measured in years.
Debian stable handles this just fine with a minimum of fuss, and yet some people claim that debian is not ready for the enterprise. There is nothing magical about the enterprise. A system that can run for years without crashing and that does not require much maintenance is enterprise-ready enough for me, whatever other people say.
To get back on topic: I have been running 2.6pre9 on my home system for some time now, and I did not have any issues with it. I will wait for maybe 2.6.2 and then I will update the above server to 2.6. I won’t lose any sleep doing it since my experiences with 2.6 have been extremely good so far.
Can you link to the memory corruption problem–other than with preempt enabled? And what about this 24GB limit? It’s 16TB, not 24GB. Link to PPP problems?
It has been extensively tested; for the past five months I have been running it, and it’s extremely stable and fairly issue-free.
http://kerneltrap.org/node/view/1816
Don’t assume that I am a Windows fanboy. From the tone of your post, it sounds as though your accuse me of Windows trolling.
Of course there will be another 2.4 release, probably quite a few. It has just gone into maintenance mode that is all, just like the 2.2 kernel.
I think 2.6 is reasonably stable, though I would not use it on a server yet. Yes there are a number of issues remaining, but nothing I saw looked “critical.” They had to release a 2.6 sometime to get it out to a wider audience, there just are not nough people willing to run a beta kernel. All that said, I read the link you attached and still could not find the reference to the 24GB limit, did I miss it?
(Also, it is always nice to include links when you make statements like that. I had not seen that document before and found it quite enlightening.)