The Linux Thread - The Autist's OS of Choice

Frail Snail said:
This isn't the first time I've come across GNU or Linux shit breaking POSIX compatibility. but I don't have the mental fortitude to keep track of it anyway. Maybe there's a shell script linter for it somewhere out there. Bashisms are another can of worms, with regular POSIX shell being a pain in the ass void of features.
Click to expand...
afaik gnu awk and bash don't break compatibility but add extensions. but from the little bash scripting I've done, it has so many useful features over standard sh you wish it was standard
 
  • Agree
  • Like
Reactions: Frail Snail and Baguette Child
Churros con Manteca said:
Whenever sed falls short for the task I'm doing, Perl's always there to save the day. If I want to search and replace a paragraph or a block Perl can do the job.
Click to expand...
All perl code looks like line noise, like you left an acoustic modem off the hook and then screeched autistically for a minute or two and nobody can figure out what the fuck it does.
 
  • Agree
  • Feels
  • Winner
Reactions: Isam, notafederalagent, Wood and 4 others
Churros con Manteca said:
From here and on I cannot exactly predict what's going to happen, but Lennart got hired by Microsoft indeed.
Click to expand...
bwahaha well if the shoe fits. Systemd dicksucking central /r/linux has no mention of it so my guess is discussion of the topic is verboten by tranny decree. (or reddits shitty search isn't showing it to me, also quite possible)

I always thought the systemd obfuscation-by-complexity and it's being hell-bent of being one monolithic thing instead of many little easily forkable pieces was fully on purpose and a not-so-stated design goal. Always. My mind never doubted this. I'm guessing it's only a question of time until it comes with binary blobs that are totally for your own protection and any discussion of is shut down immediately. They're defintively going with a slowly-boil-the-frog approach here.
 
  • Agree
  • Like
  • Feels
Reactions: Francesco Dellamorte, Frail Snail, 419 and 7 others
3119967d0c said:
Poettring is working on making Linux equivalent to his employer's product on the desktop by adding better persistence for malware across boots.
Click to expand...

He was playing the long con all along.
1657231191100.png
 
  • Like
Reactions: 419, Churros con Manteca, Knight of the Rope and 3 others
Hello friends. I've been using Linux for about 5-6 years now and recently switched from Arch to Gentoo, from i3 to dwm, and from urxvt to st. Loving the new setup. I've also been trying to learn Bourne Shell and BASH, but it's been kinda slow going. My code is almost certainly still pretty flawed, but it'll get there. Below is from when I was working on my replacement for neofetch.
rice_specs_script_01.png
 
  • Like
Reactions: 419, Smith Banquod, Spasticus Autisticus and 6 others
awoo said:
usually I don't post these but this is an interesting topic after the recent discussion on awk
Click to expand...
I'm not properly Perl-pilled unfortunately. I don't think it's completely unreadable, but the syntax isn't easy enough to justify the effort. The points listed seem compelling, but what about startup time outside of daemon services?

He Who Points And Laughs said:
Rated your post Hawaiian, but I also hope so. There are some aspects of SystemD that are nice, but on the whole it wasn't necessary. There's nothing wrong with OpenRC and binary logs are pure faggotry.
Click to expand...
The aspects that are nice are the features that were requested by companies who pay Red Hat, i.e. embedded sector and FAGMAN. The rest are pet ideas of developers, who are massive speds and Apple fetishists, that get thrown at the Linux desktop serfs. When they don't clap and start mentioning verboten terms like "OpenRC" and "runit", Poettering/Microsoft and redditors get very upset. At that point, you can expect mentions of SysVinit and The Future of all your OS internals hidden behind an API of systemd or something similar (and that's a good thing!)

A Humble Moose said:
Hello friends. I've been using Linux for about 5-6 years now and recently switched from Arch to Gentoo, from i3 to dwm, and from urxvt to st. Loving the new setup. I've also been trying to learn Bourne Shell and BASH, but it's been kinda slow going. My code is almost certainly still pretty flawed, but it'll get there. Below is from when I was working on my replacement for neofetch.
View attachment 3473540
Click to expand...
Shellcheck would be complaining at those unquoted command results. That is, "$()" instead of $() to prevent whitespace fuckery.
 
  • Informative
Reactions: A Humble Moose
Frail Snail said:
Shellcheck would be complaining at those unquoted command results. That is, "$()" instead of $() to prevent whitespace fuckery.
Click to expand...
Sorry if this is a bit of a newbie question, but I am still quite new to this. What do you mean by "whitespace fuckery?" Is it just generally better practice to quote commands?
 
  • Like
Reactions: notafederalagent
A Humble Moose said:
Sorry if this is a bit of a newbie question, but I am still quite new to this. What do you mean by "whitespace fuckery?" Is it just generally better practice to quote commands?
Click to expand...
Let's say you have a script to delete a file and you give an unprivileged user permissions to run it

deletelog.sh:
#! /bin/bash
rm /opt/application/log/$1

and you allow "sudo deletelog.sh file"
Well, now the user runs:
sudo deletelog.sh "file /etc/passwd"

Now you've just let the user delete any file on the system.

With $0 you can influence what it is by making symlinks(among other ways), so you can do stuff like:
ln -s /usr/bin/stupid_script.sh "rm -Rf /etc/passwd"
depending on what it's doing with $0
 
  • Informative
  • Like
  • Agree
Reactions: Churros con Manteca, notafederalagent, Frail Snail and 4 others
You must log in or register to reply here.
Back