/etc/resolv.conf file is empty (was: Network problem {start of part 2})
Further developments on this:
When I rebooted after the installation, I lost my ability to access the
Net (again). I checked the contents of /etc/resolv.conf and there was
nothing in that file - apparently it is generated by Network Manager, so
I reinstalled Network Manager and manually copied over what I had had in
there originally, i.e.:
But, after rebooting this file was again blank, stopping me from
accessing the Net. How can I ensure that this file remains populated
between reboots? Or does this file get generated by some other
function, and in which case, what?
Thanks for the assistance.
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
/etc/resolv.conf file is empty (was: Network problem {start of part 2})
On 08/05/11 11:55, Brian wrote:
On Sun 08 May 2011 at 10:34:00 +0100, AG wrote:
But, after rebooting this file was again blank, stopping me from
accessing the Net. How can I ensure that this file remains populated
between reboots? Or does this file get generated by some other
function, and in which case, what?
What is the output of
dpkg -l | grep resolvconf
dpkg -l | grep resolvconf
rc resolvconf
1.48 name server information handler
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
/etc/resolv.conf file is empty (was: Network problem {start of part 2})
On Sun, 08 May 2011 13:30:59 +0100, AG wrote:
> On 08/05/11 11:55, Brian wrote:
>> On Sun 08 May 2011 at 10:34:00 +0100, AG wrote:
>>
>>> But, after rebooting this file was again blank, stopping me from
>>> accessing the Net. How can I ensure that this file remains populated
>>> between reboots? Or does this file get generated by some other
>>> function, and in which case, what?
>> What is the output of
>>
>> dpkg -l | grep resolvconf
>>
>>
> dpkg -l | grep resolvconf
> rc resolvconf
> 1.48 name server information handler
Ein? >>>:-)
So you finally do have it installed.
Remember that this package can be also interferring with your "/etc/
resolv.conf" file so either you configure it properly or you remove it.
Choose your poison :-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.08.13.29.19@gmail.com">http://lists.debian.org/pan.2011.05.08.13.29.19@gmail.com
05-08-2011, 01:46 PM
AG
/etc/resolv.conf file is empty (was: Network problem {start of part 2})
On 08/05/11 14:29, Camaleón wrote:
On Sun, 08 May 2011 13:30:59 +0100, AG wrote:
On 08/05/11 11:55, Brian wrote:
On Sun 08 May 2011 at 10:34:00 +0100, AG wrote:
But, after rebooting this file was again blank, stopping me from
accessing the Net. How can I ensure that this file remains populated
between reboots? Or does this file get generated by some other
function, and in which case, what?
What is the output of
dpkg -l | grep resolvconf
dpkg -l | grep resolvconf
rc resolvconf
1.48 name server information handler
Ein?>>>:-)
So you finally do have it installed.
Remember that this package can be also interferring with your "/etc/
resolv.conf" file so either you configure it properly or you remove it.
Choose your poison :-)
And yet ...
$ sudo apt-get remove --purge resolvconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
resolvconf*
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
So it must be some libraries? But even inserting the wildcard throws
the same response, witness:
$ sudo apt-get remove --purge resolvconf*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'resolvconf' for regex 'resolvconf*'
The following packages will be REMOVED:
resolvconf*
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
What does this mean?
AG
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
/etc/resolv.conf file is empty (was: Network problem {start of part 2})
On Sun, 08 May 2011 14:46:39 +0100, AG wrote:
> On 08/05/11 14:29, Camaleón wrote:
(...)
>>> dpkg -l | grep resolvconf
>>> rc resolvconf
>>> 1.48 name server information handler
>> Ein?>>>:-)
>>
>> So you finally do have it installed.
>>
>> Remember that this package can be also interferring with your "/etc/
>> resolv.conf" file so either you configure it properly or you remove it.
>> Choose your poison :-)
> And yet ...
>
> $ sudo apt-get remove --purge resolvconf Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
> resolvconf*
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> So it must be some libraries? But even inserting the wildcard throws
> the same response, witness:
(...)
The asterisk at the end of the package means that configuration files are
going to be removed. That's normal when you invoke the "--purge" argument.
Wait... the package is marked as "rc", so it's not installed but the
configuration files remains. Maybe you can use "dpkg --purge resolvconf"
instead :-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.05.08.14.23.02@gmail.com">http://lists.debian.org/pan.2011.05.08.14.23.02@gmail.com
/etc/resolv.conf file is empty (was: Network problem {start of part 2})
