Re: iproute, NM and ifupdown
- Date: Tue, 28 Aug 2018 14:58:38 -0500
- From: David Wright <deblis@xxxxxxxxxxxxxxxxx>
- Subject: Re: iproute, NM and ifupdown
On Tue 28 Aug 2018 at 14:57:58 (-0400), Gene Heskett wrote:
> On Tuesday 28 August 2018 14:16:15 David Wright wrote:
> > On Mon 27 Aug 2018 at 19:21:00 (-0400), Gene Heskett wrote:
> > > On Monday 27 August 2018 15:59:09 David Wright wrote:
> > > > On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> > > > > On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > > > > > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
> > > > > > > Most recently on a stretch install on a rock64 I had to
> > > > > > > erect immutable attributes to resolv.conf after making it a
> > > > > > > real file, and e-n-i to make networking Just Work.
> > > > > >
> > > > > > /etc/resolv.conf is a rather different topic, because it is
> > > > > > not related to a specific interface and may be written by
> > > > > > several pieces of software, including but not limited to
> > > > > > NetworkManager when configuring *any* interface. I would
> > > > > > suggest using resolvconf but I suspect you would not like it
> > > > > > either.
Reread what you wrote:
> > > > > Ohkaay, but where's the docs on this mysterious resolvconf?
> > > > >
> > > > > What we do have is missing (wheezy) or horribly incomplete
> > > > > (jessie).
> > > > >
> > > > > But I'll have to take that back, my apologies. I just read the
> > > > > stretch version on that rock64. And as man pages go, its
> > > > > decent. And I'll have to do some experimenting as its possible I
> > > > > can train it to behave.
> > > > >
> > > > > And curious I blink compared the jessie vs stretch versions,
> > > > > stretch's is both longer AND more complete, and two different
> > > > > authors and formatted completely different. And wheezy doesn't
> > > > > even have the man page. I don't even know if it should, maybe
> > > > > not for wheezy, lots of water has been recycled since those
> > > > > installs were made, so I'll plead oldtimers.
That's about the *man pages* for resolvconf.
> > > > This is very strange. I just did (in 80 column xterms):
> > [snipped various properties of resolvconf's man page on
> > wheezy/jessie/stretch.]
> > > > So one can't help wondering exactly what is installed on your
> > > > machines if things don't match. Note that there are significant
> > > > differences between the different versions, so following the
> > > > stretch/jessie man page could give you problems on a wheezy
> > > > machine. (I haven't checked out backports.)
> > >
> > > What is installed on 4 of the 6 boxes here, is a wheezy install
> > > thats been tweaked to A: put a realtime kernel on it so it can run
> > > linuxcnc on real hardware. The stretch I'll install here after my
> > > new drive cage arrives, and I found today that newegg's fedex is a
> > > week for delivery, its not expected to arrive here before Thursday
> > > evening, has also been tweaked to run LinuxCNC, probably by a real
> > > time kernel replacement..
> > Which kernel you run should have no connection with the contents of
> > Debian's resolvconf packages. You should still have these three:
> > 4575 Jun 19 2012 /usr/share/man/man8/resolvconf.8.gz
> > 4500 Jan 27 2015 /usr/share/man/man8/resolvconf.8.gz
> > 4500 May 19 2016 /usr/share/man/man8/resolvconf.8.gz
Those are the man pages (your "docs") for wheezy/jessie/stretch.
They should be on your various systems according to Debian codename.
> not on any wheezy sourced from the linuxcnc install iso, David
Well, look again. In /usr/share/man/man8/, not /etc/.
> My /etc/resolv.conf is a real file and looks something like this:
> nameserver 192.168.71.1
> search hosts nameserver
> And it Just Works.
Yes, /etc/resolv.conf is not a man page. And I don't suppose your
/etc/resolv.conf is missing from wheezy or horribly incomplete in
jessie, which is what you were claiming for the *docs*.
And note that none of this is about the man page for resolv.conf which
is in section (5) rather than (8) as it's about a file, not a command.
If you read the latter, you'll see that your line "search hosts nameserver"
doesn't make a lot of sense.
But that's a conversation we had last year.