Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On 1/9/24 03:15, Thomas Schmitt wrote: Hi, Nicholas Geovanis wrote: You ruined my day :-) It was not my fault. Send complaints to the people who convened as "High Sierra Group" in 1986. Something similar to IBM's kludgiest relic of the early 1960s has appeared in linux? The unixoid commu

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

Bret Busby (12024-01-09): > Whilst, as I previously made the point, this is all off-topic for a Debian > operating system users mailing list, one (and, only one) of the applications > of version numbers as part of file descriptors, with (in the case of > VAX/VMS) up to the last seven versions of a

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

Hi, Bret Busby wrote: > Whilst, as I previously made the point, this is all off-topic for a Debian > operating system users mailing list But i found a premium excuse in the debian-cd and debian-live ISOs. :o) > the last seven versions of a file, being retained, was a > useful tool for software

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On 9/1/24 16:02, Thomas Schmitt wrote: Hi, Nicholas Geovanis wrote: The idea that we need version numbers embedded in filenames involuntarily may be "natural" to somebody. I have never seen any version other than ";1" (and ISOs which simply ignore the specs about file names). It's a non

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

Hi, Nicholas Geovanis wrote: > You ruined my day :-) It was not my fault. Send complaints to the people who convened as "High Sierra Group" in 1986. > Something similar to IBM's kludgiest relic of the early 1960s has appeared > in linux? The unixoid community added System Use Protocol and Rock

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On Mon, Jan 8, 2024, 11:38 AM Thomas Schmitt wrote: > Hi, > > Bret Busby wrote: > > > .; > > Jeremy Nicoll wrote: > > IBM's MVS & its successors, most recently z/OS, have something > > similar called a GDG (or Generation Data Group). > > The principle made it into ISO 9660 specifications. > > To

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On 8 Jan 2024, at 9:17, Bret Busby wrote: > But, apart from the functionality that I have not seen in any other operating > system, of using an extra file descriptor of version number, so the whole > filename would be something like > .; > (I am not sure whether that syntax is correct - I have n

Re: systemd-timesyncd

On 2024-01-07, Andrew M.A. Cater wrote: > >> Take care, stay warm, well, and unvaxed. >> ^^^ > > Gene - no partisan opinions, please, as per Code of Conduct? Nothing sucks like a VAX! > All best, as ever, > > Andy

Re: systemd-timesyncd

On 1/7/24 19:39, Nicholas Geovanis wrote: On Sun, Jan 7, 2024, 4:51 PM Charles Curley > wrote: On Sun, 7 Jan 2024 20:36:12 + "Andrew M.A. Cater" mailto:amaca...@einval.com>> wrote: > > Take care, stay warm, well, and unvaxed. > >   

Re: systemd-timesyncd

On 1/7/24 17:51, Charles Curley wrote: On Sun, 7 Jan 2024 20:36:12 + "Andrew M.A. Cater" wrote: Take care, stay warm, well, and unvaxed. ^^^ Gene - no partisan opinions, please, as per Code of Conduct? Oh, come on! Just because Gene doesn't like cer

Re: systemd-timesyncd

Is it supposed to be installed by the net-installer? There does not seem > to be any man pages other than the bog std stuff. When I found the > /etc/systemd/timesyncd I immediately asked the system for man timesyncd, > got this: > gene@coyote:/etc$ man timesyncd > No manual entry for timesyncd >

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

Hi, Bret Busby wrote: > > .; Jeremy Nicoll wrote: > IBM's MVS & its successors, most recently z/OS, have something > similar called a GDG (or Generation Data Group). The principle made it into ISO 9660 specifications. To make this thread relevant for Debian, let's assume that somebody asked abo

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On Mon, 8 Jan 2024, at 09:17, Bret Busby wrote: > But, apart from the functionality that I have not seen in any other > operating system, of using an extra file descriptor of version number, > so the whole filename would be something like > .; IBM's MVS & its successors, most recently z/OS, hav

Re: VAX emulation/simulation (was Re: systemd-timesyncd)

On 8/1/24 08:44, The Wanderer wrote: On 2024-01-07 at 19:20, Nicholas Geovanis wrote: On Sun, Jan 7, 2024, 4:51 PM Charles Curley wrote: On Sun, 7 Jan 2024 20:36:12 + "Andrew M.A. Cater" wrote: Gene - no partisan opinions, please, as per Code of Conduct? Oh, come on! Just because

Re: systemd-timesyncd

> Quit using Google search. Use DuckDuckGo. Use StartPage instead, aka ixquick.com -- System Information GTK 3.24.39 / GLib 2.78.3 Locale: en_US.UTF-8 (charset: UTF-8) Operating System: Linux 6.6.9-amd64 (x86_64)

Re: systemd-timesyncd

On Mon, 8 Jan 2024 10:02:25 +0700 Max Nikulin wrote: > Isn't it /etc/systemd/timesyncd.conf, not /etc/systemd/timesyncd? It > might be a reason why systemd-timesyncd did not follow configuration. It is indeed /etc/systemd/timesyncd.conf. However, there is also /etc/systemd/timesyncd.conf.d/, so

Re: systemd-timesyncd

On 08/01/2024 03:36, Andrew M.A. Cater wrote: On Sun, Jan 07, 2024 at 02:51:26PM -0500, gene heskett wrote: gene@coyote:/etc$ man timesyncd No manual entry for timesyncd What package contains the manpages for a bookworm amd64 install I expect to do anything I might want to do? apt install man

Re: systemd-timesyncd

On 08/01/2024 02:51, gene heskett wrote: When I found the /etc/systemd/timesyncd I immediately asked the system for man timesyncd, got this: gene@coyote:/etc$ man timesyncd No manual entry for timesyncd Isn't it /etc/systemd/timesyncd.conf, not /etc/systemd/timesyncd? It might be a reason why

VAX emulation/simulation (was Re: systemd-timesyncd)

On 2024-01-07 at 19:20, Nicholas Geovanis wrote: > On Sun, Jan 7, 2024, 4:51 PM Charles Curley > wrote: > >> On Sun, 7 Jan 2024 20:36:12 + >> >> "Andrew M.A. Cater" wrote: >>> Gene - no partisan opinions, please, as per Code of Conduct? >> >> Oh, come on! Just because Gene doesn't like cer

Re: systemd-timesyncd

On Sun, Jan 7, 2024, 4:51 PM Charles Curley wrote: > On Sun, 7 Jan 2024 20:36:12 + > "Andrew M.A. Cater" wrote: > > > > Take care, stay warm, well, and unvaxed. > > > ^^^ > > > > Gene - no partisan opinions, please, as per Code of Conduct? > > Oh, come on!

Re: systemd-timesyncd

On Sun, 7 Jan 2024 20:36:12 + "Andrew M.A. Cater" wrote: > > Take care, stay warm, well, and unvaxed. > > ^^^ > > Gene - no partisan opinions, please, as per Code of Conduct? Oh, come on! Just because Gene doesn't like certain ancient Digital Equipment

Re: systemd-timesyncd

Hi Gene, Am 07.01.2024 um 20:51 schrieb gene heskett: On 1/7/24 10:48, Max Nikulin wrote: ... systemd-timesyncd is a NTP-client, not a server. It is shipped with man pages and works out of the box (of course, if network is properly configured). Is it supposed to be installed by the net-inst

Re: systemd-timesyncd

On Sun, Jan 07, 2024 at 02:51:26PM -0500, gene heskett wrote: > On 1/7/24 10:48, Max Nikulin wrote: > > On 07/01/2024 02:17, gene heskett wrote: > > > Is it supposed to be installed by the net-installer? There does not seem to > be any man pages other than the bog std stuff. When I found the > /et

Re: systemd-timesyncd

On 1/7/24 11:24, John Hasler wrote: Gene writes: Lately, everytime I go anywhere near google or a gmail link I get attacked by a virus that calls itself norton antivirus. Delete all your Firefox caches and upgrade Firefox. That phishing malware has nothing to do with Google or Norton. You ac

Re: systemd-timesyncd

On 1/7/24 10:48, Max Nikulin wrote: On 07/01/2024 02:17, gene heskett wrote: If debian is going to supply systemd's timesyncd as a client, I expected a bookworm install to just work. It did not and without docs I have to pester the list, which has gotten me a bad rep because the lack of docs f

Re: systemd-timesyncd

Gene writes: > Lately, everytime I go anywhere near google or a gmail link I get > attacked by a virus that calls itself norton antivirus. Delete all your Firefox caches and upgrade Firefox. That phishing malware has nothing to do with Google or Norton. You acquired it by visiting an infected or