Most normal photo of me and @equinox on the last photo of this:

https://mastodon.social/@ripencc/113386357094792057

Imagine wondering “When’s the next time that Christmas will be a Tuesday/Wednesday, for those sweet optimal public holidays (Jan 1st being exactly a week later)?”

Now imagine asking, idk, google or Siri or god forbid an actual calendar, instead of turning to the best tool for the job: systemd.

#systemd #linuxadmin #linux #systemd

I love the idea that the company that built "the" taxi app has gone full circle to having jumbo sized smartphones in airports

See everyone at RIPE89 soon!

@benjojo Part of the glibc res_init() code where it reads the `domain` and `search` parameters from /etc/resolv.conf - if the configured search list ends up empty, it populates it with an entry based on the system hostname (chopping off the first part); search for domain_from_hostname() in resolv/res_init.c

...which works well enough for most systems when they have FQDN hostnames *under* a domain, as opposed to just the bare domain.

So it's not a nsswitch feature as such; it's a feature of Glibc's libresolv which happens to be used by libnss_dns (and deliberately unimplemented by systemd-resolved's nsswitch module from what I remember).

https://sourceware.org/git/?p=glibc.git;a=blob;f=resolv/res_init.c;h=b838dc70642e19353892e2396387211d8fdb61fd;hb=HEAD#l301

(to be honest, although I don't like putting FQDNs in the system hostname in general, it befuddles me in particular when people have just the bare domain as their server name. it's like, "Address: London" in a way)

Wow, incredibly cursed DNS/NSS quirk I have ran into.

If a machines hostname is FQDN like test.com and you do a lookup without some local cache involved like systemd-resolved. NSS rules will turn a query for whatever into whatever.com:

# hostname
test.com

# cat /etc/resolv.conf 
nameserver 192.168.181.1

# getent ahosts google
2a00:1450:4009:820::200e STREAM google.com
2a00:1450:4009:820::200e DGRAM  
2a00:1450:4009:820::200e RAW    
216.58.204.78   STREAM 
216.58.204.78   DGRAM  
216.58.204.78   RAW    

# ping google    
PING google(zzz) 56 data bytes
64 bytes from ...1e100.net (2a00:...): icmp_seq=1 ttl=116 time=7.40 ms

I knew having your hostname as a FQDN was a bad idea, but this is a """interesing""" one, Reminds me of a previous run in with DNS Search Paths

So nice to be back in a country that doesn't pose an arrest risk for crossing the road in a unsanctioned place (vs US and Canada etc)

A flight itinerary so complicated you can now remember the booking reference without any effort

Created this for later/the next mikrotik based explosion that I deal with

heh, the video stabilisation got confused during taxi

In-flight WiFi and its consequences have been a disaster for the human race

When in Canada I suppose

I think I first came to San Francisco like 10 years ago almost exactly to now, the one thing that has not changed over time are the tech product billboards.

it's weird because I am used to seeing these as banner ads or whatever, but nope, here they are on the side of the road just chilling

Mods are asleep, post cursed motherboards

hmph, Long time since I've seen a kettle with a "kettle lead" (C13/C15) connector

@benjojo is no longer asking

It's entirely possible there may be too many WiFi access points inside the datahall of HE FMT2

I went to the Bay Model!

Super cool seeing it in person after looking at many images of it

Spotting supermicros with the rack ear condoms still on

Average IP version

WHY ARE WE SHOUTING

Guy looks like Charlie from Smiling Friends

Good god, I need something to zap me when I attempt to book a pre 10AM flight from LHR