Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263943 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-11-29 19:00 +0100 |
| Last post | 2023-11-29 22:20 +0100 |
| Articles | 20 on this page of 100 — 17 participants |
Back to article view | Back to linux.debian.user
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
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-12-01 03:40 +0100 |
| Message-ID | <HG1BD-ae4z-7@gated-at.bofh.it> |
| In reply to | #263995 |
On 01/12/2023 01:44, gene heskett wrote: > > /e/n/i waa replaced, and nothing in an ip a or ip r was changed. [...] > On 11/30/23 07:31, Max Nikulin wrote: >> May it be that klipper-related "optimizers" add some script? >> > klipper runs fine on several other bananapi-m5 here, w/o any special > treatment [...] > root@mkspi:/# journalctl -b > /root/xindi/src/mks_wpa_cli.cpp: 416 > Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: > Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-NETWORK-NOT-FOUND > Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] So to install "klipper is just a program" you run some scripts that overwrite /etc/network/interfaces and you blame NetworkManager and some other stuff instead. Good luck in your attempts to find pieces of your "3d" network configurator in cron tasks, all kinds of init scripts, and systemd units. It is completely unrelated to Debian. > which requires it get rid of the 169.254.nnn.nnn its using now. This case 169.254.x.y IPv4LL addresses is a manifestation of another trouble. These addresses can coexist with 192.168.x.y addresses. Do not concentrate on link local addresses. > I don't want or need a dhcp-server. 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 - setup a DHCP server in your network and provide to 3d wizards environment they expect.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 04:30 +0100 |
| Message-ID | <HG2o1-af0h-1@gated-at.bofh.it> |
| In reply to | #264012 |
On 11/30/23 21:37, Max Nikulin wrote: > On 01/12/2023 01:44, gene heskett wrote: >> >> /e/n/i waa replaced, and nothing in an ip a or ip r was changed. > [...] >> On 11/30/23 07:31, Max Nikulin wrote: >>> May it be that klipper-related "optimizers" add some script? The classic NIH syndrome, advertized even. >>> >> klipper runs fine on several other bananapi-m5 here, w/o any special >> treatment > [...] >> root@mkspi:/# journalctl -b >> /root/xindi/src/mks_wpa_cli.cpp: 416 >> Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: >> Jan 02 02:56:20 mkspi bash[1443]: CTRL-EVENT-NETWORK-NOT-FOUND >> Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] > > So to install "klipper is just a program" you run some scripts that > overwrite /etc/network/interfaces and you blame NetworkManager and some > other stuff instead. If you would bother to read what I posted, you would have seen that networkmangler claimed credit for that overwritten /e/n/i file. > Good luck in your attempts to find pieces of your "3d" network > configurator in cron tasks, all kinds of init scripts, and systemd > units. It is completely unrelated to Debian. > >> which requires it get rid of the 169.254.nnn.nnn its using now. > > This case 169.254.x.y IPv4LL addresses is a manifestation of another > trouble. These addresses can coexist with 192.168.x.y addresses. Do not > concentrate on link local addresses. > >> I don't want or need a dhcp-server. > > 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 > - setup a DHCP server in your network and provide to 3d wizards > environment they expect. > 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. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-12-01 05:10 +0100 |
| Message-ID | <HG30J-afNe-3@gated-at.bofh.it> |
| In reply to | #264015 |
Klipper runs on OctoPi, a customized Linux distribution. As installed it is set up to use DHCP. You can either install a DHCP server on your network and it will just work, or you can figure out how to modify OctoPi to do things your way. You seem to be banging your head against a wall trying to do the latter. BTW my network experience goes back to bang paths. I'm currently using both hosts files and DHCP. -- John Hasler john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 11:10 +0100 |
| Message-ID | <HG8D7-akvt-1@gated-at.bofh.it> |
| In reply to | #264017 |
On 11/30/23 23:04, John Hasler wrote: > Klipper runs on OctoPi, a customized Linux distribution. As installed > it is set up to use DHCP. You can either install a DHCP server on your > network and it will just work, or you can figure out how to modify > OctoPi to do things your way. You seem to be banging your head against > a wall trying to do the latter. klipper runs on anything armhf or better. OctoPi isn't even on the property here. It only has one address, USB-like from the output of /dev/serial/by-id. Not supported by every controller card maker, but if present, that is a unique string derived from chipid which the stm family of micro's supports. klipper is actually two parts, the controller is reflashed, and the rest of it runs on the pi clone. Mostly python, the housekeeping might run on wintel for all I know. > BTW my network experience goes back to bang paths. I'm currently using > both hosts files and DHCP. I'm not surprised John, I've seen your name here and there for decades. OT: We had some of the bang paths at WDTV, where I was the CE from 1984 to mid 2002. Then we bought a block of 16 addresses. We had a web page online to dialup folks, served by am amiga, writing the code in ARexx long before PHP came out, months before any other tv station in the country had a web page. I wrote much of that ARexx. A do anything language that had hooks into everything in amigados. Bill Hawes, who wrote ARexx was stiffed by commode door, making less than 500$ from sales of the language book he sold himself. We were upset that a very talented coder was screwed so badly and I don't think he ever wrote another byte for free, but he had an empty account on vger for a long time. One thing amigados never had was a cron, so Jim Hines and I wrote EZCron which we published on an amigados list. Instant world wide use. Fun and games and fond memories from 30+ years ago. /OT: Take care and stay well John. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2023-12-01 18:00 +0100 |
| Message-ID | <HGf1T-ao5U-7@gated-at.bofh.it> |
| In reply to | #264017 |
On 2023-12-01, John Hasler <john@sugarbit.com> 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 communities in the Amazon rainforest for email exchange and other uses. A patch to Ian's UUCP was contributed to UUCP Debian Linux package[17] to adapt for the HERMES (High-Frequency Emergency and Rural Multimedia Exchange System) project, which provides UUCP HF connectivity.[18] https://en.wikipedia.org/wiki/UUCP It's experiencing a comeback, it seems!
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2023-12-01 19:50 +0100 |
| Message-ID | <HGgKl-ap85-5@gated-at.bofh.it> |
| In reply to | #264047 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Dec 01, 2023 at 04:55:01PM -0000, Curt wrote: > On 2023-12-01, John Hasler <john@sugarbit.com> 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, oh... my first "Internet" (not in the sense of IP, obviously!) connection was via UUCP. Mail and Usenet. 14.4K modem. Ftpmail to "download" stuff. Times, those. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | John Hasler <john@sugarbit.com> |
|---|---|
| Date | 2023-12-01 20:30 +0100 |
| Message-ID | <HGhn4-apAk-9@gated-at.bofh.it> |
| In reply to | #264050 |
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 john@sugarbit.com Elmwood, WI USA
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-12-01 05:20 +0100 |
| Message-ID | <HG3ap-afVB-1@gated-at.bofh.it> |
| In reply to | #264015 |
On 01/12/2023 10:24, gene heskett wrote: > If you would bother to read what I posted, you would have seen that > networkmangler claimed credit for that overwritten /e/n/i file. 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". I am not familiar with QIDI, kiauth.sh, and similar 3rd party stuff. What I see in your messages are false claims, e.g. that DHCP addresses are unstable. DHCP servers *may* be configured to assign fixed addresses to particular clients.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 11:50 +0100 |
| Message-ID | <HG9fP-akII-3@gated-at.bofh.it> |
| In reply to | #264018 |
On 11/30/23 23:18, Max Nikulin wrote: > On 01/12/2023 10:24, gene heskett wrote: >> If you would bother to read what I posted, you would have seen that >> networkmangler claimed credit for that overwritten /e/n/i file. > > 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". =NetworkManager overwrites /etc/network/interfaces. Sheesh, part of the "slang-guage" for decades. MetworkManager has well earned that alias. I have made it a habit to remove the x attribute of that headache. Funny thing, even as far back as wheezy, absolutely nothing had the chutzpah to log it wasn't executable. Its gradually been made remove-able but early on removing it tore down the system to where it could only be re-installed from the install cd's. It was a solution to a problem we never had unless you were carrying a lappy into ever library on the planet. > I am not familiar with QIDI, kiauth.sh, and similar 3rd party stuff. > > What I see in your messages are false claims, e.g. that DHCP addresses > are unstable. DHCP servers *may* be configured to assign fixed addresses > to particular clients. > My ISP does that, so my exterior net address has been stable for over a decade, but I've tried it 2-3 times in the 2000's and got unstable addresses from the distro versions of dhcp every time. My ISP gives the router a stable address because its linked to the MAC of the router, so while I have 2 interchangeable routers, the backup has cloned its MAC to match, so my net cost to run a web page on this machine is the namecheap 5 year fee of $20 the last time I paid it. But the whole, several gigabyte page was lost a year ago when two quite new, 2T seagates went tits down in the night within 2 days of each other, one was my boot drive, the other vtapes from Amanda. That was the last straw and today 8 machines here have only 2 spinning rust drives remaining. They will be replaced with SSD's when I bring those buster machines up to bookworm or Trixie. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Date | 2023-12-01 12:40 +0100 |
| Message-ID | <HGa2d-ale2-1@gated-at.bofh.it> |
| In reply to | #264025 |
[Multipart message — attachments visible in raw view] — view raw
On Dec 01, 2023, gene heskett wrote: > On 11/30/23 23:18, Max Nikulin wrote: > > [...] > > What I see in your messages are false claims, e.g. that DHCP addresses > > are unstable. DHCP servers *may* be configured to assign fixed addresses > > to particular clients. > > > My ISP does that, so my exterior net address has been stable for over a > decade, but I've tried it 2-3 times in the 2000's and got unstable > addresses from the distro versions of dhcp every time. Your router just renews its lease within the renewal window. If you had no power for a week, then your router would lose its lease, and the IP address would change. That is -- no, your ISP does not reserve your IP address at all. Likewise, a Debian box running isc-dhcp-server (or any of the other myriad of options) will hand out the same address to the same machine forever, provided that machine asks to renew before the lease expires. Note that if we're talking about devices that leave your network, this somewhat goes out the window; because if they happened to join a remote network that happens to share the same subnet, AND that network tells them to use a different IP address (e.g. home was 192.168.1.100, starbucks told your laptop '100' wasn't available), then the laptop MAY request the IP address Starbucks gave when you get back home. -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-12-01 16:30 +0100 |
| Message-ID | <HGdCN-anpf-5@gated-at.bofh.it> |
| In reply to | #264025 |
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". > > =NetworkManager overwrites /etc/network/interfaces. Sheesh, part of the > "slang-guage" for decades. > > MetworkManager has well earned that alias. I have made it a habit to > remove the x attribute of that headache. I asked it because earlier you posted > root@mkspi:/etc# nmcli > -bash: nmcli: command not found 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 not interested in you *speculations*. In a previous episode you blamed NetworkManager in breaking of /etc/resolv.conf. Actually it was you who put incorrect info into NetworkManager configuration: https://lists.debian.org/msgid-search/ZT-gj6fkYCbNzPSs@wooledge.org
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 20:30 +0100 |
| Message-ID | <HGhn4-apAk-7@gated-at.bofh.it> |
| In reply to | #264038 |
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 >>> "networkmangler" overwrites "/e/n/i". >> >> =NetworkManager overwrites /etc/network/interfaces. Sheesh, part of >> the "slang-guage" for decades. >> >> MetworkManager has well earned that alias. I have made it a habit to >> remove the x attribute of that headache. > > I asked it because earlier you posted > >> root@mkspi:/etc# nmcli >> -bash: nmcli: command not found > > 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 not interested in you > *speculations*. > > In a previous episode you blamed NetworkManager in breaking of > /etc/resolv.conf. Actually it was you who put incorrect info into > NetworkManager configuration: > https://lists.debian.org/msgid-search/ZT-gj6fkYCbNzPSs@wooledge.org 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 deleted the line saying it was managed by networkmanager. The evidence I have is that the original file was restored, has only lo and the line giving credit to networkmanager was restored, my additions were gone. Based on the evidence I can see, what else am I supposed to think? Maybe something in armbian-config overwrote it. IDK, but thats the clues I have. But I have NOT found ambian-config yet. > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-12-01 20:50 +0100 |
| Message-ID | <HGhGp-apGC-1@gated-at.bofh.it> |
| In reply to | #264055 |
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 deleted the line saying it was managed by networkmanager.
> The evidence I have is that the original file was restored, has only lo and
> the line giving credit to networkmanager was restored, my additions were
> gone. Based on the evidence I can see, what else am I supposed to think?
What you showed us above, where you tried to run nmcli, was perfect.
It contains your shell prompt (which tells us your username and hostname
and current working directory), the command you ran, and its output.
Hell, we even learned you're in a bash login shell, which is not
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, so we'd know *when* it was altered, if your
system clock is accurate (which it might not be, given the thread's
original subject).
The mtime might not be useful to us, but it might be more useful to *you*,
as you might know what time the system clock had the last time you ran
that 'kiauh' script or whatever it was. Maybe that's what undoes your
changes?
If it turns out the modification took place in the wee hours of the
morning, then it's more likely a cron job or systemd timer kicks off
the process that undoes the changes.
If /e/n/i turns out to be a symbolic link on your system, then its
target may give us some hints about which program is messing with it.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 23:00 +0100 |
| Message-ID | <HGjIe-aqQI-3@gated-at.bofh.it> |
| In reply to | #264060 |
On 12/1/23 14:42, Greg Wooledge wrote: > 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 deleted the line saying it was managed by networkmanager. >> The evidence I have is that the original file was restored, has only lo and >> the line giving credit to networkmanager was restored, my additions were >> gone. Based on the evidence I can see, what else am I supposed to think? > > What you showed us above, where you tried to run nmcli, was perfect. > It contains your shell prompt (which tells us your username and hostname > and current working directory), the command you ran, and its output. > Hell, we even learned you're in a bash login shell, which is not > immediately relevant, but is a nice detail to have. > > What we need is more of that. > > ls -ld /etc/network/interfaces root@mkspi:/etc# ls -ld /etc/network/interfaces -rwxr-xr-x 1 root root 106 Jul 24 19:10 /etc/network/interfaces The rest of the files mentioned here have an mtime about a day later but 7 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, if your > system clock is accurate (which it might not be, given the thread's > original subject). The clock is apparently restarted from midnight 12/1/2022 at every reboot. And I don't know if the rockchip64 has a clock. Most of the pi's don't. Since this is 12/1/2023, saying it about a year out of date is a pretty accurate statement. > The mtime might not be useful to us, but it might be more useful to *you*, > as you might know what time the system clock had the last time you ran > that 'kiauh' script or whatever it was. Maybe that's what undoes your > changes? > > If it turns out the modification took place in the wee hours of the > morning, then it's more likely a cron job or systemd timer kicks off > the process that undoes the changes. > 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. > If /e/n/i turns out to be a symbolic link on your system, then its > target may give us some hints about which program is messing with it. > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2023-12-01 23:40 +0100 |
| Message-ID | <HGkkV-arj6-7@gated-at.bofh.it> |
| In reply to | #264069 |
On Fri, Dec 01, 2023 at 04:57:25PM -0500, gene heskett wrote:
> root@mkspi:/etc# ls -ld /etc/network/interfaces
> -rwxr-xr-x 1 root root 106 Jul 24 19:10 /etc/network/interfaces
OK. Now we have something to work with, at least.
> date
> Tue 03 Jan 2023 06:44:56 AM PST
> 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 have everything straight.
At some point in the recent past, you edited /e/n/i. Then you rebooted,
an undetermined amount of time later, and after the reboot, the file had
been restored to the state shown above. Yes?
If we assume the file wasn't changed *prior* to the reboot, then something
in the operating system startup must be overwriting this file.
If your assertion about the clock being set to 2022-12-01 each boot is
correct, then the timestamp on the file is *not* coming from the system
clock. It's probably coming from whatever "gold copy" of the file is
being 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 greg 3329 Nov 12 08:28 copy-of-bashrc*
Fri Dec 1 17:05:52 EST 2023
unicorn:~$
Of course there are many others. Extracting a .tar.gz archive, for
example, is another way to do it.
You could look through the system startup stuff, wherever that is on
this operating system, and see if you find anything about restoring
factory default configuration files.
If you can't find it, the people who support this operating system might
be able to tell you exactly what's happening, and why. You really ought
to talk to them.
As a side note, copying a "gold standard" /e/n/i file which happens to
contain a comment *saying* that it's from Network Manager would retain
that comment, possibly leading to some confusion. One might argue that
the OS vendor should have replaced the comment with something more
accurate. (E.g. "This interfaces file is copied from ____ to /etc/network
at boot time. Do not edit this file in /etc/network. If you need to
modify it, edit it in ____ instead, but you do so at your own risk.")
That's another thing you could talk to the OS support people about,
assuming my guesswork holds up.
***********
Now let's talk about NTP. Originally you asked about installing and
configuring an NTP service on this printer. And you had some concerns
because you didn't know how to assign a static IP address to it.
However, you've stated a few times now that you *are* able to ssh into
it, from some other host on your network.
The fact that you can ssh into it means that it's got a working IP
address (either v4 or v6), and that your ssh client is able to determine
that IP address and connect to it. So, either it's already got a static
address, or your ssh client configuration is very clever, and knows
how to determine the printer's dynamic address.
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*, and
specifically, it should be able to contact an NTP server on your network
to synchronize its system clock.
So all you should have to do is:
1) Determine which host on your network will act as your NTP server. Get
an NTP package installed and running on that host, and configure it
to allow connections from your LAN. You may select more than one if
you like.
2) Make sure the NTP server(s) are getting their time synced correctly,
most likely from public NTP sources on the Internet.
3) Install an NTP package on the printer, and configure it to use your
designated local NTP server(s).
4) Ensure that the NTP services all start at boot time, and don't get
their configuration files overwritten or anything like that.
If some part of this doesn't work, then please report the exact nature
of the failure, with details (commands and their output). Example
commands that would be useful in debugging might include:
date
ntpq -p
systemctl status ntp # or some sysv-rc equivalent
ls -ld /etc/ntp.conf
cat /etc/ntp.conf
journalctl -u ntp # if it's systemd-based; otherwise:
grep ntpd /var/log/syslog | tail -n20
You get the idea, I hope. Your logs might be in some other location.
Find them. Read them.
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-12-02 12:20 +0100 |
| Message-ID | <HGwcp-ayvP-1@gated-at.bofh.it> |
| In reply to | #264071 |
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*, and > specifically, it should be able to contact an NTP server on your network > to synchronize its system clock. My guest is that a 169.254.x.y address allows to connect from other hosts that belongs to the same network segment, but the router discards outgoing packets instead of applying masquerading rules. Or the host does not send non-local packets because it does not know a router and no hosts respond to ARP requests. Having IPv4LL addresses, it is possible to connect to other hosts withing the same subnet using multicast mDNS (name.local) or LLMNR name resolution. Actually having a spare ethernet port or a WiFi card that supports hot spot mode, it is possible to create a subnet for this 3d printer. NetworkManager allows to create a "shared" connection with a few clicks. It launches dnsmasq as DNS and DHCP server. The only downside is NAT, so ssh to the printer will require to connect the host sharing network. However it will solve the NTP issue.
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2023-12-02 08:50 +0100 |
| Message-ID | <HGsVb-awtx-1@gated-at.bofh.it> |
| In reply to | #264055 |
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 not interested in you >> *speculations*. [...] > 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 deleted the line saying it was managed by > networkmanager. The evidence I have is that the original file was > restored, has only lo and the line giving credit to networkmanager was > restored, my additions were gone. Based on the evidence I can see, what > else am I supposed to think? The only problem is that neither upstream sources nor debian patches in buster or bookworm contain the "Network is managed" text as in (from an earlier message): > root@mkspi:/# cat /etc/network/interfaces > source /etc/network/interfaces.d/* > # Network is managed by Network manager<-this line I had removed > auto lo > iface lo inet loopback So ask the 3d printer vendor why you see this misleading line and why ifupdown and NetworkManager are broken. I had a hope that you would at least check list of processes, systemd units, init scripts for something suspicious. Instead I still see speculations again and attempts to blame NetworkManager developers for no reason. Have you tried some online translator to guess meaning of the following? > Jan 02 02:56:20 mkspi bash[1443]: 已获取到了扫描的结果 > Jan 02 02:56:20 mkspi bash[1443]: [Dec 10 2022][15:22:28] /root/xindi/src/mks_wpa_cli.cpp: 416 > Jan 02 02:56:20 mkspi bash[1443]: 收到wpa回调信息: > Jan 02 02:56:20 mkspi bash[1443]: WPS-AP-AVAILABLE Have you find files containing these messages?
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2023-12-01 08:40 +0100 |
| Message-ID | <HG6hX-aiZL-1@gated-at.bofh.it> |
| In reply to | #264015 |
Hello, On Thu, Nov 30, 2023 at 10:24:35PM -0500, gene heskett wrote: > On 11/30/23 21:37, Max Nikulin wrote: > > So to install "klipper is just a program" you run some scripts that > > overwrite /etc/network/interfaces and you blame NetworkManager and some > > other stuff instead. > If you would bother to read what I posted, you would have seen that > networkmangler claimed credit for that overwritten /e/n/i file. 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. 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 > > - setup a DHCP server in your network and provide to 3d wizards > > environment they expect. > > > 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 -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | "Andrew M.A. Cater" <amacater@einval.com> |
|---|---|
| Date | 2023-12-01 19:30 +0100 |
| Message-ID | <HGgqZ-ap1M-5@gated-at.bofh.it> |
| In reply to | #264022 |
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. > As ever, our collective expertise here is primarily Debian - we have no clue what a derived distribution may or may not do. > 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 > > > - 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 >
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-12-01 22:30 +0100 |
| Message-ID | <HGjfb-aqHo-3@gated-at.bofh.it> |
| In reply to | #264048 |
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. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
[toc] | [prev] | [next] | [standalone]
Page 3 of 5 — ← Prev page 1 2 [3] 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web