Chown will happen automatically on the new install then?
or do I need to issue "chown -R mark:mark /home/mark" afer I ceate mark?
You'll automatically own /home/mark, and /home/mark-old. You will not own /home/markz; that will be owned by a nonexistent 502/502. As root you will need to run chown -R mark:mark /home/markz to own it.
Because I'll automatically own mark, that means it will default to full ownership. I shouldn't run into the sme problem I just had where tow accounts jhad the same UID/GID but ownership was confused, correct?
Just to exercise my wits on this... In doing the new install, I decided to start off with a completely new user, UID/GID. Let's call it karl with UID/GID 505.
Now, it would only have ownership of karl. Nothing else, correct? I would have to join groups mark-old and markz in order to gain access to the files. I wouldn't have to issue a chown because of different GID/UIDs from mark-old and markz.
Totally unnecessary. If you did create user karl, he would own none of your personal data, only his own home. He could not join group mark and markz because those users would not exist on the new system. Creating them would only create unnecessary complication, which is what we're trying to avoid. As complication goes up, so does the chance of error.
By creating only
one user,
mark, with
UID/GID 500/500 mark would be created to own
all your present data from the start,
nothing else needed. User
mark will have
/home/mark as his
~ directory, and will try to use
no other. Things will be, for all practical matters just as they were on your old installation, before you started messing around.
The only thing different will be that some of your
personal data will be in the
/home/mark-old directory. You will have full access to it, but the obvious thing to do is
move it to the new
/home/mark directory. Your present firefox settings and bookmarks will exist in
/home/mark-old/.mozilla. If you copy that to
/home/mark/.mozilla before opening the newly installed firefox, when you first open it, all you
settings, extensions, and bookmarks will already be in place;
no first time use
setup required. The same for
each other application that has a
~/.<directory>Your new amarok installation will be different from the old, so there's no need to save any of the old amarok files. The new ones will be proper for the new version installed. You will not want to save any of the old KDE files, except some individual unique contact type items. When I did my 2010 release installations, I moved nothing from the old KDE files except my contacts.