Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #264096

Re: time question, as in ntp?

From gene heskett <gheskett@shentel.net>
Newsgroups linux.debian.user
Subject Re: time question, as in ntp?
Date 2023-12-02 11:50 +0100
Message-ID <HGvJn-ay77-11@gated-at.bofh.it> (permalink)
References (7 earlier) <HG1BD-ae4z-7@gated-at.bofh.it> <HG2o1-af0h-1@gated-at.bofh.it> <HG6hX-aiZL-1@gated-at.bofh.it> <HGgqZ-ap1M-5@gated-at.bofh.it> <HGjfb-aqHo-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 12/1/23 16:22, gene heskett wrote:
> On 12/1/23 13:27, Andrew M.A. Cater wrote:
>> On Fri, Dec 01, 2023 at 07:30:35AM +0000, Andy Smith wrote:
>>> Hello,
>>>
>>> On Thu, Nov 30, 2023 at 10:24:35PM -0500, gene heskett wrote:
>>>
>> <snip>
>>
>> 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 this context - and the OS and versions
>> they are running.
>>
>> List the functions you want each to have.
>>
>> As others have noted, it's REALLY hard to work out what you're doing.
>>
>> If machines and printers expect DHCP, then you're going to have to
>> amend files. Do back up the files you change.
>>> 1. There is nothing in Debian that ever overwrites the
>>>     /etc/network/interfaces file. But you aren't running Debian on
>>>     this machine, so we are all having difficulty helping you.
>>>     Because this is DEBIAN-user.
> 
> I'm well aware of that Andy, but TBH, this list may be the deepest pool 
> of knowledgeable people on the planet, most of my machines are running 
> debian. Those that are running buster have been stuck as the switch to 
> python 3 with bullseye broke linuxcnc.  Thats now been fixed and has 
> been for a while but I've had my own projects that took priority.  There 
> will not be any spinning rust here when I do update to bookworm or trixie.
> 
>> As ever, our collective expertise here is primarily Debian - we have no
>> clue what a derived distribution may or may not do.
> 
> There is also an overtone of NIH here. These programs are tools and one 
> does his (or her) best thinking well outside the box at times.
> 
>>> 2. All you've described is a line in a file which says, "Network is
>>>     managed by NetworkManager". There is NO indication WHICH piece of
>>>     software put that line there, it really could be anything.
>>>     Because you aren't running Debian. Since NetworkManager can be
>>>     set up to run arbitrary commands, it certainly COULD be YOUR
>>>     setup of NetworkManager. Or something else entirely different.
>>>     It's nothing in Debian, though.
>>>
>>>>> Then you are incompatible with software you are trying to run. Your
>>>>> options:
>>>>> - do not allow scripts coming with klipper or its installer to touch
>>>>> network configuration
> 
> They never have, they just use it. And I've used up my patience in 
> explaining that and being mostly ignored.
> 
>>>>> - setup a DHCP server in your network and provide to 3d wizards
>>>>> environment they expect.
>>>>>
>>
>> "Su and say" is not great: running third party scripts on non-Debian 
>> systems
>> and you get to keep both pieces unless you undersand what kiauh and 
>> Klipper
>> are doing, be careful.
>>
>>>> Again, Max, its your way or the hiway. I'd be willing to guess that my
>>>> network experience goes back at least a decade before your first 
>>>> class in cs
>>>> 101. /etc/hosts files worked in 1990 then as now, we just have to 
>>>> get the
>>>> dhcp crap out of the way.  And you and your insistence on using dhcp 
>>>> which
>>>> has never given me a stable address are definitely NOT helping.
>>>
>>> This like some sort of farce.
>>>
>>> You have an operating system hard-coded to use DHCP, but you won't
>>> use DHCP, so it doesn't work. You can't work out how to make it not
>>> want DHCP; you won't ask the people who made it how; instead you ask
>>> us completely uninvolved folks how to do it. When we tell you to
>>> configure it for static networking you say you can't because it
>>> wants DHCP. When we say use DHCP then, you say, "oh I see it's your
>>> way or the hiway, I'll have you know I was crafting IP packets from
>>> raw bean sprouts before you kids ever drew breath!"
>>>
>>> So would I be correct in saying that you want US to work out how to
>>> do this thing in software we don't use and that's off-topic here,
>>> and that's the only answer you'll accept?
>>>
>>> Or have I misunderstood and there is some other direction you would
>>> like to go with this?
>>>
>>> Thanks,
>>> Andy
>>>
>>
>> It does seem to be a problem on this list that we can't always get
>> clear explanations 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 TLM 4.19.0-25-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.289-2
> (2023-08-08) x86_64 GNU/Linux
> Running on an off-lease Dell Optiplex computer.
> 
> 2. A 4 axis mill sold by grizzly as the G0704 running on another 
> off-lease Dell, named go704, using an uptodate buster, uname -a=
> Linux GO704 4.19.0-25-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.289-2 
> (2023-08-08) x86_64 GNU/Linux
> also using linuxcnc.
> 
> 3. Another 4 axis gantry style mill sold as the 6040, also running 
> buster with a rt kernel and linuxcnc on another off-lease Dell. uname -a=
> Linux sixty40 4.19.0-25-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.289-2 
> (2023-08-08) x86_64 GNU/Linux
> 
> 4. Another lathe, a bigger Sheldon from the mid WW-II time, running on a 
> raspberry pi 4b, bookworm, uname -a=
> Linux rpi4.coyote.den 6.1.54-rt15 #1 SMP PREEMPT_RT Wed Sep 20 20:36:44 
> AEST 2023 aarch64 GNU/Linux
> and linuxcnc=LinuxCNC/AXIS version 2.10.0~pre0
> 
> All of the above linuxcnc versions are the current master from the 
> linuxcnc.org's buildbot, updated several times a week as I play the 
> canary in a coal mine part looking for showstopper bugs. #4 above was 
> the first on the planet to run linuxcnc on a pi.  I did it just to see 
> if I could.  The whole shebang w/o the lathe power, draws 20 watts 
> including the monitor, those Dell's are power pigs at 300 watts counting 
> the monitors.
> 
> #5, and currently offline being rebuilt, is a 3d printer, a creality 
> Ender 5 Plus, already has a bananapi-m5 running an arm64 armbian jammy, 
> a BTT octopus  controller. Stepper/servo's on x&y. is already running 
> the klipper suite of tools.
> 
> #6, a tronxy-400 3d printer with similar state and configuration except 
> it a corexy design.
> 
> #7, a two trees Sapphire 5, after the 3rd controller died, is slowly 
> being rebuilt with the same BTT card and klipper, and is a corexy design.
> 
> #8 is this problem child, unknown controller, some sort of a rockchip 
> board running armbian 64 buster and klippers suite of tools. uname -a=
> Linux mkspi 5.16.20-rockchip64 #trunk SMP PREEMPT Mon Jul 25 01:58:45 
> UTC 2022 aarch64 GNU/Linux. A corexy design.
> 
> There will probably be more of #8, its doing a great job. Faster by x4 
> than any of the others did stock. If I don't miss roll call first. Still 
> have about 5 or 6 years left in the pacemakers battery.
> 
> Like I said, boring.
> 
> Take care and stay well Andy.
> 
> Cheers, Gene Heskett.

And I was sidetracked, and forgot this machine, a huge tower case with 
an asus Z370-A II mobo, 6 core low power i5,  32gigs of dram, and 6 or 7 
TB of SSD storage. Running bookworm of course.

My appologies.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 19:00 +0100
  Re: time question, as in ntp? Dan Ritter <dsr@randomstring.org> - 2023-11-29 19:20 +0100
    Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 19:40 +0100
  Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-29 19:20 +0100
    Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-29 20:10 +0100
      Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-29 20:20 +0100
        Re: time question, as in ntp? Jeffrey Walton <noloader@gmail.com> - 2023-11-30 01:30 +0100
      Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 22:00 +0100
        Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 00:00 +0100
          Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:40 +0100
            Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:40 +0100
              Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 11:50 +0100
          Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 03:50 +0100
            Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
  Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-29 19:30 +0100
    Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 20:00 +0100
      Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-29 20:30 +0100
        Re: time question, as in ntp? "Andrew M.A. Cater" <amacater@einval.com> - 2023-11-29 21:00 +0100
          Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:10 +0100
        Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 01:00 +0100
          Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 02:30 +0100
            Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 03:00 +0100
              Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 03:50 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 05:20 +0100
                Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 05:40 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 10:20 +0100
                Re: time question, as in ntp? Karen Lewellen <klewellen@shellworld.net> - 2023-11-30 05:50 +0100
                Re: time question, as in ntp? Karen Lewellen <klewellen@shellworld.net> - 2023-11-30 05:50 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
              Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-11-30 11:50 +0100
          Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 03:40 +0100
            Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 05:10 +0100
              Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 06:00 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 10:20 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 13:20 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 11:20 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-11-30 13:40 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 14:20 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 20:00 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 19:50 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 03:40 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 04:30 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 05:10 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 11:10 +0100
                Re: time question, as in ntp? Curt <curty@free.fr> - 2023-12-01 18:00 +0100
                Re: time question, as in ntp? <tomas@tuxteam.de> - 2023-12-01 19:50 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 20:30 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 05:20 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 11:50 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 12:40 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 16:30 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 20:30 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 20:50 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 23:00 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 23:40 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-02 12:20 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-02 08:50 +0100
                Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-12-01 08:40 +0100
                Re: time question, as in ntp? "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-01 19:30 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 22:30 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-02 03:40 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-02 11:50 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 15:20 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-30 20:10 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 20:20 +0100
                Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 21:00 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-11-30 21:30 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 03:10 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 04:10 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 04:40 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-01 05:20 +0100
                Re: time question, as in ntp? David Wright <deblis@lionunicorn.co.uk> - 2023-12-01 06:10 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 11:50 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 12:00 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 12:30 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 14:30 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 15:40 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 19:50 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 14:30 +0100
                Re: time question, as in ntp? Dan Purgert <dan@djph.net> - 2023-12-01 14:50 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 19:50 +0100
                Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-12-01 04:20 +0100
                Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-11-30 15:20 +0100
      Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-11-30 17:20 +0100
        Re: time question, as in ntp? Greg Wooledge <greg@wooledge.org> - 2023-11-30 19:10 +0100
          Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-01 02:40 +0100
        Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-01 17:30 +0100
          Re: time question, as in ntp? Andy Smith <andy@strugglers.net> - 2023-12-01 21:50 +0100
          Re: time question, as in ntp? Charles Curley <charlescurley@charlescurley.com> - 2023-12-02 00:10 +0100
            Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-02 17:40 +0100
              Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-04 04:10 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-04 05:40 +0100
                Re: time question, as in ntp? Max Nikulin <manikulin@gmail.com> - 2023-12-04 11:10 +0100
                Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-12-04 10:50 +0100
                Re: time question, as in ntp? Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-04 15:40 +0100
                Re: time question, as in ntp? <tomas@tuxteam.de> - 2023-12-04 15:40 +0100
                Re: time question, as in ntp? John Hasler <john@sugarbit.com> - 2023-12-04 16:00 +0100
                Re: time question, as in ntp? Tom Dial <tddial@comcast.net> - 2023-12-05 09:40 +0100
  Re: time question, as in ntp? Lee <ler762@gmail.com> - 2023-11-29 20:20 +0100
    Re: time question, as in ntp? gene heskett <gheskett@shentel.net> - 2023-11-29 22:20 +0100

csiph-web