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 5 of 9 — ← Prev page 1 2 3 4 [5] 6 7 8 9 Next page →
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2024-01-06 15:30 +0100 |
| Subject | Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTfQt-1eiN-11@gated-at.bofh.it> |
| In reply to | #265579 |
The documentation for Chrony is: chrony.conf (5) - chronyd configuration file chronyc (1) - command-line interface for chrony daemon chronyd (8) - chrony daemon Also see /usr/share/doc/chrony . Don't use "pool" to sync to a single source. Use "server". man chrony.conf -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-06 20:10 +0100 |
| Subject | SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTkdr-1hdz-1@gated-at.bofh.it> |
| In reply to | #265585 |
On 1/6/24 09:25, John Hasler wrote: > The documentation for Chrony is: > > chrony.conf (5) - chronyd configuration file > chronyc (1) - command-line interface for chrony daemon > chronyd (8) - chrony daemon > > Also see /usr/share/doc/chrony . > > Don't use "pool" to sync to a single source. Use "server". does this also work for ntpsec? Yes it does, thank you for the hint, John. now that printer is hitting only my server instead of pestering the debian pool. > > man chrony.conf is on the missing list for armbian buster, John. And is not debians problem. Which is what is running this 3d printer. Do you know the name of the man page package that would install those man pages? chrony isn't the only man pages missing. > > 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 | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2024-01-06 20:40 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTkGu-1hmJ-11@gated-at.bofh.it> |
| In reply to | #265592 |
Try manpages.org . -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-06 21:40 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] |
| Message-ID | <HTlCx-1hV9-3@gated-at.bofh.it> |
| In reply to | #265594 |
On 1/6/24 14:33, John Hasler wrote: > Try manpages.org . That is downright tasty stuff, bookmarked, thank you John. 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 | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2024-01-06 23:10 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] |
| Message-ID | <HTn1E-1iSg-7@gated-at.bofh.it> |
| In reply to | #265596 |
[Multipart message — attachments visible in raw view] — view raw
* On 2024 06 Jan 14:34 -0600, gene heskett wrote: > On 1/6/24 14:33, John Hasler wrote: > > Try manpages.org . > > That is downright tasty stuff, bookmarked, thank you John. For us Debian users a better choice would seem to be: https://manpages.debian.org/ The only thing is that I don't see a category for oldstable and oldoldstable, etc. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-01-07 01:10 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand timezone] |
| Message-ID | <HToTL-1k2x-1@gated-at.bofh.it> |
| In reply to | #265597 |
On Sat, Jan 06, 2024 at 03:49:05PM -0600, Nate Bargmann wrote: > For us Debian users a better choice would seem to be: > > https://manpages.debian.org/ > > The only thing is that I don't see a category for oldstable and > oldoldstable, etc. It's by release code name, e.g. "buster" instead of "oldoldstable". <https://manpages.debian.org/buster/grep> (which is easy to remember and to type manually) takes you to a disambiguation page that links to <https://manpages.debian.org/buster/grep/egrep.1.en.html> and so on. If you skip the release name and just go to <https://manpages.debian.org/awk> it takes a guess and redirects you to <https://manpages.debian.org/bookworm/9base/awk.1plan9.en.html> which is not the GNU awk page, but hey, it's *one* awk page. I have no idea why some conflicts result in a disambiguation page, and others result in a guess. <https://manpages.debian.org/gawk> takes you to <https://manpages.debian.org/bookworm/gawk/gawk.1.en.html> which is more likely what you wanted. If you want an older release's man page, you can edit the URL and replace "bookworm" with "bullseye" or whatever. So, there's a certain intuitiveness to the URL bar interface, but also some surprises, when multiple source packages all provide a man page with the same name.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-07 05:30 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdandtimezone] |
| Message-ID | <HTsXn-1mqd-7@gated-at.bofh.it> |
| In reply to | #265597 |
On 1/6/24 17:06, Nate Bargmann wrote: > * On 2024 06 Jan 14:34 -0600, gene heskett wrote: >> On 1/6/24 14:33, John Hasler wrote: >>> Try manpages.org . >> >> That is downright tasty stuff, bookmarked, thank you John. > > For us Debian users a better choice would seem to be: > > https://manpages.debian.org/ The pages at manpages.org are better colored and a larger, much easier to read font. Content I believe, was the same on the file I cheked. > > The only thing is that I don't see a category for oldstable and > oldoldstable, etc. > > - Nate > 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 | Nate Bargmann <n0nb@n0nb.us> |
|---|---|
| Date | 2024-01-07 12:30 +0100 |
| Subject | Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdandtimezone] |
| Message-ID | <HTzvQ-1qWl-7@gated-at.bofh.it> |
| In reply to | #265602 |
[Multipart message — attachments visible in raw view] — view raw
* On 2024 06 Jan 22:27 -0600, gene heskett wrote: > On 1/6/24 17:06, Nate Bargmann wrote: > > * On 2024 06 Jan 14:34 -0600, gene heskett wrote: > > > On 1/6/24 14:33, John Hasler wrote: > > > > Try manpages.org . > > > > > > That is downright tasty stuff, bookmarked, thank you John. > > > > For us Debian users a better choice would seem to be: > > > > https://manpages.debian.org/ > > The pages at manpages.org are better colored and a larger, much easier to > read font. Content I believe, was the same on the file I cheked. If so, you were fortunate to find a page that matched that installed on your system. The manpages.org link won't have pages for some third party packages that manpages.debian.org will. For example, the former does not have a page for 'hamlib' and the latter does. In Debian it is a bug if a package does not have a man page so you will find many more at the manpages.debian.org link. Also, the text size of a Web page can be increased with Ctrl-+ (works on Firefox and Chromium, likely others). - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Web: https://www.n0nb.us Projects: https://github.com/N0NB GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2024-01-07 12:40 +0100 |
| Subject | Re: SOLVED FOR GENE |
| Message-ID | <HTzFv-1qZr-1@gated-at.bofh.it> |
| In reply to | #265604 |
Nate Bargmann composed on 2024-01-07 05:04 (UTC-0600): > the text size of a Web page can be increased with Ctrl-+ (works on > Firefox and Chromium, likely others). Doing so is called a defensive response, something to be expected in response to (needless) offensive behavior. Browsers have default fonts selectable by users for good reason. Websites shouldn't be assuming user settings are wrong. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | jeremy ardley <jeremy.ardley@gmail.com> |
|---|---|
| Date | 2024-01-07 13:10 +0100 |
| Subject | Re: SOLVED FOR GENE |
| Message-ID | <HTA8x-1rpq-1@gated-at.bofh.it> |
| In reply to | #265605 |
On 7/1/24 19:37, Felix Miata wrote: > Doing so is called a defensive response, something to be expected in response to > (needless) offensive behavior. Browsers have default fonts selectable by users for > good reason. Websites shouldn't be assuming user settings are wrong. Using Debian 12 I recently upgraded my monitor to a high pixel count model. Most websites became unreadable as the font size was then tiny. I won't go through the many steps I took to fix this, none of which was entirely successful, but I now mostly have the ability to read my screens using Firefox and Google Chrome with individual site settings as required
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2024-01-07 13:40 +0100 |
| Subject | Re: SOLVED FOR GENE |
| Message-ID | <HTABA-1rzy-17@gated-at.bofh.it> |
| In reply to | #265606 |
On 1/7/24 13:00, jeremy ardley wrote: > > On 7/1/24 19:37, Felix Miata wrote: Please stop this unreadable pointless thread. -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2024-01-11 14:30 +0100 |
| Subject | Re: SOLVED FOR GENE |
| Message-ID | <HV3ia-2mFz-3@gated-at.bofh.it> |
| In reply to | #265605 |
On Sun, Jan 07, 2024 at 06:37:08AM -0500, Felix Miata wrote: >Doing so is called a defensive response, something to be expected in response to >(needless) offensive behavior. Browsers have default fonts selectable by users for >good reason. Websites shouldn't be assuming user settings are wrong. That's a fight that was lost a long time ago.
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2024-01-11 18:10 +0100 |
| Subject | Re: SOLVED FOR GENE |
| Message-ID | <HV6J4-2oP9-17@gated-at.bofh.it> |
| In reply to | #265785 |
Michael Stone composed on 2024-01-11 08:26 (UTC-0500): > On Sun, Jan 07, 2024 at 06:37:08AM -0500, Felix Miata wrote: >>Doing so is called a defensive response, something to be expected in response to >>(needless) offensive behavior. Browsers have default fonts selectable by users for >>good reason. Websites shouldn't be assuming user settings are wrong. > That's a fight that was lost a long time ago. That the offense became virtually universal doesn't make it OK. Truth doesn't stop being truth because of being universally ignored. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
[toc] | [prev] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2024-01-06 23:50 +0100 |
| Subject | manpages package [WAS Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTnEl-1j4V-7@gated-at.bofh.it> |
| In reply to | #265594 |
On Sat, Jan 06, 2024 at 01:17:13PM -0600, John Hasler wrote: > Try manpages.org . > -- > John Hasler > john@sugarbit.com > Elmwood, WI USA > If you're on a Debian system, this should already be installed but otherwise apt-get install manpages Also - manpages.debian.org gives you a searchable interface to all the Debian manpages. All the best Andy (amacater@debian.org)
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-06 18:10 +0100 |
| Subject | Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTilj-1g4A-1@gated-at.bofh.it> |
| In reply to | #265579 |
On 06/01/2024 18:40, gene heskett wrote:
> Put all system clocks on UTC, and then /etc/timezone is the actual
> string specifying the local offset. No doubt some user confusion, but
> overall a lot simpler.
I still do not see any connection with splitting a part of files and
links into another package tzdata-legacy. Kernel anyway keeps time in
UTC, RTC nowadays is mostly in UTC as well.
Notice that /etc/timezone is a legacy Debian-specific way, most of
applications use the /etc/localtime symlink.
I do not think there are strong reasons for tzdata-legacy, but I do not
see a reason for rant as well.
> Or, if someone know how to make systemd's timesyncd actually work, I've
> not been able to do that on 7 machines here, that would be appreciated
> too. Lack of documentation (man pages) for that puppy is a major
> blockaid here on bookworm.
Even if you do not use search engines for some reason, have you tried to
ask at least systemd itself?
systemctl help systemd-timesyncd
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-06 20:40 +0100 |
| Subject | Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] |
| Message-ID | <HTkGu-1hmJ-9@gated-at.bofh.it> |
| In reply to | #265590 |
On 1/6/24 12:07, Max Nikulin wrote: > On 06/01/2024 18:40, gene heskett wrote: >> Put all system clocks on UTC, and then /etc/timezone is the actual >> string specifying the local offset. No doubt some user confusion, but >> overall a lot simpler. > > I still do not see any connection with splitting a part of files and > links into another package tzdata-legacy. Kernel anyway keeps time in > UTC, RTC nowadays is mostly in UTC as well. > > Notice that /etc/timezone is a legacy Debian-specific way, most of > applications use the /etc/localtime symlink. > > I do not think there are strong reasons for tzdata-legacy, but I do not > see a reason for rant as well. > >> Or, if someone know how to make systemd's timesyncd actually work, >> I've not been able to do that on 7 machines here, that would be >> appreciated too. Lack of documentation (man pages) for that puppy is >> a major blockaid here on bookworm. > > Even if you do not use search engines for some reason, have you tried to > ask at least systemd itself? > > systemctl help systemd-timesyncd Does not exist as I manually deleted it and installed ntpsec when I could not find any docs to help make it work. I needed a timeserver that did not depend on debians pool and ntpsec answered the call. I set it up as a stratum 2 server, referencing the debian pool and just now got done re-configuring ntp.conf on the rest of my machines that are currently booted, to use this machine as a server. 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. > . 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-07 16:50 +0100 |
| Subject | systemd-timesyncd |
| Message-ID | <HTDzr-1tko-13@gated-at.bofh.it> |
| In reply to | #265595 |
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).
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2024-01-07 17:30 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTEca-1tLQ-9@gated-at.bofh.it> |
| In reply to | #265610 |
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 malicious Web site. Quit using Google search. Use DuckDuckGo. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-07 21:20 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTHMJ-1vWO-3@gated-at.bofh.it> |
| In reply to | #265611 |
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 acquired > it by visiting an infected or malicious Web site. > > Quit using Google search. Use DuckDuckGo. checkrootkit and rkhunter aren't finding anything. FF caches, can they be cleaned w/o loosing bookmarks? And I do use ddg when I can. 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 Kroeger <mbone@gmx.co.uk> |
|---|---|
| Date | 2024-01-08 06:50 +0100 |
| Subject | Re: systemd-timesyncd |
| Message-ID | <HTQGl-1BBk-1@gated-at.bofh.it> |
| In reply to | #265611 |
> 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)
[toc] | [prev] | [next] | [standalone]
Page 5 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