Re: Change / to /Home and Reinstall Without Losing Anything?
Hi,
Thanks for that - I wondered...(will it get all the configuration files?)
Hmm...It seems the link in my first post didn't copy properly. Here it is again:
http://embraceubuntu.com/2006/01/29/...own-partition/
Here's a quote, plus code:
And another from the same link:
I don't know enough about how linux works to judge whether or not I should be concerned - but I see there is apparently reason for concern in some instances - and that's enough reason for me to be cautious.
(Someone parsed the debian command I pasted from the link in the comments section, if you're interested.)
Thanks again...
Hi,
I'm worried about what you might mean by "rooted Dolphin". I would NOT advise using Dolphin in root (aka "sudo") mode, just to copy data files. In fact, you can mess things up pretty badly doing that -- the copied files will have root privileges and the user will not be able to change them.
I'm not sure what data files would need any type of "special handling" just to copy them. I would use "cp", not "mv", so the original file stays intact, until you have confirmed that you have it. You'll have to tell more about what you read, or what this concern is.
http://embraceubuntu.com/2006/01/29/...own-partition/
Here's a quote, plus code:
Now, Copy files over:
Since the “/home” directory will have hardlinks, softlinks, files and nested directories, a regular copy (cp) may not do the job completely. Therefore, we use something we learn from the Debian archiving guide:
$cd /home/
$find . -depth -print0 | cpio --null --sparse -pvd /mnt/newhome/
Since the “/home” directory will have hardlinks, softlinks, files and nested directories, a regular copy (cp) may not do the job completely. Therefore, we use something we learn from the Debian archiving guide:
$cd /home/
$find . -depth -print0 | cpio --null --sparse -pvd /mnt/newhome/
* –sparse is used to write files with large blocks of zeros as sparse files. A sparse file is a file that may contain considerably less actual data than its size might suggest: i.e. a file with a single byte of data written at its millionth byte will be a 1MB sparse file, full of zeroes except for the last byte. Archive commands such as ‘cpio’ will usually, for efficiency, ignore the zeroes. Since we are aiming to copy exactly, –sparse here forces their recognition.
(Someone parsed the debian command I pasted from the link in the comments section, if you're interested.)
Thanks again...
Comment