Linux Kernel 2.6.32 LTS Reaches End of Life In February 2016 (softpedia.com)

← Back to Stories (view on slashdot.org)

Linux Kernel 2.6.32 LTS Reaches End of Life In February 2016 (softpedia.com)

Posted by timothy on Saturday January 30, 2016 @06:29PM from the long-time-coming dept.

An anonymous reader writes: The oldest long-term supported Linux kernel branch finally reaches end of life next month, but before going into the deepest darkest corners of the Internet, it just dropped one more maintenance release, Linux kernel 2.6.32.70 LTS. Willy Tarreau dropped the news about the release of Linux kernel 2.6.32.70 LTS on January 29, 2016, informing all us that this will most likely be the last maintenance release in the series, as starting with February 2016 it will no longer be supported with security patches and bugfixes. Linux 2.6 first came out in December, 2003, and 2.6.16 (the first long-term release) in March 2006.

116 comments

Min score:

Reason:

Sort:

So long by Anonymous Coward · 2016-01-30 18:32 · Score: -1

And thanks for all the bugs. First post for open sores!
RHEL6 by fnj · 2016-01-30 18:33 · Score: 1

What happens to RHEL6?
1. Re:RHEL6 by Anonymous Coward · 2016-01-30 18:39 · Score: -1, Troll
  
  I guess you'll have to get off your fat lazy ass and upgrade to a proper modern system equipped with systemd
2. Re: RHEL6 by Anonymous Coward · 2016-01-30 18:40 · Score: 0
  
  The SystemD replaced it.
3. Re:RHEL6 by whoever57 · 2016-01-30 19:00 · Score: 3, Insightful
  
  What happens to RHEL6?
  Red Hat will back port fixes, just like they do with many, many packages.
  
  --
  The real "Libtards" are the Libertarians!
4. Re:RHEL6 by arth1 · 2016-01-30 19:02 · Score: 5, Informative
  
  What happens to RHEL6?
  EL6 will still be supported by Red Hat and Scientific Linux for many years to come.
  There are alternatives, like Gentoo, but for inexplicable reasons, Gentoo has dropped support for kernel 3.2, which is currently the kernel with the longest remaining support (until May 2018).
  4.4, the second most LTS, is too bleeding edge for many. If the goal is to keep a system with max uptime, but still get critical kernel fixes if and only if needed, the best bet might be to stay at EL6 for now.
5. Re:RHEL6 by Anonymous Coward · 2016-01-30 19:04 · Score: -1
  
  Gentoo is for faggots. The inexplicable is now explained.
6. Re:RHEL6 by Anonymous Coward · 2016-01-30 19:07 · Score: 0
  
  It's open source. That's the great thing. RH can take the code and maintain it themselves if the community doesn't do any thing with it until they retire RHEL6
7. Re:RHEL6 by Anonymous Coward · 2016-01-30 19:16 · Score: 4, Interesting
  
  Please no. The swallowing of stderr makes it very difficult to troubleshoot startup problems. Just today I had a simple problem that was very hard to find because of systemd:
  # systemctl start mongod ; echo $? 0 # journalctl -u mongod Jan 30 20:58:29 storage3.maui.ascentis-prod.com systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database.... Jan 30 20:58:29 storage3.maui.ascentis-prod.com runuser[5767]: pam_unix(runuser:session): session opened for user mongod by (uid=0 Jan 30 20:58:29 storage3.maui.ascentis-prod.com mongod[5760]: Starting mongod: [FAILED] Jan 30 20:58:29 storage3.maui.ascentis-prod.com systemd[1]: mongod.service: control process exited, code=exited status=1 Jan 30 20:58:29 storage3.maui.ascentis-prod.com systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database. Jan 30 20:58:29 storage3.maui.ascentis-prod.com systemd[1]: Unit mongod.service entered failed state. Jan 30 20:58:29 storage3.maui.ascentis-prod.com systemd[1]: mongod.service failed.
  Notice starting it exited with no error, and there's no clue as to what happened in the journal!
8. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:18 · Score: 0
  
  Oh please. As if the average person even knows how to check the exit status.
9. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:20 · Score: 1, Informative
  
  Did you have a /var/lib/mongo/mongo.lock file? If so, the problem was your own fault.
10. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:21 · Score: 0
  
  MongoDB isn't stable yet. You shouldn't use it.
11. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:23 · Score: 1
  
  systemd correctly handles exit statuses even though they're old cruft that should be removed. Your startup script is broken.
12. Re:RHEL6 by kthreadd · 2016-01-30 19:23 · Score: 4, Informative
  
  They already do that. The 2.6.32 kernel that you get in RHEL 6 is not exactly the same 2.6.32 that you get from kernel.org. There are many backported features already implemented that the upstream kernel does not include.
13. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:24 · Score: -1
  
  Because you don't know how to use the journal. Everything is properly logged unlike with syslog.
14. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:26 · Score: -1
  
  I guess you're just not strong enough for handling the superior solution that is SystemD.
15. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:27 · Score: 0
  
  This. His unit file is broken.
16. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:28 · Score: -1
  
  This. systemd is better than SysV init scripts in every way. He'd have even more problems without systemd.
17. Re:RHEL6 by Anonymous Coward · 2016-01-30 19:30 · Score: -1
  
  I thought systemd was for faggots. gentoo lets you avoid systemd.
18. Re:RHEL6 by Anonymous Coward · 2016-01-30 19:30 · Score: 0
  
  It's open source. That's the great thing. RH can take the code and maintain it themselves if the community doesn't do any thing with it until they retire RHEL6
  The greatest thing is your OS vendor does't write the system, they "maintain" it with duct tape and super glue.
19. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:30 · Score: 0
  
  Why in the hell would you check exit statuses in 2016? How long is your beard?
20. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:31 · Score: 0
  
  You are the one doing something wrong, not systemd.
21. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:35 · Score: 0
  
  Those old people don't understand that the rest of the world has moved on.
22. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:36 · Score: 0
  
  Exactly. His unit file is broken.
23. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:37 · Score: -1
  
  Also, it's about time MongoDB developers get their shit together and make sure their product runs smooth under SystemD.
24. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:40 · Score: 5, Informative
  
  Did you have a /var/lib/mongo/mongo.lock file? If so, the problem was your own fault.
  You are correct. That was the problem, but I still don't think systemd should have exited with a 0 (no error) or swallowed the log message that clearly stated the problem. When I ran "sudo mongod mongod -f /etc/mongod.conf" the problem was clearly output to the console. After deleting the lock file, systemd was able to start MongoDB.
  I've seen this problem on dozens of servers since we have nearly 300 MongoDB instances. systemd makes life much harder.
25. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:42 · Score: -1
  
  They're useless in desktop systems so systemd is correct in dropping that out of date concept.
26. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:43 · Score: 1
  
  No. Exit statuses should still be reported for hysterical raisins.
27. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:45 · Score: 0
  
  Wow, the signal to noise ratio here has dropped to almost nothing. Fix your unit files.
28. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:47 · Score: 0
  
  I'm upset INTERCAL doesn't run any longer, but you don't see me bitching here about it.
29. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:48 · Score: 0
  
  He is also probably still a JCL fanboi
30. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:50 · Score: 0
  
  KIBO is the problem with systemd. The systemd guys always blame the unit files, but never offer fixes.
31. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:53 · Score: 0
  
  What do dried grapes have to do with broken exit statuses?
32. Re: RHEL6 by Anonymous Coward · 2016-01-30 19:59 · Score: -1
  
  Indeed. SysV would be like going back to the crusty CONFIG.SYS / AUTOEXEC.BAT times.
33. Re: RHEL6 by KGIII · 2016-01-30 20:09 · Score: 1
  
  Actually, I'm just shocked that someone got the signal to noise ratio pointed in the right direction. Most people say that exactly backwards. "I like that place. The signal to noise ratio is really low!" Well, they are not necessarily wrong. I'm just not sure why one would prefer an environment where separation of noise and signal is difficult. It is really kind of odd how frequently someone posts it backwards.
  
  --
  "So long and thanks for all the fish."
34. Re: RHEL6 by Anonymous Coward · 2016-01-30 20:25 · Score: 0
  
  Of course the problem is his fault. But it's the fault of the system for hiding the error from him. I mean, if your systems never have a single error, you WOULD like a system that doesn't bother writing the errors out in a sensible way.
35. Re: RHEL6 by Anonymous Coward · 2016-01-30 20:39 · Score: 0
  
  You admit it's your own damn fault.
36. Re:RHEL6 by arglebargle_xiv · 2016-01-30 20:41 · Score: 5, Funny
  
  systemctl start mongod
  Well there's your problem, you've mangled your languages. If you'd used:
  systemctl start mondieu
  you'd have got the response you were expecting:
  # Bonjour, je m'appelle Linus.
37. Re: RHEL6 by Anonymous Coward · 2016-01-30 20:58 · Score: 0
  
  he he he
38. Re:RHEL6 by 93+Escort+Wagon · 2016-01-30 21:14 · Score: 1
  
  It's open source. That's the great thing. RH can take the code and maintain it themselves if the community doesn't do any thing with it until they retire RHEL6
  I'm not sure why people still don't get that the largest part of this so-called "community" is made up of paid Red Hat employees.
  Linux isn't really being maintained by a bunch of guys doing it for free out of the goodness of their hearts in their spare time.
  
  --
  #DeleteChrome
39. Re: RHEL6 by Anonymous Coward · 2016-01-30 21:22 · Score: 0
  
  I don't know, are you running Wine, maybe?
40. Re:RHEL6 by thegarbz · 2016-01-30 21:52 · Score: 1, Informative
  
  Notice starting it exited with no error, and there's no clue as to what happened in the journal!
  Yeah I notice that. Which means either:
  a) you didn't setup systemd-system.conf to your liking.
  b) mongodb isn't outputting the error.
  c) you couldn't be stuffed reading the log file for mongo (not everything logs to syslog or the journal)
  d) you assume systemd is magical and the computer will run itself despite configuration problems or coding errors in the software.
  e) all of the above.
41. Re:RHEL6 by Anonymous Coward · 2016-01-30 21:59 · Score: 0
  
  systemctl rmpkg systemd
  # Bonjour, bienvenue sur unix.
42. Re:RHEL6 by Zontar+The+Mindless · 2016-01-30 21:59 · Score: 1
  
  I thought making throw-away posts about faggots was for... well, you know.
  
  --
  Il n'y a pas de Planet B.
43. Re: RHEL6 by thegarbz · 2016-01-30 22:27 · Score: 2, Informative
  
  or swallowed the log message that clearly stated the problem
  Sounds like someone hasn't setup systemd to their liking. In it's most verbose form journald will capture more and log more than any previous system including saving outputs from the console that previously were lost and capturing messages before syslog starts.
  But you need to read the manual first, and if you don't like the defaults complain to the maintainer of your distribution, and has nothing to do with systemd itself which will only swallow logs if you tell it to.
44. Re: RHEL6 by Anonymous Coward · 2016-01-30 23:03 · Score: 2, Interesting
  
  Because it (still) points out there is an error? Did exit codes suddenly become deprecated?
45. Re:RHEL6 by Anonymous Coward · 2016-01-30 23:49 · Score: 1
  
  You're still mangling languages, it is:
  $ contrôledusystème démarre mondieu
46. Re: RHEL6 by pslytely+psycho · 2016-01-31 00:23 · Score: 1
  
  Mongo never was very stable...
  
  https://www.youtube.com/watch?v=O8cDfnQD0ws
  
  "Mongo only pawn in game of life."
  
  --
  Donald Trump, on a crusade to make Nixon look respectable
47. Re: RHEL6 by Anonymous Coward · 2016-01-31 00:45 · Score: 4, Insightful
  
  or swallowed the log message that clearly stated the problem
  Sounds like someone hasn't setup systemd to their liking. In it's most verbose form journald will capture more and log more than any previous system including saving outputs from the console that previously were lost and capturing messages before syslog starts.
  But you need to read the manual first, and if you don't like the defaults complain to the maintainer of your distribution, and has nothing to do with systemd itself which will only swallow logs if you tell it to.
  The DEFAULT drops errors logged from the historical source errors are reported to.
  That's FUCKING STUPID.
  It's like putting a land mine in a dog owner's yard, then telling him he should have had a bunch of military engineers sweep his yard for mines before his dog got blown to bits.
  NO YOU FUCKING MORON YOU DON'T PLACE THE MINES IN THE FIRST FUCKING PLACE!!!!!
48. Re: RHEL6 by Anonymous Coward · 2016-01-31 00:49 · Score: 0
  
  > Sounds like no one has setup systemd to their liking.
  Fixed that for you. And that's because no one can The churn on new features and disabling six month old ones is killing ordinary users who are just trying to get on with their projects.
49. Re: RHEL6 by Anonymous Coward · 2016-01-31 01:11 · Score: 0
  
  systemd correctly handles exit statuses even though they're old cruft that should be removed. Your startup script is broken.
  Yeah, a simple indicator of success/failure that's been standard for decades is "old cruft".
  You don't know what cruft is, do you? Here's a hint: cruft is something needlessly complex, unstable, unreliable, and that's a solution in search of a problem. systemd is the epitome of cruft.
  Go back to Windows.
50. Re: RHEL6 by buchanmilne · 2016-01-31 01:16 · Score: 1
  
  Set Type=forking in your service unit (the default is simple, which expects inetd-style services).
51. Re: RHEL6 by Junta · 2016-01-31 01:18 · Score: 1
  
  The issue is that every configuration issue is going to be 'your own fault'. However the point of diagnostic data is to identify when something goes wrong and why. The complaint here is that systemctl exited with rc 0 (so a script to do something to the service wouldn't know there was a problem) and that log data that traditionally would have said in clear terms what went wrong is discarded.
  This is like saying it is ok for a compiler to just say 'compile error' and return success because any syntax errors are the programmers own fault.
  
  --
  XML is like violence. If it doesn't solve the problem, use more.
52. Re:RHEL6 by Junta · 2016-01-31 01:23 · Score: 1
  
  Much to my chagrin when I have to do out-of-tree stuff that seeks kernel-devel as '2.6.32' and says 'oh, then I need to define stuff that wasn't defined in 2.6.32' only to break the compile because RHEL backported all sorts of stuff, and still call it '2.6.32'. This has always bugged me about RHEL, they end up with something that doesn't map to kernel.org version at *all*, but the version still suggests otherwise.
  SuSE stopped that stuff and actually upgraded the kernel when they felt the features were ready.
  
  --
  XML is like violence. If it doesn't solve the problem, use more.
53. Re:RHEL6 by Anonymous Coward · 2016-01-31 01:25 · Score: 0
  
  Actually it's both.
54. Re: RHEL6 by Opportunist · 2016-01-31 02:27 · Score: 4, Insightful
  
  9 out of 10 times when something goes wrong in your system it's your own damn fault. That's what logs are for, to inform you where you made the mistake.
  By your logic, the only output we should get is a segfault to show that the program barfed, for only then it's the programmer's fault and for everything else, well, sucks to be you, why did you make that mistake?
  
  --
  We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
55. Re:RHEL6 by buchner.johannes · 2016-01-31 02:33 · Score: 1
  
  Gentoo is a bleeding edge, rolling release distribution. They do not keep old versions of any package around.
  
  --
  NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
56. Re: RHEL6 by Anonymous Coward · 2016-01-31 02:44 · Score: 0
  
  You are the one doing something wrong, not systemd. Take a stress pill and think things over. Stop. My mind is going. I can feel it.
57. Re: RHEL6 by Livius · 2016-01-31 02:52 · Score: 1
  
  Sounds like someone hasn't set up systemd to their liking.
  Blaming the victim. Unless the purpose of systemd is to elevate system configuration to an art form whose purpose is aesthetics and critique, then that is a problem with systemd.
  You know, like every critic of systemd has been saying all along.
58. Re:RHEL6 by Anonymous Coward · 2016-01-31 02:56 · Score: 0
  
  What happens to RHEL6?
  You can't google for "RHEL end of life", can you? Did that for you. Here's the resulting page: https://access.redhat.com/support/policy/updates/errata. Your question should be: what happens to RHEL 5? Its kernel is even older: 2.6.18. The answer is "Extended support starts in 2017".
59. Re: RHEL6 by thegarbz · 2016-01-31 04:42 · Score: 0
  
  Yeah I understand what you mean. Just the other day I opened up my linux box and was upset to realise that I got a file not found error message when I typed ipconfig /all. I mean we should expect all software to work the same way shouldn't we? Anyway once I found out that I was typing a windows command I finished setting up nginx and got another error that it wouldn't read /etc/apache2/apache2.conf I mean what the hell, it's just a http server right? Worse still it would seem that this server has different options and I need to actually learn how to set it up, after all it doesn't do anything useful out of the box by default.
  Now tell me I'm stupid so I can tell you to not blame the victim.
  If you think telling someone they should learn to setup their PC the way they like is victim blaming then you're delusional.
  But at least we can agree on something, since your post is quite consistent with the rest of systemd criticism... it contains no substance and boils down to "waah I don't want to RTFM".
  In the mean time wake me when systemd won't do exactly what the GP actually wanted which can be set via a single line in /etc/systemd/system.conf
60. Re:RHEL6 by F.Ultra · 2016-01-31 05:31 · Score: 1
  
  systemd does not swallow stderr, looking at the default mongodb unit file I noticed that some one with a brain damage put this line in there "ExecStart=/usr/bin/mongod --quiet --config /etc/mongodb.conf". See the --quiet flag there? It tells mongodb to not produce any stderr at all, hence why systemd also wouldn't capture it, it cannot capture that which isn't produced.
61. Re: RHEL6 by F.Ultra · 2016-01-31 05:35 · Score: 3, Interesting
  
  The proper blame is on the mongodb developers since they are the ones who have created the defunct unit file for mongodb. It's not systemd that drops logs, it's mongodb that is configured to not produced any since it's launched with --quiet in the default unit file. Now this is probably done due to it starting as a SysVinit project and on SysVinit one would have do disable stderr since otherwise the console would get completely garbled, just that they forgot that systemd is not as stupid as the older init system.
62. Re: RHEL6 by Anonymous Coward · 2016-01-31 06:05 · Score: 1
  
  Unfortunately, in an open source world, documentation can often be a rarity, and good documentation even rarer, and in this area systemd is significantly worse than average.
63. Re: RHEL6 by Anonymous Coward · 2016-01-31 06:07 · Score: 0
  
  And everything related to systemd seems to have fairly obscure, inconsistent syntax as well.
  (Don't even get me started on that horrific abortion that is firewalld).
64. Re: RHEL6 by guruevi · 2016-01-31 06:23 · Score: 1
  
  Unless someone explicitly did daemon > /var/log/mydaemon.log, a standard log and syslog would just log everything you sent to it by default and the daemon itself could specify where and how it got sent. Journald not only needs the app but also needs itself instructions on its logging level and verbosity in very arcane journald style specifications. If I'm doing a one-off change, I don't even bother with systemd. It takes me 30-40 lines and 5 file changes to set up a simple script that runs every so often and its logging correctly, in those cases I have a single systemd thing that calls a script that has all my scripts listed, crontab style, that I can add to to my pleasure.
  
  --
  Custom electronics and digital signage for your business: www.evcircuits.com
65. Re:RHEL6 by Anonymous Coward · 2016-01-31 07:40 · Score: 0
  
  Gentoo is a bleeding edge, rolling release distribution. They do not keep old versions of any package around.
  O RLY?
66. Re:RHEL6 by Anonymous Coward · 2016-01-31 08:15 · Score: 0
  
  EL6 will still be supported by Red Hat and Scientific Linux for many years to come.
  Do you know if this applies to CentOS 6 as well? I have some systems running CentOS 6 (2.6.32-573.12.1) and I'm avoiding CentOS 7, let's just say "for various reasons." I migrated these machines to CentOS 6 from Debian, which is now off my list as well, and have grown fond enough of CentOS that it would suck to have to change distros again.
67. Re: RHEL6 by Nikker · 2016-01-31 10:05 · Score: 1
  
  That's garbage. The entire reason error codes even exist is to help the user manage the software, what rational do you have that keeping the reported error code secret is a good thing?
  
  --
  A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
68. Re: RHEL6 by Anonymous Coward · 2016-01-31 11:14 · Score: 0
  
  The proper blame is on the mongodb developers since they are the ones who have created the defunct unit file for mongodb. It's not systemd that drops logs, it's mongodb that is configured to not produced any since it's launched with --quiet in the default unit file.
  Prove your claim otherwise YOU ARE NOTHING BUT A TROLL
69. Re: RHEL6 by Anonymous Coward · 2016-01-31 12:44 · Score: 0
  
  Everything obiviously. :)
70. Re: RHEL6 by Anonymous Coward · 2016-01-31 14:28 · Score: 0
  
  "In it's most verbose form journald will capture more and log more than any previous system including saving outputs from the console that previously were lost and capturing messages before syslog starts."
  Funny. For the past fifteen years my Gentoo Linux systems have saved even the _first_ (uptime == 0.000000) outputs from the kernel in /var/log/messages .
  syslog-ng has been around since 1998 and has been doing just about everything that journald does, since _long_ before journald existed. You should read the syslog-ng feature list and both https://tools.ietf.org/html/rfc5848 and https://tools.ietf.org/html/rfc5424 . (Further reading can be found at the "Internet standard documents" section of the syslog Wikpedia page.)
71. Re:RHEL6 by Anonymous Coward · 2016-01-31 17:28 · Score: 0
  
  Support for RHEL6 ends on 2020. RH will backport or patch anything needed until 2020. So, thanks to RH the 2.6.32 kernel will keep alive for some years.
72. Re:RHEL6 by Drinking+Bleach · 2016-01-31 20:36 · Score: 1
  
  CentOS tracks RHEL completely. For as long as Red Hat supports RHEL6, CentOS 6 will be updated. (New Red Hat-maintained versions of 2.6.18 still show up in CentOS 5 updates, even.)
73. Re: RHEL6 by Anonymous Coward · 2016-02-01 01:09 · Score: 0
  
  For that matter, what does a uterus have to do with dried grapes?
74. Re: RHEL6 by thegarbz · 2016-02-01 02:02 · Score: 1
  
  systemd is significantly worse than average.
  This problem is literally one of not removing the # on a line in system.conf. It is also well described in the man pages for system.conf. It's also well described in the RedHat manual. Okay that's the first 3 google results done, you can go look up some more if you think the documentation is so horrible.
  The only bad documentation for systemd is the API documentation. End user configuration is quite adequately described not just in its own man pages, but also in documentation from various distributions.
75. Re:RHEL6 by arth1 · 2016-02-01 05:09 · Score: 1
  
  As far as I know, they will. However, they do not provide long term support themselves for more than a couple of years, and just mirror upstreams.
  ScientificLinux does, but part of that is likely because they also have additional packages in addition to the RHEL base, while CentOS does not have that. All they have to support is logo changes and similar, which can be expected to be long term stable.
Softpedia again? by Anonymous Coward · 2016-01-30 18:42 · Score: 0

No thanks http://lkml.iu.edu/hypermail/linux/kernel/1506.0/02415.html
1. Re:Softpedia again? by Anonymous Coward · 2016-01-30 18:44 · Score: -1
  
  Useless faggot
2. Re:Softpedia again? by Anonymous Coward · 2016-01-31 11:23 · Score: 0
  
  Useless faggot
  USELESS TROLL
Faggot by Anonymous Coward · 2016-01-30 18:46 · Score: -1

Nigger
Softpedia article content by Anonymous Coward · 2016-01-30 18:53 · Score: 0

Linux kernel 2.6.32.70 LTS now available for download
Jan 30, 2016 21:35 GMT By Marius Nestor
The oldest long-term supported Linux kernel branch finally reaches end of life next month, but before going into the deepest darkest corners of the Internet it just dropped one more maintenance release, Linux kernel 2.6.32.70 LTS.
Willy Tarreau dropped the news about the release of Linux kernel 2.6.32.70 LTS on January 29, 2016, informing all us that this will most likely be the last maintenance release in the series, as starting with February 2016 it will no longer be supported with security patches and bugfixes.
"I've just released Linux 2.6.32.70. As a reminder, EOL for 2.6.32 is set to Feb 2016," said Willy Tarreau in the announcement. "There *might* be another version in the next 2 weeks if we find important things to fix or if Ben gets a few more security fixes, and after that it should be all. So please consider this one as the most likely last one."
Users are urged to move to the newest LTS release
Linux kernel 2.6.32.70 LTS is a normal milestone that changes a total of 59 files, with 487 insertions and 187 deletions. Among the changes, we can notice a few improvements to the x86, s390, PA-RISC, and MIPS hardware architectures, as well as to the EXT4, NFS, FUSE, and sysv filesystems, updates to the ISDN, SPI, SCSI, USB, and networking drivers, and a lot of fixes for networking stack.
Users of a GNU/Linux operating system running on a kernel from the Linux 2.6.32 LTS series, are urged to either update to the 2.6.32.70 maintenance release or start migrating to the newest and most advanced long-term supported version, Linux kernel 4.4 LTS. You can download the Linux kernel 2.6.32.70 LTS sources right now from the kernel.org website or via Softpedia and start compiling by hand.
1. Re: Softpedia article content by Anonymous Coward · 2016-01-30 19:07 · Score: 0
  
  Ok but will it run Crysis?
2. Re: Softpedia article content by ls671 · 2016-01-30 21:34 · Score: 1
  
  Unsure, but it runs Tetris fine.
  
  --
  Everything I write is lies, read between the lines.
People still do this? by Anonymous Coward · 2016-01-30 19:02 · Score: -1

I thought once systemd boots it starts its own forked Linux kernel as one of its plugins. Why do you people still mess with that crap on their own. systemd has made this practice obsolete
Oh, wow! by __aaclcg7560 · 2016-01-30 19:07 · Score: 2

I had no idea that Linux had a Windows XP mode.
1. Re: Oh, wow! by Anonymous Coward · 2016-01-30 19:12 · Score: 0
  
  You disable the xp mode by passing "nomodeset" in the kernel startup line, e.g. in your grub.cfg
2. Re:Oh, wow! by Nexion · 2016-01-30 20:10 · Score: 1
  
  LMAO
3. Re:Oh, wow! by dwywit · 2016-01-30 20:15 · Score: 1
  
  Oh, yeah. As long as users refuse to upgrade *cough*digital cinema*cough*, there'll be jaw-dropping amongst the community.
  Still using 2.6.13 under Fedora. Apparently we users (projectionists) aren't to be trusted with our own equipment, so no root access, and we get an upgrade every three years or so, whenever we scream loud enough and promise to pay for it.
  To their credit, the "upgrade" includes a calibration of sound+vision, so there's that.
  
  --
  They sentenced me to twenty years of boredom
NOTE TO MODERATORS by Anonymous Coward · 2016-01-30 20:06 · Score: 3, Insightful

I agree, it doesn't really provide useful information on how to track down the issue. Dealing with syslog was a pain in the ass in some ways to track down problems associated with a particular daemon, but I'm not sure systemd solves the issue.
That said, I see a number of AC posts criticizing you for your views on systemd. It seems every night recently, a troll posts a bunch of AC comments in response to an early post, pretending to have a conversation with itself but contributing nothing of substance. Last night, it was claiming Facebook encourages gun violence and that AK-47s are sold in Facebook's parking lot. The night before, it was posting about how Republicans want people to die and kill people's family members who don't support Republicans. It's almost certainly a single troll who needs to be modded down to -1. Please take note, moderators, and mod the replies accordingly. And to the new management of Slashdot, if you see this, please consider banning the IPs associated with these crapfloods. Thanks!
1. Re:NOTE TO MODERATORS by Zontar+The+Mindless · 2016-01-30 21:57 · Score: 2
  
  A *troll* would make us laugh or piss us off. The AC poster you're referring to is simply a waste of protoplasm wasting electrons in its too-plentiful spare time.
  
  --
  Il n'y a pas de Planet B.
Hey!?!?! by Nexion · 2016-01-30 20:16 · Score: -1, Offtopic

Hey, if I get a sig that says "fuck slashdot" can I get a 0 rating upon post whilst logged in? Please?
Fuck you, sellout Slashdot. You need to die. You betrayed every last nerd upon you delivered new that mattered. DIAF.
1. Re:Hey!?!?! by Zontar+The+Mindless · 2016-01-30 22:05 · Score: 5, Insightful
  
  Dice no longer own Slashdot.
  Here, let me get you a paper towel or something for you to clean yourself up with--you look a bit foolish with all that foam hanging from your mouth.
  
  --
  Il n'y a pas de Planet B.
2. Re:Hey!?!?! by Anonymous Coward · 2016-01-30 22:39 · Score: 0
  
  He doesn't care. He's been corrected about this before but is still posting the same nonsense. I don't think your post will get him to reconsider his misplaced anger.
My karma... good... by Nexion · 2016-01-30 20:21 · Score: -1, Offtopic

Slashdot's however leaves much to be desired.
1. Re:My karma... good... by Zontar+The+Mindless · 2016-01-30 23:48 · Score: 1
  
  What part of Dice Holdings Inc. no longer own Slashdot are you failing to understand?
  Perhaps you should wait until you've sobered up before posting again? You're setting a bad example for the youngsters.
  
  --
  Il n'y a pas de Planet B.
WTF moderators by Anonymous Coward · 2016-01-30 20:29 · Score: 1

This guy posts a helpful technical response and gets voted down. I too have run into this same bug.
1. Re: WTF moderators by Anonymous Coward · 2016-01-30 20:46 · Score: 0
  
  Vote? Found the guy from reddit.
Asus routers still running on this ancient kernel by Anonymous Coward · 2016-01-30 20:58 · Score: 0

A pitty most Broadcom SoC based routers, even the most recent ones still ship with this kernel. Which makes plugging in USB devices a living hell for lack of drivers.
Still on 2.6.32 because of Distro by Misagon · 2016-01-30 21:56 · Score: 2

I still run an old Ubuntu LTS install with Linux 2.6.32, but that is mostly because so that I would not have to run a Ubuntu version with that abomination called "Unity" or Gnome 3. I could not see that Ubuntu had offered any upgrade path to another LTS release that would not force any of that crap upon me. I also did not want to get a system that was a mix of installs from different sources.
My old Ubuntu has served me well for this time. Time to look around for some other distribution then... Mint?
BTW. At work I installed CentOS 6 on a brand new machine, this Thursday. I installed CentOS 7 first but gave it up because of Gnome 3.

--
"We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
1. Re:Still on 2.6.32 because of Distro by Anonymous Coward · 2016-01-30 22:42 · Score: 1
  
  I recommend just installing XFCE on Ubuntu, but Mint is also an option if you're a Gnome2 fan.
2. Re:Still on 2.6.32 because of Distro by serviscope_minor · 2016-01-31 01:01 · Score: 1
  
  I'm running ubuntu 14.04 with fvwm. Unity is the default but it's easy to switch. There's no need to run an a ancient system. I'll a almost certainly upgrade to 16.04 when the time comes.
  
  --
  SJW n. One who posts facts.
3. Re:Still on 2.6.32 because of Distro by Maow · 2016-01-31 01:20 · Score: 4, Informative
  
  I still run an old Ubuntu LTS install with Linux 2.6.32, but that is mostly because so that I would not have to run a Ubuntu version with that abomination called "Unity" or Gnome 3. I could not see that Ubuntu had offered any upgrade path to another LTS release that would not force any of that crap upon me.
  My mom runs 10.04 and is a long way away, so I tested in a VM
  do-release-upgrade
  Which brought the VM to 12.04, then I ran it again, bringing the VM to 14.04.
  Then something like
  sudo apt-get install mate-desktop
  And it worked. I did the entire process multiple times to be sure, and documented it on a web site somewhere.
  One issue was in trying to remove Unity via sudo apt-get remove unity.
  In one instance it caused an issue, in another it worked. Might have been a mistake I made.
  But there is an update path available.
  
  also did not want to get a system that was a mix of installs from different sources.
  I did have to add the Mate repo if I recall, but they're pretty trust-worthy; I wouldn't consider it problematic.
  Worth a try!
4. Re:Still on 2.6.32 because of Distro by Junta · 2016-01-31 01:29 · Score: 1
  
  The lack of updates for upstream 2.6.32 is the least of your worries for running Lucid.
  One, unless you were compiling your own kernel, the efforts after April of last year upstream had no bearing on your distro, since they weren't bothering to pull it in anyway.
  For another, the kernel is but one of a huge chunk of unmaintained code in a distro that gave up it's last bit of support April last year.
  If you want new but familiar, choose a MATE environment. It carries on the traditional experience the best. You can experiment with things like Cinnamon as well. Gnome shell has a 'classic' mode, though I personally think it misses the point and only superficially looks familiar without capturing the real reasons why I thought Gnome 2 was so mature.
  
  --
  XML is like violence. If it doesn't solve the problem, use more.
5. Re:Still on 2.6.32 because of Distro by Blaskowicz · 2016-01-31 01:31 · Score: 2
  
  If you're not in a hurry / don't really need to care you may wait for Ubuntu 16.04 (Ubuntu Mate) or Mint 18 Mate.
6. Re:Still on 2.6.32 because of Distro by present_arms · 2016-01-31 01:52 · Score: 3, Interesting
  
  PCLinuxOS is still systemd free and no gnome 3 or unity and is stable, very stable :) You just have to get used to no sudo we do things as God intended with a proper root password and su to gain root :P Alie
  
  --
  http://chimpbox.us
7. Re:Still on 2.6.32 because of Distro by Anonymous Coward · 2016-01-31 06:51 · Score: 0
  
  I like straight Debian. But ubuntu with lxde is nice and stable too.
8. Re:Still on 2.6.32 because of Distro by Anonymous Coward · 2016-01-31 15:41 · Score: 0
  
  I recently built up 2 CentOS 6.x (mostly LAMP) servers, running 4.4 kernels, using Gnome or xfce. So far everything's perfect.
9. Re:Still on 2.6.32 because of Distro by Anonymous Coward · 2016-01-31 19:30 · Score: 0
  
  I installed CentOS 7 a while back on my new work machine. Gnome 3 in (CentOS 7 default)classic mode is totally fine. Besides, I spend 99.9% of my time in emacs and terminal anyway. In the context of support EOL, both CentOS 6 (Nov 30 2020) and 7 (Jun 30 2024) are fine..
But will it still run on a 80386? by jfdavis668 · 2016-01-31 00:49 · Score: 1

Will this still run on the 80386, which was the original goal of Linux?
1. Re:But will it still run on a 80386? by Anonymous Coward · 2016-01-31 04:11 · Score: 1
  
  By that metric, Linux is indeed a failure.
2. Re:But will it still run on a 80386? by Drinking+Bleach · 2016-01-31 20:42 · Score: 1
  
  2.6.32.70 should. 80386 support was dropped in 3.5.y and further.
  Please note that no mainstream distro has supported the 386 in the past couple decades. You'll have to be building all your own stuff to get it working.
Netcraft? by Anonymous Coward · 2016-01-31 03:41 · Score: 0

It is not dead until Netcraft, well, you know...
What's so special... by unixisc · 2016-01-31 12:47 · Score: 1

... about version 2.6.32? Was it the last one that didn't have systemd? Or something else? I know that Linus jumped to version 3 after that, and so on, but aside from that leap, is there anything else about 2.6.32 that makes it so special that dropping support for it is newsworthy?
1. Re:What's so special... by Drinking+Bleach · 2016-01-31 20:45 · Score: 1
  
  2.6.39 was actually the one that directly preceded 3.0 ;)
  Nothing particularly special about 2.6.32 compared to the others, but it just happened to be one release in which all the major enterprise distributions landed on for one release cycle (Debian 6, RHEL 6, SLES 11, ...). That fact alone just kind of drove to keeping it maintained officially, and everyone on those distributions could stay happy with new upstream kernels of that series without breaking any sort of compatibility on their systems (eg, any kernel modules installed).
2. Re:What's so special... by wtarreau · 2016-02-01 10:29 · Score: 1
  
  In fact my own usage in my projects as well as at my company has justified to take it over till last summer. And since Moritz and Ben from the debian LTS team have done an incredible job at feeding me with security backports for free, when Ben told me that debian 6 would be maintained till february, I found it the least I could do to pursue its maintenance for a few extra months to return the favor. So the fact that it's been used by debian has indeed justified 6 more months, which is nice already.
  Acute observers will also note that in parallel Greg has also pushed 3.10 EOL quite far. It's just an indication that LTS is more of a team than isolated individuals the kernel.org table seems to imply. People talk out of public lists. Some devote more time, some less, but everybody helps all other ones as time permits. This is a fun adventure that will go on after 2.6.32 :-)
  Oh BTW, 3.2 is quite close to 2.6.32, it should be an excellent, riskless replacement. Over the last year I've pulled fixes exclusively from it.