| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Maximus at UNIX |
BJ>> I believe there was something else at the time that also BJ>> drove the 2 second decision -- that was out of other fido BJ>> based sosftware implementations. WM> Two seconds is the limit of resolution in the FAT filesystem. WM> That's ultimately where it comes from. ml> and that only because the date/time stamp was taken ml> from the original, one message per file, format (ie: ml> *.msg)... the stamp in the message header can/could be ml> different than the one on the disk but that the same ml> structures were (apparently?) used, lead us down this ml> road... Ah.... Yes.... This is jogging some old bits out of my memory..... We will need to address this long term..... Using the Unix time standard would allow finear granularity, but will break when the 32 bit clock rolls over -- depending on how the rolling over of the epoch is handled in various flavors of Unix, Linux, etc. And, who is going to have 60+ year old messages to show the error? Any way.... Time to move on to another subject..... Take care..... Bob Jones, 1:343/41 --- Maximus/2 3.01* Origin: Top Hat 2 BBS (1:343/41) SEEN-BY: 633/267 270 @PATH: 343/41 10/345 106/1 2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.