Hey Aug!

..but isn't yours,

$ ./_install/bin/busybox date -Ins
2026-01-19T03:31:42,219647248+00:00

..incorrect with the TZ offset?

Nope. It is bang on. All my machines sync their clocks to UTC. Doesn't everybody? Anyhow easy enough to convert. On my regular linux box;

$ TZ=PST8PDT date --date="2026-01-19T03:31:42,219647248+00:00" 2026-01-18T19:31:42,219647248-08:00

but then it screws up a proper sort ... not that it would matter any to me. What REALLY matters is that nanosecond output is doable today and, perhaps when I get my hands on a hardware clock that can resolve to a nanosecond, accurate to a nanosecond. I'll need to upgrade all the networking hardware to take advantage of it but by that time I'll probably want to do that anyhow.

I call it future compatibilty.

Дуже груви,
Maurice

-o -o o- o- -o -o -o -o o- -o o- -o
(\ (\ /) /) (\ (\ (\ (\ /) (\ /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... Gæð a wyrd swa hio scel.
Fate ever goes as it must.
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hej Maurice!

$ TZ=PST8PDT date --date="2026-01-19T03:31:42,219647248+00:00"

You forgot the formatting string at the end. The above should have been;

$ TZ=PST8PDT date --date="2026-01-19T03:31:42,219647248+00:00" +"%FT%T,%N%:z" 2026-01-18T19:31:42,219647248-08:00

Much better now. The above format matches busybox's output for the 'date -Ins' command.

Not that any of this matters any but this way we can at least pretend to care about compatibilty issues with XP. :::shudder:::

Het leven is goed,
Maurice

-o o- -o o- o- o- o- -o -o -o o- -o -o o- o- -o
(\ /) (\ /) /) /) /) (\ (\ (\ /) (\ (\ /) /) (\
^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
... I've got squirrels in my pants!
--- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint @ (2:280/464.113)