Slashdot Mirror
Linux Kernel 2.6.32 LTS Reaches End of Life In February 2016 (softpedia.com)
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.
Red Hat will back port fixes, just like they do with many, many packages.
The real "Libtards" are the Libertarians!
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!
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.
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!!!!!
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.