Aren't we whistling past the graveyard here? Why the hell should a system upgrade cause a sudo failure?? Or am I an idiot for wondering why the adminsitrator should be locked out of his system because he was bold enough to upgrade? Has any one bugged this? Or asked why even?

-------- Original Message -------- Subject: Re: [wlug] sudo broken after upgrade from gutsy to hairy^Whardy From: "James Pluck" <papabearnz(a)gmail.com> Date: Wed, April 30, 2008 3:12 pm To: "Waikato Linux Users Group" <wlug(a)list.waikato.ac.nz>

On Wed, Apr 30, 2008 at 2:48 PM, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:

...

2008/4/30 James Pluck <papabearnz(a)gmail.com>:

...

On Wed, Apr 30, 2008 at 2:26 PM, Bruce Kingsbury <zcat(a)zcat.geek.nz> wrote:

...

...

...

*brain-break* Shouldn't that be 127.0.0.1?

Nope. 127.0.1.1

Why is Localhost 1.1 in Ubuntu instead of 0.1 as is the norm?

Enquiring minds and all that :)

localhost is still 127.0.0.1, the name of the machine is 127.0.1.1

Ahh! I wasn't aware of that. I learned something today *grin*

And I have no idea why. Googling only comes up with problems caused by it..

...

no explanation of why they set things up this way.

Hmmm - interesting.

-- James Pluck PalmOS Ergo Sum "Dear IRS: I would like to cancel my subscription. Please remove my name from your mailing list..."<hr>_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug