superkret

joined 2 months ago
[–] [email protected] 2 points 13 hours ago (1 children)
[–] [email protected] 8 points 23 hours ago

I used to have an old Zenit ET. I loved that thing cause it had a small solar cell that powered the lightmeter (which was just an analog indicator moving over a scale).
So it needed no batteries.

When I moved to a new place I accidentally toppled an oak wood wardrobe which fell on the camera.
The wardrobe then had a hole in its back panel, the camera still worked fine.

[–] [email protected] 47 points 1 day ago* (last edited 1 day ago) (3 children)

I have an old Soviet mechanical wristwatch that cost 3€ on an Eastern German flea market.
Compared to other watches it sounds like a Diesel tractor, the bezel rotates freely and the wristband pulls my arm hair out.
When I wear it, it's too fast and when I don't wear it, it's too slow.

But I only wear it during the day and take it off at night, and that way it's been keeping perfect time for 15 years.

 
[–] [email protected] 5 points 1 day ago* (last edited 1 day ago)

In the Battles of Xing and Lin-Kedin

 
[–] [email protected] 41 points 2 days ago* (last edited 1 day ago) (5 children)

Termux. A Debian-based Linux system running on top of unrooted Android.
It lets you interface with your phone's functions (GPS, calls, etc.), and install packages to extend functionality.
Turned my phone into a mobile network troubeshooting device, lets me grep through my sms, and I can ssh into my server on the go.

With AnLinux you can install a full standard linux system in it, including a GUI, and connect to it with a VNC viewer. (AnLinux is just a helper script linking to some dude's repo, so if you are at all security-minded, you can also bootstrap and install any Linux distro manually).
So you could have a Debian with Gnome desktop running on your unrooted phone.

[–] [email protected] 10 points 2 days ago (1 children)

It's vanilla Fedora preconfigured for gaming on Proton, then made immutable.

[–] [email protected] 15 points 3 days ago* (last edited 3 days ago) (1 children)

Does there need to be a solution?
Do E-Sports competitions on identical certified hardware and otherwise ban people caught cheating.
Root kits aren't necessary for having fun in a game.

[–] [email protected] 18 points 3 days ago

There's also been a Republican campaign for years to actually try and make those votes not count.

[–] [email protected] 25 points 3 days ago* (last edited 3 days ago)

Nooo, one day I'll have the time to build my writing utensil repair business.
And then I'll need the domain penisbroken.com

[–] [email protected] 3 points 3 days ago

Endeavour is great but it's not simply Arch with an installer. Quite a few things are configured differently under the hood.

[–] [email protected] 44 points 3 days ago

"Hi, I'm Vincent Adultman. Just in case you're wondering, I'm definitely not 3 kids in a trenchcoat pretending to be an adult. Now let's do a business."

 

I wonder what "limited lifetime warranty" means.

34
Flatpak on Slackware (alien.slackbook.org)
 

shared from: https://feddit.org/post/1848262

I like the Slackware approach of installing the kitchen sink by default. Disk space is cheap.
But I find that the cluttering of the menus in KDE is a bit annoying. I use search to start my applications, and a lot of the time I have to type almost the full program name to get to the app I actually use.
What's the easiest way to hide a large number of programs from the menus, which is also easily reversible?

My first idea was renaming the .desktop files in /usr/share/applications to .hidden
But they seem to be recreated automatically.

Another idea was to copy .desktop files from /usr/share/applications to ~/.local/share/applications and then do:
printf "\nHidden=True" | tee -a ~/.local/share/applications/*.desktop

But I tried to add this manually with one test file and it didn't seem to have any effect.
Is there a config file somewhere that specifies in which paths .desktop files are parsed?

Or is there a better way?

Thanks a lot, and happy slacking!

[Solved] Slackware comes with kmenuedit which can be accessed by right-clicking the app menu.

205
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]
 

Blog post alert

Let me start off by saying: If you just want to have a working system to do your thing with minimal effort, Slackware isn't for you (anymore).

Running Slackware today is like being gifted a Ford Model T by a weird, bearded museum curator, and then finding out that after some minor modifications and learning how to drive it, you can keep up with any modern car on the road. Only it has no ABS, AC, power steering, starter motor, crumple zones, airbags or seatbelts.

Most people who still run it (by any realistic estimate, fewer than 10000 people in the world now) have been running it since the 90's and follow the advice not to change a running system to the letter. So why should anyone who hasn't studied CompSci in Berkeley in the 90's try it today?

First of all, the most widely known criticism (it has no dependency resolution) is a bit of a misunderstanding. Slackware is different. The recommended installation method is a full installation, which means you install everything in the repository up front. That way, all dependencies are already resolved. And you have a system you can use equally well on a desktop or server. It uses 20GB but disk space is essentially free now.

What if you need something that isn't in the repo? Well, do whatever the fuck you want. Use Slackbuilds, which aren't officially supported but endorsed by Slackware's dev. Use Sbopkg, a helper script with dependency resolution very much like Arch's AUR helpers. Use the repos of sister distros like SalixOS that include dependency resolution. Install RPM packages. Install Flatpaks. Unpack tarballs wherever you want them. Go the old school way of compiling from source and administering your own system yourself. Slackware doesn't get in the way of whatever you want to do, cause there's nothing there to get in the way.

It's the most KISS distro that exists. It's the most stable one, too. Any distro-specific knowledge you acquire will stay valid for decades cause the distro hardly ever changes. It's also the closest to "Vanilla Linux" you can get. Cause there really isn't anything there except for patched, stable upstream software and a couple of bash scripts.

Just be mindful of the fact that Slackware is different (because the Linux ecosystem as a whole has moved on from its roots).
One example:
Up-to-date Slackware documentation isn't on Google, it's in text files written by the guy who maintained the distro for 31 years, which come preinstalled with your system. Or on linuxquestions.org, where the same guy posts, asks for input from users, and answers questions regularly.

It's still a competent system, if you have the time and inclination to make it work. And it's a blast from the past, where computing was about collaborating with like-minded freaks on a personal level. And I love that.

view more: next ›