The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.
The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.
systemd, not SystemD, or system d.
But yeah, wonderful talk!
Once git no longer depends on it, it’ll be gone from my system
Nah, gross. You need to set a bunch of global options to get sane behavior on errors.
Nushell is shaping up really really nicely, and it’ll actually stop executing if something fails! Even if that happens in a pipe! And it’s not super eager to convert between arrays and strings if you use the wrong cryptic rune.
You can theme plasma and turn the effects off. Why isn’t that exactly what you want?
You can update the whole base image. Vanilla OS and SteamOS have an A/B partition that holds the currently-in-use image and can also hold a to-be-used image.
Updating works by adding the to-be-used image, setting a configuration option that tells the system to boot that one, and on the next boot it’ll check if the new one is bootable, then either boot it and mark it as working, or boot into the old one and display an error about how out wasn’t able to boot into the new one.
There’s smart things going on like maybe hard linking files that didn’t change between the two images and therefore saving space and copying time.
The result is that you never have a broken system, but you can still frequently update the base image.
I feel like that has been superseded by Nix these days. Arch is now boring stable tech.
You say that as if somebody was disputing that.
The distinction ceased to be meaningful the minute language servers got introduced.
Laptop tries to reboot for 5th update of the day
I can’t connect to the internet, Dave, I’m afraid I cannot allow you to start me up again
You try to ignore helpful tips from the guy next to you, pretending your headphones are still active.
You choke back tears as Windows had enough from your feeble attempts to boot and the power button stops doing anything.
What 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 tar
command that is shipped by BSDs, so it’s also tar
.
One example for it is … tar!
It’s insane that this isn’t consistent.
Any combination of -h
, -?
and --help
exists 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)
That’s just completely wrong. Just try e.g. replacing the journald backend with the old text based syslog, and not only will you discover that is possible (which directly contradicts what you just said), it’s also easy!