[500] in athena10
Re: Suggested amendments to the Athena10 docs.
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Tue Sep 16 17:29:04 2008
Cc: William Cattey <wdc@mit.edu>, athena10@mit.edu
Message-Id: <E7F7FC88-2EE8-4CED-B48A-672056B68474@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Tim Abbott <tabbott@mit.edu>
In-Reply-To: <alpine.DEB.1.10.0809161643210.1869@vinegar-pot.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 16 Sep 2008 17:28:18 -0400
On Sep 16, 2008, at 4:49 PM, Tim Abbott wrote:
> Sorry, I should have been more clear in my question.
>
> The current Debathena nsswitch setup does not allow you to add a
> nonlocal (i.e. Athena) user to a local group. So, my guess is that
> what is happening here is that you deleted the local wdc user, and
> then you tried to add the (nonlocal) wdc user to the local admin
> group, which is prevented in a way that I would expect to
> potentially result in a usage message.
Uh, really? That kind of sucks. We've been operating under the
assumption that the right thing to do is add an Athena user to the
local admin group, so that they can
a) sudo
b) Have the little update notifier thing in the panel run.
Also, it seems to work just fine on my Athena 10 machine as
described. If there is no way for an Athena user to be added to the
admin group, then we need to completely rethink a lot of things in
documentation. Also, if this is the case, why was it not pointed out
a month ago that the documentation is incorrect?
-Jon
