On 06/16/2012 01:28 PM, Camaleón wrote: > On Sat, 16 Jun 2012 13:06:11 -0400, Gilbert Sullivan wrote: > >> On 06/16/2012 10:42 AM, Camaleón wrote: >>> If you are using the "resolvconf" package I bet you have to trust what >>> the "/etc/revolv.conf" file warning says in uppercase about do not >>> editing the file because is dynamically changed ;-) >>> >>> http://wiki.debian.org/NetworkConfiguration#The_resolvconf_program >>> >>> OTOH, I never used this package before, I don't know what's for nor how >>> is configured so I can't give you any feedback on this other than >>> reading the available docs and man pages :-) >>> >>> >> Hi, Camaleón! >> >> Oh yes. I know now to fiddle with that file -- and any other that warns >> twinkies like me to keep hands off! >> >> I believe I am in the process of learning something of real use from >> Matthew Grant, who has been corresponding with me wrt Bug# 677642 on the >> Debian BTS. >> >> I've been wondering why the resolvconf package was apparently behaving >> differently than it used to behave, and why the /etc/resolv.conf looked >> different than it used to look. >> >> Matthew pointed out that my use of netscript 2.4 is sort of non-standard >> for a regular Debian desktop. > > (...) > > And he is right. > > The first thing I would do is removing that package if you don't need it > at all (I don't have it installed, BTW, and running "apt-cache rdepends > netscript" returns void so no other package seems to depend on it). >
Well, I'm in the situation of not being sure whether or not it's a good idea for me to remove netscript 2.4 and go back to ifupdown. Apparently, netscript was pulled in by virtualbox. I installed that weeks ago so that I could do some testing of a couple of other GNU/Linux operating systems, and also so that I could fire up an old database analysis package in a DOS VM. If and when I actually create them, I'm going to want to use networking for some of those VMs, and I'm not sure how well that will work without netscript. Anyway, the previous version of netscript never seemed to cause me any problems. It was the new one (version 2.4) that appears to have made things go a little weird on this system. In point of fact, my basic networking works well enough -- other than the delay in boot times when I'm connected by a fixed IP address. And even that is easily overcome by simply hitting <Ctrl>+<C>. I guess there's no harm in doing some experimentation with the various packages to see if I can find a comfortable solution. I guess if I have troubles with networking VMs I could always go back to netscript. I do think that it's interesting that aptitude suggests resolvconf for the netscript package. But I removed resolvconf this morning, and name resolution started working again. Unfortunately, a fiasco with the ISP settings for the cable modem and problems with their name servers (and the correction of same this morning) has muddied the waters enough that I can't really be certain which action fixed what problem. Now I don't even really know whether or not I should be pursuing the bug report I filed against netscript. I don't want to be making stupid noises for the maintainers just when they really need to be concentrating on stuff that actually matters for the upcoming Wheezy freeze. As always, thanks! Best regards, Gilbert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fdcc6ba.50...@comcast.net
