1. Forum
  2. FidoNet
  3. LINUX

  • Most recent message

    From Scott Street@1:266/625 to All on Sat Jun 6 17:29:12 2026
    Seems I trigged a bug in my code with that last message. Which was meant
    for a completely different area.

    ... to err is human, to really louse things up; you need a computer.
    ---
    * Origin: -={ The Digital Post }=- (1:266/625.0)
  • From Maurice Kinal@1:153/7001.64222 to Scott Street on Sun Jun 7 00:34:06 2026
    Hey Scott!

    @MSGID: 1:266/625 6a2458e9f2b1d9e9

    A 64-bit nanosecond unixtime? If so you've convinced me to follow suit on my new experimental point. Also with the TZUTC kludge's handling of UTC.

    Welcome to the 21st century ... just shy of 26 years too late. Oh well, no time like the present eh?

    Life is good,
    Maurice

    -o o- -o o- -o o- -o o-
    (\ /) (\ /) (\ /) (\ /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Wea bið wundrum clibbor. Wolcnu scriðað.
    Sorrow is strangely clinging. Clouds glide on.
    --- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
    * Origin: One of us @ (1:153/7001.64222)
  • From Scott Street@1:266/625 to Maurice Kinal on Sun Jun 7 12:28:02 2026
    @MSGID: 1:266/625 6a2458e9f2b1d9e9

    A 64-bit nanosecond unixtime? If so you've convinced me to follow
    suit on my new experimental point.


    Well, not exactly; two values where computed and squished together, it really is: (unix time 32b)6a2458e9 (msg CRC32)f2b1d9e9

    Though, it appears I read the spec and missed the fact that the serialno is only supposed to be 8 characters (which means 32b in hex). So I've got to rethink the MSGID generation.

    Welcome to the 21st century ... just shy of 26 years too late. Oh
    well, no time like the present eh?

    We've got a few years before the unsigned 32 int runs out of space for the current time. JAM uses a uint32_t for time. It needs to be a uint64_t soon, before Feb 7, 2106. One of the things on my back burner is to upgrade JAM's format for uint64 dates. I'm on the fence about making the storage pointers 64b, the 32b ones will still address 4Gb in a file and 4.2 million messages in a given message base. (64b file index could address 18billion terabytes -- which, according to Google, is more storage on all the planet.)

    ---
    * Origin: <=-[ The Digital Post ]-=> (1:266/625)
  • From Maurice Kinal@1:153/7001 to Scott Street on Sun Jun 7 21:07:35 2026
    Hey Scott!

    it really is: (unix time 32b)6a2458e9 (msg CRC32)f2b1d9e9

    Ah! I was thinking the last 8 characters were strftime's %N output, which for all time is restricted to 000000000-3b9ac9ff, which puts f2b1d9e9 way out of range. I should have checked more closely before guessing nanoseconds.

    I've got to rethink the MSGID generation.

    I am sticking with unixtime. However in my case I don't restrict to 8 characters so in 2106 it will automagically tack on an extra hex charater (nibble) which will be good until "Sun Aug 20 07:32:15 UTC 4147" before it tacks on another nibble bringing the total to 10 hex characters. I am not married to the nanosecond part but it does make an excellent method to ensure uniqueness for all time.

    I'm on the fence about making the storage pointers 64b

    Agreed. I prefer the method that doesn't limit the output to 8 and use unixtime. Only have to wait until "Sun Feb 7 06:28:16 UTC 2106" before it switches to 9 characters (36b). I can hardly wait. ;-)

    Life is good,
    Maurice

    -o o- o- o- o- o- o- -o -o o- -o o-
    (\ /) /) /) /) /) /) (\ (\ /) (\ /)
    ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^ ^^
    ... Ne nanwuht ne byð yfel, ær mon wene þæt it yfel seo.
    Nothing is misery unless one thinks it is misery.
    --- GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Benny Pedersen@2:230/0 to Scott Street on Mon Jun 8 08:46:44 2026
    Hello Scott!

    06 Jun 2026 17:29, Scott Street wrote to All:

    Seems I trigged a bug in my code with that last message. Which was
    meant for a completely different area.

    +1

    ... to err is human, to really louse things up; you need a computer.

    you proved it :)


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/7.0.11-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Sean Dennis@1:18/200 to Scott Street on Tue Jun 9 19:58:01 2026
    Scott Street wrote to All <=-

    Seems I trigged a bug in my code with that last message. Which was
    meant for a completely different area.

    It's not a bug, it's an unintended feature!

    -- Sean

    ... Morfy's law: enythink thit ken go rong willl.

    --- MultiMail/Linux
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)