Re: [expert] new drive - moving directories
On Sat, Sep 30, 2000 at 10:49:32AM -0400, Hoyt wrote: It would be far simpler to boot to a floppy-based Linux like tomsrtbt to do the job. If you suggest this, than my answer is: No! The simplest thing would be to go to init level 1 and do all the moving around. And it's a lot faster than booting tomsrtbt. Alexander Skwar -- Homepage: http://www.digitalprojects.com | http://www.dp.ath.cx Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191 Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] new drive - moving directories
Patrick Erler wrote: hello MANDRAKE! i'd like to add a new harddrive to my system and move some of the bigger directories to it. i have basically no problem with the operation but one thing. beside moving uncritical directories like /home i'd like to move my /var tree and /tmp to the new drive... i'm afraid of crashing my system because there must be a time when the tree to be moved is not available to the system. i plan to [snip]] PATwere I undertaking such a task I'd avoid those concerns by shuting down my system, booting up with tomsrtbt, making the changes and then restarting my system. The self contained floppy based rescue system, tomsrtbt, can be obtained at: http://www.toms.net/rb/ Alan Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
[expert] new drive - moving directories
hello MANDRAKE! i'd like to add a new harddrive to my system and move some of the bigger directories to it. i have basically no problem with the operation but one thing. beside moving uncritical directories like /home i'd like to move my /var tree and /tmp to the new drive... i'm afraid of crashing my system because there must be a time when the tree to be moved is not available to the system. i plan to 1) cp -dpR /var /mnt/drive2 2) rm -rf /var 3) ln -s /mnt/drive2/var / what will happen between 2) and 3) when a daemon tries to write to the logs or the tmp dir? PAT -- vcard/LDAP/PGP: http://dresden-online.com/~perler/identity.html PGP fingerprint: DAC6 2FDA 1ED7 AD55 BD1F 5142 3D5F 72BF Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] new drive - moving directories
On Sat, Sep 30, 2000 at 04:03:05PM +0200, Patrick Erler wrote: 1) cp -dpR /var /mnt/drive2 2) rm -rf /var 3) ln -s /mnt/drive2/var / what will happen between 2) and 3) when a daemon tries to write to the logs or the tmp dir? If /var is just a normal directory, and not a mount point, I would do it different. 1) cp -dpR /var /mnt/drive2 2) cp -dpR /var/log /mnt/drive2/var 3) mv /var /oldvar 4) ln -s /mnt/drive2/var / 5) restart all the daemons that do logging, eg. syslogd and possibly some more 6) rm -rf /var This way, the daemons have still a valid file handle to log to, and all you might lose are some seconds of log between steps 3 and 5. And if you put all those commands on one command line you will have only a very short hole. The reason why I'd suggest to re-copy /var/log in step 2) is that the logs that are copied over to the new place are as recent as can be. Alexander Skwar -- Homepage: http://www.digitalprojects.com | http://www.dp.ath.cx Sichere Mail? Mail an [EMAIL PROTECTED] fuer GnuPG Keys ICQ:7328191 Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] new drive - moving directories
- Original Message - From: "Alexander Skwar" [EMAIL PROTECTED] To: "Patrick Erler" [EMAIL PROTECTED] Cc: "MANDRAKE" [EMAIL PROTECTED] Sent: Saturday, September 30, 2000 10:23 AM Subject: Re: [expert] new drive - moving directories On Sat, Sep 30, 2000 at 04:03:05PM +0200, Patrick Erler wrote: 1) cp -dpR /var /mnt/drive2 2) rm -rf /var 3) ln -s /mnt/drive2/var / what will happen between 2) and 3) when a daemon tries to write to the logs or the tmp dir? If /var is just a normal directory, and not a mount point, I would do it different. 1) cp -dpR /var /mnt/drive2 2) cp -dpR /var/log /mnt/drive2/var 3) mv /var /oldvar 4) ln -s /mnt/drive2/var / 5) restart all the daemons that do logging, eg. syslogd and possibly some more 6) rm -rf /var This way, the daemons have still a valid file handle to log to, and all you might lose are some seconds of log between steps 3 and 5. And if you put all those commands on one command line you will have only a very short hole. The reason why I'd suggest to re-copy /var/log in step 2) is that the logs that are copied over to the new place are as recent as can be. It would be far simpler to boot to a floppy-based Linux like tomsrtbt to do the job. Hoyt Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
