[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: adding a 386 chroot in /home



I installed the situation you described:

# /etc/fstab
# ia32 chroot
/home           /home/chroot/sid-ia32/home none  bind            0       0
/tmp            /home/chroot/sid-ia32/tmp none   bind            0       0
proc            /home/chroot/sid-ia32/proc proc  defaults        0       0
/sys            /home/chroot/sid-ia32/sys none  bind        0       0


# chroot /home/chroot/sid-ia32/

and it work for the most part without problems.
Only evolution would not run saying that the system configuration 
was different than it expected.



On Mon, 2004-11-22 at 20:16 +0000, Alan Woodland wrote:
> It migh in practice work except for anything which tries to recurse 
> through your directory structure which might well "get stuck". Since its 
> going to be on the same FS though it might be easier than run the risk 
> of things doing this to just make a hard link for the directories in 
> /home that you want to be accesible in the chroot  (ie ln /home/username 
> /home/sid-ia32/home/username) which will work.
> 
> Alan
> 
> Alexandru Cabuz wrote:
> 
> >Hello,
> >
> >Is there any particular reason why in the AMD64 Debian howto the i386
> >chroot is setup in /var/chroot/sid-ia32 or can it be anywhere?
> >
> >I am asking because on my system /var is its own partition, and is not
> >big enough to house a i386 system. Same thing for the /, /tmp and /usr
> >filesystems. My big partition is the /home partition.
> >
> >Would there be any problem putting my chroot in /home/sid-ia32?
> >Because then, in the chroot, I would make /home point to /home in the
> >amd64 system, which would contain the chroot, so the filesystem would
> >be like the snake swallowing its own tail. Would it not freak out, or
> >in any case, protest at this state of affairs (the filesystem I mean)?
> >
> >Thanks.
> >
> >Alex.
> >
> >
> >  
> >
> 
> 



Reply to: