New 10.4 32 bit install, needs dns info

[Tom H]

On Sun, May 2, 2010 at 9:52 PM, Gene Heskett <gene.heskett at verizon.net> wrote:
> On Sunday 02 May 2010, Tom H wrote:
>>On Sun, May 2, 2010 at 4:13 AM, Gene Heskett <gene.heskett at verizon.net>
> wrote:
>>> On Sunday 02 May 2010, Tom H wrote:
>>>>On Sat, May 1, 2010 at 6:51 PM, Gene Heskett <gene.heskett at verizon.net>
>>>
>>> wrote:
>>>>> This is for the iface eth0 static
>>>>> stanza in /etc/networking/interfaces
>>>>>
>>>>> The net is working locally by hosts file translations, but the manpage
>>>>> for interfaces does not demo how a dns address is passed.
>>>>>
>>>>> And of course, /etc/resolv.conf has no data other than claims to have
>>>>> been generated by network-manager, which I'd druther not fight with
>>>>> when a simple /etc/init.d/networking start should just do it. ISTR on
>>>>> 6.06, I was able to kill NM, and then hand edit resolv.conf, then make
>>>>> it immutable and that was the end of that, but it was also 6.06 and I
>>>>> expect things are done differently now.
>>>>>
>>>>> This should come up on boot using all static addressing.
>>>>
>>>>If you are not using NM, why don't you uninstall it and hand edit
>>>>/etc/network/interfaces and /etc/resolv.conf (without any need to set
>>>>immutable, etc)?
>>>
>>> Ok, I'll do that later today.  Thanks.
>>
> And that worked.  I removed NM, started networking, then fixed resolv.conf &
> everything in that regard is now working..
>
>>You're welcome.
>>
>>There are two other options.
>>
>>1. Only configure lo in /etc/network/interfaces and configure your
>>static address and other settings in NM's GUI.
>
> I did try that, but couldn't get it to save my changes.
>
>>2. Configure the static address in /etc/network/interfaces but change
>>the "managed" setting in /etc/NetworkManager/nm-system-settings.conf
>>so you still have NM on your box shozld you need it.
>
> Its gone, just as well.  I've been doing it this way since about 1998. NM has
> always seemed to me to be a half baked solution in search of a problem, and
> if it cannot find a problem, then by golly it will make up one of its own.
> Its been quite good at that on my watch.
>
> Thank you Tom.

You're welcome.

I have tried in the past managing my wired setup myself and my
wireless setup through NM (rather than at the CLI out of sheer
laziness) and it worked well, but anyone who follows at least one
Linux list knows that NM-related problems are frequent... If NM (and
its dos and don'ts) and its configuration (and the location and syntax
of all its config files) were fully documented, there would would far
fewer problems.