KDE for desktops with a mouse, Gnome for laptops with a touchpad. Both are great!
superkret
joined 2 months ago
I work in IT, and by now, every single 3-letter-abbreviation makes my eyelid twitch.
I'm guessing they just defined the standard for any round fired by a human-portable rifle, without worrying about whether it's possible to meet the standard.
My guess is, the institute developed a competent armor, showcased it and got the contract to build them.
Then several levels of managers and executives decided to use a bit less material, use a cheaper supplier and skip a few QC steps, pocketing the surplus contract money.
And then they re-used the vests taken off fallen soldiers several times, sewing shut the bullet holes in the cloth covering (or not).
The extra plate stops rifle rounds up to caliber .308 / 7.62mm (which carry more force than the assault rifles used by most infantry now), at least in the American Level III/IV vests.
Funnily enough, the European standard goes up to armor ratings that would protect against 3 point blank shots from 14.5Γ114mm rounds (what this thing shoots), but I couldn't find a picture of any armor with that rating, and it would likely break every bone in your torso even if the bullet doesn't penetrate.
This is what Level III/IV full body armor looks like:
It's actually a mix of both.
My wife bought them from a market in Tunisia. The seller told her it's a spice mixture for lazy wives, cause you won't need any other spices in the kitchen to make your food taste good.
So that's how she labelled it.
It's caraway, cumin, anise and saffron.
Aysenur Ezgi Eygi was taking part in a protest against Jewish settlement expansion in the town of Beita, in the occupied West Bank
Jewish-Israeli activist Jonathan Pollak, who was at the protest, told BBC World Service's Newshour programme he had seen "soldiers on the rooftop aiming".
He said he had heard two separate shots, "with like a second or two distance between them".
"I looked up, there was a clear line of sight between the soldiers and where we were.
In a statement, the Israel Defense Forces (IDF) said: "During Israeli security forces activity adjacent to the area of Beita, the forces responded with fire toward a main instigator of violent activity who hurled rocks at the forces and posed a threat to them.
Damn, she must have been quite strong, to be able to hurl rocks at snipers on a rooftop.
You may not like it, but this is what peak cat length looks like.
"I found this strange fucking object" vs "I found this strange fucking object"
28
[Solved] [Slackware] What's the best way to hide the preinstalled software you don't need from the KDE menu?
(feddit.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/*.desktopBut 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.
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 βΊ
I don't understand.
The words "too", "much" and "butter" don't make any sense in that order.