00:07 <Piraty> the µlibc ABI warning is old news, yes? https://openwrt.org/docs/guide-user/additional-software/extroot_configuration#system_upgrade

00:21 <slh> Piraty: in practice, the situation with musl isn't that different - there have been a number of breaking ABI changes with musl already

00:22 <Piraty> like time_t?

00:23 <Piraty> are breaking changes published or even announced in advance?

00:40 <slh> like time_t, yes

05:10 <owrt-images-builds> Build [#53](https://buildbot.openwrt.org/images/#/builders/219/builds/53) of `master_ath79/generic` completed successfully.

07:31 <djfe> what would your thoughts be on OpenWrt switching to the TLD ".internal" once the ICANN signs this proposal?

07:32 <djfe> https://www.theregister.com/2024/01/29/icann_internal_tld/

07:32 <djfe> https://itp.cdn.icann.org/en/files/root-system/identification-tld-private-use-24-01-2024-en.pdf

07:32 <djfe> openwrt.internal instead of openwrt.lan

07:34 <quinq> “as the name implies, it's intended for internal use only”

07:34 <quinq> wat

07:34 <quinq> Then it doesn't have its place on external DNS

07:35 <quinq> Ahhh, I missed the first sentence of the article

07:36 <quinq> But why making it an ICANN TLD instead of adding it to DNS RFC as reserved

07:40 <slh> .internal is damned long (especially compared to .lan) - and why jump, after ICANN has just moved after over 20 years of ignorance (the alternative would be to defer the decision until there is a risk of conflict)

07:42 <slh> in theory, 'good' - but considering that ICANN has totally ignored over two decades of precedence (and remembering how .local has been redefined in the past) and how they picked a bad (=long) domain now...

07:49 <quinq> agreed

07:49 <quinq> .internal-not-to-be-exported-to-internet

07:50 <djfe> I don't think personal opinions should play into this. It's soon going to be decided and we can either follow the decision or decide against it. One thing might look better in the public eye.

07:56 <dhewg> you can already use .internal, nothing is stopping you. in fact I have with openwrt for a few years

07:57 <djfe> slh: I can see why you were offended and I won't be able to change your opinion. Still: thank you for your input :)

07:58 <djfe> dhewg: interesting point. My idea was to propose changing the TLD for all new OpenWRT installations (not the existing ones)

08:02 <dhewg> I'm not so sure you can ensure that distinction. If one has openwrt with just the default dnsmasq settings (so .lan), and openwrt default changes to .internal, followed by a sysupgrade -u, that would change an existing setup and probally break it

08:03 <dhewg> that probably won't hit many users, but the chances of breakage is more than 0

08:48 <f00b4r0> if it ain't broke, don't fix it.

09:00 <f00b4r0> nbd: I have a full mt7915 crash dump with debug enabled: http://sprunge.us/yGqQSN let me know if you need more

09:01 <f00b4r0> the device is still powered up

09:05 <f00b4r0> fwiw the crash seems to consistently occur after about 5d uptime (for this particular device at that location, at least)