ot me some interesting results:
> >
> > ● systemd-timesyncd.service - Network Time Synchronization
> >Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
> > vendor preset: enabled)
> > Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
On 08/03/2024 07:17, gene heskett wrote:
I have NDI how to extract chrony's logs from journalctl.
- man journalctl,
- docs listed on the systemd web site.
@mkspi:/etc/init.d$
yet timedatectl is still there and shows:
mks@mkspi:/etc/init.d$ timedatectl
Local time: Thu 2024-03-07 11:15:53 EST
Universal time: Thu 2024-03-07 16:15:53 UTC
RTC time: Thu 2024-03-07 11:04:39
Time zone: America
printer is arm stuff, its old armbian buster vintage.
> > > mks@mkspi:/etc/init.d$ sudo apt purge systemd-timesyncd
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > Package 'systemd-timesyncd' is n
On 3/7/24 14:16, Roy J. Tellason, Sr. wrote:
On Wednesday 06 March 2024 12:42:12 pm Greg Wooledge wrote:
How do I get the RTC to agree with the right time?
"hwclock -w" to copy the system clock to the hardware clock (RTC). This
should also be done during shutdown, but it doesn't
Local time: Thu 2024-03-07 11:15:53 EST
Universal time: Thu 2024-03-07 16:15:53 UTC
RTC time: Thu 2024-03-07 11:04:39
Time zone: America/New_York (EST, -0500)
System clock synchronized: no
NTP service: inactive
RTC
On Thu, Mar 07, 2024 at 02:33:05PM -0500, Roy J. Tellason, Sr. wrote:
> On Thursday 07 March 2024 09:02:44 am Teemu Likonen wrote:
> > systemctl status systemd-timesyncd.service
>
> This got me some interesting results:
>
> ● systemd-timesyncd.service - Network Time Synchr
Roy J. Tellason, Sr. wrote:
> I don't ordinarily shut this machine down for the most part. Every once in a
> while all of my swap partition gets filled up, and then there's this
> continuous hard drive activity that I'm assuming is what they mean by
> "thrashing". The only option at that
On Thursday 07 March 2024 09:02:44 am Teemu Likonen wrote:
> systemctl status systemd-timesyncd.service
This got me some interesting results:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor pre
On Wednesday 06 March 2024 12:42:12 pm Greg Wooledge wrote:
> > How do I get the RTC to agree with the right time?
>
> "hwclock -w" to copy the system clock to the hardware clock (RTC). This
> should also be done during shutdown, but it doesn't hurt to do it now.
newly installed, 0 to remove and 2 not upgraded.
> mks@mkspi:/etc/init.d$
> yet timedatectl is still there and shows:
> mks@mkspi:/etc/init.d$ timedatectl
> Local time: Thu 2024-03-07 11:15:53 EST
>Universal time: Thu 2024-03-07 16:15:53 UTC
>
On 3/7/24 11:18, Jeffrey Walton wrote:
On Thu, Mar 7, 2024 at 8:44 AM wrote:
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
[...]
Now, how do I assure timedatectl stays stopped on a reboot? [...]
I'll have to leave this to others more fluent in systemd-ish.
Mask the
On 3/7/24 10:59, Greg Wooledge wrote:
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
So I purged ntpsec and re-installed chrony which I had done once before with
no luck but this time timedatectl was stopped and it worked!
Now, how do I assure timedatectl stays stopped
On Thu, Mar 7, 2024 at 8:44 AM wrote:
>
> On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
>
> [...]
> Now, how do I assure timedatectl stays stopped on a reboot? [...]
>
> I'll have to leave this to others more fluent in systemd-ish.
Mask the systemd-timesyncd service. Masking is
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
> So I purged ntpsec and re-installed chrony which I had done once before with
> no luck but this time timedatectl was stopped and it worked!
>
> Now, how do I assure timedatectl stays stopped on a reboot?
Which versi
* 2024-03-07 08:31:16-0500, gene heskett wrote:
> So I purged ntpsec and re-installed chrony which I had done once before
> with no luck but this time timedatectl was stopped and it worked!
>
> Now, how do I assure timedatectl stays stopped on a reboot? systemd's
> docs are po
On Thu, Mar 07, 2024 at 08:31:16AM -0500, gene heskett wrote:
[...]
> So I purged ntpsec and re-installed chrony which I had done once before with
> no luck but this time timedatectl was stopped and it worked!
great :-)
> Now, how do I assure timedatectl stays stopped on a reboot? [.
to be Big. This option may appear an
unlimited number of times.
Normally, ntpd exits with a message to the system log if the off‐
set exceeds the panic threshold, which is 1000 s by default. This
option allows the time to be set to any value without restric‐
tion; however
On Wed, Mar 06, 2024 at 09:36:56PM -0500, Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> > no place in the ntpsec docs, nor the chrony docs
> > does it show the ability to slam the current time into the SW clock on these
> > arm syst
appear an
unlimited number of times.
Normally, ntpd exits with a message to the system log if the off‐
set exceeds the panic threshold, which is 1000 s by default. This
option allows the time to be set to any value without restric‐
tion; however, this can happen only once. If the threshold
On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> no place in the ntpsec docs, nor the chrony docs
> does it show the ability to slam the current time into the SW clock on these
> arm systems at bootup's first access time.
Traditionally, this was done by the ntpdate comma
Look at the chronyd settime command and the chrony.conf makestep
directive. These are intended for your situation.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
ed to take into account that many of us are
already using a different NTP implementation, besides systemd's.
I can turn either off, but no place in the ntpsec docs, nor the chrony
docs does it show the ability to slam the current time into the SW clock
on these arm systems at bootup's first a
On Wed, Mar 06, 2024 at 05:56:29PM -0500, gene heskett wrote:
> On 3/6/24 12:42, Greg Wooledge wrote:
> > On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> > > sudo timedatectl set-ntp true
> >
> > But *don't* do that if you're using some other NTP program instead of
>
On 3/6/24 12:42, Greg Wooledge wrote:
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
Mine shows:
Local time: Wed 2024-03-06 12:09:44 EST
Universal time: Wed 2024-03-06 17:09:44 UTC
RTC time: Wed 2024-03-06 17:20:53
Time zone: America/New_York
On 3/6/24 13:37, Teemu Likonen wrote:
It seems that you have solved the problem but here is another hint.
"timedatectl" is a good high-level tool for querying and adjusting time
settings. Without command-line arguments it prints a lot of useful info:
$ t
On Wed 06 Mar 2024 at 07:07:36 (-0500), Greg Wooledge wrote:
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting t
On Wed, Mar 6, 2024 at 7:08 AM Greg Wooledge wrote:
>
> On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> > It seems that you have solved the problem but here is another hint.
> > "timedatectl" is a good high-level tool for querying and adjusting time
&
On Wed, Mar 6, 2024 at 12:13 PM Roy J. Tellason, Sr. wrote:
>
> On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote:
> > * 2024-03-06 02:47:06+0800, hlyg wrote:
> >
> > > my newly-installed deb11 for amd64 shows wrong time, it lags behind
> > > corre
On Wed, Mar 06, 2024 at 12:31:46PM -0500, Roy J. Tellason, Sr. wrote:
> Mine shows:
>
> Local time: Wed 2024-03-06 12:09:44 EST
> Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -050
* 2024-03-06 12:31:46-0500, Roy J. Tellason, Sr. wrote:
> Local time: Wed 2024-03-06 12:09:44 EST
> Universal time: Wed 2024-03-06 17:09:44 UTC
> RTC time: Wed 2024-03-06 17:20:53
>Time zone: America/New_York (EST, -0500)
> Network time on: yes
>
On Wednesday 06 March 2024 12:37:09 am Teemu Likonen wrote:
> * 2024-03-06 02:47:06+0800, hlyg wrote:
>
> > my newly-installed deb11 for amd64 shows wrong time, it lags behind
> > correct time by 8 hours though difference between universal and local
> > is ok.
>
>
On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a
* 2024-03-06 02:47:06+0800, hlyg wrote:
> my newly-installed deb11 for amd64 shows wrong time, it lags behind
> correct time by 8 hours though difference between universal and local
> is ok.
It seems that you have solved the problem but here is another hint.
"timedatectl" i
On Tue, Mar 5, 2024 at 7:07 PM hlyg wrote:
>
> [...]
>
> Windows shall not cause problem, i rarely use Windows
>
> i don't know if ntp is running, what's default configuration by deb11
> amd64 installer?
If you are dual booting Linux and Windows, then see
Thank Greg Wooledge! it's solved with your help
i reboot to enter bios, it use UTC
then i change 3rd line of /etc/adjtime to UTC, reboot to take effect,
time is shown correctly now
i am timezone 0800, 8 hours ahead of GMT
both /etc/localtime points to same place
On Tue, Mar 05, 2024 at 08:28:49PM +0800, hlyg wrote:
> Thank Greg Wooledge!
>
> zhou@debian:~$ date
> Wed 06 Mar 2024 04:07:02 AM CST
> zhou@debian:~$ date -u
> Tue 05 Mar 2024 08:07:07 PM UTC
>
> above is from deb11 for i386, it's correct
OK, and your time zone
On 3/5/24 20:28, hlyg wrote:
Thank Greg Wooledge!
zhou@debian:~$ date
Wed 06 Mar 2024 04:07:02 AM CST
zhou@debian:~$ date -u
Tue 05 Mar 2024 08:07:07 PM UTC
above is from deb11 for i386, it's correct
zhou@debian:~$ date
Tue 05 Mar 2024 08:13:23 PM CST
zhou@debian:~$ date -u
Tue 05 Mar 2024
Thank Greg Wooledge!
zhou@debian:~$ date
Wed 06 Mar 2024 04:07:02 AM CST
zhou@debian:~$ date -u
Tue 05 Mar 2024 08:07:07 PM UTC
above is from deb11 for i386, it's correct
zhou@debian:~$ date
Tue 05 Mar 2024 08:13:23 PM CST
zhou@debian:~$ date -u
Tue 05 Mar 2024 12:13:27 PM UTC
above is from
On Wed, 6 Mar 2024 02:47:06 +0800
hlyg wrote:
> wifi connection is good, i suppose both correct time with server
> automatically
Not necessarily. You should install an NTP client if you haven't
already. I suggest systemd-timesyncd.
--
Does anybody read signatures any more?
On Wed, Mar 06, 2024 at 02:47:06AM +0800, hlyg wrote:
> my newly-installed deb11 for amd64 shows wrong time, it lags behind correct
> time by 8 hours though difference between universal and local is ok.
Run the commands "date" and "date -u" and show us the output.
T
my newly-installed deb11 for amd64 shows wrong time, it lags behind
correct time by 8 hours though difference between universal and local is
ok.
i am normal user, i install only from main of deb11 plus wifi adapter
firmware, though i don't install security update. i don't know where i
can
Hi,
On Mon, Feb 19, 2024 at 10:52:16AM +1100, Keith Bainbridge wrote:
> I said sometime in this thread that timeshift (and Back in Time) use hard
> links to create progressive copies of the system. The more I think about how
> hard links reportedly work, I reckon it can't be simply hard
On Thu, Jan 18, 2024 at 01:30:44PM +, c.bu...@posteo.jp wrote:
> Hello,
>
> I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool using
> rsync in the back.
>
> I would like to kindly ask if someone want to contribute to the Dutch
> translation o
Dear Rogerio,
thanks for your offer.
On 2024-01-19 17:16 "Rogerio R. Silva" wrote:
> I could help if there are not enough people working on this.
> Please, let me know.
Portuguese is still at 34%. But Brazilian is complete.
Beside translating untranslated strings there is also a need to
gt;> Em qui., 18 de jan. de 2024 às 13:01, Yuri Musachio <
>>> yuri.musac...@gmail.com> escreveu:
>>>
>>>> Christian, hi!
>>>>
>>>> I will do.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
&g
>> Em qui., 18 de jan. de 2024 às 13:01, Yuri Musachio <
>> yuri.musac...@gmail.com> escreveu:
>>
>>> Christian, hi!
>>>
>>> I will do.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Best,
>>>
&
;> Christian, hi!
>>
>> I will do.
>>
>>
>>
>>
>>
>>
>>
>> Best,
>>
>> On Jan 18 2024, at 8:37 am, c.bu...@posteo.jp wrote:
>>
>> Hello,
>>
>> I am upstream maintainer of "Back In Time" [1] [2]
I'd like to help, too.
Sincerely yours,
Atenágoras
Em qui., 18 de jan. de 2024 às 13:01, Yuri Musachio
escreveu:
> Christian, hi!
>
> I will do.
>
>
>
>
>
>
>
> Best,
>
> On Jan 18 2024, at 8:37 am, c.bu...@posteo.jp wrote:
>
> Hello,
>
>
Christian, hi!
I will do.
Best,
On Jan 18 2024, at 8:37 am, c.bu...@posteo.jp wrote:
> Hello,
>
> I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
> using rsync in the back.
>
> I would like to kindly ask if someone want to contribute to
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the Swedish
translation of that application. The current state of translation is
47%.
We offer a web-based front-
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the Dutch
translation of that application. The current state of translation is
92%.
We offer a web-based front-
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the Catalan
translation of that application. The current state of translation is
92%.
We offer a web-based front-
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the
Portuguese translation of that application. The current state of
translation is 23%.
We offer a web-based front-
ld you like to restore a previous
configuration?
{appName} er ikke konfigureret. Vil du rulle tilbage til en tidligere
opsætning?
Use modification time & size for file change detection.
Brug ændringstid og størrelse til at opdage filændringer
Take a snapshot (checksum mode)
Opret et tilstands-b
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the Danish
translation of that application. The current state of translation is at
28%. Without improvement I need
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want to contribute to the Polish
translation of that application. The current state of translation is at
65%.
We offer a web-based front-
Hello,
I can help with that.
I will start contributing on Webslate as soon as possible.
Thank you,
Iliana Panagopoulou
Στις Τετ 10 Ιαν 2024 στις 2:24 μ.μ., ο/η έγραψε:
>
> Hello,
>
> I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
> using rsync
Hello,
I am upstream maintainer of "Back In Time" [1] [2] a GUI backup tool
using rsync in the back.
I would like to kindly ask if someone want so contribute to the Greek
translation of that application. The current state of translation is at
26%. Some strings are left for t
presentation will be driven by
> > > other needs.
> >
> > If anyone is looking for inspiration, I think what PostgreSQL does is one of
> > the best and most complete implementations I've seen.
>
> I know nothing concerning the datetime type in Oracle.
>
w nothing concerning the datetime type in Oracle.
Postgres stores timestamps as a numbers. Its power is reliable
conversion to client time zone (or between time zones). "timestamp with
time zone" is actually duration since epoch (UTC) and conversion to a
time zone on select.
However stor
On Thu, Dec 07, 2023 at 10:18:44PM -0600, Nicholas Geovanis wrote:
[...]
> All of these considerations are what brought Oracle to create a proprietary
> "datetime" datatype and use it to store all "real" dates/times. If you need
> a different format for display purposes or a human readable
On Fri, Dec 08, 2023 at 09:11:12AM +0700, Max Nikulin wrote:
> On 07/12/2023 23:08, tomas wrote:
> > On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> > > On 07/12/2023 21:22, John Hasler wrote:
> > > > Databases should never store local time.
> >
On Thu, Dec 7, 2023, 8:11 PM Max Nikulin wrote:
> On 07/12/2023 23:08, tomas wrote:
> > On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> >> On 07/12/2023 21:22, John Hasler wrote:
> >>> Databases should never store local time.
> >>
> >&g
On 07/12/2023 23:08, tomas wrote:
On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
On 07/12/2023 21:22, John Hasler wrote:
Databases should never store local time.
There are exceptions when storing UTC instead of local time leads to
undesired consequences.
Heh. There was one
On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> On 07/12/2023 21:22, John Hasler wrote:
> > Databases should never store local time.
>
> I am anticipating a new branch of hot discussion.
>
> There are exceptions when storing UTC instead of local time
On 07/12/2023 21:22, John Hasler wrote:
Databases should never store local time.
I am anticipating a new branch of hot discussion.
There are exceptions when storing UTC instead of local time leads to
undesired consequences.
Planned (future) events may be bound namely to local time. So
William Torrez Corea wrote:
> One page by means of firefox has a latency of 49.9 ms.
>
>
> *How can I improve the latency?*
>
> I want a latency of 0 ms
Every page is different.
You can measure with the developer tools, in the performance
tab.
Things you can try:
- different network
Hi,
>> $ cat /etc/network/interfaces
[...]
>> # The primary network interface
>> allow-hotplug ens32
>> iface ens32 inet static
> Depending on what services your computer runs, you may wish to change
> "allow-hotplug ens32" to "auto ens32".
Thanks that one got by me when I created a new
On 12/4/23 02:43, gene heskett wrote:
So the next question is, is ntpsec serving my time, or utc. This hdware clock
is supposedly set to UTC, but what is ntpsec serving? It s/b serving UTC IMO.
But I'm in the dark here, haven't had to fool with this in the last 24 years.
I'm pretty sure
chronyc tracking
will tell you what time Chrony thinks it is.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Mon, Dec 04, 2023 at 09:30:14AM -0500, Stefan Monnier wrote:
[...]
> It's serving *the* time :-)
Well put :-)
Cheers
--
t
signature.asc
Description: PGP signature
> So I put the dhcpd-server on this machine and it worked exact as Dan said it
> would. Then I enabled ntpsec to serve and thats working to the whole world.
> But the chrony on the printer is stuck in the PST timezone, ignoring the
> contents of /etc/timezone.
In Unix/Linux
On 04/12/2023 11:38, John Hasler wrote:
Max Nikulin wrote:
From my point of view, it should be possible to put a file with
mapping of mac addresses to desired IPs and names to his dd-wrt
router. I expect that dnsmasq is running or can be installed
there. Dnsmasq as a DHCP server on the router
-cable/
CNC machines don't need accurate time. They need precise internal
synchronization but that isn't related to the system clocks. The
default NTP configuration in most Linux distributions will take care of
the system clocks if they have access to the Internet.
I was kidding. However "a
Max Nikulin wrote:
> From my point of view, it should be possible to put a file with
> mapping of mac addresses to desired IPs and names to his dd-wrt
> router. I expect that dnsmasq is running or can be installed
> there. Dnsmasq as a DHCP server on the router should be better than
> maintaining
accurate time. They need precise internal
synchronization but that isn't related to the system clocks. The
default NTP configuration in most Linux distributions will take care of
the system clocks if they have access to the Internet.
I was kidding. However "access to the Internet" is the re
Max Nikulin wrote:
> As to a GPS receiver, it should be doable and 169.254.x.y addresses
> will not be an issue any more. Be careful with cables when connecting
> it however: https://www.wired.com/2012/02/neutrinos-faulty-cable/
CNC machines don't need accurate time. They need precise
On 2023-11-30 19:06, gene heskett wrote:
On 11/30/23 09:14, John Hasler wrote:
Gene writes:
I want to put it at 192.168.71.100/24. How do I do that in
/etc/dhcpcd.conf?
You don't. That file tells the client how to get an ip (among other
things) from the server. The default configuration
On 02/12/2023 05:33, Greg Wooledge wrote:
In either case, the static-ness or dynamic-ness of the address is much
less important than the fact that the address*works*. You are able
to communicate with the printer, using your network.
This means the printer should be able to communicate*back*,
ns of what has *actually* been done.
Andy
That list of machines is long Andy, and possibly boring.
1. The 2nd machine I converted, affectionately known as tlm.coyote.den,
( The Little Monster ), a 7x12 lathe running buster with a real time
kernel and linuxcnc, all uptdate. uname -a=
Linux
On 02/12/2023 02:24, gene heskett wrote:
On 12/1/23 10:27, Max Nikulin wrote:
so I have to repeat it. You *do* *not* have NetworkManager installed
hence it can not overwrite files.
What particular *evidences* do you have that namely NetworkManager
overwrites /etc/network/interfaces? I am
Gene writes:
> Like I said, boring.
Not boring at all. I assume that you also have a desktop or laptop on
that network? If I was running it I would *definitely* be using DHCP.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
expertise on the gpsd email list. But I would
start with the web site, including the how-to on setting up a time
server. https://gpsd.io https://gpsd.io/gpsd-time-service-howto.html
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
> The clock is apparently restarted from midnight 12/1/2022 at every reboot.
> This overwrite was done that way as soon as I could login at the old address
> with ssh so I have to say it was done by network start time in the bootup
> from a 10 second power down.
All right, then. Let's see if I
months newer than the actual time it has ATM,
date
Tue 03 Jan 2023 06:44:56 AM PST
would be an excellent starting point. It would tell us whether your /e/n/i
is a regular file or a symbolic link. If it's a regular file, we would
get the last modified time, so we'd know *when* it was altered
That list of machines is long Andy, and possibly boring.
1. The 2nd machine I converted, affectionately known as tlm.coyote.den,
( The Little Monster ), a 7x12 lathe running buster with a real time
kernel and linuxcnc, all uptdate. uname -a=
Linux TLM 4.19.0-25-rt-amd64 #1 SMP PREEMPT RT
Hello,
On Fri, Dec 01, 2023 at 11:21:05PM +0700, Max Nikulin wrote:
> On 30/11/2023 23:12, Andy Smith wrote:
> > Unless you have a dedicated time source (e.g. GPS receiver, atomic
> > decay source, …)
>
> A nitpick. I am puzzled by the word "decay" in this context
immediately relevant, but is a nice detail to have.
What we need is more of that.
ls -ld /etc/network/interfaces
would be an excellent starting point. It would tell us whether your /e/n/i
is a regular file or a symbolic link. If it's a regular file, we would
get the last modified time
tomas writes:
> Oh, oh... my first "Internet" (not in the sense of IP, obviously!)
> connection was via UUCP.
Likewise.
--
John Hasler ihnp4!stolaf!bungia!foundln!john
j...@sugarbit.com
Elmwood, WI USA
On 12/1/23 10:27, Max Nikulin wrote:
On 01/12/2023 17:42, gene heskett wrote:
On 11/30/23 23:18, Max Nikulin wrote:
On 01/12/2023 10:24, gene heskett wrote:
Then, please, explain clearly what is "networkmangler", what is
"/e/n/i", and what particular evidences you have that namely
On Fri, Dec 01, 2023 at 04:55:01PM -, Curt wrote:
> On 2023-12-01, John Hasler wrote:
> >
> > BTW my network experience goes back to bang paths. I'm currently using
> > both hosts files and DHCP.
>
> In addition to legacy use, in 2021 new and innovative UUCP uses are
> growing [...]
Oh,
On 12/1/23 08:42, Dan Purgert wrote:
On Dec 01, 2023, gene heskett wrote:
[lotsa snipping ... ]
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
On 12/1/23 08:25, Greg Wooledge wrote:
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
On Fri, Dec 01, 2023 at 07:30:35AM +, Andy Smith wrote:
> Hello,
>
> On Thu, Nov 30, 2023 at 10:24:35PM -0500, gene heskett wrote:
>
Gene,
Please do us *all* a favour to try and help you.
Write us out a list of all your machines - and if a printer has an
embedded SBC, it's a machine in
On 2023-12-01, John Hasler wrote:
>
> BTW my network experience goes back to bang paths. I'm currently using
> both hosts files and DHCP.
In addition to legacy use, in 2021 new and innovative UUCP uses are
growing, especially for telecommunications in the HF band, for example,
for
On 30/11/2023 23:12, Andy Smith wrote:
Unless you have a dedicated time source (e.g. GPS receiver, atomic
decay source, …)
A nitpick. I am puzzled by the word "decay" in this context. Electron
transition between energy states in atomic clocks is not decay.
Nuclear decay is hard
On 01/12/2023 17:42, gene heskett wrote:
On 11/30/23 23:18, Max Nikulin wrote:
On 01/12/2023 10:24, gene heskett wrote:
Then, please, explain clearly what is "networkmangler", what is
"/e/n/i", and what particular evidences you have that namely
"networkmangler" overwrites "/e/n/i".
spond to the MAC address of that printer, no
> > response to any other MAC that might come calling.
>
> The pool is for "anyone who comes calling".
>
> Your reserved addresses should be outside the pool.
At one time (or I'm just conflating isc-dhcp-server with som
On Dec 01, 2023, gene heskett wrote:
> [lotsa snipping ... ]
>
> 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
1 - 100 of 5601 matches
Mail list logo
