Clearly there was.

Glad to hear it’s not gonna starve.

Kinda yeah, but I think that just comes from storing the output of the PWD command.

The system call that returns that value is called getcwd().

Kinda, but it’s pretty much all horrendously outdated bitching about superficial flaws in tools from 40 years ago.

All the worse that Debian has both useradd and adduser. I never remember which is the one I want. And in Redhat-derivatives it’s something even more confusing.

The only thing I ever want to do is add a user to a group, is that too much to ask?

No. “Print working directory” is the command to print (display) the “cwd” (current working directory).

those in power

I think you found the reason.

We’ve tried doing nothing and we’re all out of ideas!

So which is dumber: Reaganomics or whatever the fuck stupid shit trump is doing.?

No need to answer, I can guess.

Late 1970s / early 1980s.

Yeah… that all makes sense and those docks seem decent. The piece of the puzzle that’s missing for me is: how does docker turn a yaml config that says like … (from their example):

> frontend:
>     image: example/webapp
>     ports:
>       - "443:8043"
>     networks:
>       - front-tier
>       - back-tier
>     configs:
>       - httpd-config
>     secrets:
>       - server-certificate

… into actual operating, functioning container blobs? e.g. How does it know that “secrets: server-certificate means that it should take an ssl cert and place it in the container? How does it know where to place that certificate?

I mean I’d rather get told to “rtfm” than hear “it just works” with no explanation

No they’re still there in NTFS. It’s definitely still a thing, although automatic creation of 8.4 file names can be disabled.

Just Microsoft things.

I thought they removed 8.3 file names a while back though?

Bad bot.

Musicbrainz Picard is a lot easier than beets, although it does require some introductory concepts to make sense (e.g. terminology like “release”, “release group”). And it makes it too easy to accidentally poison datasets in an attempt to be helpful. Harder to automate than beets, too.

Both of them also benefit from a decent knowledge of where your files came from, not as good for a random pile of mp3s.

Got any good resources for learning?

In my (limited) experience Docker is just “run some script from a random GitHub that loads more stuff from a random GitHub… now you have a blob of code on your PC somewhere that’s unmodifiable and inaccessible unless it’s a web app in which case it’s listening on a random port with no access to any system resources”

I assume there’s something more I need to be doing but all the learning resources just kinda assume you understood wtf it’s doing.

But it’s gone downhill, it used to be good when it was a serious news show.

Because other people stop existing in that bubble, because they become part of the background, bubbled people stop caring about them.

See also !fuckcars@lemmy.world

Ah yeah that makes sense. I was absolutely not thinking of a Super Target.