Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Input Devices Red Hat Software Linux

Fedora 16 Will Number UIDs From 1000 124

dotancohen writes "Sharing users between Fedora and Debian-based distros just got a little easier. Beginning with Fedora 16, the Red-Hat based distro will number its human user UIDs starting from 1000, as opposed to the old 500. Though this change is intended to facilitate interoperability with other distros, it risks breaking backward compatibility with older Fedora releases including the newly released Fedora 15."
This discussion has been archived. No new comments can be posted.

Fedora 16 Will Number UIDs From 1000

Comments Filter:
  • by armanox ( 826486 ) <asherewindknight@yahoo.com> on Wednesday May 25, 2011 @12:12PM (#36239928) Homepage Journal

    time_t is fixed for 64-bit systems. And for the 32-bit systems, well, we still have until 2038 to fix that problem.

  • Re:Am I the only one (Score:4, Informative)

    by nabsltd ( 1313397 ) on Wednesday May 25, 2011 @02:30PM (#36241978)

    I'm perfectly fine with them changing the default... but MAKE IT CONFIGURABLE! It'd just have to be one file in /etc, so one could easily jack with it for migrations. How difficult is that?!? Who knows, maybe it already exists and I just couldn't find it?

    You mean like /etc/login.defs?

  • Re:Am I the only one (Score:5, Informative)

    by icebike ( 68054 ) on Wednesday May 25, 2011 @02:43PM (#36242148)

    If you're talking about an upgrade, then no. Change the UIDs and all of the files that were owned by the previous UIDs are now orphans.

    Nonetheless, this still seems utterly unimportant.

    Well, actually, that's not exactly true.

    I've been thru this with other distros in the past, and in-place upgrades are never really a problem as you mention,
    because the same users/groups are retained. Therefore no files become orphans.

    New users just start higher when they are added. You can also make a simple setting to continue using 500 as the first user
    if you want, you are not forced to start at 1000.

    Moving data to a new server is where it gets messy, to say nothing about NFS coordination.

    In our case, being a small size installations we opted to simply build a "find and chown" script to be run once, rather than
    continuing with the legacy numbering.

If all else fails, lower your standards.

Working...