LinuxBBQ

Don't know if cortana works with bash...
http://www.omgubuntu.co.uk/2016/03/micr ... windows-10

^ I can't predict what this is going to end, but I find it a bit ironic from both sides. Where "ironic" means "$$$".

^ I don't know it either, but I share the same "$$$" thoughts that you have.

^^^^
I just went through all the scripts that Eric has. Thanks for the reminder about building my own. I use his SlackBuilds script and a few others to take care of my installs. I also use Ruari Oedegaard's (ruario) latest-firefox script.

^^^^^ Doc, his old server finally crapped out due to overload. Now, he can easily handle the K-town (KDE Plasma) upgrade builds, Slackware Live, Slackware Current, docs.slackware, his own wiki, and a bunch of other stuff thanks to donations and help.

^ Ah, great news!

franksinistra wrote:^ build one yourself? Using alienbob's script, you only need a few minor modifications to the script if you want to run it from debian host. :)

That is pretty dank! I might give it a go just for the heck of it.

Kind of entertaining: https://bugs.debian.org/cgi-bin/bugrepo ... bug=819703

Debian forks xscreensaver, just so they can keep out-of-date versions? :)

^ I was just reading that thread. jwz's posts are hilarious. Yeesh, I always dump xscreensaver and install slock, personally.

^ slock? Sweet, I haven't used that before! I'll give it a spin :D 'i3lock -c 121212' is usually my default.

Lately xscreensaver is popping up at boot on a couple of machines. It soon disappears, but it is annoying. Not my PCs, so I don't recommend slock, but yes, annoying.

I saw this crap on Slackware but they updated the package and it removed the message from xscreensaver. Never liked it though. Wasn't there also some strange license about it we talked once on Munch?

^ Yes, there was discussion of changing the eye-cancer that is the xscreensaver splash screen, etc., but the artist specifically asked in the docs not to do so. Someone on Munch had come up with a nicer one (perhaps it was #! themed, too?)

^ Oh yes, I remember using the #!-themed xscreensaver back in my days.

As the author states: the license is WTFPL so...
If you don't plan to redistribute it (and even if you do), then see above.. reminds me of the npm package 'issue'

PS. i3lock for me.

slock here, and actually on every system that has suckless-tools installed (all?)

Regarding xscreensaver, it gets better:

https://www.jwz.org/blog/2016/04/i-woul ... reensaver/

And a version without the message:

https://sourceforge.net/projects/fixed-xscreensaver/

Now people are throwing shit on each other, the open source way. :) Is it Debian's poor policy, is it jwz's ignorance? Who knows. But I know one thing, I am happy to not use xscreensaver and stable releases are shit anyway. :D :D

^ You gotta love that so much time, effort, and energy are being wasted on software that really serves no practical purpose any more (unless you use old CRT monitors). I don't need to save my screen with bloated pretty (ugly!) pictures, I just need to lock the fucker without a clusterfuck of code. And so, slock. :)

Slackware 14.2 RC2:

Fri Apr 15 20:37:37 UTC 2016
Finally got some fixes we were waiting for in this new kernel.
It's been almost a month since 14.2rc1 so we'll call this Slackware
14.2 release candidate 2. Almost there. Get in any last-minute
bug reports quickly. :-)

^^ this.

slock for me. I stopped using xscreensaver when this bug was filed. At the time I was using aptosid with Xfce and would just use Power Manager and get rid of xscreensaver.

That bug, that sucker. It still does the same thing therefore everybody switched to lightlocker in the X/Ubuntu world.