Michael Stone composed on 2018-05-21 10:05 (UTC-0400): > On Mon, May 21, 2018 at 09:55:42AM -0400, Felix Miata wrote:
>>OS/2 and DOS AFAICT never got that option. A LAN that is a mix of LOCAL and >>UTC >>isn't fun, especially with one or more that can't not, which is what I have >>with >>a Linux STB providing no LOCAL option and multiple OS/2's providing no UTC >>option. > I'm afraid I don't understand how things like old standalone boxes > impact what makes sense going forward. You do understand that there's no > relationship between the RTC clock and the displayed time? (That is, you > can set the RTC to UTC and still interact with the system in local > time.) Typically, I record on a STB that has no support for /etc/adjtime or /etc/localtime and see via FTP login the new recording's timestamp is tomorrow until I wait several hours, and then see it was "recorded" hours after the program guide and my clock said it aired. I live in today, not tomorrow, and have no interest in clock time outside an hour or two's drive from home. Different timestamps across the LAN interfere with evaluation which files of same name are the newer when choosing, copying, backing up or restoring. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
