Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #210698 > unrolled thread
| Started by | Gene Heskett <gheskett@shentel.net> |
|---|---|
| First post | 2019-07-04 03:10 +0200 |
| Last post | 2019-07-07 13:30 +0200 |
| Articles | 20 on this page of 94 — 14 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Assorted arm-buster problems #1 Gene Heskett <gheskett@shentel.net> - 2019-07-04 03:10 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-04 09:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 10:50 +0200
Re: Assorted arm-buster problems - network configuration Felix Miata <mrmazda@earthlink.net> - 2019-07-04 11:30 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 11:50 +0200
Re: Assorted arm-buster problems - network configuration mick crane <mick.crane@gmail.com> - 2019-07-04 12:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 16:50 +0200
Re: Assorted arm-buster problems - network configuration mick crane <mick.crane@gmail.com> - 2019-07-04 19:20 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-05 06:00 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 12:40 +0200
Re: Assorted arm-buster problems - network configuration Jonas Smedegaard <jonas@jones.dk> - 2019-07-05 13:20 +0200
Re: Assorted arm-buster problems - network configuration Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-05 14:50 +0200
Re: Assorted arm-buster problems - network configuration Reco <recoverym4n@enotuniq.net> - 2019-07-05 15:10 +0200
Re: Assorted arm-buster problems - network configuration Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-05 15:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 02:30 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 02:20 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-06 15:50 +0200
Re: Assorted arm-buster problems - network configuration Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-08 14:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-08 15:00 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-08 16:30 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-06 07:30 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 17:50 +0200
Re: Assorted arm-buster problems - network configuration Reco <recoverym4n@enotuniq.net> - 2019-07-04 18:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 19:40 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-04 21:10 +0200
Re: Assorted arm-buster problems - network configuration Tixy <tixy@yxit.co.uk> - 2019-07-04 22:00 +0200
Re: Assorted arm-buster problems - network configuration <tomas@tuxteam.de> - 2019-07-04 22:10 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-04 22:50 +0200
Re: Assorted arm-buster problems - network configuration <tomas@tuxteam.de> - 2019-07-04 22:50 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 11:10 +0200
Re: Assorted arm-buster problems - network configuration Reco <recoverym4n@enotuniq.net> - 2019-07-05 09:00 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-05 11:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 17:20 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-05 19:30 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-05 20:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 13:00 +0200
Re: Assorted arm-buster problems - network configuration Tixy <tixy@yxit.co.uk> - 2019-07-05 13:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 17:40 +0200
Re: Assorted arm-buster problems - network configuration Jonas Smedegaard <jonas@jones.dk> - 2019-07-05 13:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 17:50 +0200
Re: Assorted arm-buster problems - network configuration Jonas Smedegaard <jonas@jones.dk> - 2019-07-05 19:10 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 03:30 +0200
Re: Assorted arm-buster problems - network configuration <tomas@tuxteam.de> - 2019-07-05 13:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 18:00 +0200
Re: Assorted arm-buster problems - network configuration Reco <recoverym4n@enotuniq.net> - 2019-07-05 14:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 20:40 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-06 06:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 10:40 +0200
Re: Assorted arm-buster problems - network configuration Curt <curty@free.fr> - 2019-07-05 11:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 16:30 +0200
Re: Assorted arm-buster problems - network configuration Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-05 15:10 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 02:20 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-05 21:30 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-05 22:20 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-05 22:30 +0200
Re: Assorted arm-buster problems - network configuration <tomas@tuxteam.de> - 2019-07-05 22:50 +0200
Re: Assorted arm-buster problems - network configuration Curt <curty@free.fr> - 2019-07-06 10:20 +0200
Re: Assorted arm-buster problems - network configuration <tomas@tuxteam.de> - 2019-07-06 12:50 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-06 21:40 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-07 08:50 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-08 19:40 +0200
Re: Assorted arm-buster problems - network configuration Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 20:10 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-08 20:50 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-08 21:50 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-08 23:20 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-08 21:20 +0200
Re: Assorted arm-buster problems - network configuration Curt <curty@free.fr> - 2019-07-07 11:00 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-08 19:50 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 03:40 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-06 21:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 00:20 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-07 06:20 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 07:00 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-07 17:10 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-07 09:00 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 13:20 +0200
Re: Assorted arm-buster problems - network configuration Jonas Smedegaard <jonas@jones.dk> - 2019-07-07 14:50 +0200
Re: Assorted arm-buster problems - network configuration Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-07 18:30 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 23:00 +0200
Re: Assorted arm-buster problems - network configuration Reco <recoverym4n@enotuniq.net> - 2019-07-07 22:00 +0200
Re: Assorted arm-buster problems - network configuration Brian <ad44@cityscape.co.uk> - 2019-07-08 20:30 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-04 23:00 +0200
Re: Assorted arm-buster problems - network configuration Lee <ler762@gmail.com> - 2019-07-04 19:50 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-04 22:50 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-05 12:10 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-05 18:10 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-06 03:20 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-06 07:10 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-06 18:10 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 02:40 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 03:40 +0200
Re: Assorted arm-buster problems - network configuration David Wright <deblis@lionunicorn.co.uk> - 2019-07-07 06:30 +0200
Re: Assorted arm-buster problems - network configuration andreimpopescu@gmail.com - 2019-07-07 09:10 +0200
Re: Assorted arm-buster problems - network configuration Gene Heskett <gheskett@shentel.net> - 2019-07-07 13:30 +0200
Page 1 of 5 [1] 2 3 4 5 Next page →
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-04 03:10 +0200 |
| Subject | Re: Assorted arm-buster problems #1 |
| Message-ID | <yfYq5-4sr-1@gated-at.bofh.it> |
On Wednesday 03 July 2019 16:12:31 Reco wrote: And Gene moved. Question unanswered yet. > Hi. > > On Wed, Jul 03, 2019 at 02:57:35PM -0400, Gene Heskett wrote: > > Regardless of what I do, I cannot get rid of the avahi junk in an ip > > a report, so my local 192.168.xx.nn/24 net is the only thing that > > works. pinging a net name like yahoo.com gets me a successful > > address. But no response from yahoo because its sending the ping > > from an avahi based address, which since thats outside of my /24 > > netmask, doesn't get thru the router. > > > > So, how do I get rid of the avahi stuff? > > > > I've a nominally 10 machine 192.168.nn.xx that is 100% static based > > on host files so I want avahi absolutely and totally neutered, > > emasculated, gone Forever plus 100 years at least. > > > > How can I do that? > > Just a friendly advise. Consider moving this to debian-user, as this > particular problem is not ARM-specific. > > Also please consider posting all future similar problems (involving > configuration of a resolver, IP routing and package management) to > debian-user. > > Thank you in advance, Reco 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [next] | [standalone]
| From | andreimpopescu@gmail.com |
|---|---|
| Date | 2019-07-04 09:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yg4c9-7YP-1@gated-at.bofh.it> |
| In reply to | #210698 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 03 iul 19, 21:03:19, Gene Heskett wrote: > On Wednesday 03 July 2019 16:12:31 Reco wrote: > > And Gene moved. Question unanswered yet. > > Hi. > > > > On Wed, Jul 03, 2019 at 02:57:35PM -0400, Gene Heskett wrote: > > > Regardless of what I do, I cannot get rid of the avahi junk in an ip > > > a report, so my local 192.168.xx.nn/24 net is the only thing that > > > works. pinging a net name like yahoo.com gets me a successful > > > address. But no response from yahoo because its sending the ping > > > from an avahi based address, which since thats outside of my /24 > > > netmask, doesn't get thru the router. > > > > > > So, how do I get rid of the avahi stuff? > > > > > > I've a nominally 10 machine 192.168.nn.xx that is 100% static based > > > on host files so I want avahi absolutely and totally neutered, > > > emasculated, gone Forever plus 100 years at least. > > > > > > How can I do that? It's not necessarily avahi doing that. A DHCP client might also configure a 169.254.*.* address for you if it doesn't receive a reply. In order to have the slightest chance of helping you it is necessary for you to provide the information as per below. Files should preferably be attached, to avoid issues with copy-paste. Please do not edit anything except to obscure private information (e.g. passwords or a public IP you don't want to post). 1. content of /etc/network/interfaces and all files under /etc/network/interfaces.d/ (I seem to recall you are using ifupdown) 2. Full output of: apt list --installed 'network-manager*' # might be empty apt list --installed 'avahi*' # might be empty systemctl status systemd-networkd ip a # short for 'ip address' ip r # short for 'ip route' 3. Information on anything (and I do mean anything) else you might have done to your network configuration after installing buster, including but not limited to: * installing stuff, especially if from source * removing stuff (especially if not 'purged', dpkg -l would tell) * manual changes to files (deletions/permissions/etc. (especially those unnecessary "fixes" you call "neutering") For the record/archives: other users are not seeing your problems. Buster is - at least for me - the best Debian release yet. The problems you are seeing are, at least partially, of your own doing, most likely due to wrong configuration and an approach of using the equivalent of a shotgun to kill a fly and then complaining your walls are full of holes. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-04 10:50 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yg5Bg-fH-13@gated-at.bofh.it> |
| In reply to | #210704 |
On Thursday 04 July 2019 03:16:31 andreimpopescu@gmail.com wrote: > On Mi, 03 iul 19, 21:03:19, Gene Heskett wrote: > > On Wednesday 03 July 2019 16:12:31 Reco wrote: > > > > And Gene moved. Question unanswered yet. > > > > > Hi. > > > > > > On Wed, Jul 03, 2019 at 02:57:35PM -0400, Gene Heskett wrote: > > > > Regardless of what I do, I cannot get rid of the avahi junk in > > > > an ip a report, so my local 192.168.xx.nn/24 net is the only > > > > thing that works. pinging a net name like yahoo.com gets me a > > > > successful address. But no response from yahoo because its > > > > sending the ping from an avahi based address, which since thats > > > > outside of my /24 netmask, doesn't get thru the router. > > > > > > > > So, how do I get rid of the avahi stuff? > > > > > > > > I've a nominally 10 machine 192.168.nn.xx that is 100% static > > > > based on host files so I want avahi absolutely and totally > > > > neutered, emasculated, gone Forever plus 100 years at least. > > > > > > > > How can I do that? > > It's not necessarily avahi doing that. A DHCP client might also > configure a 169.254.*.* address for you if it doesn't receive a reply. > > In order to have the slightest chance of helping you it is necessary > for you to provide the information as per below. > > Files should preferably be attached, to avoid issues with copy-paste. > > Please do not edit anything except to obscure private information > (e.g. passwords or a public IP you don't want to post). > > > 1. content of /etc/network/interfaces and all files under > /etc/network/interfaces.d/ > > (I seem to recall you are using ifupdown) > > 2. Full output of: > apt list --installed 'network-manager*' # might be empty > apt list --installed 'avahi*' # might be empty > systemctl status systemd-networkd > ip a # short for 'ip address' > ip r # short for 'ip route' > > 3. Information on anything (and I do mean anything) else you might > have done to your network configuration after installing buster, > including but not limited to: > * installing stuff, especially if from source First, on a u-booting raspi you don't "install". You either download an image and put it on a u-sd card with dd, or you generate your own image. Which is what I have done by using a utility from guysoft called RealtimePi, which takes the June 20th version of raspian buster lite apart, and supposedly puts it back together with a realtime patched version of a compatible kernel, which should have been a 4.19.50-rt-v7 kernel, but when put on a u-sd, and the u-sd booted, turns out to have the unpatched kernel in it. Why I watched it spend an hour building the older 4.4.114-rt-v7 kernel and then it didn't use it is something I have not found yet in the build.log. Which I can't get to ATM because ssh isn't working either. I can't get any of that until I can make ssh work, which it is not at the moment. ISTR if I restart it from its own console, it might work. Depends on the phase of the moon because it might decide to use the 169 addresses for everything. these two lines at the top of /e/n/i.d/eth0 auto eth0 iface eth0 inet static is supposed to tell n-m and company to keep their hands off that interface, and plainly it is not. It is totally ignoreing the rest of that file, so while I may get a valid address, but not one fixed gateway|route. Sitting here. playing with ip on this machine, I finally figured out how to get rid of the 169.254.xx.yy trash in the eth0 setup, and its possible I might be able to put a postup command or two to clean house and make it work, like I did with stretch on a rock64. > * removing stuff (especially if not 'purged', dpkg -l would tell) > * manual changes to files (deletions/permissions/etc. > (especially those unnecessary "fixes" you call "neutering") I will do whatever it takes to make it "Just Work". But so much has been changed with buster that I don't really know where to start. Jessie ran good, but realtime wasn't as real as needed, stretch runs a much better realtime, but each "upgrade" has been harder and harder to make the networking Just Work. > For the record/archives: other users are not seeing your problems. Am I the only holdout on the whole English speaking planet still useing static networking configs? I really, seriously, doubt that. But I will state that every release newer than wheezy has made it progressively more difficult to make a staticly defined network work. Way too many chefs stirring in the same pot is how I see it. > Buster is - at least for me - the best Debian release yet. It may well be, but its worthless to me running in a Faraday cage because I cannot control the networking. And its worthless to me until I can get a realtime kernel built into the u-sd. I build this stuff to do a job, and if it can't do the job, I've got 1500 lbs of cast iron I can't control to make it move. > The problems you are seeing are, at least partially, of your own > doing, most likely due to wrong configuration and an approach of using > the equivalent of a shotgun to kill a fly and then complaining your > walls are full of holes. Sorry, I don't see it that way, I see a concentrated effort to make me use dhcpd, instead of static, every machine in the system knows the address of ALL the other machines on my local 192.168.xx.nn/24 network. Using dhcp means I'd have to setup a 2nd this side of my router. I will try to make ssh work later today, and I will reanswer this message if I can do that. > Kind regards, > Andrei 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2019-07-04 11:30 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yg6dX-HM-3@gated-at.bofh.it> |
| In reply to | #210707 |
Gene Heskett composed on 2019-07-04 04:42 (UTC-0400): > every release newer than wheezy has made it progressively > more difficult to make a staticly defined network work. Given the myriad of successes in your 8+ decades, I'm baffled that you are continually flummoxed by fixed IP networking. Maybe it's because I only use X86 hardware, but DHCP is the only thing that has given me any trouble lately, and that's only because of a NIC driver that is apparently quite broken. Fixed IP here just continues to work as before. Could it be because I've been planting net.ifnames=0 on every cmdline since before Wheezy, along with 70-persistent-net.rules (which seems unnecessary any more), and a shared hosts file? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-04 11:50 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yg6xj-O6-5@gated-at.bofh.it> |
| In reply to | #210708 |
On Thursday 04 July 2019 05:25:05 Felix Miata wrote: > Gene Heskett composed on 2019-07-04 04:42 (UTC-0400): > > every release newer than wheezy has made it progressively > > more difficult to make a staticly defined network work. > > Given the myriad of successes in your 8+ decades, I'm baffled that you > are continually flummoxed by fixed IP networking. Maybe it's because I > only use X86 hardware, but DHCP is the only thing that has given me > any trouble lately, and that's only because of a NIC driver that is > apparently quite broken. Fixed IP here just continues to work as > before. Could it be because I've been planting net.ifnames=0 on every > cmdline since before Wheezy, along with 70-persistent-net.rules (which > seems unnecessary any more), and a shared hosts file? The shared hosts file has been a feature here since the second came online it round '00 to run an harbor freight milling machine, And I'm not sure in a pi's config, where to put the net.ifnames=0. /boot/cmdline.txt maybe? You have grub to splice all that together, but the pi's are u-boot, as most of the arm stuff is. But with the pi4 coming online, with 4Gigs a dram, I'd sure like to see grub-2 ported to arms. That would greatly simplicate kernel swapping. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2019-07-04 12:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yg70l-1de-3@gated-at.bofh.it> |
| In reply to | #210707 |
On 2019-07-04 09:42, Gene Heskett wrote: <snipped> > Sorry, I don't see it that way, I see a concentrated effort to make me > use dhcpd, instead of static, every machine in the system knows the > address of ALL the other machines on my local 192.168.xx.nn/24 network. > > Using dhcp means I'd have to setup a 2nd this side of my router. I will > try to make ssh work later today, and I will reanswer this message if I > can do that. I like having ipfire or pfsense on a separate box doing DHCP server. you can make other PCs static by making their lease fixed. and then everything is in one place. well that's how I understand it anyway. mick. -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-04 16:50 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygbdD-3Bo-1@gated-at.bofh.it> |
| In reply to | #210710 |
On Thursday 04 July 2019 06:15:56 mick crane wrote: > On 2019-07-04 09:42, Gene Heskett wrote: > <snipped> > > > Sorry, I don't see it that way, I see a concentrated effort to make > > me use dhcpd, instead of static, every machine in the system knows > > the address of ALL the other machines on my local 192.168.xx.nn/24 > > network. > > > > Using dhcp means I'd have to setup a 2nd this side of my router. I > > will try to make ssh work later today, and I will reanswer this > > message if I can do that. > > I like having ipfire or pfsense on a separate box doing DHCP server. > you can make other PCs static by making their lease fixed. > and then everything is in one place. > well that's how I understand it anyway. > > mick. I do have a dhcpd configured in dd-wrt. but its set to only respond to the MAC's of my sons smartfones when they come by and I enable the radio. That way their phones can use my bandwidth. If I could control which way those are bridged so the local AMC's see locals at fixed addresses, while the wifi stuff is bridged only to the internet, that would be ideal. But I don't believe I can control the bridge direction based on the MAC of the client. So I'd have to setup a separate server, ideally in the distribution switch, that assigned a dhcp address according to the incoming MAC. In my lashup, I have a managed switch, but its running the default setup which does not enable a dhcpd, if it even has one. And I can't think of a way to ping picnc, and reliably hit 192.168.xx.yy, the address of picnc. Using host files for local dns is so much simpler. Now I've been standing in front of its monitor for about an hour, a neck breaker because its well above my eye level. With NIX-Crafts ip tutorial in hand, trying to get rid of the default route in the 169.254 range, and while it may not return a syntax error thats usually gibberish, showing something thats totally disconnected from what I told it to do, there is no way in hell to delete the 169.junk from an ip r report. And this is with a sudo in front of whatever. If I try to ping yahoo.com it properly asks my isp's dns for an address for yahoo, gets it and displays it but then pings it from the 169 address, which is of coarse sent to /dev/null in the router if it even gets that far as it must traverse the switch to get that far. I've tried to dpkg --purge the dhcp* stuff I can see, but dpkg says its not installed so it must be in the kernel, a non-realtime 4.19.50 for armhf. So unless someone can tell me how to nuke, or at least change its preference for the 169 crap as defaults, this rpi-3b will never be able to run on buster. I must be able to make it use the 192.168.nn.hostname-address for everything. But something is overriding me. What is it? And can I nuke or otherwise disable it? The scripts in /etc/init.d for both avahi-daemon and dhcpd have been removed by rm. Made absolutely zero difference to an ip a or ip r report. I can only conclude that systemd thinks its smarter than me. I have armbian installed on a rock64, and there I had a heck of a time with the stretch version of this same routing problem, but duplicating that setup on buster, and getting working results cannot be done with the tools at hand. Someone gave me a link to a systemd tut, a pdf I was gonna print but its almost 40 pages thats both 5 years out of date, and by page 2 has dissolved into undecypherable jargon that needs translated to working English. Is there an uptodate one for dummies that actually covers buster? Thanks everybody. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2019-07-04 19:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygdyN-57z-5@gated-at.bofh.it> |
| In reply to | #210716 |
On 2019-07-04 15:40, Gene Heskett wrote: > On Thursday 04 July 2019 06:15:56 mick crane wrote: > >> On 2019-07-04 09:42, Gene Heskett wrote: >> <snipped> >> >> > Sorry, I don't see it that way, I see a concentrated effort to make >> > me use dhcpd, instead of static, every machine in the system knows >> > the address of ALL the other machines on my local 192.168.xx.nn/24 >> > network. >> > >> > Using dhcp means I'd have to setup a 2nd this side of my router. I >> > will try to make ssh work later today, and I will reanswer this >> > message if I can do that. >> >> I like having ipfire or pfsense on a separate box doing DHCP server. >> you can make other PCs static by making their lease fixed. >> and then everything is in one place. >> well that's how I understand it anyway. >> >> mick. > I do have a dhcpd configured in dd-wrt. but its set to only respond to > the MAC's of my sons smartfones when they come by and I enable the > radio. That way their phones can use my bandwidth. If I could control > which way those are bridged so the local AMC's see locals at fixed > addresses, while the wifi stuff is bridged only to the internet, that > would be ideal. pfsense, ipfire have got handy web GUI's for all that. I have WAP plugged in that is blocked to the local network but allowed to the internet. got to say I admire your tenacity. cheers mick -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | andreimpopescu@gmail.com |
|---|---|
| Date | 2019-07-05 06:00 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygny9-3Aw-1@gated-at.bofh.it> |
| In reply to | #210707 |
[Multipart message — attachments visible in raw view] — view raw
On Jo, 04 iul 19, 04:42:40, Gene Heskett wrote: > On Thursday 04 July 2019 03:16:31 andreimpopescu@gmail.com wrote: > > > > 3. Information on anything (and I do mean anything) else you might > > have done to your network configuration after installing buster, > > including but not limited to: > > * installing stuff, especially if from source > First, on a u-booting raspi you don't "install". You either download an > image and put it on a u-sd card with dd, or you generate your own image. > > Which is what I have done by using a utility from guysoft called > RealtimePi, which takes the June 20th version of raspian buster lite > apart, and supposedly puts it back together with a realtime patched > version of a compatible kernel, which should have been a 4.19.50-rt-v7 > kernel, but when put on a u-sd, and the u-sd booted, turns out to have > the unpatched kernel in it. Why I watched it spend an hour building the > older 4.4.114-rt-v7 kernel and then it didn't use it is something I have > not found yet in the build.log. Which I can't get to ATM because ssh > isn't working either. Just the fact that you are running Raspbian instead of pure Debian is already an important clue and possibly a major hindrance in helping you (we don't know what other customizations have been done to that). I will bet you this though: that image has usable dpkg and apt. If I'm right, do you promise to put the "shotgun" away? :) If I'm wrong I offer to dig up my Raspberry Pi and try to reproduce your problems. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-05 12:40 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygtNf-7o5-1@gated-at.bofh.it> |
| In reply to | #210742 |
On Thursday 04 July 2019 23:54:21 andreimpopescu@gmail.com wrote: > On Jo, 04 iul 19, 04:42:40, Gene Heskett wrote: > > On Thursday 04 July 2019 03:16:31 andreimpopescu@gmail.com wrote: > > > 3. Information on anything (and I do mean anything) else you might > > > have done to your network configuration after installing buster, > > > including but not limited to: > > > * installing stuff, especially if from source > > > > First, on a u-booting raspi you don't "install". You either download > > an image and put it on a u-sd card with dd, or you generate your own > > image. > > > > Which is what I have done by using a utility from guysoft called > > RealtimePi, which takes the June 20th version of raspian buster lite > > apart, and supposedly puts it back together with a realtime patched > > version of a compatible kernel, which should have been a > > 4.19.50-rt-v7 kernel, but when put on a u-sd, and the u-sd booted, > > turns out to have the unpatched kernel in it. Why I watched it > > spend an hour building the older 4.4.114-rt-v7 kernel and then it > > didn't use it is something I have not found yet in the build.log. > > Which I can't get to ATM because ssh isn't working either. > > Just the fact that you are running Raspbian instead of pure Debian is > already an important clue and possibly a major hindrance in helping > you (we don't know what other customizations have been done to that). > Humm, someplace, in the last week, I read on a debian site, that raspian was the officially supported armhf version of debian ??? Or was that my imagination, out to play without a chaperone? > I will bet you this though: that image has usable dpkg and apt. If I'm > right, do you promise to put the "shotgun" away? :) yup, and if the repos were open... They are not as I've previously posted. I can report that apt --purge does not, I still see an /etc/nsswitch.conf, even though ts been purged. > If I'm wrong I offer to dig up my Raspberry Pi and try to reproduce > your problems. I have solved both problems, so that won't be needed. OTOH, I would be interested in how you might make anything newer than wheezy actually work on a staticly defined host file based network without a dhcpd server on any machine accessible to the local network. Even wheezy took some mods to make it work starting with setting a chattr +i on everything network related because that N-M had not yet been taught to leave a 'static' defined network alone, or you could load up a root copy of mc, and nuke anything that looked like it belonged to N-M. It didn't spam the logs with squawks about the immutable flags, so that was a plus. > Kind regards, > Andrei Thanks Andrei. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Jonas Smedegaard <jonas@jones.dk> |
|---|---|
| Date | 2019-07-05 13:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygupX-7Qz-1@gated-at.bofh.it> |
| In reply to | #210756 |
[Multipart message — attachments visible in raw view] — view raw
Quoting Gene Heskett (2019-07-05 12:35:53) > On Thursday 04 July 2019 23:54:21 andreimpopescu@gmail.com wrote: > > Just the fact that you are running Raspbian instead of pure Debian > > is already an important clue and possibly a major hindrance in > > helping you (we don't know what other customizations have been done > > to that). > > > Humm, someplace, in the last week, I read on a debian site, that > raspian was the officially supported armhf version of debian ??? Or > was that my imagination, out to play without a chaperone? Raspbian is a _derivative_ of Debian, not official Debian: https://wiki.debian.org/Derivatives/Census/Raspbian - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-07-05 14:50 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygvP3-67-3@gated-at.bofh.it> |
| In reply to | #210756 |
On Fri, Jul 05, 2019 at 06:35:53AM -0400, Gene Heskett wrote: > yup, and if the repos were open... They are not as I've previously > posted. I can report that apt --purge does not, I still see > an /etc/nsswitch.conf, even though ts been purged. ... what. Gene, /etc/nsswitch.conf is NOT part of any Debian package. It's part of the core installation. It is absolutely fundamental to the operation of basically every single piece of the operating system above the boot loader, the kernel, the ld.so shared library loader, and libc. If you remove /etc/nsswitch.conf, you won't be able to look up user names, or service port names, or host names, or basically *any* kind of names of anything at all. (Or, at best, you'll get some sort of default behavior compiled into the C library routines, if any.) wooledg:~$ dpkg -S /etc/nsswitch.conf dpkg-query: no path found matching pattern /etc/nsswitch.conf Since nsswitch.conf isn't part of a package, there is absolutely no reason you should think that purging ANY package would remove it. And there is absolutely no reason you should *want* to remove it.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-07-05 15:10 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygw8p-rI-1@gated-at.bofh.it> |
| In reply to | #210769 |
Hi. On Fri, Jul 05, 2019 at 08:41:47AM -0400, Greg Wooledge wrote: > On Fri, Jul 05, 2019 at 06:35:53AM -0400, Gene Heskett wrote: > > yup, and if the repos were open... They are not as I've previously > > posted. I can report that apt --purge does not, I still see > > an /etc/nsswitch.conf, even though ts been purged. > > ... what. > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. Actually, nsswitch.conf is created by postinst script of libc-bin package, to technically nsswitch.conf is a part of libc-bin. > It's part of the core installation. It is absolutely fundamental to > the operation of basically every single piece of the operating system > above the boot loader, the kernel, the ld.so shared library loader, > and libc. nsswitch.conf(5) says: The Name Service Switch (NSS) configuration file, /etc/nsswitch.conf, is used by the GNU C Library... > wooledg:~$ dpkg -S /etc/nsswitch.conf > dpkg-query: no path found matching pattern /etc/nsswitch.conf grep nsswitch /var/lib/dpkg/info/* Reco
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-07-05 15:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygwi6-uU-5@gated-at.bofh.it> |
| In reply to | #210771 |
On Fri, Jul 05, 2019 at 04:02:36PM +0300, Reco wrote: > On Fri, Jul 05, 2019 at 08:41:47AM -0400, Greg Wooledge wrote: > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. > > Actually, nsswitch.conf is created by postinst script of libc-bin > package, to technically nsswitch.conf is a part of libc-bin. Even if it's created by libc-bin's postinst, it still wouldn't be removed when libc-bin is (hypothetically) purged, because it's not a registered conffile of that package. Of course, one should NOT purge libc-bin. wooledg:~$ dpkg -s libc-bin Package: libc-bin Essential: yes [...] Conffiles: /etc/bindresvport.blacklist 4c09213317e4e3dd3c71d74404e503c5 /etc/default/nss d6d5d6f621fb3ead2548076ce81e309c /etc/gai.conf 28fa76ff5a9e0566eaa1e11f1ce51f09 /etc/ld.so.conf 4317c6de8564b68d628c21efa96b37e4 /etc/ld.so.conf.d/libc.conf d4d833fd095fb7b90e1bb4a547f16de6 [...] Whatever Gene did, it's absolutely not normal or desirable for nsswitch.conf to vanish. I still think he deleted it by hand and then forgot the exact sequence of steps which led to its disappearance, so he simply blamed it on purging ahavi-daemon.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-06 02:30 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygGKt-6BA-1@gated-at.bofh.it> |
| In reply to | #210772 |
On Friday 05 July 2019 09:17:47 Greg Wooledge wrote: > On Fri, Jul 05, 2019 at 04:02:36PM +0300, Reco wrote: > > On Fri, Jul 05, 2019 at 08:41:47AM -0400, Greg Wooledge wrote: > > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. > > > > Actually, nsswitch.conf is created by postinst script of libc-bin > > package, to technically nsswitch.conf is a part of libc-bin. > > Even if it's created by libc-bin's postinst, it still wouldn't be > removed when libc-bin is (hypothetically) purged, because it's not a > registered conffile of that package. > > Of course, one should NOT purge libc-bin. > > wooledg:~$ dpkg -s libc-bin > Package: libc-bin > Essential: yes > [...] > Conffiles: > /etc/bindresvport.blacklist 4c09213317e4e3dd3c71d74404e503c5 > /etc/default/nss d6d5d6f621fb3ead2548076ce81e309c > /etc/gai.conf 28fa76ff5a9e0566eaa1e11f1ce51f09 > /etc/ld.so.conf 4317c6de8564b68d628c21efa96b37e4 > /etc/ld.so.conf.d/libc.conf d4d833fd095fb7b90e1bb4a547f16de6 > [...] > > Whatever Gene did, it's absolutely not normal or desirable for > nsswitch.conf to vanish. I still think he deleted it by hand and then > forgot the exact sequence of steps which led to its disappearance, so > he simply blamed it on purging ahavi-daemon. I didn't say that. If I made that impression I didn't intend to. I removed it by hand about 2 hours back but that u-sd has not been inserted in the pi yet as I'm also the chief cook and bottle washer here and it was time I played chef with a bag of beef stir fry to feed the two of us. With the missus disabled, I do it all. And next is to go recycle the dishwasher. :( 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-06 02:20 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygGAN-6yx-1@gated-at.bofh.it> |
| In reply to | #210769 |
On Friday 05 July 2019 08:41:47 Greg Wooledge wrote: > On Fri, Jul 05, 2019 at 06:35:53AM -0400, Gene Heskett wrote: > > yup, and if the repos were open... They are not as I've previously > > posted. I can report that apt --purge does not, I still see > > an /etc/nsswitch.conf, even though ts been purged. > > ... what. > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. It's part > of the core installation. It is absolutely fundamental to the > operation of basically every single piece of the operating system > above the boot loader, the kernel, the ld.so shared library loader, > and libc. IOW, the image I have in my pocket probably don't work until I locate a copy and put it back in. But just for grins, check the buster its running: yes, its still there and I think intact: gene@shop:~$ cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis But that begs another question Greg. If it hasn't anything to do with avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch package with it? > If you remove /etc/nsswitch.conf, you won't be able to look up user > names, or service port names, or host names, or basically *any* kind > of names of anything at all. (Or, at best, you'll get some sort of > default behavior compiled into the C library routines, if any.) > > wooledg:~$ dpkg -S /etc/nsswitch.conf > dpkg-query: no path found matching pattern /etc/nsswitch.conf > > Since nsswitch.conf isn't part of a package, there is absolutely no > reason you should think that purging ANY package would remove it. And > there is absolutely no reason you should *want* to remove it. The only reason I removed it, was to complete the libnsswitch removal that removing avahi-daemon took out. Somehow I am missing an actual dependency of one on the other. Call me puzzled. Thanks Greg. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-07-06 15:50 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <ygTeG-5tr-3@gated-at.bofh.it> |
| In reply to | #210816 |
On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > On Friday 05 July 2019 08:41:47 Greg Wooledge wrote: > > On Fri, Jul 05, 2019 at 06:35:53AM -0400, Gene Heskett wrote: > > > yup, and if the repos were open... They are not as I've previously > > > posted. I can report that apt --purge does not, I still see > > > an /etc/nsswitch.conf, even though ts been purged. > > > > ... what. > > > > Gene, /etc/nsswitch.conf is NOT part of any Debian package. It's part > > of the core installation. It is absolutely fundamental to the > > operation of basically every single piece of the operating system > > above the boot loader, the kernel, the ld.so shared library loader, > > and libc. > > IOW, the image I have in my pocket probably don't work until I locate a > copy and put it back in. But just for grins, check the buster its > running: yes, its still there and I think intact: > gene@shop:~$ cat /etc/nsswitch.conf > # /etc/nsswitch.conf > # > # Example configuration of GNU Name Service Switch functionality. > # If you have the `glibc-doc-reference' and `info' packages installed, > try: > # `info libc "Name Service Switch"' for information about this file. > > passwd: compat > group: compat > shadow: compat > > hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 > networks: files > > protocols: db files > services: db files > ethers: db files > rpc: db files > > netgroup: nis > > But that begs another question Greg. If it hasn't anything to do with > avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch > package with it? > > > If you remove /etc/nsswitch.conf, you won't be able to look up user > > names, or service port names, or host names, or basically *any* kind > > of names of anything at all. (Or, at best, you'll get some sort of > > default behavior compiled into the C library routines, if any.) > > > > wooledg:~$ dpkg -S /etc/nsswitch.conf > > dpkg-query: no path found matching pattern /etc/nsswitch.conf > > > > Since nsswitch.conf isn't part of a package, there is absolutely no > > reason you should think that purging ANY package would remove it. And > > there is absolutely no reason you should *want* to remove it. > > The only reason I removed it, was to complete the libnsswitch removal > that removing avahi-daemon took out. Somehow I am missing an actual > dependency of one on the other. Call me puzzled. I'm puzzled too. Can you tell us which package you're talking about as I can only find: Package lib32nss-mdns Package libnss3 Package libnss3-1d Package libnss3-dbg Package libnss3-dbgsym Package libnss3-dev Package libnss3-tools Package libnss3-tools-dbgsym Package libnss-cache Package libnss-cache-dbgsym Package libnss-db Package libnss-db-dbgsym Package libnss-dns-udeb Package libnss-docker Package libnss-docker-dbgsym Package libnss-extrausers Package libnss-extrausers-dbgsym Package libnss-files-udeb Package libnss-gw-name Package libnss-gw-name-dbgsym Package libnss-ldap Package libnss-ldapd Package libnss-ldap-dbgsym Package libnss-ldapd-dbgsym Package libnss-libvirt Package libnss-libvirt-dbgsym Package libnss-lwres Package libnss-lwres-dbgsym Package libnss-mdns Package libnss-mdns-dbgsym Package libnss-mdns-i386 Package libnss-myhostname Package libnss-myhostname-dbgsym Package libnss-mymachines Package libnss-mymachines-dbgsym Package libnss-mysql-bg Package libnss-pgsql2 Package libnss-pgsql2-dbgsym Package libnss-rainbow2 Package libnss-rainbow2-dbgsym Package libnss-resolve Package libnss-resolve-dbgsym Package libnss-securepass Package libnss-securepass-dbgsym Package libnss-sss Package libnss-sss-dbgsym Package libnss-systemd Package libnss-systemd-dbgsym Package libnss-unknown Package libnss-unknown-dbgsym Package libnss-winbind Package libnss-winbind-dbgsym Package libnss-wrapper Package libnss-wrapper-dbgsym Package libpam-ccreds Package libpam-ldap Package nslcd Package nsscache Package nss-passwords Package nss-updatedb Package pynslcd Package winbind Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-07-08 14:40 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yhB61-6C4-1@gated-at.bofh.it> |
| In reply to | #210837 |
On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > But that begs another question Greg. If it hasn't anything to do with > > avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch > > package with it? > I'm puzzled too. Can you tell us which package you're talking about as > I can only find: > > Package lib32nss-mdns > Package libnss3 [snip] I'm pretty sure Gene means this one: wooledg:~$ apt-cache show avahi-daemon | grep libnss Recommends: libnss-mdns As I demonstrated somewhere else in this thread,[1] removing avahi-daemon also removes libnss-mdns, and installing avahi-daemon also installs libnss-mdns, at least when using apt with whatever settings I'm currently using. Which are probably pretty close to the defaults. [1] https://lists.debian.org/debian-user/2019/07/msg00258.html
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2019-07-08 15:00 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yhBpn-6IE-5@gated-at.bofh.it> |
| In reply to | #210991 |
On Monday 08 July 2019 08:36:38 Greg Wooledge wrote: > On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > > But that begs another question Greg. If it hasn't anything to do > > > with avahi-daemon, whyinhell did purging avahi-daemon take the > > > libnsswitch package with it? > > > > I'm puzzled too. Can you tell us which package you're talking about > > as I can only find: > > yes, thats the one > > Package lib32nss-mdns > > Package libnss3 > > [snip] > > I'm pretty sure Gene means this one: > > wooledg:~$ apt-cache show avahi-daemon | grep libnss > Recommends: libnss-mdns > > As I demonstrated somewhere else in this thread,[1] removing > avahi-daemon also removes libnss-mdns, and installing avahi-daemon > also installs libnss-mdns, at least when using apt with whatever > settings I'm currently using. Which are probably pretty close to the > defaults. > > [1] https://lists.debian.org/debian-user/2019/07/msg00258.html ditto's here. But I think I'll disable the kernel pinning until such time as I get a realtime built and installed. Thanks Greg. 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) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-07-08 16:30 +0200 |
| Subject | Re: Assorted arm-buster problems - network configuration |
| Message-ID | <yhCOu-7GN-7@gated-at.bofh.it> |
| In reply to | #210991 |
On Mon 08 Jul 2019 at 08:36:38 (-0400), Greg Wooledge wrote: > On Sat, Jul 06, 2019 at 08:46:19AM -0500, David Wright wrote: > > On Fri 05 Jul 2019 at 20:10:42 (-0400), Gene Heskett wrote: > > > But that begs another question Greg. If it hasn't anything to do with > > > avahi-daemon, whyinhell did purging avahi-daemon take the libnsswitch > > > package with it? > > > I'm puzzled too. Can you tell us which package you're talking about as > > I can only find: > > > > Package lib32nss-mdns > > Package libnss3 > [snip] > > I'm pretty sure Gene means this one: > > wooledg:~$ apt-cache show avahi-daemon | grep libnss > Recommends: libnss-mdns > > As I demonstrated somewhere else in this thread,[1] removing avahi-daemon > also removes libnss-mdns, and installing avahi-daemon also installs > libnss-mdns, at least when using apt with whatever settings I'm currently > using. Which are probably pretty close to the defaults. > > [1] https://lists.debian.org/debian-user/2019/07/msg00258.html Yes, thanks for that; posting saves others from having to test what's going on. I guess we should hardly be surprised. So the Debian system that's allegedly completely broken (and has been "nuked" into who knows what shape) turns out to be not a Debian system at all. Such a waste of time. Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 1 of 5 [1] 2 3 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web