Yes, but the problem is exactly what the problem is and nothing else. So, my response remains the same: you have a problem with the permissions.
Quote:
mkfs.ext2 -q /dev/ram1 63400
mount /dev/ram1 /home
cp -R -p /backup/home /
chown -R username:usergroup /home/username
chmod -R 755 /home/username
chmod 644 /home/username/.dmrc
[edit] Problems
* At login an error message appears
file $HOME/.dmrc is being ignored
file should have 644 permissions
and home directory should be owned
by user and not writable to others
|
If it means anything, I had this exact problem and solved it by doing a chown of my entire directory, to either 644 or 744. It should be 744 and I think that is what I did.
I think your problem started the exact way mine did. I copied a directory that was owned by another user into a directory owned by another user. You may not realize that's what you've done, but in fact it may be what your OS thinks you are doing.
Quote:
--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.
|
Quote:
chown -R username:usergroup /home/username
|
Try:
Code:
chown -r --from=currentuser:currentgroup /home/username
Not sure if that would make a difference.
Also, I did take a look at the commands, and they could be written better.
From what I understand, it should just be necessary to make a backup of the /home/username directory NOT the entire home directory. This may not seem important, but I'll invoke Occam's razor. One less assumption for us to worry about.
It may be necessary to rewrite those commands.
so try this
Code:
mkfs.ext2 -q /dev/ram1 63400
mount /dev/ram1 /home/username
cp -R -p /backup/home/username /home/username
sudo chown -R --from=currentuser:currentgroup /home/username
sudo chmod -R 755 /home/username
sudo chmod 644 /home/username/.dmrc
OK, just to briefly explain my changes, We are now mounting /dev/ram1 directly to the user who is logging in [assumes one user, though this could be fairly easily configured to do this for the current user, as in multiple users, whichever is logging in now].
We also copy ONLY the current user's directory from the backup to the /home/username
I made this command more specific. That is how it is read in the manpages. Once again, Occam's razor. I can't be certain that does the same thing, so I am eliminating the need to make that assumption.
BTW, if we assumed all the files were in place where they needed to be [properly mounted and copied] then the original chown commands SHOULD have done the trick. Which means that files are NOT where they need to be or there is some other problem with the mounting that the OP [on the other forum] did not take into account.
I changed the copy commands [and hopefully the chown] enough to see if it can be so easily solved or if you are going to have to do more research into ram drives.