On Saturday 27 March 2004 18.30, ns@nickselby.com wrote:
I was unable (or didn't see it) to tell how to let YAST know that the home directory for all my files was on /dev/hda3 .
You could have done it in the "expert partitioning" dialog. Simply select "/home" as the mount point for hda3 and tell it not to format it. It's possible to do that in the installation.
It asked me the user name and passwrd and I told it, but as I hadn't had the chance yet to put /dev/hda3 into the ftab at the time, it didn't give me the option to use /dev/hda3/username as the home directory.
I was able to create a user on the new /dev/hda2/home directory, and I was able to create a user using the directory /dev/hda3/username directory. HOWEVER, while I can log into the first, when I try to log into the second KDE complains that it can't find files, including dcop server, and crashes. Obviously, because the config files in that directory are left over from when iut was a home directory in my Suse 8.2 installation.
So: I guess the question is, which .files should I replace in the old -dev/hda3/username - directory in order that they be updated by 9.0's Yast when it creates a user? How can I replace the config files in the /dev/hda3/username director[es] so that the new installation will recognize /dev/hda3 as "home" and delete the /home directory in /dev/hda2 ?
Well, you don't want to delete /home on hda2, you want to use it as a mount point for hda3. Log in as root (that way, /home will be unused for the duration of this exercise), delete the directories you have under your new /home (or move them to hda3, depending on whether you want to keep them or not), then add a line to fstab like /dev/hda3 /home reiserfs defaults 1 2 (all in one line, naturally) Then unmount hda3 in case it is already mounted, and do "mount /home". If you already have a line in fstab pointing to hda3, then delete it. Then you're done. As for the KDE config files, the quickie way is to delete or rename /home/<user>/.kde and let it get regenerated on login. Also, in case you didn't already check it (you didn't mention it so I don't know) make sure that the home directory is actually owned by the new user you created. If you tell YaST's user creation that the home dir should be a preexisting directory, it may not be (no, not a bug, there are times when you don't want a home directory to be owned by the user, but it does make logging in with that user a bit more difficult)