The Linux Thread - The Autist's OS of Choice

Why should it even care about that in >current year?

This is the sort of goofy systemd thing that always happens. If that fails it should just ignore it and connect to an ntp server once it comes up like every other thing in existence.
You say that, but these bugs are hilarious:
And finally found the bug I was referencing:
PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

inb4 those bugs are fixed and not a problem anymore.
systemd is all consuming and totalist, so its natural to get blamed for everything when it is everything, and then some more in the future.
 
What does Linux run on though? Who deliberately runs Linux? It is disproportionately populated with people running ancient shit. And often that RTC battery has been dead for years. That shit should just be cleaned up upon boot. Maybe even mark the battery as dead, so these things can be disregarded.

It's not like someone's Sony Vaio from 1998 is running a nuclear facility.
Amazin'. How do you, as someone supposedly competent, more than ten years after Y2K, manage to create a 2038 bug?
It reads like they did it deliberately. Why? I assume tism of some sort.
 
It reads like they did it deliberately. Why? I assume tism of some sort.
The real tism is printing the same message in a loop so tight it can cause the kernel log buffer to give up and kernel panic, happened in my case that I need to use another non-systemd Linux to reset the time after fixing the battery.
Related: Linus throwing a fit at systemd devs appropriating "debug" and printing so hard it crashes the kernel.
 
What do they hope to accomplish by doing this? Flatpak has far more support across the entirety of Linux when compared to snaps.
Snaps are fucking trash and need to go away. Flatpak isn't perfect but at least they're better supported. Canonical have gone full retard in the last few years.
 
I want to ask if Canonical thinks it can push its weight around at the same level as IBM/Red Hat, but I am not connected with anyone who currently uses Ubuntu on the server nor desktop, and of those who were, they and had issues with Snaps have already moved on. Their adoption rate might go down by a small amount when their migration scripts inevitably break for those who use Flatpak over Snaps on Ubuntu, but I can't imagine a huge exodus happening.

Am I way off base here?
 
Asahibros... I don't feel so good...

1677317219229.png

https://rosenzweig.io/
 
Their adoption rate might go down by a small amount when their migration scripts inevitably break for those who use Flatpak over Snaps on Ubuntu, but I can't imagine a huge exodus happening.

Am I way off base here?
Nobody seems to understand what happened here but it triggered a horde of autists typing away angrily at their keyboards anyway.

Ubuntu does not have Flatpak installed by default. It's still in the repos. Canonical asked the maintainers of the variants to not install Flatpak by default. The only popular one that did is Kubuntu. It will still be in the repos. That's it.

For server usage you'd just use containers anyway.
 
I changed my desktop from Manjaro to Endevour. I had to format it anyway since it had been a while and a bunch of shit had piled up on my main drive and I was gonna swap GPU so I just decided to change OS already. Been pretty nice so far. Had a few small issues like the Endevour coming out of the install with the whole "clicking once opens a file" which I cannot for the life of me figure out why you would make the default but that was a tiny thing that 30 seconds of tweaking solved. I was worried at first that it was taking way too long to boot up but after the first 3 times it is not the lightning fast boot up I expected a fresh install to be. I assume it was a case of the system getting used to the hardware and the installation of all the drivers and software I needed and stuff.

I am thinking of setting up a Pen Drive to have a portable Linux install that I can carry with me and just slot onto PCs to use. I considered using ParrotOS since I have used it before in VMs to a very good experience and it lets me pre-install a bunch of software on the setup itself but I found the results to be quite dissapointing. It was much slower than in the VM and it would have graphical glitches. Seems even USB 3.0 isn't up to it. So I am looking for something that would work better. I tried to do a Puppy Linux one with FossaPup but it didn't work, when I booted it just showed me a GRUB terminal and I didn't know how to proceed because I am dumb.

BTW, the way I am doing these portable installs is I setup a VM without a virtual hd and then have the VM connect to the PenDrive I want to use. Then when the setup asks what drive to use I direct it to use the USB drive. It worked perfectly fine for the ParrotOS install. I assume this is the best way to do it right? Booting up the entire PC for a install seems wasteful, and I heard some rumors of fucking up the boot of the actual main system to the point one dude recommended disconnecting it do make such installs which sounds annoying and retardadedly over the top I am not opening my shit and pulling my SSD out just for that.
 
I changed my desktop from Manjaro to Endevour.

Manjaro is deceptively attractive to me. I don't know how much it diverged from Arch Linux in the decade and change that it's been around. That being said, there's something that just fundamentally unnerves me about its "delayed" rolling release model. I mean, Debian Testing and CentOS Stream both occupy similar niches; yet they've both got massive community (and enterprise in Stream's case) backing to ensure some modicum of quality control.

This blog post by Allan McRae, one of the committers to Arch Linux at the time of writing, outlined some pretty fundamental design flaws with the distro. Mind you, McRae's criticism stems from the project's overly ambitious beginnings when it was still very rough around the edges. I know that Manjaro has changed significantly since then, but I still can't bring myself to "trust" it.

Debian Testing ultimately builds into Debian Stable X.0; CentOS Stream eventually builds into RHEL X.0 (and its many de-branded clones). Manjaro, to this effect, does not use its delayed rolling release model to build onto a more stable platform. It just elects to temporarily dam up the rolling release from Arch's repositories, "test" them for a couple of weeks, then release "as-is" with minimal (if any) patching. I've had Arch installs borked by critical updates of stuff like glibc, Pacman, and the like where I neglected to read the Arch Linux home page to get the instructions for X/Y/Z workaround to critical updates that will bork if executed blindly.

I don't know if the same has ever happened on Manjaro, but the thought alone puts me off from ever giving it a chance for a long-term home use situation. If I really wanted long-term stable, I'd just go with Rocky Linux or anything built off of Debian Stable.
 
Nobody seems to understand what happened here but it triggered a horde of autists typing away angrily at their keyboards anyway.

Ubuntu does not have Flatpak installed by default. It's still in the repos. Canonical asked the maintainers of the variants to not install Flatpak by default. The only popular one that did is Kubuntu. It will still be in the repos. That's it.

For server usage you'd just use containers anyway.
I'd still prefer if Canonical stopped using the corpse of desktop Ubuntu to try to force their Snaps on everyone. What's wrong with letting people easily opt out of using Snaps or Flatpaks?
 
Manjaro is deceptively attractive to me. I don't know how much it diverged from Arch Linux in the decade and change that it's been around. That being said, there's something that just fundamentally unnerves me about its "delayed" rolling release model. I mean, Debian Testing and CentOS Stream both occupy similar niches; yet they've both got massive community (and enterprise in Stream's case) backing to ensure some modicum of quality control.

This blog post by Allan McRae, one of the committers to Arch Linux at the time of writing, outlined some pretty fundamental design flaws with the distro. Mind you, McRae's criticism stems from the project's overly ambitious beginnings when it was still very rough around the edges. I know that Manjaro has changed significantly since then, but I still can't bring myself to "trust" it.

Debian Testing ultimately builds into Debian Stable X.0; CentOS Stream eventually builds into RHEL X.0 (and its many de-branded clones). Manjaro, to this effect, does not use its delayed rolling release model to build onto a more stable platform. It just elects to temporarily dam up the rolling release from Arch's repositories, "test" them for a couple of weeks, then release "as-is" with minimal (if any) patching. I've had Arch installs borked by critical updates of stuff like glibc, Pacman, and the like where I neglected to read the Arch Linux home page to get the instructions for X/Y/Z workaround to critical updates that will bork if executed blindly.

I don't know if the same has ever happened on Manjaro, but the thought alone puts me off from ever giving it a chance for a long-term home use situation. If I really wanted long-term stable, I'd just go with Rocky Linux or anything built off of Debian Stable.

I never had any such bork ups with Manjaro in the about 20 months I used it for. However I still changed to Endevour for 3 main reasons: It was getting bloated with old stuff I had installed, forgotten dependencies, and old files so I was gonna at very least re-install it. Second reason is that Endevour is closer to Arch which means better support for AUR stuff and less dependent on official repositories. And the thing that convinced me I had to swap from Manjaro is the fact that recently they forgot to deal with their SSL certificate and it expired. This was the fourth time they let it expire. That just SCREAMS sus to me. If they let something like that happen so many times it simply comes off as the team being disfunctional.
 
They have done it a fifth! :smug:
Wait, it's happened FIVE times?

I knew it happened once, but I assumed that people were bringing it up in the same way people in Linux world bring up ancient news as somehow contemporaneously relevant, like Amazon in Ubuntu or some email written by someone at Microsoft in 1996.

How is it even possible to allow this to happen so many times when their reputation took such a hit off of the first time?
 
  • Like
Reactions: std::string
Wait, it's happened FIVE times?

I knew it happened once, but I assumed that people were bringing it up in the same way people in Linux world bring up ancient news as somehow contemporaneously relevant, like Amazon in Ubuntu or some email written by someone at Microsoft in 1996.

How is it even possible to allow this to happen so many times when their reputation took such a hit off of the first time?
Eh, once you've done something three times, doing it another won't hurt.
 
I used Manjaro as my first daily driven Arch experience and it was alright at first but it seems inevitable they will break something just by updating which is saying something since vanilla Arch is less of a pain.
I've used Endeavour and had zero issues, it's a nice experience.
 
Back