SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Surprisingly, the announcement contains an apology from Mr. Torvalds for his past behavior and he goes on to say he is going to take a little time off to reflect upon it (and get some help).
I can’t wait for the mass exodus from Linux now that it’s been infiltrated by SJWs. Hahahah
Interesting words from that Mrs./Mr./It who describe {her,him,it}self as "Code Witch" and is right on the author of the original "code of conduct" adapted and adopted now by the Linux Kernel:
A little off topic but related to Mr. Torvald's introspection about his behavior/language. I like the guy, IMO, his sharpness, toughness and resilience is what made the kernel as solid and stable as it is today. I just hope he won't be driven by the community into some form of "pussification". I say, give the guy a megaphone and let him bitch about whatever he likes, a project like that needs a Biggus Dickus at the helm. Besides, it's the usual "melody" that we got used with coming from behind the kernel development. Scientifically, it also looks to be healthy: https://www.sciencedaily.com/release...0117105107.htm https://www.nytimes.com/2017/07/27/s...r-cursing.html
CoCs, political correctness and SJWs are ruining everything. Heaps of great people without jobs, but political, bureaucratic paper pushers everywhere, it's sickening.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Original Poster
Rep:
The politically correct nazis won't stop until they have destroyed Western Civilization. What they don't, and won't, understand is Western societies' enemies don't care a hoot about political correctness (a form of divide and conquer) and are using it against the West in their effort to destroy us.
There was a time in the U.S. when I thought the people were strong enough to withstand those who would destroy the country, but, sadly, from what I have seen of the last couple of generations, they don't have the strength of character. I would say the WWII generation was the last that could weather the current political storm, but almost all of them have passed on.
I might live another twenty years, but if things don't change, and soon, for the better, I hope not.
Just another opinion: how the kernel community chooses to organise itself is not our business here, and neither are your opinions about whether that will have any effect on how you live your own lives.
Just another opinion: how the kernel community chooses to organise itself is not our business here, and neither are your opinions about whether that will have any effect on how you live your own lives.
Unless you already figured out a backup plan to move Slackware to another kernel, BSD maybe, or even move to a BSD distro for good and ditch Linux, I believe these latest developments at the kernel head are worrying news. The Slackware community, as maybe also the communities from other distros, are entitled to care about the kernel their distro is built upon and share their opinions and concerns in a kernel related thread.
As you have the right to your opinion, you also have the right to ignore these posts & move along, I believe, that's another opinion
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
<Godwin's Law>
Last edited by michaelk; Today at 18:21.
Well, well.... it wasn't totally unexpected that someone would make my point. That it was a modulator exercising his own version of political correctness should indicate he shouldn't be a modulator.
Last edited by cwizardone; 09-18-2018 at 08:44 PM.
Just another opinion: how the kernel community chooses to organise itself is not our business here, and neither are your opinions about whether that will have any effect on how you live your own lives.
I must try to remember this. I shouldn't have, or voice, an opinion on the methodology or ethics of something that can directly affect me.
55020, I respect your work for Slackware, but I find this to be a bizarre and rather dangerous mode of thinking and something which, I thought, the community once tried to stand against.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,607
Rep:
Two comments:
* cwizardone, I've restored the content of your post.
* That said, many recently posts are *wildly* off-topic. Further off-topic posts will not be tolerated.
Linux 3.16~4.18.8 Affected By Another Potential Local Privilege Escalation Bug
Written by Michael Larabel in Security on 19 September 2018 at 07:47 AM EDT. 9 Comments
SECURITY --
From June of 2014 with Linux 3.16 until last week, the Linux kernel was affected by another potential local privilege escalation bug.
Fortunately, Linus Torvalds fixed it last week prior to taking his leave of absence. But the issue was fixed by Linus in removing the vmacache_flush_all code entirely on the basis of it being expensive, buggy, and unnecessary.
It was then posted to oss-sec on Tuesday that this vmacache code could lead to a a use-after-free situation and potentially local privilege escalation. The vulnerability is now published today as CVE-2018-17182. But if you switch now to the latest Linux kernel stable releases or are riding Linux Git, you should be in good shape.
Last edited by cwizardone; 09-19-2018 at 10:08 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
