mikshaw
Group: Members
Posts: 4856
Joined: July 2004 |
|
Posted: Aug. 06 2006,14:59 |
|
It has an impact on RAM in that it uses less than a normal setup. One thing to note is that /home/dsl will appear to still be in /ramdisk, but that is only a link to /mnt/xxxn/home/dsl (or maybe to /home/dsl...i have never quite figured that out). You cannot send that boot option after the bootloader has done its work. However, you can run commands to accomplish the same task (it's just more work for you). I did this for a little while from /opt/bootlocal.sh before I started using the persistent home boot option. Essentially the procedure is: Become root. Create a /home directory on a linux-formatted partition (ext or reiser). Copy the /ramdisk/home/dsl directory into the new home directory, making sure you keep dsl.staff ownership of these files. Mount the new home to /home. Point the /ramdisk/home link to the new home. I'm not sure right now if this is necessary. If it's already pointing to /home then you don't have to do this.
Drawbacks....
Persistent home does not work on a currently-mounted volume, such as the partition on which KNOPPIX resides. If you need to use the same partition you must use the "toram" boot option, but that would be a bad idea for you.
Occasionally a DSL upgrade will make a small change to a config file that ultimately has a larger impact on the way DSL behaves. If you do not temporarily disable the home boot option when upgrading you may miss one or more of these config changes.
Using incorrect syntax or non-existent location while specifying a "home=" location *may* result in data loss. I did this twice while experimenting with changing home locations, although those experiments were not typical user behavior and you should not be too concerned.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|