Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264851 > unrolled thread
| Started by | Albretch Mueller <lbrtchx@gmail.com> |
|---|---|
| First post | 2023-12-17 11:20 +0100 |
| Last post | 2023-12-17 15:10 +0100 |
| Articles | 20 on this page of 166 — 34 participants |
Back to article view | Back to linux.debian.user
difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 11:20 +0100
Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-17 12:00 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 12:10 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 16:30 +0100
Re: difference in seconds between two formatted dates ... "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-17 17:00 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 17:10 +0100
Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-17 17:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 23:50 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 00:10 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 01:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 02:20 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 07:00 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 07:10 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 13:20 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-18 14:10 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 14:20 +0100
date can't parse its own output was: difference in seconds between two formatted dates ...) <tomas@tuxteam.de> - 2023-12-18 14:40 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 19:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 20:20 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-20 07:10 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 08:40 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-21 06:00 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-21 06:40 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 02:30 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 13:20 +0100
RTC and (old) Windows [was: difference in seconds between two formatted dates ...] <tomas@tuxteam.de> - 2023-12-21 13:30 +0100
Re: RTC and (old) Windows [was: difference in seconds between two formatted dates ...] David Christensen <dpchrist@holgerdanske.com> - 2023-12-21 23:30 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 02:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-22 04:10 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-20 08:50 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-20 13:20 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 13:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-20 14:20 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 14:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-20 16:10 +0100
Re: difference in seconds between two formatted dates ... Nicolas George <george@nsup.org> - 2023-12-20 16:30 +0100
systemd and timezone (was: Re: difference in seconds between two formatted dates ...) Max Nikulin <manikulin@gmail.com> - 2023-12-21 04:50 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) <tomas@tuxteam.de> - 2023-12-21 07:00 +0100
Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-21 17:10 +0100
Re: systemd and timezone Nicholas Geovanis <nickgeovanis@gmail.com> - 2023-12-22 02:00 +0100
Re: systemd and timezone Andy Smith <andy@strugglers.net> - 2023-12-22 13:50 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) Jeffrey Walton <noloader@gmail.com> - 2023-12-21 17:30 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) tomas@tuxteam.de - 2023-12-21 18:40 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) Dan Ritter <dsr@randomstring.org> - 2023-12-21 15:30 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) <tomas@tuxteam.de> - 2023-12-21 16:10 +0100
Re: systemd and timezone (was: Re: difference in seconds between two formatted dates ...) Nicolas George <george@nsup.org> - 2023-12-21 23:00 +0100
Re: systemd and timezone gene heskett <gheskett@shentel.net> - 2023-12-22 01:00 +0100
Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-22 13:50 +0100
Re: systemd and timezone <tomas@tuxteam.de> - 2023-12-22 14:40 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 15:20 +0100
Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 16:50 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 17:30 +0100
Re: systemd and timezone "Arno Lehmann, ITS" <al@its-lehmann.de> - 2023-12-22 20:20 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 21:00 +0100
Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 20:50 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 21:20 +0100
Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 07:20 +0100
Re: systemd and timezone Sven Joachim <svenjoac@gmx.de> - 2023-12-22 21:20 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 22:40 +0100
Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 00:30 +0100
Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 00:50 +0100
Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 01:10 +0100
Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 07:20 +0100
Re: Support for SysV service scripts deprecated in systemd 255 (was: systemd and timezone) Felix Miata <mrmazda@earthlink.net> - 2023-12-23 08:10 +0100
Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 12:10 +0100
Re: systemd and timezone Nate Bargmann <n0nb@n0nb.us> - 2023-12-23 02:00 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-23 02:20 +0100
Re: systemd and timezone <tomas@tuxteam.de> - 2023-12-22 17:10 +0100
Re: systemd and timezone Jeffrey Walton <noloader@gmail.com> - 2023-12-22 21:00 +0100
Re: systemd and timezone Nicolas George <george@nsup.org> - 2023-12-22 23:40 +0100
Re: systemd and timezone Charles Kroeger <mbone@gmx.co.uk> - 2024-01-06 03:30 +0100
Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2024-01-06 05:30 +0100
Re: systemd and timezone gene heskett <gheskett@shentel.net> - 2024-01-06 06:40 +0100
tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 07:20 +0100
Re: tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 08:10 +0100
Re: tzdata-legacy [was: Re: systemd and timezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-06 10:20 +0100
Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 13:10 +0100
Re: tzdata-legacy [was: Re: systemd and timezone] Greg Wooledge <greg@wooledge.org> - 2024-01-06 16:10 +0100
Re: tzdata-legacy [was: Re: systemd and timezone] David Wright <deblis@lionunicorn.co.uk> - 2024-01-07 18:30 +0100
was: Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 13:00 +0100
Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] John Hasler <john@sugarbit.com> - 2024-01-06 15:30 +0100
SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 20:10 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] John Hasler <john@sugarbit.com> - 2024-01-06 20:40 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 21:40 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-06 23:10 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] Greg Wooledge <greg@wooledge.org> - 2024-01-07 01:10 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdandtimezone] gene heskett <gheskett@shentel.net> - 2024-01-07 05:30 +0100
Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdandtimezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-07 12:30 +0100
Re: SOLVED FOR GENE Felix Miata <mrmazda@earthlink.net> - 2024-01-07 12:40 +0100
Re: SOLVED FOR GENE jeremy ardley <jeremy.ardley@gmail.com> - 2024-01-07 13:10 +0100
Re: SOLVED FOR GENE john doe <johndoe65534@mail.com> - 2024-01-07 13:40 +0100
Re: SOLVED FOR GENE Michael Stone <mstone@debian.org> - 2024-01-11 14:30 +0100
Re: SOLVED FOR GENE Felix Miata <mrmazda@earthlink.net> - 2024-01-11 18:10 +0100
manpages package [WAS Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] "Andrew M.A. Cater" <amacater@einval.com> - 2024-01-06 23:50 +0100
Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 18:10 +0100
Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 20:40 +0100
systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-07 16:50 +0100
Re: systemd-timesyncd John Hasler <john@sugarbit.com> - 2024-01-07 17:30 +0100
Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-07 21:20 +0100
Re: systemd-timesyncd Charles Kroeger <mbone@gmx.co.uk> - 2024-01-08 06:50 +0100
Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-07 21:10 +0100
Re: systemd-timesyncd "Andrew M.A. Cater" <amacater@einval.com> - 2024-01-07 22:00 +0100
Re: systemd-timesyncd Charles Curley <charlescurley@charlescurley.com> - 2024-01-08 00:00 +0100
Re: systemd-timesyncd Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-08 01:40 +0100
VAX emulation/simulation (was Re: systemd-timesyncd) The Wanderer <wanderer@fastmail.fm> - 2024-01-08 02:10 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) Bret Busby <bret@busby.net> - 2024-01-08 10:40 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Jeremy Nicoll" <jn.ml.dbi.73@letterboxes.org> - 2024-01-08 11:40 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-08 13:20 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-09 01:00 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-09 09:20 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) Bret Busby <bret@busby.net> - 2024-01-09 10:40 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-09 11:20 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) Nicolas George <george@nsup.org> - 2024-01-09 11:40 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) gene heskett <gheskett@shentel.net> - 2024-01-09 12:30 +0100
Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Niall O'Reilly" <niall+lists@no8.be> - 2024-01-08 21:50 +0100
Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-08 16:00 +0100
Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-08 16:00 +0100
Re: systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-08 04:40 +0100
Re: systemd-timesyncd Curt <curty@free.fr> - 2024-01-08 18:00 +0100
Re: systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-08 04:20 +0100
Re: systemd-timesyncd Charles Curley <charlescurley@charlescurley.com> - 2024-01-08 05:10 +0100
Re: systemd-timesyncd Mark Fletcher <mark27q1@gmail.com> - 2024-01-08 14:50 +0100
mktime (was: Re: systemd and timezone) Max Nikulin <manikulin@gmail.com> - 2023-12-23 18:00 +0100
Re: mktime (was: Re: systemd and timezone) Jeffrey Walton <noloader@gmail.com> - 2023-12-23 19:30 +0100
Re: mktime Max Nikulin <manikulin@gmail.com> - 2023-12-24 03:40 +0100
Re: mktime (was: Re: systemd and timezone) <tomas@tuxteam.de> - 2023-12-24 08:40 +0100
Re: mktime Max Nikulin <manikulin@gmail.com> - 2023-12-28 03:40 +0100
Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-21 16:30 +0100
Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-22 03:20 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-22 08:00 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-21 05:40 +0100
Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-21 06:50 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-21 07:10 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-21 08:10 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 13:40 +0100
Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-21 16:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 19:30 +0100
Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-21 21:00 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 21:10 +0100
Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-21 21:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 22:40 +0100
Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-22 00:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 16:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-25 18:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 08:00 +0100
Re: difference in seconds between two formatted dates ... "Thomas Schmitt" <scdbackup@gmx.net> - 2023-12-26 08:30 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 16:00 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-26 16:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 19:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-26 22:40 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-27 01:40 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-27 01:50 +0100
When strace breaks process or is blocked (was: Re: difference in seconds between two formatted dates ...) Max Nikulin <manikulin@gmail.com> - 2023-12-27 17:50 +0100
Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-18 03:30 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 00:10 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-25 01:10 +0100
Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 01:30 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-25 02:20 +0100
Re: difference in seconds between two formatted dates ... "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-25 11:40 +0100
Re: difference in seconds between two formatted dates ... Tixy <tixy@yxit.co.uk> - 2023-12-25 09:10 +0100
Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-27 00:00 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-17 19:00 +0100
Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-17 19:30 +0100
Re: difference in seconds between two formatted dates ... Teemu Likonen <tlikonen@iki.fi> - 2023-12-17 12:50 +0100
Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 12:10 +0100
Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-17 15:10 +0100
Page 6 of 9 — ← Prev page 1 2 3 4 5 [6] 7 8 9 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-07 21:10 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTHD3-1vTz-3@gated-at.bofh.it> |
| In reply to | #265610 |
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 for this stuff has me in a screw google frame of mind by >> the time I get around to asking the list. Lately, everytime I go >> anywhere near google or a gmail link I get attacked by a virus that >> calls itself norton antivirus. That is an oxymoron, like military >> intelligence. > > I have no idea what malware you have on your machines. > > 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-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 So one of the first things I did, after getting an orca-less install ( that took about 26 installs before someone said I had to unplug ALL my usb stuff which other than keyboard/mouse buttons I did leave plugged in because the only other stuff I had here was ps2 based, finally getting an orca-less install, all the other installs were because bookworm with orca removed by removing the exec bits of the executables because apt wouldn't purge it, will not reboot without them forcing a reinstall any time I had to reboot) and getting t-bird setup so I could do email was to install ntpsec, which can be a server. and worked as a client OOTB. Even if timesyncd might have worked, its not a server as you note. But if there are man pages on timesyncd, that is not what they are named. Now I decide to use this ntpsec install as a server to the rest of my systems here, thereby unloading the debian pool a bit, and the lack of docs bytes me again. I'm playing the 10,000 monkeys re-writing Shakespear scene here and catching it for not using google, and got the help I needed from John's post to look at manpages.org. And that seems to have started another endless thread I'll get blamed for. My lack of man pages has been asked, and ignored before, so I'll ask again: What package contains the manpages for a bookworm amd64 install I expect to do anything I might want to do? Take care, stay warm, well, and unvaxed. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2024-01-07 22:00 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTIpr-1w9s-5@gated-at.bofh.it> |
| In reply to | #265627 |
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 > /etc/systemd/timesyncd I immediately asked the system for man timesyncd, got > this: > 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 manpages (as noted in a message above earlier in the thread). > Take care, stay warm, well, and unvaxed. > ^^^^^^^^^^^ Gene - no partisan opinions, please, as per Code of Conduct? All best, as ever, Andy > Cheers, Gene Heskett. > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis >
[toc] | [prev] | [next] | [standalone]
| From | Charles Curley <charlescurley@charlescurley.com> |
|---|---|
| Date | 2024-01-08 00:00 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTKhz-1xgW-3@gated-at.bofh.it> |
| In reply to | #265629 |
On Sun, 7 Jan 2024 20:36:12 +0000 "Andrew M.A. Cater" <amacater@einval.com> 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 products…? -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
[toc] | [prev] | [next] | [standalone]
| From | Nicholas Geovanis <nickgeovanis@gmail.com> |
|---|---|
| Date | 2024-01-08 01:40 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTLQm-1yiN-7@gated-at.bofh.it> |
| In reply to | #265631 |
[Multipart message — attachments visible in raw view] — view raw
On Sun, Jan 7, 2024, 4:51 PM Charles Curley <charlescurley@charlescurley.com> wrote: > On Sun, 7 Jan 2024 20:36:12 +0000 > "Andrew M.A. Cater" <amacater@einval.com> 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 products…? > Come on.... There has to be a linux-based VAX simulator somewhere out there for Gene :-D So he can practice getting VAXed... :-D ....said the man who used to use LSI-11's :-D -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > >
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2024-01-08 02:10 +0100 |
| Subject | VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HTMjn-1yHg-1@gated-at.bofh.it> |
| In reply to | #265634 |
[Multipart message — attachments visible in raw view] — view raw
On 2024-01-07 at 19:20, Nicholas Geovanis wrote: > On Sun, Jan 7, 2024, 4:51 PM Charles Curley <charlescurley@charlescurley.com> > wrote: > >> On Sun, 7 Jan 2024 20:36:12 +0000 >> >> "Andrew M.A. Cater" <amacater@einval.com> wrote: >>> Gene - no partisan opinions, please, as per Code of Conduct? >> >> Oh, come on! Just because Gene doesn't like certain ancient Digital >> Equipment products…? >> > > Come on.... There has to be a linux-based VAX simulator somewhere out there > for Gene :-D > So he can practice getting VAXed... :-D > ....said the man who used to use LSI-11's :-D $ apt-cache show simh Package: simh [...] Description-en: Emulators for 33 different computers This is the SIMH set of emulators for 33 different computers: [...] DEC VAX (but cannot include the microcode due to copyright) No idea whether it'd be enough, but if anyone does actually want to pursue the idea, it might be worth looking at. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Bret Busby <bret@busby.net> |
|---|---|
| Date | 2024-01-08 10:40 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HTUgW-1E48-7@gated-at.bofh.it> |
| In reply to | #265635 |
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 <charlescurley@charlescurley.com> >> wrote: >> >>> On Sun, 7 Jan 2024 20:36:12 +0000 >>> >>> "Andrew M.A. Cater" <amacater@einval.com> wrote: > >>>> Gene - no partisan opinions, please, as per Code of Conduct? >>> >>> Oh, come on! Just because Gene doesn't like certain ancient Digital >>> Equipment products…? >>> >> >> Come on.... There has to be a linux-based VAX simulator somewhere out there >> for Gene :-D >> So he can practice getting VAXed... :-D >> ....said the man who used to use LSI-11's :-D > > $ apt-cache show simh > Package: simh > [...] > Description-en: Emulators for 33 different computers > This is the SIMH set of emulators for 33 different computers: > [...] > DEC VAX (but cannot include the microcode due to copyright) > > > No idea whether it'd be enough, but if anyone does actually want to > pursue the idea, it might be worth looking at. > If anyone really wants to run VAX/VMS, or, another version of VMS, then you should read the article at https://www.theregister.com/2022/08/03/linux_may_soon_lose_support/ which has applicable links. 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 <filename>.<extension>;<version number> (I am not sure whether that syntax is correct - I have not used VAX/VMS, for about 35-40 years) retaining (from memory) up to the last seven versions of a file, really, why bother? In these times (and, even back then, when UNIX system V was the main UNIX system that was commercially used, and, even when BSD 4.2 was the main UNIX version), a decent systems level "C" programmer should be able to write a utility to do it. When I was being taught VAX-FORTRAN (which, from memory, was enhanced FORTRAN-77, the last FORTRAN before FORTRAN-90, with FORTRAN-90 introducing pointers to FORTRAN) and "C", and I remarked that VAX-FORTRAN had 8-byte precision, that "C" did not, the "C" lecturer simply said that a "C" programmer could create the data type, and write the maths libraries, to deal with it. So, running VAX/VMS, or a version of the VMS operating system, is a bit like running XENIX or MINIX, or, like a friend of that time, who had an operational PDP on his flat (apartment) balcony, that he had obtained an kept for playing with octal programming. It would, I expect6, be done for no other reason, than the sake of doing it. But, all of that, and, the subject and thread of this message thread, are completely off-topic, for a Debian operating system mailing list, I think. .... Bret Busby Armadale Western Australia (UTC+0800) .................
[toc] | [prev] | [next] | [standalone]
| From | "Jeremy Nicoll" <jn.ml.dbi.73@letterboxes.org> |
|---|---|
| Date | 2024-01-08 11:40 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HTVcZ-1EC0-1@gated-at.bofh.it> |
| In reply to | #265645 |
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
> <filename>.<extension>;<version number>
IBM's MVS & its successors, most recently z/OS, have something
similar called a GDG (or Generation Data Group).
It's handed via system catalogs - which are the indexes which tell
you where specific files are. Dataset names do not contain disk
(or tape, or virtual tape) names and don't have the sort of
hierarchical names relating to a root & mount point like most
files in Linux.
For a lot of files the catalogs say which disk a file is currently on
& the disk's "VTOC" - volume table of contents - says where on
the disk that file is.
Anyway if one defines eg
DEFINE GENERATIONDATAGROUP -
(NAME(PQR.TEST.THIS) LIMIT(8) SCRATCH NOEMPTY)
then the system will maintain 8 separate copies of a file
named "PQR.TEST.THIS".
You can refer to the newest created one as PQR.TEST.THIS(0)
or the next oldest by PQR.TEST.THIS(-1) or its ancestor by
PQR.TEST.THIS(-2) etc. You can refer to the whole lot (so
eg to read all the contents of as many of these files as
happen to exist at some point in time) simply by leaving
the (n) part off the name.
To create a new file you refer to PQR.TEST.THIS(+1); after
you finish using the file the system throws away the very
oldest one & rejigs its index of them all so this latest one
is now able to be referred to via (0) - and the specific
files previously referred to by -1, -2, -3 etc all shift up by
one.
For the whole duration of the process that creates a new
generation of such a file, the index of subsidiary versions
is locked so that no other process can simultaneously
create new ones or delete any of them (ie not just delete
the one about to be the oldest, no longer required one).
The files are typically used for storing chunks of
continuously occurring data, eg transactions or logs. You
might start each business day with no files in such a GDG
then accumulate any number of successive tranches of some
sort of transaction data in them, then - perhaps at the end
of day process the whole lot into one "daily" file & reset
the GDG ready for the next day's processing. You might
then have a set of daily GDGs which get merged into
weekly files, monthly ones etc.
You can also find out the internal name by which a
specific generation of the file is named & refer to it
directly, eg PQR.TEST.THIS.G00
- thus meaning one doesn't have to know such a file's
relationship to the successive generation structure.
Back in the 1990s when I last used these there could be
up to 255 or so files in each GDG. That limit might have
increased since then.
Ref: https://www.ibm.com/docs/en/zos/2.2.0?topic=files-processing-generation-data-groups
--
Jeremy Nicoll - my opinions are my own.
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-08 13:20 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HTWLL-1FCa-1@gated-at.bofh.it> |
| In reply to | #265646 |
Hi, Bret Busby wrote: > > <filename>.<extension>;<version number> 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 about the peculiar filenames in the netinst ISO when mounting its plain ISO 9660 personality: $ sudo mount -o norock,nojoliet,map=off debian-12.2.0-amd64-netinst.iso /mnt/iso mount: /dev/loop0 is write-protected, mounting read-only $ find /mnt/iso /mnt/iso /mnt/iso/BOOT /mnt/iso/BOOT/GRUB /mnt/iso/BOOT/GRUB/EFI.IMG;1 /mnt/iso/BOOT/GRUB/FONT.PF2;1 ... /mnt/iso/_DISK/MKISOFS.;1 /mnt/iso/_DISK/UDEB_INC.;1 Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | Nicholas Geovanis <nickgeovanis@gmail.com> |
|---|---|
| Date | 2024-01-09 01:00 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HU7Hb-1M1x-1@gated-at.bofh.it> |
| In reply to | #265651 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Jan 8, 2024, 11:38 AM Thomas Schmitt <scdbackup@gmx.net> wrote: > Hi, > > Bret Busby wrote: > > > <filename>.<extension>;<version number> > > 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 about the peculiar filenames in the netinst ISO when mounting > its plain ISO 9660 personality: > > $ sudo mount -o norock,nojoliet,map=off debian-12.2.0-amd64-netinst.iso > /mnt/iso > mount: /dev/loop0 is write-protected, mounting read-only > $ find /mnt/iso > /mnt/iso > /mnt/iso/BOOT > /mnt/iso/BOOT/GRUB > /mnt/iso/BOOT/GRUB/EFI.IMG;1 > /mnt/iso/BOOT/GRUB/FONT.PF2;1 > ... > /mnt/iso/_DISK/MKISOFS.;1 > /mnt/iso/_DISK/UDEB_INC.;1 > > > Have a nice day :) > You ruined my day :-) Something similar to IBM's kludgiest relic of the early 1960s has appeared in linux? The idea that we need version numbers embedded in filenames involuntarily may be "natural" to somebody. But just seems sloppy to me. And I've been an IBM mainframe admin and developer too. Thomas > >
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-09 09:20 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HUfv4-1RdO-21@gated-at.bofh.it> |
| In reply to | #265681 |
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 Ridge Interchange Protocol in the early 1990s in order to get X/Open functionality on top of ISO 9660. That's POSIX with long file names (up to 255 bytes) and paths (up to 1024 bytes) where only 0-byte and '/' have special meanings. A company Who Must Not Be Named introduced Joliet to store names of up to 64 characters in a 16 bit character set (while still ignoring the difference between uppercase and lowercase). Linux mount(8) introduced a character mapping from the uppercase character set of ISO 9660 to lowercase. This mapping also removes the version part of the file names. > 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-functional relic, which in Linux can only be uncovered if you suppress Rock Ridge, Joliet, and name mapping during the mount command. > And I've been an IBM mainframe admin and developer too. In the times when a full scale mainframe came with a female discus thrower ? http://www.ibmsystem3.nl/5444/images/5444DISK.jpg Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | Bret Busby <bret@busby.net> |
|---|---|
| Date | 2024-01-09 10:40 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HUgKu-1RUc-5@gated-at.bofh.it> |
| In reply to | #265696 |
On 9/1/24 16:02, Thomas Schmitt wrote: > Hi, > > Nicholas Geovanis wrote: <snip> > >> 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-functional relic, which > in Linux can only be uncovered if you suppress Rock Ridge, Joliet, and > name mapping during the mount command. > > >> And I've been an IBM mainframe admin and developer too. > 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 file, being retained, was a useful tool for software developers, but, responsible software development, and, especially, the teaching of responsible software development, have been abandoned, over the last decades. And, that, in itself, is a good example where reverting to a previous version, would be good. .... Bret Busby Armadale Western Australia (UTC+0800) .................
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-09 11:20 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HUhnb-1Sn8-1@gated-at.bofh.it> |
| In reply to | #265699 |
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 developers, but, responsible software development, > and, especially, the teaching of responsible software development, have been > abandoned, over the last decades. This has obviously been replaced by Source Code Control System, which now has its final successor under the name Git. (A coarse substitute are frequently taken incremental backups.) Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2024-01-09 11:40 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HUhGx-1Stx-11@gated-at.bofh.it> |
| In reply to | #265699 |
[Multipart message — attachments visible in raw view] — view raw
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 file, being retained, was a > useful tool for software developers, but, responsible software development, > and, especially, the teaching of responsible software development, have been > abandoned, over the last decades. Could it that “responsible software development” have not been abandoned, like old geezers like to pretend, but rather has moved to using solutions that do not suffer the ugly limitations of implementations in the kernel? Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-09 12:30 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HUisV-1SZs-3@gated-at.bofh.it> |
| In reply to | #265696 |
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 community added System Use Protocol and Rock Ridge Interchange > Protocol in the early 1990s in order to get X/Open functionality on top > of ISO 9660. That's POSIX with long file names (up to 255 bytes) and > paths (up to 1024 bytes) where only 0-byte and '/' have special meanings. > > A company Who Must Not Be Named introduced Joliet to store names of up > to 64 characters in a 16 bit character set (while still ignoring the > difference between uppercase and lowercase). > > Linux mount(8) introduced a character mapping from the uppercase character > set of ISO 9660 to lowercase. This mapping also removes the version part > of the file names. > > >> 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-functional relic, which > in Linux can only be uncovered if you suppress Rock Ridge, Joliet, and > name mapping during the mount command. > > >> And I've been an IBM mainframe admin and developer too. > > In the times when a full scale mainframe came with a female discus > thrower ? > http://www.ibmsystem3.nl/5444/images/5444DISK.jpg Ohmy$DIETY! A trip down memory lane. I recall those things, absolute pieces of junk, needed daily 4 hour calibration TLC to make them work for a couple hours. In a TI mainframe, circa 1978, these were made by dynex. I do NOT remember them fondly. 5 megabyte capacity. IBM's 8" floppies in the system 360 were thousands of times more dependable by 1985. In those times, my office trs-80 Color Computer had more memory than the 360, and with os9 level 2, a mini-unix, was faster than the 360. > > Have a nice day :) You too! > > Thomas > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | "Niall O'Reilly" <niall+lists@no8.be> |
|---|---|
| Date | 2024-01-08 21:50 +0100 |
| Subject | Re: VAX emulation/simulation (was Re: systemd-timesyncd) |
| Message-ID | <HU4Jj-1KeQ-5@gated-at.bofh.it> |
| In reply to | #265645 |
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 > <filename>.<extension>;<version number> > (I am not sure whether that syntax is correct - I have not used VAX/VMS, for about 35-40 years) > retaining (from memory) up to the last seven versions of a file, really, why bother? It was also a feature (with slightly different syntax) of DEC's TOPS-20, before VAX/VMS was released. I don't recall what the limit on retained versions was. ... Niall
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-08 16:00 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTZgB-1GVL-1@gated-at.bofh.it> |
| In reply to | #265634 |
On 1/7/24 19:39, Nicholas Geovanis wrote: > On Sun, Jan 7, 2024, 4:51 PM Charles Curley > <charlescurley@charlescurley.com > <mailto:charlescurley@charlescurley.com>> wrote: > > On Sun, 7 Jan 2024 20:36:12 +0000 > "Andrew M.A. Cater" <amacater@einval.com > <mailto:amacater@einval.com>> 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 products…? > > > Come on.... There has to be a linux-based VAX simulator somewhere out > there for Gene :-D > So he can practice getting VAXed... :-D > ....said the man who used to use LSI-11's :-D Glutton for punishment I take it? > > -- > Does anybody read signatures any more? > > https://charlescurley.com <https://charlescurley.com> > https://charlescurley.com/blog/ <https://charlescurley.com/blog/> > Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-08 16:00 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTZgB-1GVL-5@gated-at.bofh.it> |
| In reply to | #265631 |
On 1/7/24 17:51, Charles Curley wrote: > On Sun, 7 Jan 2024 20:36:12 +0000 > "Andrew M.A. Cater" <amacater@einval.com> 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 products…? > Chuckle. That however, does bring back the memories of the PDP-11/23a that was supplied by Sci-Atl and CBS to control a 7 meter C-band satellite dish, to say it was unstable was the understatement of the century. But it came with a maintenance contract so I let the field engineers from DE, worry about it, but everytime it crashed, we lost several thou, because we were selling toothpaste instead of dog food, and CBS didn't pay us for those mistakes. I grew increasing frustrated with DE because in the end, they changed every component in that machine but the frame rail with the seriel number. The computer guy in NYC CBS HQ finally traded me his test mule figuring he could fix it so we updated DE's seriel number list and traded machines. But, he couldn't fix it either, so he then had no test mule to check other stations boards and software updates. Then it snowballed from there with CBS finally forced to replace every pdp11-23a at their affiliate sites, with an I've Been Moved, industrial version pc, and an artic real time interface card as a control interface. His pdp11-23a Just Worked, as did the IBM. That of course had a very visible positive effect on our P&L reports. So yeah, you could say I did not have any great faith in DEC. Early on but after the warranty on it expired, it used a DEC VT220 for local admin stuff. Nothing fancy but when I called DEC looking for a HOT for it, was not available but they did have a vt550 they wanted nearly 6 grand for, and would not guarantee it would work. CBS could call it up on the phone so they did for about 10 days while I reworked a vt100 clone that ran on os9, the nix clone for a trs-80 color computer 3, making a 100% compatible vt220 out of it. That worked until the IBM came in. So here is a guy named Gene, that has never owned a "PC" cuz I was doing things a pc couldn't, on a color computer, switching to the Amiga in the 90's, and built my first linux machine, installing RH5.0 on it in 1998. Built lots of other machines starting with an RCA 1802, but never a VAX. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-08 04:40 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTOEx-1A1c-3@gated-at.bofh.it> |
| In reply to | #265629 |
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 manpages (as noted in a message above earlier in the thread). Just to avoid possible confusion. Installing of the manpages package will not make man pages for all debian packages available locally. E.g. systemd-timesyncd(8) is shipped in the systemd-timesyncd package. It is great that https://manpages.debian.org exists and allows to read docs before installing a package.
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2024-01-08 18:00 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HU18J-1I2L-1@gated-at.bofh.it> |
| In reply to | #265629 |
On 2024-01-07, Andrew M.A. Cater <amacater@einval.com> 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
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-08 04:20 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTOlb-1zUn-9@gated-at.bofh.it> |
| In reply to | #265627 |
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 systemd-timesyncd did not follow configuration.
Did looked into this file? On Debian 12 bookworm it contains (I have no
idea concerning modification by Chinese 3d printers manufacturers on the
top of Debian-derivatives):
# See timesyncd.conf(5) for details.
I do not see any problem with the /etc/systemd/timesyncd.conf file
documented in "man timesyncd.conf".
Besides appropos(1) (or "man -k") and "systemctl help" already mentioned
in this thread, there are another ways
dpkg -S /etc/systemd/timesyncd.conf
systemd-timesyncd: /etc/systemd/timesyncd.conf
dpkg -L systemd-timesyncd | grep /man/
/usr/share/man/man5
/usr/share/man/man5/timesyncd.conf.5.gz
/usr/share/man/man8
/usr/share/man/man8/systemd-timesyncd.service.8.gz
/usr/share/man/man5/timesyncd.conf.d.5.gz
/usr/share/man/man8/systemd-timesyncd.8.gz
These tools do not rely on remote content and should work even if a
twisted pair cable has a degraded hot magenta wire. Certainly arbitrary
failures may be expected if Chrome has stolen port 80 and Firefox is
under an attack of an antivirus.
[toc] | [prev] | [next] | [standalone]
Page 6 of 9 — ← Prev page 1 2 3 4 5 [6] 7 8 9 Next page →
Back to top | Article view | linux.debian.user
csiph-web