Re: difference in seconds between two formatted dates ...

On Thu, Dec 21, 2023 at 02:51:50PM -0500, gene heskett wrote: > can us see your /etc/ntpsec/ntp.conf? And, do you have a > /var/log/ntpsec subdir ownwd by ntpsec:ntpsec? unicorn:~$ ls -ld /var/log/ntpsec /etc/ntpsec/ntp.conf ls: cannot access '/var/log/ntpsec': No such file or directory -rw-r--r

Re: Is there a problem with Linux-image-6.1.0-16?

On Thu, Dec 21, 2023 at 09:02:34AM -0500, Gary Dale wrote: > Several days ago my main server upgraded to kernel 6.1.0-16 but various > other devices that are also running Bookworm seem stuck at 6.1.0-13. They > are all using the same architecture. Some are using the same mirror as the > server that

Re: difference in seconds between two formatted dates ...

On Thu, Dec 21, 2023 at 10:36:06PM +0700, Max Nikulin wrote: > I have another guess. systemd-timedated is activated on demand and reads > /etc/localtime. It exits a half of a minute later. Perhaps second command > caused start of new process since the old one was dead already. Hmm. OK, logs do se

Re: Help: network abuse

On Thu, Dec 21, 2023 at 12:00:55PM +, Alain D D Williams wrote: > My home PC is receiving, for hours at a time, 12-30 kB/s input traffic. This > is > unsolicited. I do not know what it is trying to achieve but suspect no good. > It > is also eating my broadband allowance. > 11:08:56.354303 I

Re: difference in seconds between two formatted dates ...

On Thu, Dec 21, 2023 at 06:08:26AM +, Albretch Mueller wrote: > and what would the systemd way to synch the RTC (Real Time Clock) and > UTC? I don't understand this question at all. The system clock value is normally written to the RTC as a backup when the system shuts down. Then, the RTC va

Re: difference in seconds between two formatted dates ...

On Wed, Dec 20, 2023 at 10:52:33PM -0600, David Wright wrote: > Sorry for the synecdoche, but I think it expresses the comprehensive > setting of UTC across the entirety of the computer and its operating > system, from the RTC, through /etc/timezone and /etc/localhost, to > the users' sessions. By

Re: lists

On Wed, Dec 20, 2023 at 12:05:26PM -0500, Pocket wrote: > I was kicked at 2% How do you *know*? What you *know* is that you *saw* *one* email message stating that emails have been trouble reaching you, and that if this continues, you will be unsubscribed. What if there were more, that you did *n

Re: difference in seconds between two formatted dates ...

On Wed, Dec 20, 2023 at 01:12:35PM +, Albretch Mueller wrote: > The only way I see is for the running computer on "exposed mode" to > check via systemd if the time zone has been changed Huh? None of this makes any sense. First of all, the system's default time zone only changes if a user wi

Re: difference in seconds between two formatted dates ...

On Wed, Dec 20, 2023 at 07:43:51AM +, Albretch Mueller wrote: > I do see the good in what you are suggesting to me and I will have to > include time zones in the file names as well and deal with the > possible cases (someone working at Charles de Gaulle Airport in > Paris/France boards a plane

Re: system not updating

On Tue, Dec 19, 2023 at 01:37:40PM -0500, Michael Grant wrote: > On the one that's not getting updates: > > [strange /etc/apt #1939] apt policy openvpn > openvpn: > Installed: 2.6.3-1+deb12u2 > Candidate: 2.6.3-1+deb12u2 It's already upgraded. Perhaps this system has unattended-upgrades inst

Re: system not updating

On Tue, Dec 19, 2023 at 12:57:36PM -0500, Michael Grant wrote: > I have 3 debian servers which are mostly the same. 2 of them if I run > apt list --upgradable, I get a list of 20 or so packages to update. > One of them only shows this: [...] > linux-image-amd64/stable-updates 6.1.67-1 amd64 [upgra

Re: Mouse single click handling?

On Tue, Dec 19, 2023 at 05:01:46PM +0100, local10 wrote: > I've been replacing them, I have 4-5 mice like that, they all fail with the > same defect after 6-12 months or so. So I thought perhaps there was a way to > fix them instead of buying a new one every 6-12 months. If you can fix the hardwar

Re: difference in seconds between two formatted dates ...

On Mon, Dec 18, 2023 at 12:35:29PM -0600, David Wright wrote: > OK, I tried running it (attached). What should it show? That the OP is confused about many things. > # date --help No shebang. But the script uses bash syntax. When executed FROM BASH, the script will "work" because bash will inte

Re: difference in seconds between two formatted dates ...

On Mon, Dec 18, 2023 at 02:07:14PM +0100, to...@tuxteam.de wrote: > I'm still amazed the OP hasn't understood that "date" can output > custom formats -- and that it's not always possible to parse back > a date in some custom format into a meaningful timestamp. unicorn:~$ date +"On this the %dth da

Re: difference in seconds between two formatted dates ...

On Mon, Dec 18, 2023 at 06:02:48AM +, Albretch Mueller wrote: > On 12/18/23, David Wright wrote: > > Another problem in what you posted is that you sometimes run date > > in your local timezone (generally for the "now" times), but you > > append +00:00 as the timezone for those --date strings

Re: Problem with /var/cache/apt/archives/

oo many symlinks is not > visually apparent. Well, why not *show us*? Here's one way to produce that error message: unicorn:~$ mkdir /tmp/subdir unicorn:~$ ln -s link /tmp/subdir/link unicorn:~$ ls /tmp/subdir/link/foo ls: cannot access '/tmp/subdir/link/foo': Too many levels of

Re: difference in seconds between two formatted dates ...

On Sun, Dec 17, 2023 at 03:28:58PM +, Albretch Mueller wrote: > On 12/17/23, Greg Wooledge wrote: > > On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote: > >> ... after some long processing for which seconds would be exact > >> enough, then I wo

Re: difference in seconds between two formatted dates ...

On Sun, Dec 17, 2023 at 10:12:11AM +, Albretch Mueller wrote: > ... after some long processing for which seconds would be exact > enough, then I would like to get the seconds elapsed since dt00 Are you working in bash, or sh? It makes a difference here. Others have already mentioned using "d

Re: was nvramtool removed from the package repository?

On Sat, Dec 16, 2023 at 02:04:26PM +, Albretch Mueller wrote: > E: Unable to locate package nvramtool Note to future readers: the actual question was contained in the Subject: header rather than the body. The original Subject: header said, "was nvramtool removed from the package repository?"

Re: Problem with /var/cache/apt/archives/

On Sat, Dec 16, 2023 at 08:45:41AM -0500, Stephen P. Molnar wrote: > I am running Bookworm on my Debian computer. When I installed the OS I > selected the option for separate /var etc, and selected the default sizes of > the partitions. How many disks are there? *How* did you partition them? Are

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

On Fri, Dec 15, 2023 at 11:05:41PM -0500, Matt wrote: > I had to go to Wikipedia to understand the context of the discussion. I did > read all the posted emails in the thread. > > https://en.wikipedia.org/wiki/RAID Knowing what RAID is... is good. But ultimately, the main takeaway from this thre

Re: setting IFS to new line doesn't work while searching?

On Fri, Dec 15, 2023 at 02:30:21PM +0100, Nicolas George wrote: > Greg Wooledge (12023-12-15): > > readarray -d '' fndar < <( > > find "$sdir" ... -printf 'stuff\0' | > > sort -z --otherflags > > ) > It i

Re: setting IFS to new line doesn't work while searching?

On Fri, Dec 15, 2023 at 01:42:14PM +0100, Nicolas George wrote: > Also, note that file names can also contain newlines in general. The > only robust delimiter is the NUL character. True. In order to be 100% safe, the OP's code would need to look more like this: readarray -d '' fndar < <(

Re: setting IFS to new line doesn't work while searching?

On Fri, Dec 15, 2023 at 12:33:01PM +, Albretch Mueller wrote: > #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td > %TI:%TM|%s\n' | sort --version-sort --reverse)) > the array construct ($( ... )) is using the space (between the date > and the time) also to split array elements

Re: differences among amd64 and i386

On Thu, Dec 14, 2023 at 09:54:08PM +, fuf wrote: > Near a half month ago I bought a comp. made into 2011 year and didn't knew > which Debian12 to put: i386 or amd64?, chose i386 as thought that old comp. > didn't take amd64. > i386-netinst Debian 12 was being installed perfectly, and later I c

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. Just for the record, saying you have the "latest" version of

Re: The bug

On Wed, Dec 13, 2023 at 04:13:44PM +0100, to...@tuxteam.de wrote: > On Wed, Dec 13, 2023 at 10:10:37AM -0500, Greg Wooledge wrote: > > On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote: > > > If so, then IIUC the answer is a resounding "YES, it is safe!". &

Re: The bug

On Wed, Dec 13, 2023 at 09:56:46AM -0500, Stefan Monnier wrote: > If so, then IIUC the answer is a resounding "YES, it is safe!". > It just may be unusable, so you may have to downgrade to 6.1.0-13 until > the problem is fixed. > > That's a very different issue from the ext4 corruption problem in

Re: Is it safe to install Bookworm on a new machine now?

On Tue, Dec 12, 2023 at 05:47:48PM -0800, Rick Thomas wrote: > Is there a netinst iso that I can use to safely install Bookworm (stable) on > a new PC? Well, with a netinst, the issue isn't what's on the netinst medium. It's what's on the Debian mirrors, which the installer will use for most of

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Mon, Dec 11, 2023 at 07:38:02PM +0100, Stella Ashburne wrote: > Please see Greg's reply to my other post (URL: > https://lists.debian.org/debian-user/2023/12/msg00640.html). > > For your convenience, I quote a section of his reply (see below): > > "Yes, because linux-image-amd64 *right now* d

Re: "echo" literally in sh scripts (was: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...)

On Mon, Dec 11, 2023 at 10:16:35AM -0500, Stefan Monnier wrote: > > 1) Many implementations of echo will interpret parts of their argument(s), > >in addition to processing options like -n. If you want to print a > >variable's contents to standard output without *any* interpretation, > >

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 02:00:49PM +, Albretch Mueller wrote: > Ach, yes! I forgot echo by default appends a new line character at > the end of every string it spits out. In order to suppress it you need > to use the "n" option: "echo -n ..." > > _FL_TYPE=" abc á é í ó ú ü ñ Á É Í Ó Ú Ü Ñ

Re: Release process notes [WAS Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)]

On Mon, Dec 11, 2023 at 02:35:07PM +0100, Stella Ashburne wrote: > Suppose linux-image-6.1.0-15-amd64 is installed successfully and I reboot my > device. > > A few days from now, I decide to remove linux-image-6.1.0-15-amd64 because it > is buggy and so in a terminal, I type the commands: > > s

Re: From which kernel should I upgrade my installed Debian to linux-image-6.1.0-15-amd64?

On Mon, Dec 11, 2023 at 02:16:39PM +0100, Stella Ashburne wrote: > (3) doesn't matter which kernel to upgrade from That.

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 02:11:46PM +0100, to...@tuxteam.de wrote: > On Mon, Dec 11, 2023 at 07:42:10AM -0500, Greg Wooledge wrote: > > Looks like GNU tr in Debian 12 still doesn't handle multibyte characters > > correctly: > > > > unicorn:~$ echo 'maña

Re: Image handling in mutt

On Mon, Dec 11, 2023 at 01:41:09PM +0100, Arno Lehmann wrote: > I do not see the relevance of the discussion about file name extensions, > types, suffixes for Debian. Even more so as you are at the stage of > repeating statements without bringing new value. In fact, there seems to be > no goal with

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 09:37:42AM +0100, to...@tuxteam.de wrote: > 2. This is tr, not regexp, so '[A-Za-z0-9.]' isn't doing what you >think it does. It will match '[', 'A' to 'Z', 'a' to 'z','.' and >']'. I guess you want to say 'A-Za-z0-9.' Well spotted. > 3. As a convenience, tr has

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 11:25:13AM +, Albretch Mueller wrote: > In the case of: "ASCII text" > what should come out of it is: "ASCII_text" > not: "ASCII_text_" > no underscore at the end. That is the question I have. OK, here's my guess. The lines of code that you showed us are not actuall

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

On Mon, Dec 11, 2023 at 04:31:22AM +0100, Stella Ashburne wrote: > Someone on a social media platform stated that there are only two "canonical" > [sic] ways to verify the version of Debian installed on a system. They are: > > uname -a > > /proc/version > > Do you agree with the above statement

Re: why would "tr --complement --squeeze-repeats ..." append the substitution char once more? ...

On Mon, Dec 11, 2023 at 02:53:07AM +, Albretch Mueller wrote: > echo "abc123" > file.txt > ftype=$(file --brief file.txt) > echo "// __ \$ftype: |${ftype}|" > ftypelen=${#ftype} > echo "// __ \$ftypelen: |${ftypelen}|" > > # removing spaces ... > ftype2=$(echo "${ftype}" | tr --complement --sq

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

On Mon, Dec 11, 2023 at 03:26:16AM +0100, Stella Ashburne wrote: > What command did you use? Was it > > sudo dpkg -i linux-image-amd64_6.1.55-1_amd64.deb Yes. On Mon, Dec 11, 2023 at 03:32:55AM +0100, Stella Ashburne wrote: > As of writing this reply, there's a new point release, 12.4.0 > > Wha

Re: Unattended Upgrades Ran Anyway.

On Sun, Dec 10, 2023 at 02:10:43PM -0700, Charles Curley wrote: > On Sun, 10 Dec 2023 14:51:48 -0600 > David Wright wrote: > > > I think it might be worth googling and reading "three levels of off" > > (with the quotes). > > > > 1. You can stop a service. That simply terminates the running > >

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

On Sun, Dec 10, 2023 at 10:08:21AM -0500, Greg Wooledge wrote: > On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote: > > That will work: you might also want to apt-get purge > > linux-image-6.1.0-14-amd64 > > but you've done the main thing. > > Note

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That should be sufficient to let you know

Re: Need clarifications about how to deal with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)

On Sun, Dec 10, 2023 at 01:41:14PM +, Andrew M.A. Cater wrote: > That will work: you might also want to apt-get purge > linux-image-6.1.0-14-amd64 > but you've done the main thing. Note that purging 6.1.0-14 will also remove the linux-image-amd64 metapackage, which has a hard dependency on it

Re: IMPORTANT: do NOT upgrade to new stable point release

On Sat, Dec 09, 2023 at 07:18:20PM +, Michael Kjörling wrote: > If you upgraded this morning, then I would expect that you are okay > for now. That doesn't appear to be true. > Per #5 in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > the bug is present in kernel Debian package ve

Re: ToG Linux (first draft of a RFC) ...

On Sat, Dec 09, 2023 at 02:50:16PM +0100, Arno Lehmann wrote: > On 09.12.23 at 10:13, Albretch Mueller wrote: > > As anyone could see you could even run a network of detached > > computers without networking interfaces in a "touch of God" kind of > > way, > > At this point it becomes quite clear

Re: Apt 2 not fully installed or removed.

On Sat, Dec 09, 2023 at 02:26:41AM -0500, Timothy M Butterworth wrote: > > Removing php-horde (5.2.23+debian0-6) ... > > /var/lib/dpkg/info/php-horde.postrm: 28: /etc/apache2/envvars: > > /etc/default/locale: Permission denied > I figured out the problem and apt is working fine now. Was it the pe

Re: Image handling in mutt

On Fri, Dec 08, 2023 at 05:59:58PM -0500, Pocket wrote: > On 12/8/23 17:54, Greg Wooledge wrote: > > cc(1) looks at the file extension to decide what kind of content each > > named argument file is expected to contain. > No it looks for a suffix So Debian files have "suff

Re: Image handling in mutt

On Fri, Dec 08, 2023 at 04:50:04PM -0600, John Hasler wrote: > Greg writes: > > cc(1) and make(1) would like to have a talk with you. > > Those are applications and can do whatever they want. The OS does not > care about extensions. What do you consider "the OS" to be, then?

Re: Image handling in mutt

On Fri, Dec 08, 2023 at 05:41:57PM -0500, Pocket wrote: > > On 12/8/23 17:31, Greg Wooledge wrote: > > On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote: > > > In Unix and Linux there isn't a file extension, that is a microsoft > > > invention. > > cc

Re: Image handling in mutt

On Fri, Dec 08, 2023 at 05:06:15PM -0500, Pocket wrote: > In Unix and Linux there isn't a file extension, that is a microsoft > invention. cc(1) and make(1) would like to have a talk with you.

Re: ntpsec as server questions

On Fri, Dec 08, 2023 at 04:12:54PM +, Bonno Bloksma wrote: > Hi Greg, > > bool isleapyear (int year) { > > if (year % 400 == 0) return true; > > if (year % 100 == 0) return false; > > if (year % 4 == 0) return true; > > return false; > >

Re: ntpsec as server questions

On Thu, Dec 07, 2023 at 11:19:19PM -0500, gene heskett wrote: > [...] a method for determining leap years. It was also > used in some astronomical programs for lunar and solar eclipses. This I > think was the reason that all unix times start at midnight 1/1/1970. In the > FWIW dept this time formul

Re: ntpsec as server questions

On Thu, Dec 07, 2023 at 11:19:19PM -0500, gene heskett wrote: > Of minor interest to me, not once in the above link does it credit the K&R > Manual for C, which has a method for determining leap years. The what now? Leap years are defined by the Gregorian Calendar, as declared in the 16th century

Re: ntpsec as server questions

On Fri, Dec 08, 2023 at 09:38:43AM +0700, Max Nikulin wrote: > - IANA TZ DB does not support timezones disappeared before 1970. > Ohhh, *this* is the kind of reference I've been looking for. So, we simply acknowledge that historical clock

Re: debian forgot usr pw

On Thu, Dec 07, 2023 at 08:06:52PM -0500, gene heskett wrote: > Thats bug #1. Single for rescue demands a root pw. This isn't a bug. It's just how things *are*. People who choose not to set a root password are simply setting themselves up for this failure. It *will* happen eventually. I strong

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 11:46:50PM -0600, David Wright wrote: > On Wed 06 Dec 2023 at 18:16:42 (-0500), Pocket wrote: > > Which BTW this whole discussion about timezones is just water over the dam. > > > > The system should be set to UTC, the "timezone" issue is really just a > > "human" issue as

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 07:37:32PM -0500, Pocket wrote: > > On 12/6/23 19:26, Greg Wooledge wrote: > > On Wed, Dec 06, 2023 at 07:23:18PM -0500, Pocket wrote: > > > On 12/6/23 19:12, Greg Wooledge wrote: > > > > So, basically every reference I can find, and ev

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 07:23:18PM -0500, Pocket wrote: > On 12/6/23 19:12, Greg Wooledge wrote: > > So, basically every reference I can find, and every reference I've *ever* > > found, other than Pocket's email, has said that America/New_York is > > correct f

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 06:11:16PM -0500, Pocket wrote: > Because DST was not in force/usage except the metro NYC. Every where else > didn't use/have it. > > That makes EST5DST correct except for NYC and America/New_York completely > incorrect except of course NYC. (EST5EDT not EST5DST.) Now thi

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 02:50:50PM -0500, Pocket wrote: > Well since I am not going to set any of my systems to a time in 1920, then I > believe I am save from the time machines. It's not just about your system's current time. It's about timestamps that you handle in any kind of software. If yo

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 01:02:45PM -0500, Pocket wrote: > TZ=POSIX;date > Wed Dec 6 18:00:38 POSIX 2023 "POSIX" is not a valid timezone name in Debian 12. Therefore you're just seeing UTC here. Giving an invalid TZ always gives you UTC, but with whatever crazy-ass name you used echoed back at y

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 05:40:00PM -, Curt wrote: > POSIX format specification > > The POSIX time zone format is the traditionally used format for AIX systems > and > provides a slight performance advantage over the Olson time zone format. > Example of a POSIX format is EST5EDT. > > The

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 12:06:04PM -0500, Pocket wrote: > From the README > > The information in the time zone data files is by no means authoritative; > fixes and enhancements are welcome.  Please see the file CONTRIBUTING > for details > > I take that as chaos reins supreme and one zone is no b

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 11:28:40AM -0500, Pocket wrote: > diff /usr/share/zoneinfo/EST5EDT /usr/share/zoneinfo/America/New_York > Binary files /usr/share/zoneinfo/EST5EDT and > /usr/share/zoneinfo/America/New_York differ unicorn:/usr/share/zoneinfo$ ls -l EST5EDT -rw-r--r-- 1 root root 2310 May 28

Re: ntpsec as server questions

On Wed, Dec 06, 2023 at 10:44:42AM -0500, Pocket wrote: > Well POSIX has worked for me since the days of Xenix and System V. Well, most of the goofy time zone changes were all *before* that. But there's at least one that happened more recently unicorn:~$ TZ=EST5EDT date -d '2006-03-12 +4 hou

Re: Found a liar

On Tue, Dec 05, 2023 at 12:52:27PM +0200, y...@vienna.at wrote: > BECAUSE: > sudo apt remove zsh > and your box doesn 't work any longer as you want it to work What is the actual error/problem you experienced?

Re: ntpsec as server questions

On Mon, Dec 04, 2023 at 03:19:33PM -0500, gene heskett wrote: > On 12/4/23 07:17, Greg Wooledge wrote: > > ls -hal /etc/localtime > > Aha! You found it, but how do I change it? > root@mkspi:/etc# cat timezone > America/New_York > root@mkspi:/etc# ls -hal /etc/localtime >

Re: ntpsec as server questions

On Mon, Dec 04, 2023 at 02:11:51PM -0500, gene heskett wrote: > That leave the localtime error pretty much up to the date command, or is > there something else screwing with this? Where ALL in this chain does > /etc/timezone get used, which is currently set to: > America/New_York ls -ld /etc/*time

Re: ntpsec as server questions

On Tue, Dec 05, 2023 at 12:01:35AM +0700, Max Nikulin wrote: > On 04/12/2023 23:34, Greg Wooledge wrote: > > > WTH? Where is that false 12 hour offset coming from? > > There is no 12 hour offset. One is being reported in 24-hour time, and > > the other in 12-hour time (i

Re: ntpsec as server questions

On Mon, Dec 04, 2023 at 10:55:47AM -0500, gene heskett wrote: > root@mkspi:/etc# chronyc sources > 210 Number of sources = 1 > MS Name/IP address Stratum Poll Reach LastRx Last sample > > === > ^* coyote.coyote.den

Re: systemd-journald log location

On Mon, Dec 04, 2023 at 11:46:23AM +, Adam Weremczuk wrote: > Is it a good idea to move it from /run/log/journal to e.g. /var/journal-log? > > I can't find a suitable option in /etc/systemd/journald.conf If you want to enable persistent journal storage (which by the way has become the default

Re: ntpsec as server questions

On Mon, Dec 04, 2023 at 05:55:25AM -0500, Pocket wrote: > On 12/4/23 03:58, gene heskett wrote: > > I have this printer getting its time info from this machine's ntpsec but > > the chrony in the printer is ignoring /etc/timezone, stuck in PST or 4 > > hours behind me when comparing the output of "d

Re: ntpsec as server questions

On Mon, Dec 04, 2023 at 06:32:38AM -0500, gene heskett wrote: > On 12/4/23 05:55, Pocket wrote: > > ntpq -p > I don't have that on the printer, it is running chrony. A quick Google search for "chrony equivalent of ntpq" gives me wh

Re: ntpsec as server questions

On Sun, Dec 03, 2023 at 07:42:42PM -0500, gene heskett wrote: > in the docs (thanks for hiding them & doing away with manpages) it says: > --- > To make the DHCP server in the Debian package isc-dhcp-server send NTP > server > information, add a line like the following at an appropriate place:

Re: Telnet

On Sun, Dec 03, 2023 at 11:52:51AM -0700, Charles Curley wrote: > On Sun, 3 Dec 2023 17:00:44 +0100 > Marco Moock wrote: > > > > > > > How do you find 1994? It seems to be a mail from yesterday: > > > > For me it sounded like a joke. > > > > Telnet is unencrypted (although it is possible to

Re: packages listed vs. apt-rdepends --follow=Depends ...

On Sat, Dec 02, 2023 at 10:28:14PM -0600, David Wright wrote: > On Sat 02 Dec 2023 at 13:48:34 (+), Darac Marjal wrote: > > On 02/12/2023 04:22, Greg Wooledge wrote: > > apt-get has the side effect of installing the packages on the > > connected system. > > Not

Re: Non-delivery reports from postmas...@ewetel.de

On Sat, Dec 02, 2023 at 09:41:10PM +, Andy Smith wrote: > It should have gone to Debian's mailing list software, so > that the rejection could have been automatically handled. > > It doesn't seem to be happening any more so perhaps it was, or the > Debian listmasters disabled the user's subscr

Re: Telnet

On Sat, Dec 02, 2023 at 05:01:37PM +0100, Marco Moock wrote: > Am 02.12.2023 um 09:50:00 Uhr schrieb William Torrez Corea: > > > sudo telnet 192.168.1.1 Also, just for the record, there is *no* need to use sudo here.

Re: packages listed vs. apt-rdepends --follow=Depends ...

On Sat, Dec 02, 2023 at 06:15:17AM +, Albretch Mueller wrote: > They are even using "AI" to mess with > people they target and it doesn't matter if they know well (which they > have actually told me) that you are not a criminally minded dude, a > threat to society, ... and they are quite litera

Re: packages listed vs. apt-rdepends --follow=Depends ...

On Fri, Dec 01, 2023 at 10:01:54PM -0600, David Wright wrote: > On Fri 01 Dec 2023 at 21:55:42 (-0500), Greg Wooledge wrote: > > apt install ./myfile.deb > > That requires you to be online, aka "exposed mode". The OP only > exposes a live USB to the outside wo

Re: packages listed vs. apt-rdepends --follow=Depends ...

On Sat, Dec 02, 2023 at 02:52:25AM +, Albretch Mueller wrote: > direct dependencies of packages which haven't been downloaded, > install. I need to download those packages. > These should be a straightforward way to do that or an easy hack. I'm still struggling to figure out what the X is in

Re: time question, as in ntp?

ing restored during startup. There are *lots* of ways a file could be copied and retain the mtime of the original file. "cp -a" is one of them. unicorn:~$ cp -a .bashrc copy-of-bashrc; ls -lad .bashrc copy-of-bashrc; date -rwxr-xr-x 1 greg greg 3329 Nov 12 08:28 .bashrc* -rwxr-xr-x 1 greg

Re: didn't can use "fdisk"!

into the /etc/default/su file. unicorn:~$ cat /etc/default/su ALWAYS_SET_PATH yes unicorn:~$ su Password: root@unicorn:/home/greg# declare -p PATH declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" root@unicorn:/home/greg#

Re: time question, as in ntp?

On Fri, Dec 01, 2023 at 02:24:20PM -0500, gene heskett wrote: > > > root@mkspi:/etc# nmcli > > > -bash: nmcli: command not found > I do not know the mechanism by which my addition and deletions were done > during boot, I had added the correct data to put eth0 at 192.168.71.100 in > /e/n/i, and had

Re: didn't can use "fdisk"!

On Fri, Dec 01, 2023 at 07:06:58PM +, fuf wrote: > I'm embarrassed because didn't can use "fdisk"! > I work as normal user, open the terminal, switch to "root" user but get: > root@debian:/sbin# fdisk -l > bash: fdisk: command not found https://wiki.debian.org/NewInBuster#Changes Or the tl;d

Re: time question, as in ntp?

On Fri, Dec 01, 2023 at 08:20:57AM -0500, gene heskett wrote: > You claim I don't have to do anything to that printer machine, so I > installed the ICC server here. I have done zip to the dhcpd.conf which looks > as it it is fully disabled. Assuming I want a pool of 16 addresses, say from > 192.168

Re: time question, as in ntp?

On Thu, Nov 30, 2023 at 08:33:47PM -0500, gene heskett wrote: > This machine has a working ntp On Thu, Nov 30, 2023 at 09:05:17PM -0500, gene heskett wrote: > let me clarify: This buster machine acting like a 3d printer does NOT have > dhcpcd installed. No trace of it in /etc Only dhcp. OK, scre

Re: Could/should you set Dir::Cache::{pkgcache, srcpkgcache} = ""; if all you are doing is locally downloading dependencies of an installation package?

On Thu, Nov 30, 2023 at 04:52:01PM -0600, David Wright wrote: > BTW could you not write part of your post in the Subject line: > in order to respond to that specific part of the post, the > replier has either to top post, or paste the Subject line > back into the correct place. That's ignoring the

Re: used vs. unused packages installed

On Thu, Nov 30, 2023 at 04:06:06PM -0600, Mike McClain wrote: > Is there any way to determine which packages are used of the many > that come with an install? My first thought is that popularity-contest should be able to tell you this, because it's able to tell *Debian* which packages are "old

Re: time question, as in ntp?

On Thu, Nov 30, 2023 at 02:06:16PM -0500, gene heskett wrote: > What I just found is /etc/dhcp/dhclient.conf, which if you read it, contains > some examples at the bottom of it, such as: > -- > #alias { > # interface "eth0"; > # fixed-address 192.5.5.213; > # option subnet-mask 2

Re: time question, as in ntp?

On Thu, Nov 30, 2023 at 04:12:48PM +, Andy Smith wrote: > Once you've got your networking sorted out and you are setting up an > NTP server, your next issue will be that one NTP server isn't > enough: > > > https://www.ntp.org/ntpfaq/ntp-s-algo-real/#532-why-should-i-have-more-than-one-cl

Re: time question, as in ntp?

> On 30/11/2023 17:15, gene heskett wrote: > > I want to put it at 192.168.71.100/24. How do I do that in > > /etc/dhcpcd.conf? This is already in /etc/hosts like this: You're confusing the DHCP server and the DHCP client. People have told you that you must either configure the static IP on the h

Re: time question, as in ntp?

On Thu, Nov 30, 2023 at 09:39:04AM +, Bonno Bloksma wrote: > I never used the network manager as that is more work for me, I have no idea > how that works even. ;-) You and me both. > -=-=-=-=-=-=- > $ cat /etc/network/interfaces > # This file describes the network interfaces available on yo

Re: time question, as in ntp?

On Wed, Nov 29, 2023 at 01:52:46PM -0500, gene heskett wrote: > On 11/29/23 13:20, John Hasler wrote: > > Install chrony. But first fix that address. > > How, John? QIDI is afraid of enabling full net access because it might > overwrite some of their special stuff. Right now its running armbian b

Re: time question, as in ntp?

On Wed, Nov 29, 2023 at 01:17:18PM -0500, Dan Purgert wrote: > 'ntpd' I think (or is it systemd-timed or something like that nowadays?) Gene's system is running some derivative of buster (Debian 10). If I remember correctly, buster did not enable systemd-timed by default. The "ntp" package should

Re: texinfo infofiles

On Sat, Nov 25, 2023 at 09:44:59AM +0100, Chielllo Boss wrote: > A new install of debian does not contain texinfo by default. > After installing texinfo, many of the info files are missing. > Only after reinstalling a package, the corresponding info file will be > installed. I don't believe this i

Re: Modify user PATH in GNOME in Debian 12

On Sat, Nov 25, 2023 at 10:28:13AM +0700, Max Nikulin wrote: > SDDM does read /etc/profile and ~/.profile when starting a user session: > https://sources.debian.org/src/sddm/0.20.0-1/data/scripts/Xsession/ Interesting. I wondered whether that might be a Debian patch, since I couldn't see mention

Re: Modify user PATH in GNOME in Debian 12

On Fri, Nov 24, 2023 at 11:51:53PM +0700, Max Nikulin wrote: > I guess you are not running Gnome. I'm using fvwm. > A window manager still might do some magic by calling "systemctl > set-environment". My impression is that nowadays an application spawned by > systemd is not something unusual. Th

<    1   2   3   4   5   6   7   8   9   10   >