esa

Yeah, Ubuntu actually isn’t the first distro without GNU coreutils. Beyond Android and Busybox, there’s also stuff like Talos, which is something like … Kubernetes/Linux.

IME something like Kubernetes/Linux running “distroless” containers have a huge potential to displace traditional GNU/Linux in the server market, and I wouldn’t be surprised if someone manages to build a desktop out of it, either.

One more puzzle piece here is that du won’t report on files that have been marked for deletion but are still held on to by some process. There’s an lsof incantation to list those, but I can’t recall it off the top of my head.

It used to be part of sysadmin work to detect the processes that held on to large files if df reports that you’re running out of space, and restart them to make them let go of the file. But I haven’t done that in ages. And if you restarted the host OS that should have taken care of that.

I assume you also know how to prune container resources.

Nope! I tend mostly to use /org/repo and other subpages. The few times I find myself on / I’m just confused at how I wound up there and close the tab.

It’s even a tape archiving tool. Just pretty much nobody uses it in the original way any more.

Very much one of those “if it ain’t broke, don’t replace it” tools.

Yeah, there should be a clear separation between scripts, which should have a shebang, and interactive use.

If a script starts acting oddly after someone does a chsh, then that script is broken. Hopefully people don’t actually distribute broken script files that have some implicit dependency on an unspecified interpreter in this day and age.

That’s interesting I hadn’t thought about the JSON angle! Do you mean that you can actually use jq on regular command outputs like ls -l?

No, you need to be using a tool which has json output as an option. These are becoming more common, but I think still rare among the GNU coreutils. ls output especially is unparseable, as in, there are tons of resources telling people not to do it because it’s pretty much guaranteed to break.

I’ve been using fish (with starship for prompt) for like a year I think, after having had a self-built zsh setup for … I don’t know how long.

I’m capable of using awk but in a very simple way; I generally prefer being able to use jq. IMO both awk and perl are sort of remnants of the age before JSON became the standard text-based structured data format. We used to have to write a lot of dinky little regex-based parsers in Perl to extract data. These days we likely get JSON and can operate on actual data structures.

I tried nu very briefly but I’m just too used to POSIX-ish shells to bother switching to another model. For scripting I’ll use #!/bin/bash with set -eou pipefail but very quickly switch to Python if it looks like it’s going to have any sort of serious logic.

My impression is that there’s likely more of us that’d like a less wibbly-wobbly, better shell language for scripting purposes, but that efforts into designing such a language very quickly goes in the direction of nu and oil and whatnot.

Possibly, but the article didn’t seem to specify what the actual complaints were. Hopefully they’ve worked with some actual Apache to figure out some rebrand that’s decent towards the Apache (and addresses the complaints), but also doesn’t make the brand more different than it needs to be.

hey, a/s/f?

Also seems ripe for jokes about the missing d.

Though I guess the reasoning for why they’re changing it up is actually decent:

changing its corporate logo and overhaul its branding after being criticized by American Indian activists.

It’s the sort of thing that I think a lot of europeans will go “huh, what does a feather … ohhhh, riiiiiiiight …”. Like, my associations to the name are mostly the LAMP stack and a model of children’s bike that my parents have talked about. But we’re collectively also always rolling our eyes at people, especially foreigners, using stuff related to our heritage as marketing. Can’t imagine what that’d be like for the native americans and their history.

No, but the weirdos who insist on spelling it “SystemD” always seem to hate systemd.

systemd is pretty great. I tend to start long-running processes as user services, and I’ve even taken to starting some apps that give an old laptop trouble with systemd-run and a slice with some memory restrictions. Easy peasy, works great, all declarative, no wibbly-wobbly shell scripts involved.

But what did you learn? What are we supposed to learn? Did you get any context, like how he actually went to anger management therapy later?

Or is this just guffawing and gawping at an old angry email from a tech celebrity?

This mail is 13 years old, and doesn’t seem relevant for anything? This post seems like a lazy attempt at shit-stirring.

Yeah, JSON is essentially a side effect of having JavaScript already. It makes sense that it shows up a lot of places, especially web. But just like with JS, it’s not really good, just ubiquitous.

I’ve very barely dipped my toes in dbus before, and the option to have something else is on its face attractive (not a fan of XML and the late 90s/early aughties style of oop), but JSON for a system interface?

I mean, Kubernetes shows that yaml can work, but in this day and age I’d expect several options for serialisation, and for the default to be binary, not strings.

String serialisations are primarily for humans IMO, either as readers or writers. As writers we want something with comments (and preferably no “find the missing }” game), so for that most of us would prefer something like TOML if the data is simple enough, and actually Yaml for complexity at the level of Kubernetes—JSON manages to be even more of a PITA at that level.

But machine-to-machine? Protobuf, cap’n’proto, postcard, even CBOR should all be alternatives to examine

That’s how it starts. Just let it develop for a century or something and you’ll probably be decent at it

I escaped reddit for this?

The O is for the kind of whooshing sound

Yeah, none of that with bat:

λ bat $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
       │ File: /usr/bin/bat   <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ bat < $(type -P bat)
───────┬──────────────────────────────────────────────────────────────────────────
       │ STDIN   <BINARY>
───────┴──────────────────────────────────────────────────────────────────────────
λ

Or bat, which will just print <binary> in those cases

I think some of the stuff you worry about as a kid will just arise naturally. Ideas like not stepping on cracks, or imagining monsters in dark places are likely produced spontaneously and naturally by an underdeveloped ape brain.

But it’d be nice if we didn’t tell kids about old superstitions, yeah. Wait until they’re old enough to react with dismissal about the stupid stuff people used to believe.