Alex Samad wrote: > On Wed, Sep 16, 2009 at 10:17:26AM -0400, Robert P. J. Day wrote: >> On Wed, 16 Sep 2009, Sjoerd Hardeman wrote: >> >> > Kept thinking a bit longer: are the uids and gids of daemon users >> > actually determined during install? My experience is that these >> > users actually preserve their uid over installations quite well. >> >> nope. for example, on the old system, openldap account has a UID of >> 114. on new system, 105. numerous other daemon UID differences as >> well. so a straight copy isn't going to work here. this just gets >> trickier and trickier. > > if you have coped over the passwd/group/shadow file they should align > up, package should check to see if the uid/gid exists before creating > new ones. the only time this doesn't happen is when you do a new > install and the first packages are installed - you can't get the > passwd/group files over before then (maybe that should be a bugreport!) > > any way I use this little script to check and modify GID - it creates a > bunch of shell commands to execute >
OK, thanks for confirming, so I could cheat the installer by copying over the passwd and group files after partitioning is done and go on with the system install. Then apply set-selection and after this migrate the config and data files from the old system. Correct? this looks to be a compact way to do the job. The only thing that should be migrated in this case are databases, Correct? How can the above be applied to debootstrap - it's my favorite one for installing new systems. I'm testing this now and will report if it works. The start was promissing regards regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
