On Thu 01 Aug 2019 at 14:09:31 (-0400), Michael Stone wrote:
> On Thu, Aug 01, 2019 at 11:11:33AM -0500, David Wright wrote:
> > It surprised me that systemd doesn't just use something
> > like the gateway address if/when some address is absolutely
> > essential.
>
> Why on earth would it
Le 01/08/2019 à 20:06, Greg Wooledge a écrit :
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it
On Thu, Aug 01, 2019 at 08:16:38PM +0200, Pascal Hambourg wrote:
> Le 01/08/2019 à 19:58, Pascal Hambourg a écrit :
> > Le 01/08/2019 à 18:18, David Wright a écrit :
> > >
> > > I think that a lot of people install resolvconf (deliberately or
> > > incidentally) without really understanding what
Le 01/08/2019 à 19:58, Pascal Hambourg a écrit :
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
On Thu, Aug 01, 2019 at 11:11:33AM -0500, David Wright wrote:
It surprised me that systemd doesn't just use something
like the gateway address if/when some address is absolutely
essential.
Why on earth would it assume that the gateway is running a resolver?
On Thu, Aug 01, 2019 at 07:58:56PM +0200, Pascal Hambourg wrote:
> Le 01/08/2019 à 18:18, David Wright a écrit :
> >
> > I think that a lot of people install resolvconf (deliberately or
> > incidentally) without really understanding what it's for or what
> > it does. Then, because most people
Le 01/08/2019 à 18:18, David Wright a écrit :
I think that a lot of people install resolvconf (deliberately or
incidentally) without really understanding what it's for or what
it does. Then, because most people naturally check the contents of
/etc/resolv.conf, they indulge in all sorts of
On 2019-08-01, Curt wrote:
> On 2019-07-31, Bob Bernstein wrote:
>> I _think_ my upgrade from Jessie to Stretch -- which entailed
>> installing systemd for the first time on this box -- introduced
>> that 8.8.8.8. into my config. I've never been at a loss to
>> select my own nameservers, and
On Wed 31 Jul 2019 at 23:38:34 (+0200), Pascal Hambourg wrote:
> Le 31/07/2019 à 23:30, ghe a écrit :
> > On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> >
> > > Without resolvconf, the DHCP client would have completely overwritten
> > > resolv.conf instead of just adding one line. With resolvconf,
On Wed 31 Jul 2019 at 18:56:08 (-0400), Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced that
> 8.8.8.8. into my config. I've never been at a loss to select my own
> nameservers, and that never
On 2019-07-31, Bob Bernstein wrote:
> I _think_ my upgrade from Jessie to Stretch -- which entailed
> installing systemd for the first time on this box -- introduced
> that 8.8.8.8. into my config. I've never been at a loss to
> select my own nameservers, and that never has been one of them.
>
I _think_ my upgrade from Jessie to Stretch -- which entailed
installing systemd for the first time on this box -- introduced
that 8.8.8.8. into my config. I've never been at a loss to
select my own nameservers, and that never has been one of them.
I was not even aware of that other file
Le 31/07/2019 à 23:30, ghe a écrit :
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
Without resolvconf, the DHCP client would have completely overwritten
resolv.conf instead of just adding one line. With resolvconf, at least
you can have some control over resolv.conf.
OK. vi gives me all the
On 7/31/19 2:52 PM, Pascal Hambourg wrote:
> Without resolvconf, the DHCP client would have completely overwritten
> resolv.conf instead of just adding one line. With resolvconf, at least
> you can have some control over resolv.conf.
OK. vi gives me all the control I need over resolv.conf. I
Le 31/07/2019 à 21:44, ghe a écrit :
On 7/31/19 1:20 PM, Greg Wooledge wrote:
I still feel like you're missing the big picture here. resolvconf isn't
the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
Resolvconf does not modify
On Mi, 31 iul 19, 13:44:51, ghe wrote:
> On 7/31/19 1:20 PM, Greg Wooledge wrote:
>
> > I still feel like you're missing the big picture here. resolvconf isn't
> > the thing that's modifying your /etc/resolv.conf file.
>
> It's the thing (that was) modifying my resolv.conf.
[...]
> At
On 7/31/19 1:20 PM, Greg Wooledge wrote:
> I still feel like you're missing the big picture here. resolvconf isn't
> the thing that's modifying your /etc/resolv.conf file.
It's the thing (that was) modifying my resolv.conf.
I have 2 Enet connections: a reliable T1 and a reasonably fast WiFi.
On Wed, Jul 31, 2019 at 01:13:27PM -0600, ghe wrote:
> On 7/31/19 12:52 PM, Greg Wooledge wrote:
>
> > Removing /etc/resolvconf sounds like terrible> advice.
> > If you want to remove resolvconf, remove the> package with dpkg or apt.
> > Don't just start removing random
> configuration> files
On 7/31/19 12:52 PM, Greg Wooledge wrote:
> Removing /etc/resolvconf sounds like terrible> advice.
> If you want to remove resolvconf, remove the> package with dpkg or apt.
> Don't just start removing random
configuration> files and directories
Good point, well taken.
I've always just
On Wed, Jul 31, 2019 at 12:44:50PM -0600, ghe wrote:
> On 7/31/19 12:17 PM, Bob Bernstein wrote:
>
> > Sure enough, there it was, for eth0. I commented it out and added a line
> > for the nameserver I wanted, and bingo, we have lift off.
>
> That works, but if you want to specify the DNS server,
On 7/31/19 12:17 PM, Bob Bernstein wrote:
> Sure enough, there it was, for eth0. I commented it out and added a line
> for the nameserver I wanted, and bingo, we have lift off.
That works, but if you want to specify the DNS server, delete those 2
DNS lines in /etc...interfaces, and edit
Le 31/07/2019 à 19:56, Greg Wooledge a écrit :
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit
SOLVED, I think.
After all the reading you guys gave me I sat pondering this
morning, and it dawned on me that if I looked at 'interfaces'
and found that darn 8.8.8.8 ip in there, that I might have the
clue I needed.
Sure enough, there it was, for eth0. I commented it out and
added a line
On Wed, Jul 31, 2019 at 07:51:45PM +0200, Pascal Hambourg wrote:
> Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
> >
> > What I want to do is get rid of the google 8.8.8.8 and replace it with a
> > static nameserver suggested by my vpn.
>
> Edit /etc/network/interfaces.
That isn't a full
Le 31/07/2019 à 17:10, Bob Bernstein a écrit :
What I want to do is get rid of the google 8.8.8.8 and replace it with a
static nameserver suggested by my vpn.
Edit /etc/network/interfaces.
Hi.
On Wed, Jul 31, 2019 at 11:10:32AM -0400, Bob Bernstein wrote:
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by r$
This simplifies things greatly
> What I want to do is get rid of the google 8.8.8.8 and replace it with a
> static nameserver suggested by my vpn.
I've begun a new thread to add some back-story to my "Which
resolv.conf file?" inquiry. *Thanks* to all who have chimed in.
nb. Judah: If "DE" means "desktop environment" then I don't
think I have one. I run the minimalist icewm, and I do not have
network manager installed.
I do not want to
27 matches
Mail list logo
