Re: chroot: wiped my home directory
On Thu, Sep 15, 2005 at 07:33:56PM +0200, Jonathan Kaye wrote:
> Actually this has turned out to be a disaster. I bind-mounted my 32bit home
> directory, which was also mounted normally. Both these mounts were in the
> fstab file. I chrooted from the 64bit system and su - mylogin name and set
> the display. I tried running openoffice and wonder of wonders it opened!
> The one thing that was strange was it acted as if my 32bit home directory
> was empty (gave my the running for the first time routine). Hmm. Well the
> result of all this was that my 32bit home directory was wiped clean. Dead!
> Gone forever! Damned inconvenient that. Suicide became a serious option but
> I salvaged what I could (yes, I know, I should have backedup my home
> directory). Anyway be warned! I'm not sure if it is the mount - bind that
> does this or the combination of having the /dev/hda1 mounted twice (once in
> its entirety and the other as a bound mount for /home (tmp and proc were
> harmless and weren't mounted twice in any event) that caused all this but I
> don't need to tell anyone what the moral of this story is.
> Now if you'll permit me, aaarrrrggghhhhhh!
I have yet to have a problem with bind mounts. It really seems
something else must have caused the problem.
My fstab has this:
none /data/.chroot/debian-pure64/proc proc defaults 0 0
/tmp /data/.chroot/debian-pure64/tmp none defaults,rbind 0 0
/dev /data/.chroot/debian-pure64/dev none defaults,rbind 0 0
/home /data/.chroot/debian-pure64/home none defaults,rbind 0 0
It has worked for 6 months so far without a problem. Of course I don't
use open office either. :)
Len Sorensen
Reply to: