The Linux Thread - The Autist's OS of Choice

[The Noise]

The NPCs will never be given that order because they're tools of the same agenda. They will go after Linus though.

He's a self-described card-carrying athiest and probably a troon supporter. They would never.

 

[AnOminous]

He's a self-described card-carrying athiest and probably a troon supporter. They would never.

They already did. They basically drove him out of his own foundation, made him leave development, and grovel on his hands and knees.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

Cool. Because "fun" is excatly what sudo is missing. And WTF does it have to do with this sudo-at-home anyway? Unless you now have to link every single terminal emulator with libsystemd (or whatever the fuck it's called), AND use Gayland with a brand-new "lennarD-sudo-paint-my-terminal-d" extension.

Don't worry about it! systemd-cucked distributions will now ship with a wrapper around run0 calling itself 'sudo' which (as you say) links to libsystemd to maximize attack surface. If you want real sudo, you'll be able to install an optional package... for a couple of releases.*

Or just maintain your own copy of real sudo! This is normal, this is something that should happen, Lennart Poettring should not be raped to death and then beheaded.

The real tragedy of Hans Reiser is that he didn't kill Lennart Poettring.

*or you could just move to devuan already

 

[HahaYes]

Tell you how? By spitting out some log file... with technical data meant for developers and not end users?

Event viewer isn't much better.

It's not that hard to navigate and read event viewer/error logs in general though? You just reference the code, use a search engine if you need to get some clarification on said code and read the general output. Idk I'm not a dev but it's not that hard to narrow down what gay shit is going on by referencing event logs, literally just read it, read what happened shortly before it was generated and it'll give you the information you need. If it's a hardware issue look at your motherboards q-code/q-led or reboot the machine into BIOS and snoop around in there.

Meanwhile this is the exact group of users that Linux malware creators target.

Yeah exactly, the same type of cattle who go around downloading/clicking everything under the fucking sun while thinking it's a great idea

 

[yydszmiteg2]

Don't worry about it! systemd-cucked distributions will now ship with a wrapper around run0 calling itself 'sudo' which (as you say) links to libsystemd to maximize attack surface. If you want real sudo, you'll be able to install an optional package... for a couple of releases.*

Or just maintain your own copy of real sudo! This is normal, this is something that should happen, Lennart Poettring should not be raped to death and then beheaded.

*or you could just move to devuan already

Year 1: Sudo isn't going anywhere chuds.
Year 2:Sudo is optional now. I thought choice was a good thing chuds.
Year 3: Sudo is deprecated now, it was old and stopping progress chuds.

 

[Slav Power]

Cool. Because "fun" is excatly what sudo is missing. And WTF does it have to do with this sudo-at-home anyway? Unless you now have to link every single terminal emulator with libsystemd (or whatever the fuck it's called), AND use Gayland with a brand-new "lennarD-sudo-paint-my-terminal-d" extension.

This terminal coloring thing sounds retarded. I'm pretty fucking sure you could realize it on the terminal emulator side without having to fuck with the upper system functions. Windows Terminal gives you a little shield icon in the corner when you run it elevated because software under Windows can know it's elevation status. I'm sure you could make it so that the terminal emulator can tell when sudo/su/doas is active within it or not without having to hook it up to the init system.

To be honest, people talk about Poettering being a cunt for trying to turn Linux into Windows, but I think Windows NT developers are still more competent in OS design than Poettering is. At least Microsoft added the fancy terminal thingy as something on the terminal side and not as an integral part of the kernel.

 

[Betonhaus]

Is there going to be a point where pottering crosses a line and forces Debian to fork systemd or replace it?

 

[Rusty Metal Skull Gun]

You're all talking about sudo, but I never stopped using su. I type su and my prompt goes red, to show that I'm now root. There's nothing new under the sun.

 

[⠠⠠⠅⠑⠋⠋⠁⠇⠎ ⠠⠠⠊⠎ ⠠⠠⠁ ⠠⠠⠋⠁⠛]

Is there going to be a point where pottering crosses a line and forces Debian to fork systemd or replace it?

Nah. Not since they took out Ian Murdock.

 

[Black Willow Lurker]

Don't worry about it! systemd-cucked distributions will now ship with a wrapper around run0 calling itself 'sudo' which (as you say) links to libsystemd to maximize attack surface. If you want real sudo, you'll be able to install an optional package... for a couple of releases.*

Or just maintain your own copy of real sudo! This is normal, this is something that should happen, Lennart Poettring should not be raped to death and then beheaded.

The real tragedy of Hans Reiser is that he didn't kill Lennart Poettring.

*or you could just move to devuan already

In about 20 years, we're gonna see a potter-sudo-ng (written in Rust, of course), that would require you to run a per-user instance (fuck pipewire/pulseaudio, BTW) of an http server accepting a blow-me-666-encrypted XML string describing whatever it is you want to do, which would then be passed along to a remote server for "validation", then sent back, so that systemd can parse it (again) and shit itself because you failed the "still-has-balls-attached" check.

This terminal coloring thing sounds retarded. I'm pretty fucking sure you could realize it on the terminal emulator side without having to fuck with the upper system functions.

At least syntax highlighting is possible with zsh/fish/(probably) bash and others, so there's no need to even touch the terminal emulators for this. But yeah, dragging this shit into stuff that's being rewritten because "muh SUID" and "muh attack surface" (which is fucking rich coming from the guy behind systemd, BTW) is probably not the best idea.

 

[AnOminous]

To be honest, people talk about Poettering being a cunt for trying to turn Linux into Windows, but I think Windows NT developers are still more competent in OS design than Poettering is.

I'm not sure about is, but was maybe. Windows NT 3.5 (and 3.51) basically killed Novell Netware (imo) (and in combination with Unix and Unix-like solutions). It's too bad M$ didn't stick to the same focus on stability that let them kill what was, before then, the leading commercial server solution.

 

[emergenigger]

https://outpost.fosspost.org/d/19-systemd-wants-to-expand-to-include-a-sudo-replacement

>Lennart crowd touches the X server
>Breaks compatibility for "security reasons", among other things
>shits up the project until it's unmaintainable
>"This thing actually fucking sucks."
>"Here's our new(tm) thing."
<It fucking sucks
<<leaves
Fast forward
>bloats sudo
>"This thing actually fucking sucks. Here's our new(tm) thing."
<does exactly what the competitors did (switch from sudo to something else like doas)
(You are now here)
>>leaves

Is the kernel itself next?

And for the X part: I'm not talking out of my ass. I've seen compatibility being broken a couple of times because the Security(tm) crowd patched a vulnerability by disabling the ability to connect to Big-endian architectures without pretending it as an option in the X server list, which broke legacy setups.
From what I've seen, X has been only stripped from features so far without adding any new ones.

I don't care that you removed compilation code for a dead architecture, you're not improving the codebase. Pulling up to Sunny Acres, barging in with a gun in hand and putting the elderly out of their misery, one by one, doesn't make you a hero. Stop removing features for updoots and green activity boxes.

 

[std::string]

>bloats sudo
>"This thing actually fucking sucks. Here's our new(tm) thing."
<does exactly what the competitors did (switch from sudo to something else like doas)
(You are now here)
>>leaves

sudo deserves to die.

But actually we're just going to now have both sudo and run0 going forwards. sudo is almost a quarter million lines of code and you're not replicating whatever edge case weirdness is going on with that.

 

[emergenigger]

sudo is almost a quarter million lines of code and you're not replicating whatever edge case weirdness is going on with that.

Which is why the Gentoo crowd moved to doas. (At least I did - I never had any problems with it ever since.)

 

[GNU Abyss]

Re: the XFCE4 vs. window managers discussion, the reason I prefer WM setups is because all DEs are very standoffish with their dependencies. Case in point, try to install any XFCE4 tool by itself and watch it try to pull in more xfce4-* libraries. It's not the end of the world, I just prefer to mix & match my tools. A bar like tint2 gives you a status panel and tray without much effort on any WM.

It's not that hard to navigate and read event viewer/error logs in general though? You just reference the code, use a search engine if you need to get some clarification on said code and read the general output. Idk I'm not a dev but it's not that hard to narrow down what gay shit is going on by referencing event logs, literally just read it, read what happened shortly before it was generated and it'll give you the information you need. If it's a hardware issue look at your motherboards q-code/q-led or reboot the machine into BIOS and snoop around in there.

Have I never encountered any serious computer problems? Never had much trouble reading Windows and Linux logs. Time-consuming, sure, but not impenetrable.

 

[Trans Fat 41g]

I've tried xfwm4 as a standalone but in a handful of ways it really, really doesn't want you to use it in that way. Yes, openbox is always there, but I also find window snapping out of the box very useful to have without editing a dizzying .xml file.

 

[SIGSEGV]

I’d just like to interject for a moment. What you’re refering to as Linux, is in fact, GNU/Linux, or as I’ve recently taken to calling it, GNU plus Linux.

No, Richard, it's 'Linux', not 'GNU/Linux'. The most important contributions that the FSF made to Linux were the creation of the GPL and the GCC compiler. Those are fine and inspired products. GCC is a monumental achievement and has earned you, RMS, and the Free Software Foundation countless kudos and much appreciation.

Following are some reasons for you to mull over, including some already answered in your FAQ.

One guy, Linus Torvalds, used GCC to make his operating system (yes, Linux is an OS -- more on this later). He named it 'Linux' with a little help from his friends. Why doesn't he call it GNU/Linux? Because he wrote it, with more help from his friends, not you. You named your stuff, I named my stuff -- including the software I wrote using GCC -- and Linus named his stuff. The proper name is Linux because Linus Torvalds says so. Linus has spoken. Accept his authority. To do otherwise is to become a nag. You don't want to be known as a nag, do you?

(An operating system) != (a distribution). Linux is an operating system. By my definition, an operating system is that software which provides and limits access to hardware resources on a computer. That definition applies whereever you see Linux in use. However, Linux is usually distributed with a collection of utilities and applications to make it easily configurable as a desktop system, a server, a development box, or a graphics workstation, or whatever the user needs. In such a configuration, we have a Linux (based) distribution. Therein lies your strongest argument for the unwieldy title 'GNU/Linux' (when said bundled software is largely from the FSF). Go bug the distribution makers on that one. Take your beef to Red Hat, Mandrake, and Slackware. At least there you have an argument. Linux alone is an operating system that can be used in various applications without any GNU software whatsoever. Embedded applications come to mind as an obvious example.

Next, even if we limit the GNU/Linux title to the GNU-based Linux distributions, we run into another obvious problem. XFree86 may well be more important to a particular Linux installation than the sum of all the GNU contributions. More properly, shouldn't the distribution be called XFree86/Linux? Or, at a minimum, XFree86/GNU/Linux? Of course, it would be rather arbitrary to draw the line there when many other fine contributions go unlisted. Yes, I know you've heard this one before. Get used to it. You'll keep hearing it until you can cleanly counter it.

You seem to like the lines-of-code metric. There are many lines of GNU code in a typical Linux distribution. You seem to suggest that (more LOC) == (more important). However, I submit to you that raw LOC numbers do not directly correlate with importance. I would suggest that clock cycles spent on code is a better metric. For example, if my system spends 90% of its time executing XFree86 code, XFree86 is probably the single most important collection of code on my system. Even if I loaded ten times as many lines of useless bloatware on my system and I never excuted that bloatware, it certainly isn't more important code than XFree86. Obviously, this metric isn't perfect either, but LOC really, really sucks. Please refrain from using it ever again in supporting any argument.

Last, I'd like to point out that we Linux and GNU users shouldn't be fighting among ourselves over naming other people's software. But what the heck, I'm in a bad mood now. I think I'm feeling sufficiently obnoxious to make the point that GCC is so very famous and, yes, so very useful only because Linux was developed. In a show of proper respect and gratitude, shouldn't you and everyone refer to GCC as 'the Linux compiler'? Or at least, 'Linux GCC'? Seriously, where would your masterpiece be without Linux? Languishing with the HURD?

If there is a moral buried in this rant, maybe it is this:

Be grateful for your abilities and your incredible success and your considerable fame. Continue to use that success and fame for good, not evil. Also, be especially grateful for Linux' huge contribution to that success. You, RMS, the Free Software Foundation, and GNU software have reached their current high profiles largely on the back of Linux. You have changed the world. Now, go forth and don't be a nag.

Thanks for listening.

 

[Betonhaus]

If you used Visual Studio to write your code you don't call it Microsoft's code, do you?

 

[Belisarius Cawl]

At least syntax highlighting is possible with zsh/fish/(probably) bash and others, so there's no need to even touch the terminal emulators for this.

Yes, and you might not even get that terminal emulator warning if you're using something like JuiceSSH on your phone to get into a headless server environment.

 

[AnOminous]

Thanks for listening.

You said all this shit I didn't read. All I heard was BEAR COMPUTER.