REPLY: 2:460/256 0000064a   
   MSGID: 1:153/7001 6970403a   
   CHRS: UTF-8 4   
   Hey Aug!   
      
   > ..but isn't yours,   
   >   
   > MK> $ ./_install/bin/busybox date -Ins   
   >  MK> 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)   
   SEEN-BY: 50/22 103/705 105/81 106/201 124/5016 128/187 129/14 134/100   
   SEEN-BY: 153/135 143 148 151 153 757 7001 7715 154/10 30 110 203/0   
   SEEN-BY: 218/700 221/0 6 226/30 227/114 229/110 112 134 206 300 317   
   SEEN-BY: 229/400 426 428 470 664 700 705 240/1120 5832 263/1 266/512   
   SEEN-BY: 280/464 5003 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 460/58 256 1124 5858 633/280 712/848   
   SEEN-BY: 770/1 902/26 3634/12 5020/400 8912 5054/30 5075/35   
   PATH: 153/7001 757 280/464 460/58 229/426