Re: how avoid blank screen after some time

On 20/11/2024 11:31, Jeffrey Walton wrote: Does smplayer or mpv register a systemd inhibitor? Try: systemd-inhibit --list --no-pager --no-legend Sounds like a tool that may help to run rmmod for a TV receiver card before suspend (from a kaffeine thread several months ago) and to wait till

Re: how avoid blank screen after some time

On Tue, 19 Nov 2024 16:22:44 +0100 Hans wrote: > My hardware is a notebook Lenovo T-520, running debian/stable, fully > upgraded. I also have a t-520, running XFCE, and I have "Disable screensavers" checked. https://www.screensaversplanet.com/help/guides/mac/how-to-disable-the-screensaver-during

Re: how avoid blank screen after some time

> In KDE (and maybe other windowmanagers) the screen is going black after a > while of doing nothing. This is especially annoying, when watching a video in > firefox i.e. from youtube or watching a video in VLC. Blanking seems acceptable if your video is running in some window somewhere, but if

Re: how avoid blank screen after some time

On Tue, Nov 19, 2024 at 12:57 PM Hans wrote: > > I am searching the cause of a little issue, which some day appeared. > > The issue is the following: > > In KDE (and maybe other windowmanagers) the screen is going black after a > while of doing nothing. This is especially annoying, when watching a

Re: how avoid blank screen after some time

On Tue, Nov 19, 2024 at 12:57 PM Hans wrote: > > I am searching the cause of a little issue, which some day appeared. > > The issue is the following: > > In KDE (and maybe other windowmanagers) the screen is going black after a > while of doing nothing. This is especially annoying, when watching a

Re: how avoid blank screen after some time

e DPMS? As this issue appeared after some > upgrade, it must be added or activated somehow. Of course, if the issue is > related to DPMS at all. Since the last millennium… Defeating kernel blanking: https://lists.debian.org/debian-user/1996/12/msg00789.html I don't remember a ti

Re: how avoid blank screen after some time

On 19/11/2024 22:22, Hans wrote: The strange thing is: When watching a video with "smplayer" or with "mpv", then the screen is not going blank. My guess is that mpv properly inhibits screensaver, likely using a D-Bus call. S

Re: how avoid blank screen after some time

Does this not set dpms off permanently? This was the workaround, I already read of. I had the hope of a setting, when watching video, dpms will be automatically shut off. Since when did debian activate DPMS? As this issue appeared after some upgrade, it must be added or activated somehow. Of co

Re: how avoid blank screen after some time

On 2024-11-19 16:22:44, Hans wrote: [SNIP] > Any ideas, from where this behaviour is controlled? Or some other ideas, like > this could be fixed? [SNIP] Hello, Maybe by adding this in your $HOME/.xinitrc: xset -dpms s off xset s 0 -dpms Regards Rand

how avoid blank screen after some time

Dear list, I am searching the cause of a little issue, which some day appeared. The issue is the following: In KDE (and maybe other windowmanagers) the screen is going black after a while of doing nothing. This is especially annoying, when watching a video in firefox i.e. from youtube or watch

Re: ain't it time to fix #790955 (couldn't find any console keymaps)?

Harald Dunkel: > > trying to change console keymaps using standard localectl I > stumbled over https://bugs.debian.org/790955 and the > recommendation on > > https://www.claudiokuenzler.com/blog/1257/how-to-fix-missing-keymaps-debian-ubuntu-localectl-failed-read-list > > to install the missing k

ain't it time to fix #790955 (couldn't find any console keymaps)?

Hi folks, trying to change console keymaps using standard localectl I stumbled over https://bugs.debian.org/790955 and the recommendation on https://www.claudiokuenzler.com/blog/1257/how-to-fix-missing-keymaps-debian-ubuntu-localectl-failed-read-list to install the missing keymaps using upstrea

Re: Increasing "time" command precision

On Thu, Aug 8, 2024, 8:13 AM Greg Wooledge wrote: > On Thu, Aug 08, 2024 at 15:08:33 +0200, Franco Martelli wrote: > > The Bash's shell keyword "time" it could be fine, but I don't know how to > > redirect its output to a file (-o switch of /usr/bin/time). >

Re: Increasing "time" command precision

On Thu, Aug 08, 2024 at 15:08:33 +0200, Franco Martelli wrote: > The Bash's shell keyword "time" it could be fine, but I don't know how to > redirect its output to a file (-o switch of /usr/bin/time). https://mywiki.wooledge.org/BashFAQ/032

Re: Increasing "time" command precision

On 07/08/24 at 21:57, Thomas Schmitt wrote: The number formats are hardcoded: https://sources.debian.org/src/time/1.9-0.2/src/time.c/#L526 case 'S': /* System time. */ fprintf (fp, "%ld.%02ld", https://sources.debian.org/src/time/1.9-0.2/src/tim

Re: Increasing "time" command precision

Hi, Greg Wooledge wrote: > > > * TIMEFORMAT=... time foo will invoke /usr/bin/time, but > > >TIMEFORMAT=... eval time foo will use the builtin. I wrote: > > I wonder about the formal reason for this. > There are some mysteries in bash that I'm conten

Re: Increasing "time" command precision

On Thu, Aug 08, 2024 at 08:31:10 +0200, Thomas Schmitt wrote: > Greg Wooledge wrote: > > * TIMEFORMAT=... time foo will invoke /usr/bin/time, but > >TIMEFORMAT=... eval time foo will use the builtin. (Yeah, oops, time is a "shell keyword", not a "bu

Re: Increasing "time" command precision

Hi, Greg Wooledge wrote: > * TIMEFORMAT=... time foo will invoke /usr/bin/time, but >TIMEFORMAT=... eval time foo will use the builtin. I wonder about the formal reason for this. Is it because "time" is not listed in the man page under SHELL BUILTIN COMMANDS

Re: Increasing "time" command precision

On Wed, Aug 07, 2024 at 22:15:00 +0200, Thomas Schmitt wrote: > it turns out that TIMEFORMAT belongs to the bash builtin "time" > and that digit precision numbers only up to 3 are obeyed. > > $ export TIMEFORMAT="r=%7R > u=%4U > s=%1S" > $ time

Re: Increasing "time" command precision

Hi, it turns out that TIMEFORMAT belongs to the bash builtin "time" and that digit precision numbers only up to 3 are obeyed. $ export TIMEFORMAT="r=%7R u=%4U s=%1S" $ time echo r=0.000 u=0.000 s=0.0 $ man bash: %[p][l]R The elapsed time in seconds. [.

Re: Increasing "time" command precision

Hi, Franco Martelli wrote: > ~# export TIMEFORMAT='real%3R > user%3U > sys %3S' The manual and the source code say that the format variable is "TIME" not "TIMEFORMAT". https://sources.debian.org/src/time/1.9-0.2/src/time.c/#L656 It seems t

Increasing "time" command precision

Hello, I've installed the "time" package, I'd like to increase the number of decimals in the output (say 3) but I got only 2 decimals. Here what I tried: ~# export TIMEFORMAT='real%3R user%3U sys %3S' ~# /usr/bin/time -o elapsed ls -l ... ~# cat

Re: How to get an email notification every time a package is updated

On Sun, Jun 30, 2024 at 08:34:25PM -0700, B wrote: > > Darn and I liked your wiki. I didn't know you were a toxic. Please stop that. He was one trying to offer help. Part of that help was pointing out that your requirements, as you stated them, are incomplete and possibly contradictory. Many of

Re: How to get an email notification every time a package is updated

Darn and I liked your wiki. I didn't know you were a toxic. On 6/30/24 11:43 AM, Greg Wooledge wrote: Can I ask why? You can. I have a funny feeling we won't get an answer. The fact that B is interested in unstable*primarily* (it's the first thing mentioned) tells us an enormous amount.

Re: How to get an email notification every time a package is updated

the security concerns are greatly reduced. Getting patches onto it becomes far less of a race against time. If you also want an email when security patches are released, there is already a solution to that as well: subscribe to the debian-security-announce mailing list. https://lists.debian.org/debia

Re: How to get an email notification every time a package is updated

On Sun 30 Jun 2024 at 02:31:28 (-0700), B wrote: > Thanks for the suggestion, but unfortunately I already researched that > and there are problems. On Sat 29 Jun 2024 at 22:46:00 (-0700), B wrote: > It seems crazy that in all the history of Debian, nobody said "There's > a package I care about and

Re: How to get an email notification every time a package is updated upstream?

On Sat, Jun 29, 2024 at 22:46:00 -0700, B wrote: > On 6/29/24 7:48 PM, Greg Wooledge wrote: > > My next question: is this a package that's*installed* on your system? > > No. Not even the same arch or release as the installed system. I'll even go > further and tell you I want these notifications on

Re: How to get an email notification every time a package is updated upstream?

B wrote: > It seems crazy that in all the history of Debian, nobody said > "There's a package I care about and I want to get immediately when a > new version is released." And if they had, doing an "apt-get update" > every minute of the day would not have been any part of the desired > outcome. I

Re: How to get an email notification every time a package is updated upstream?

On 6/30/24 1:55 AM, Michael Kjörling wrote: I will readily admit that it doesn't immediately meet all of your criteria, but one possible venue especially if you are only interested in a few specific packages might be to point e.g. rss2email at the package events RSS feed available through trac

Re: How to get an email notification every time a package is updated upstream?

On 29 Jun 2024 19:15 -0700, from b...@mydomainnameisbiggerthanyours.com (B): > My objective is to get an email notification when an update is available for > a specific Debian package. > > It sounds simple. Something like this should already exist, right? The > requirements are trivial. Yet after

Re: How to get an email notification every time a package is updated upstream?

On 30/6/24 15:45, B wrote: On 6/29/24 9:30 PM, John Crawley wrote: rmadison will fetch data about package versions available in the Debian repositories. Its output might be usefully parsed by a script. Thank you! I totally forgot about madison. https://qa.debian.org/madison.php What

Re: How to get an email notification every time a package is updated upstream?

On 6/29/24 7:48 PM, Greg Wooledge wrote: Your Subject header includes the word "upstream". This word appears *nowhere* else in the entire email, and it completely moves the goalposts. Are you looking for notifications that a new Debian*package* has become available, or are you looking for noti

Re: How to get an email notification every time a package is updated upstream?

On 6/29/24 9:30 PM, John Crawley wrote: rmadison will fetch data about package versions available in the Debian repositories. Its output might be usefully parsed by a script. Thank you! I totally forgot about madison. https://qa.debian.org/madison.php

Re: How to get an email notification every time a package is updated upstream?

rest in new versions of uninstalled packages, then we have an additional bit of complexity -- how do you know whether the candidate package is "new"? You would need an "old" version number to compare against. Possible answers include "the candidate version number tha

Re: How to get an email notification every time a package is updated upstream?

talled packages, then we have an additional bit of complexity -- how do you know whether the candidate package is "new"? You would need an "old" version number to compare against. Possible answers include "the candidate version number that I got the last time I ran the scri

Re: How to get an email notification every time a package is updated upstream?

* Greg Wooledge [24-06/29=Sa 22:48 -0400]: > Your Subject header includes the word "upstream". This word appears > *nowhere* else in the entire email, and it completely moves the goalposts. "Upstream" was a misleading misnomer intended to refer to anything ... well, "upstream" of the OP's system

Re: How to get an email notification every time a package is updated upstream?

On Sat, Jun 29, 2024 at 19:15:55 -0700, B wrote: > My objective is to get an email notification when an update is available for > a specific Debian package. I already have questions. Your Subject header includes the word "upstream". This word appears *nowhere* else in the entire email, and it co

How to get an email notification every time a package is updated upstream?

questions/970136/how-do-i-make-unattended-upgrades-email-me-every-time-it-runs     apticron         https://packages.debian.org/sid/apticron  https://www.cyberciti.biz/faq/apt-get-apticron-send-email-upgrades-available/         Lots of downsides             The package must be installed on a local system

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 28/06/2024 18:42, Keith Bainbridge wrote: On 28/6/24 16:13, John Crawley wrote: Except that midnight is also 0:00, so you still have the am/pm confusion. They should have kept 0:00 just for midnight really. That's the first time I've seen anything to justify calling m

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 28/6/24 16:13, John Crawley wrote: Except that midnight is also 0:00, so you still have the am/pm confusion. They should have kept 0:00 just for midnight really. That's the first time I've seen anything to justify calling midnight AM. Thankyou But how can mid-day be after mid

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 28/06/2024 14:00, Erwan DAVID wrote: Le 28 juin 2024 13:12:03 David Wright a écrit : On Wed 26 Jun 2024 at 12:50:32 (-0400), Greg Wooledge wrote: On Wed, Jun 26, 2024 at 11:25:38 -0500, John Hasler wrote: I wrote: 12 Noon and 12 Midnight works. David Wright wrote: Except that The Wan

Re: System time/timezone, was Re: Maximum size .bash_aliases file

Le 28 juin 2024 13:12:03 David Wright a écrit : On Wed 26 Jun 2024 at 12:50:32 (-0400), Greg Wooledge wrote: On Wed, Jun 26, 2024 at 11:25:38 -0500, John Hasler wrote: > I wrote: > > 12 Noon and 12 Midnight works. > > David Wright wrote: > > Except that The Wanderer's "strictly correct" versi

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Wed 26 Jun 2024 at 12:50:32 (-0400), Greg Wooledge wrote: > On Wed, Jun 26, 2024 at 11:25:38 -0500, John Hasler wrote: > > I wrote: > > > 12 Noon and 12 Midnight works. > > > > David Wright wrote: > > > Except that The Wanderer's "strictly correct" version, M for noon, > > > is out there in so

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Wed, Jun 26, 2024 at 11:25:38 -0500, John Hasler wrote: > I wrote: > > 12 Noon and 12 Midnight works. > > David Wright wrote: > > Except that The Wanderer's "strictly correct" version, M for noon, > > is out there in some pre-2008 documents. > > If you use M for noon you should use either AM

Re: System time/timezone, was Re: Maximum size .bash_aliases file

I wrote: > 12 Noon and 12 Midnight works. David Wright wrote: > Except that The Wanderer's "strictly correct" version, M for noon, > is out there in some pre-2008 documents. If you use M for noon you should use either AM or PM for midnight. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 6/25/24 20:36, Keith Bainbridge wrote: On 23/6/24 23:22, e...@gmx.us wrote: I started using 24 hour time in junior high school with digital watches.  I just thought it made more sense, especially for setting alarms.  Several decades later I've not seen any reason to change, thou

Re: System time/timezone, was Re: Maximum size .bash_aliases file

David Wright wrote: > On Mon 24 Jun 2024 at 17:12:18 (-0500), John Hasler wrote: > > The Wanderer writes: > > > (Similar logic could be used for 11:59:59 PM, 12:00 M, and > > > 12:00:01 AM, where the standalone M would stand for "midnight". > > > That does expose one unfortunate weakness of this

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 25/6/24 07:53, The Wanderer wrote: Although I don't think anything or anyone actually does it this way, I think strictly speaking the correct 12-hour notation for that time would be "12:00 M" - followed by 12:00:01 PM, and preceded by 11:59:59 AM. Sorry to repeat you -

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 24/6/24 23:41, Erwan David wrote: AM/PM would not be so strange if between 11AM and 1 PM it was 12 AM ... Umm 12Meridian?? -- All the best Keith Bainbridge keithr...@gmail.com keith.bainbridge.3...@gmail.com +61 (0)447 667 468 UTC + 10:00

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 24/6/24 00:53, Curt wrote: On 2024-06-23, Nicholas Geovanis wrote: I think we are losing sight of the fact that all of timekeeping is an abstraction and over-generalization. Time zones were created to help regularize railroad schedules over wide areas. Timezones are an abstraction that

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 23/6/24 23:22, e...@gmx.us wrote: On 6/23/24 02:30, gene heskett wrote: A attribute the FCC forced on broadcasters as they like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time for 40 years and didn't conve

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 23/6/24 18:57, Brad Rogers wrote: On Sun, 23 Jun 2024 15:35:14 +1000 Keith Bainbridge wrote: Hello Keith, +14:00?? I've only ever heard of maxima of +/- 12:00. AFAIAC, it was political willy waving, nothing more; To be 'first' into the new millennium. As if that has any cachet what

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 23/6/24 18:56, Brad Rogers wrote: On Sun, 23 Jun 2024 13:01:10 +1000 Keith Bainbridge wrote: Hello Keith, Not to mention some cultures change how words are spelt: colour, odour, metres to quote a few. Due, mainly, to the literacy of the people that moved, rather than any deliberate cho

Re: System time/timezone, was Re: Maximum size .bash_aliases file

Well, The International BIPM writes the time with a colon: https://www.bipm.org/en/ Best Heriberto On Tuesday, June 25, 2024, David Wright wrote: > On Mon 24 Jun 2024 at 23:34:45 (+0800), Bret Busby wrote: >> On 24/6/24 21:41, Erwan David wrote: >> > Le 24/06/2024 à 2

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Mon 24 Jun 2024 at 23:34:45 (+0800), Bret Busby wrote: > On 24/6/24 21:41, Erwan David wrote: > > Le 24/06/2024 à 22:38, Curt a écrit : > > > When my mom came to visit one time in the nineties she requested I > > > change my alarm clock to AM PM time (it is n

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Mon 24 Jun 2024 at 17:12:18 (-0500), John Hasler wrote: > The Wanderer writes: > > (Similar logic could be used for 11:59:59 PM, 12:00 M, and 12:00:01 AM, > > where the standalone M would stand for "midnight". That does expose one > > unfortunate weakness of this system: unless you introduce an

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Tue, Jun 25, 2024 at 14:25:51 -0400, Roy J. Tellason, Sr. wrote: > So I have this digital clock up there in my panel, and in the virtual > machine here running Slackware I also have one. The one under Debian shows > 00:00 when it hits midnight, while the one under Slackware shows 12:00... >

Re: System time/timezone, was Re: Maximum size .bash_aliases file

nk strictly speaking the correct 12-hour notation for that time would > be "12:00 M" - followed by 12:00:01 PM, and preceded by 11:59:59 AM. > > AM stands for "ante meridiem", i.e., before the midpoint; PM stands for > "post meridiem", i.e., after the midpoin

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Mon, Jun 24, 2024 at 06:21:57PM -0400, The Wanderer wrote: > On 2024-06-24 at 18:12, John Hasler wrote: > > > The Wanderer writes: > > > >> (Similar logic could be used for 11:59:59 PM, 12:00 M, and 12:00:01 AM, > >> where the standalone M would stand for "midnight". That does expose one > >> u

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 2024-06-24 at 18:12, John Hasler wrote: > The Wanderer writes: > >> (Similar logic could be used for 11:59:59 PM, 12:00 M, and 12:00:01 AM, >> where the standalone M would stand for "midnight". That does expose one >> unfortunate weakness of this system: unless you introduce an additional >> la

Re: System time/timezone, was Re: Maximum size .bash_aliases file

The Wanderer writes: > (Similar logic could be used for 11:59:59 PM, 12:00 M, and 12:00:01 AM, > where the standalone M would stand for "midnight". That does expose one > unfortunate weakness of this system: unless you introduce an additional > layer of complexity, e.g. using "00:00 M", the notatio

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 2024-06-24 at 09:41, Erwan David wrote: > AM/PM would not be so strange if between 11AM and 1 PM it was 12 AM > ... Although I don't think anything or anyone actually does it this way, I think strictly speaking the correct 12-hour notation for that time would be "12:00 M"

Re: System time/timezone

the > components of year and month and day of the month > But, for a country that has yet to implement its constitution, it is not > really so surprising. We aren't always forced. Some devices offer only AM/PM time format and schizoid date format, but not my hand or PCs, and neither

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 6/24/24 11:42, Bret Busby wrote: On 24/6/24 21:38, Curt wrote: You can become confused, though, when filling out US forms where the birth date is written M/D/Y instead of D/M/Y, and sometimes you have to be careful not commit the silly mistake that will entrain months of delay in intricate

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 24/6/24 21:38, Curt wrote: You can become confused, though, when filling out US forms where the birth date is written M/D/Y instead of D/M/Y, and sometimes you have to be careful not commit the silly mistake that will entrain months of delay in intricate *dédales* of the administration. Thi

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 24/6/24 21:41, Erwan David wrote: Le 24/06/2024 à 22:38, Curt a écrit : On 2024-06-23, gene heskett wrote: A attribute the FCC forced on broadcasters as they like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time f

Re: System time/timezone, was Re: Maximum size .bash_aliases file

Le 24/06/2024 à 22:38, Curt a écrit : On 2024-06-23, gene heskett wrote: A attribute the FCC forced on broadcasters as they like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time for 40 years and didn't convert b

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 2024-06-24, Curt wrote: > On 2024-06-23, gene heskett wrote: >>> >> A attribute the FCC forced on broadcasters as they like to see >> transmitter logs kept in 24 hour time. I got so used to it that when I >> retired in 2002, I'd been on 24 hour time for 4

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 2024-06-23, gene heskett wrote: >> > A attribute the FCC forced on broadcasters as they like to see > transmitter logs kept in 24 hour time. I got so used to it that when I > retired in 2002, I'd been on 24 hour time for 40 years and didn't > convert back to two

Re: System time/timezone, was Re: Maximum size .bash_aliases file

17 +14 2024 > Sun Jun 23 21:24:17 +0845 2024 Yes, I corrected it, but then carelessly pasted the incorrect lines. > The fact that date(1) treats any misspelled or otherwise incorrect TZ > variable as if it were UTC, but then goes on to write the mispelled > time zone name in its *out

Re: System time/timezone, was Re: Maximum size .bash_aliases file

Brad Rogers writes: > Due, mainly, to the literacy of the people that moved, rather than any > deliberate choice. That is, spelling was often a 'best guess'. https://en.wikipedia.org/wiki/Webster's_Dictionary#Noah_Webster's_American_Dictionary_of_the_English_Language -- John Hasler j...@sugarb

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 2024-06-23, Nicholas Geovanis wrote: > > I think we are losing sight of the fact that all of timekeeping is an > abstraction and over-generalization. Time zones were created to help > regularize railroad schedules over wide areas. Timezones are an abstraction > that permit us to

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 6/23/24 09:23, e...@gmx.us wrote: On 6/23/24 02:30, gene heskett wrote: A attribute the FCC forced on broadcasters as they like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time for 40 years and didn't conve

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 6/23/24 02:30, gene heskett wrote: A attribute the FCC forced on broadcasters as they like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time for 40 years and didn't convert back to two 12 hour periods a day.

Re: System time/timezone, was Re: Maximum size .bash_aliases file

t were UTC, but then goes on to write the mispelled time zone name in its *output*, as if it were actually being recognized, has tripped me up in the past. I really wish it would just throw an error... but it doesn't.

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Sun, 23 Jun 2024 15:35:14 +1000 Keith Bainbridge wrote: Hello Keith, >+14:00?? I've only ever heard of maxima of +/- 12:00. AFAIAC, it was political willy waving, nothing more; To be 'first' into the new millennium. As if that has any cachet whatsoever. -- Regards _ "Valid sig

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Sun, 23 Jun 2024 13:01:10 +1000 Keith Bainbridge wrote: Hello Keith, >Not to mention some cultures change how words are spelt: colour, odour, >metres to quote a few. Due, mainly, to the literacy of the people that moved, rather than any deliberate choice. That is, spelling was often a 'bes

Re: System time/timezone, was Re: Maximum size .bash_aliases file

hey like to see transmitter logs kept in 24 hour time. I got so used to it that when I retired in 2002, I'd been on 24 hour time for 40 years and didn't convert back to two 12 hour periods a day. The AM/PM convention. So when I say its 22:30, its 10:30 PM to the neighbors next door. As fo

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Fri, Jun 21, 2024 at 12:18 AM David Wright wrote: > [...] > Well, that's a mouthful. And what am I to call the time that a system > issues using that system default time zone? The kernel clock counts ticks. The ticks are relative to Epoch, which is UTC. Ticks are what you see in

Re: System time/timezone, was Re: Maximum size .bash_aliases file

And before that, the creation of Pacific/Kiritimati (+14:00), which became a press story at the start of the new millennium. +14:00?? I've only ever heard of maxima of +/- 12:00. But see below As for odd time zones, we have a narrow one, somewhere between the West Australian border (wit

Re: System time/timezone, was Re: Maximum size .bash_aliases file

what term is appropriate in your > > > > opinion to describe the time displayed? > > > > > > They're out of sync. Or, at least one of them is. > > > > No, the kernel clocks are all in sync. > > Then you were unclear. You said "they di

Re: System time/timezone, was Re: Maximum size .bash_aliases file

ic/Kiritimati (+14:00), which became a press story at the start of the new millennium. > As for odd time zones, we have a narrow one, somewhere between the > West Australian border (with Sth Aust) and the first notable town on > the road West - Norseman. It's 45 mins different from Sth

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 23/6/24 00:53, David Wright wrote: Styles change: there's a tendency in English to evolve towards compound words, sometimes with hyphenation along the way. Not to mention some cultures change how words are spelt: colour, odour, metres to quote a few. But don't fret.Some people prono

Re: System time/timezone, was Re: Maximum size .bash_aliases file

is an abstraction and over-generalization. Time zones were created to help regularize railroad schedules over wide areas. Timezones are an abstraction that permit us to _pretend_ that it is (physical) noon at the same clock time over an extended area. When in fact physical high- noon, determined

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 23/6/24 01:16, to...@tuxteam.de wrote: Possible. I was happy to forget that I had anything to do with Windows 🙂 Especially delving into the registry -- All the best Keith Bainbridge keithr...@gmail.com keith.bainbridge.3...@gmail.com +61 (0)447 667 468 UTC + 10:00

Re: System time/timezone, was Re: Maximum size .bash_aliases file

here simply isn't such a term. The subject is sufficiently > complex/delicate that there can't be a term for every single situation. > I think we are losing sight of the fact that all of timekeeping is an abstraction and over-generalization. Time zones were created to help regul

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Sat, Jun 22, 2024 at 09:52:39 -0500, David Wright wrote: > On Fri 21 Jun 2024 at 07:15:32 (-0400), Greg Wooledge wrote: > > > If I boot up two computers > > > and they display different times, what term is appropriate in your > > > opinion to describe the time disp

Re: System time/timezone, was Re: Maximum size .bash_aliases file

> Yes, I realise that. The times are being displayed by the gettys, > controlled by the /etc/issue format string. Jobs are being run > by cron, logs written by rsyslogd, and so on. And the term is … ? Maybe there simply isn't such a term. The subject is sufficiently complex/delicate that there c

Re: System time/timezone, was Re: Maximum size .bash_aliases file

. > > > > It's a log time ago, but we were a shop with a few pretty knowledgeable > > folks, > > so I guess we first tried something like that. > > There was a Registry Key: > > HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUnivers

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Fri 21 Jun 2024 at 06:45:58 (+0200), to...@tuxteam.de wrote: > On Fri, Jun 21, 2024 at 09:32:10AM +0700, Max Nikulin wrote: > > On 20/06/2024 11:52, to...@tuxteam.de wrote: > > > "the system's > > > time zone" (of which some, me included, say "th

Re: System time/timezone, was Re: Maximum size .bash_aliases file

; > On 20/06/2024 11:52, to...@tuxteam.de wrote: > > [...] > > > Well, that's a mouthful. And what am I to call the time that a system > > issues using that system default time zone? If I boot up two computers > > and they display different times, what term is appropriat

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Fri 21 Jun 2024 at 07:15:32 (-0400), Greg Wooledge wrote: > On Thu, Jun 20, 2024 at 23:17:42 -0500, David Wright wrote: > > And what am I to call the time that a system > > issues using that system default time zone? > > If you mean the current time translated into that t

Re: time display was: Re: Maximum size .bash_aliases file

gt; > > wrote: > > > > > > It was late afternoon on 16Jun2024 that I wrote this. Possibly > > > 18:13:36 when I pressed send. I'd reckon it would likely have > > > been > > > 08:13:36 UTC What's wrong with my system clock. I've not re

Re: RTC, was Re: System time/timezone

On 20/6/24 11:51, Max Nikulin wrote: On 20/06/2024 02:16, Nicholas Geovanis wrote: Servers in data centers don't move around, they just sit there :-) So in my experience servers running anything non-windows have RTC set to local time. That's been on Red Hat/CentOS, Debian, Ub

Re: time display was: Re: Maximum size .bash_aliases file

on it would likely have been 08:13:36 UTC What's wrong with my system clock. I've not really looked at the time on my originals before. I'll try to remember to enter my local time as I press send I'm confused. Your time displays (Keith) look sensible to me, given they are in

Re: Time, was Re: Maximum size .bash_aliases file

On 18/6/24 03:24, e...@gmx.us wrote: And I can never remember if the dot means AM or PM.  I suspect it changes between implementations, or maybe I'm just very slow. Probably only really meant to show us when we are setting an alarm at night, for the morning, that the dot is on one and off o

Re: Time, was Re: Maximum size .bash_aliases file

On 18/6/24 01:36, David Wright wrote: Along with 350M Americans! They even use just A and P over here. And a mere dot on digital clocks. (I see you've changed it already!) I've been using 24 hour time and dMMM for a long time. I used send international cheques as part of my

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Sat, Jun 22, 2024 at 10:22:53AM +0700, Max Nikulin wrote: [...] > I think, you are biased treating "system" as tightly built-in while most of > others assume "system-wide". Taking your bias out ("you are biased" -- "most of others") I'd tend to agree :-) You do have a point. Coming from the

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On 21/06/2024 11:45, to...@tuxteam.de wrote: On Fri, Jun 21, 2024 at 09:32:10AM +0700, Max Nikulin wrote: On 20/06/2024 11:52, to...@tuxteam.de wrote: "the system's time zone" (of which some, me included, say "there's no such thing", and others disagree 🙂 Wh

Re: System time/timezone, was Re: Maximum size .bash_aliases file

On Thu, Jun 20, 2024 at 23:17:42 -0500, David Wright wrote: > And what am I to call the time that a system > issues using that system default time zone? If you mean the current time translated into that time zone, "local time" is the traditional name for it. If you mean an arb

  1   2   3   4   5   6   7   8   9   10   >