Comment Slackware not affected (Score 4, Informative) 51
Slackware has never enabled CONFIG_SMB_SERVER in any kernel.
Slackware has never enabled CONFIG_SMB_SERVER in any kernel.
Thus spake the master programmer:
"Though a program be but three lines long, someday it will have to
be maintained."
-- Geoffrey James, "The Tao of Programming"
Clearly it's Large Hadron Colliders all the way down.
Linus, is that you?
There's a COBOL shop in my small town that contracts for corporations and the government. I know several COBOL specialists in their 30s. It's actually an extremely lucrative field to get into these days, with good pay and job security.
Rewriting all that COBOL code in some other language would be bound to cause major problems.
All you need is the --enable-alsa configure option. The resulting Firefox will prefer PulseAudio if it is present, but will use pure ALSA if it is not.
Really? I've not been able to find anything other than a new release. The patches might be in git, but they are not easily found.
MINIX is obsolete.
FLIF will never kill PNG anyway as long as it keeps linking to libpng.
I've had no issues with Soylent 1.4/1.5 producing the kind of room-clearing gas that earlier versions did. It's really rather disappointing.
When's the last time it was every six months?
Hint: It was probably sometime back when the release was two CDs, and not 6 CDs and 2 double-sided DVDs.
If their plan is to get more third parties to go along with their DRM, then they haven't really learned a thing yet.
No, Linus needs to use his finger.
By what strange theory does Slackware support systemd? And how is the conversation being "held back"? At least on LQ, I think it's been discussed to death to the point where there's really nothing new to say about it.
I can say one thing for certain: you do not know that anything concerning systemd in Slackware is likely or not. Hell, *I* don't.
"The pathology is to want control, not that you ever get it, because of course you never do." -- Gregory Bateson