[juneau-lug] Re: grub 2 / UID system mismatch

  • From: James Zuelow <James_Zuelow@xxxxxxxxxxxxxxx>
  • To: "'juneau-lug@xxxxxxxxxxxxx'" <juneau-lug@xxxxxxxxxxxxx>
  • Date: Mon, 1 Feb 2010 08:17:30 -0900

For Ubuntu you probably want to edit /etc/login.defs and change the UID_MIN 
1000 to UID_MIN 500.

It's been a while, so that might be stale advice.

KDE in Debian has a similar issue -- users created with the graphical tools 
such as start their UIDs at 500, while users created with adduser start at 1000.

The default kdmrc only lists users with a UID of 1000 or higher 
(MinShowUID=1000)

So it's a bad situation where if you use the KDE kuser gui tool to create a 
user, that user will not show up on the kdm welcome screen unless you edit 
kdmrc first and set MinShowUID to 500.  And the funny thing is that it has been 
that way for YEARS without being fixed.  Sometimes developers just dig their 
heels in and refuse to admit there is a problem.

James Zuelow
Network Specialist
City and Borough of Juneau MIS (907)586-0236 

> -----Original Message-----
> From: juneau-lug-bounce@xxxxxxxxxxxxx 
> [mailto:juneau-lug-bounce@xxxxxxxxxxxxx] On Behalf Of Jamie
> Sent: Friday, 29 January, 2010 10:39
> To: juneau-lug@xxxxxxxxxxxxx
> Subject: [juneau-lug] Re: grub 2 / UID system mismatch
> 
> Mark,
> 
> Thanks for the info.  I've got 6 or more active computers 
> using the low 
> range UIDs (>=500), plus the file server, plus countless 
> backups and one 
> new distribution that using the higher range UIDs (>=1000).  
> So my clear 
> preference would be to coax Ubuntu to follow the existing 
> plan.  And I'm 
> partially there.  My existing users can use Ubuntu with their 
> existing 
> UID.  There are a few residual programs that must get the UID 
> range from 
> something other the adduser.conf file.  The login screen 
> refuses to list 
> my users, though it sees the high range one it created.  Likewise the 
> GUI admin tool to modify users & groups doesn't see my users in the 
> lower range.  There may be other programs too. 
> 
> When I run low on more important tasks, I may try to chase this one 
> down.  I just hoped someone on this list might have an easy 
> answer.  I 
> really haven't researched it yet.
> 
> -Jamie
> 
> Mark Neyhart wrote:
> > Jamie wrote:
> >   
> >>  I thought of converting all 
> >> the users' UIDs & GIDs , but there are an awful lot of 
> files already 
> >> stamped with the existing UID/GID.  Anyone else fought this one?
> >>
> >>     
> >
> > I've been through this file ownership change.  The chown command has
> > an option just for this purpose.
> >
> >    --from=CURRENT_OWNER:CURRENT_GROUP
> >      change  the  owner and/or group of each file only if 
> its current
> >      owner and/or group match those specified here.   
> Either  may  be
> >      omitted,  in  which case a match is not required for 
> the omitted
> >      attribute.
> >
> > Along with the --recursive option the wholesale change of 
> UID/GID is a
> > piece of cake.
> > ------------------------------------
> > The Juneau Linux Users Group -- http://www.juneau-lug.org
> > This is the Juneau-LUG mailing list.
> > To unsubscribe, send an e-mail to 
> juneau-lug-request@xxxxxxxxxxxxx with the word unsubscribe in 
> the subject header.
> >   
> 
> -- 
> Browns Homepage - newest pics: 27 Dec 2009 - http://jdb.homelinux.net 
> --
> Registered Linux User No: 187845  http://counter.li.org/ 
> 
> ------------------------------------
> The Juneau Linux Users Group -- http://www.juneau-lug.org
> This is the Juneau-LUG mailing list.
> To unsubscribe, send an e-mail to 
> juneau-lug-request@xxxxxxxxxxxxx with the word unsubscribe in 
> the subject header.
> ------------------------------------
The Juneau Linux Users Group -- http://www.juneau-lug.org
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
word unsubscribe in the subject header.

Other related posts: