On Wed, Sep 8, 2010 at 6:40 PM, NoOp <email@example.com> wrote:
> On 09/08/2010 01:05 PM, Tom H wrote:
>> On Tue, Sep 7, 2010 at 7:58 PM, NoOp <> wrote:
>>> So here is my question; how should/could I have done all of this
>>> easily/properly & particularly what did I miss for the GDM login name issue?
>> A WAG: without root enabled, sulogin must be use sudo behind the
>> scenes, so I don't think that there is an alternative to enabling
> I think you're right. I'll dig into it later when I have time & see if I
> can figure it out.
It doesn't really explain it but there is a patch that Ubuntu applies
to sulogin after retrieving it from Debian: Disable "root account is
locked" warning, since this is the default in Ubuntu. Document this in
From "man sulogin": If the root account is locked, as is the default
on Ubuntu, no password prompt is displayed and sulogin behaves as if
the correct password were entered.
The patch is here
but my paste's formatting has gone wild... Sorry.
>> An alternative would have been to create mavericktest and delete lucidtest.
> Yeah, but then I wouldn't have learned something :-)
> Besides, when doing that I end up with issues when I forget to set the new
> one to User ID 1000.
Of course, you can copy over some settings pre-delete (although that
might taint your profile and your testing) and change the uid to 1000
post-delete - and even script the whole thing...
ubuntu-users mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users