- 0 Posts
- 26 Comments
52·1 month agoWhat was the problem? I can see that if you don’t get past one of the steps described in the wiki, then you’re blocked. But I think if one has some experience with shell, CLIs and TUIs, it should be possible to follow the steps until you have a bootable system.
Is it worth it to try that, maybe through multiple attempts? Idk.
Do you do that every two years?
Yes, and tar works the same, it just doesn’t handle zip files.
And even if we’re pedantic: bsdtar is Arch Linux’ executable name for a port of the
tarcommand that is shipped by BSDs, so it’s alsotar.
One example for it is … tar!
It’s insane that this isn’t consistent.
Any combination of
-h,-?and--helpexists between tools (from 0 to all 3 of them)
Why remember/include the algorithm? Tar can infer that. It’s just
bsdtar xf filename.*for everything. (bsdtar handles .zip as well)
When in doubt, blame zoom. The sheer amount of completely different outlandish weird bugs and glitches as well as the fact that they were told what the correct API for screen sharing on Linux is just for them to completely ignore that and do something weird, specific, niche and bad instead … I’ve never seen something like that since like Windows xp.
I’m completely convinced they have absolutely no idea what they’re doing on the frontend (app and web) and just have the latest newbie hire hack things together until it kinda works on their machine.
what exactly is the point of running wayland if you are going to run less secure X apps with 94% of the same vulnerabilities?
When running Wayland, one X server is started per X application. So that application won’t be able to e.g. keylog others.
I personally don’t care about security here, it’s all about a flicker free Multi-monitor experience with different refresh rates per monitor. X just can’t do that under any circumstances.
OP said “bloated and full of bugs”.
I’ve been using Arch since shortly before they started using systemd and literally never ran into a systemd bug.
I have no clue at this point what “bloated” means. Maybe if everything works and you don’t have to hack up your own solution all the time, that’s “bloat”?
I literally haven’t run into a single one in the whole time Arch has been using it.
(I installed Arch shortly before it switched to systemd and have been using it since without pause)
Every other init that has unit files shipped on any distro that matches my quality standards. In other words: there are none.
Of course Linux desktops are slightly less reliable than the both less flexible and also commercially tested stacks of Apple and Microsoft.
But that doesn’t mean that OP is right. They might be one of the luddites that religiously use some ancient tech stack based on X11 or so.
As said: yes, 4.0 wasn’t ready. But 5.0 was, so I think it’s fair to assume that they learned from their mistake and 6.0 is fine too.
4 is two major versions back. For this statement to be fair, you should have evaluated it against 5. (Spoiler alert: that release was super smooth)
I tried Debian for my very first Linux install very long ago. Its installer formatted my windows partition despite me explicitly telling it not to.
Never touched it after. Not out of resentment, but because I just don’t need it for anything.
What the fuck is “System D”?
Well, if you find a TeX bug, Don Knuth will send you a cheque for $327.68. good luck!
Btw