Anybody want a peanut?

If I wanted to give it a bold facelift I’d just use the top one and remove the letters. Gives it an arrogant, “if you have to ask what this is…” vibe, which is probably a good thing for them.

IIRC that was the release that cleaned up the make output substantially.

I really don’t think it’s the devs driving these decisions…

Ok so it is fully qualified then? I’m just confused because it sounded like you were saying I wasn’t using the term correctly in your other comment.

Hmm, my understanding was that FQDN means that anyone will resolve the domain to e.g. the same IP address? Which is the case here (unless DNS rebinding mitigations or similar are employed) — but it doesn’t resolve to the same physical host in this case since it’s a private IP. Wikipedia:

A fully qualified domain name is distinguished by its lack of ambiguity in terms of DNS zone location in the hierarchy of DNS labels: it can be interpreted only in one way.

In my example, I can run nslookup jellyfin.myexample.com 8.8.8.8 and it resolves to what I expect (a local IP address).

But IANA network professional by any means, so maybe I’m misusing the term?

TIL, thanks. I use namecheap and haven’t had any problems (mikrorik router).

If you have your own domain name+control over the DNS entries, a cute trick you can use for Jellyfin is to set up a fully qualified DNS entry to point to your local (private) IP address.

So, you can have jellyfin.example.com point to 192.168.0.100 or similar. Inaccessible to the outside world (assuming you have your servers set up securely, no port forwarding), but local devices can access.

This is useful if you want to play on e.g. Chromecast/Google TV dongle but don’t want your traffic going over the Internet.

It’s a silly trick to work around the fact that these devices don’t always query the local DNS server (e.g., your router), so you need something fully qualified — but a private IP on a public DNS record works just fine!

The network gear I manage is only accessible via VPN, or from a trusted internal network…

…and by the gear I manage, I mean my home network (a router and a few managed switches and access points). If a doofus like me can set it up for my home, I’d think that actual companies would be able to figure it out, too.

Debian (i3 on laptop, headless on homelab).

But apparently my coffee is Arch.

How do we get everyone angry.

This is the problem — taking away my coffee makes me angry, but I’ll be too tired to do anything about it.

Come see the vise grips inherent in the system! Help! Help! I’m being drill pressed!

UN-Verified

Unfortunate abbreviation…

Duh, just read it back from /dev/random

You will recover the data, you just need to wait long enough.

Perhaps microwaving for significantly longer, at a low power level, would be safer and result in higher success/yield?

I think it has a lot to do with disposition and convenience. I’m lazy, and I don’t like to drive if I can help it. But I live near enough to public transportation that we’ll spontaneously decide to hop on the subway and grab dinner on the waterfront.

It’s not the money that’s preventing us from hopping in the car to go to some new beach for dinner, it’s the convenience.

I mean…it depends on the job? I go on walks during working hours all the time to clear my head and think about a problem I’m working on. I don’t try to hide this from my manager.

Just stick to elements lighter than iron and you’ll be fine.

That’s how I started using Linux — big book with CD, I think it was “RedHat Linux Secrets 5.4” or something. 2.0 or 2.2 kernel.

Honestly, it was fantastic. And almost all of it is still relevant today. (Some of the stuff on xfree86 and the chap/pap stuff not so much.)

But it gave a really solid (IMHO) intro to a Linux/*NIX system, a solid overview of coreutils, etc. And while LILO has been long replaced, and afaik /sys didn’t exist at the time, it formed a good foundation.

I’ll refrain from commenting on any init system changes that have taken place since then.

Just use your $200+ Fluke to check the batteries, problem solved.