Gentoo Archives: gentoo-amd64

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] chrooted environment not available to users
Date: Tue, 13 Dec 2005 23:06:04
In Reply to: Re: [gentoo-amd64] chrooted environment not available to users by Billy Holmes
On 12/9/05, Billy Holmes <billy@××××××.net> wrote:
> Peter Humphrey wrote: > > (Pardon my butting in, Billy; I thought my experience might help Mark.) > > no worries! What you said is pretty much on target except for the > distfiles, but as Duncan said, if you run a distfile cleaner it will > clean out the original tarball, however, the ebuild *should* download > the tarball from my site if it's not in distfiles. > > I should probably edit the patch and make it default to /mnt/gentoo32. > > Do you all think that would be the default that everyone uses? I setup > my chroot over a year ago, and I don't think the chroot handbook was > around then. > -- > gentoo-amd64@g.o mailing list > >
Hi all, Sorry for the delay responding. I'm back as of yesterday from my class and starting to use my Gentoo AMD64 machine with it's chrooted environment more intensely. Things are progressing pretty nicely: Billy - I would agree with a default of /mnt/gentoo32 for now, just to match the manual. 1) Everything seems to work fine so far as root. I have Firefox, Java, Flash and mplayer all working nicely. I can browse the web pages I need to and play the wmv video training files and do the exercises just fine. 2) As a user, and using Peter's outline of how to fix my l32 setup, I am now able to get to the chrooted environment as a user. Thanks Peter! Note that I set it up as Peter suggested with the tar file in /usr/local/portage/distfiles. I take it from reading the rest of this thread that this is not required? 3) Ar root in the chrroted environment I am not able to emerge vim successfully: lightning ~ # emerge -pv vim These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] app-editors/vim-6.4 -acl -bash-completion -cscope +gpm -minimal +nls +perl +python -ruby -vim-with-x 0 kB Total size of downloads: 0 kB lightning ~ # will fail like this: config.status: creating auto/config.h make: Entering directory `/var/tmp/portage/vim-6.4/work/vim64/src' CC="i686-pc-linux-gnu-gcc -Iproto -DHAVE_CONFIG_H -O2 -march=athlon-xp -msse2 -pipe -fomit-frame-pointer -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I/usr/lib/perl5/5.8.6/i686-linux/CORE -I/usr/include/python2.4 -pthread " srcdir=. sh ./ mkdir objects make: Leaving directory `/var/tmp/portage/vim-6.4/work/vim64/src' make: *** empty string invalid as file name. Stop. * If the above messages seem to be talking about perl * and undefined references, please try re-emerging both * perl and libperl with the same USE flags. For more * information, see: * !!! ERROR: app-editors/vim-6.4 failed. !!! Function vim_src_compile, Line 516, Exitcode 0 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. lightning ~ # I'm not clear what USE flags this message says should be the same. Possibly I should remove the perl flag from vim??? lightning ~ # emerge -pv vim perl libperl These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] app-editors/vim-6.4 -acl -bash-completion -cscope +gpm -minimal +nls +perl +python -ruby -vim-with-x 0 kB [ebuild R ] dev-lang/perl-5.8.6-r8 +berkdb -build -debug -doc +gdbm -ithreads -minimal -perlsuid 0 kB [ebuild R ] sys-devel/libperl-5.8.6-r1 +berkdb -debug +gdbm -ithreads 0 kB Total size of downloads: 0 kB lightning ~ # 4) OK, after chrooting into the new environment (l32 /bin/bash) I can run Firefox, but I'm surprised to see that I have all my bookmarks from the 64-bit environment. Is this correct? 5) Probably most important, I do not have a user account in the chrooted environment yet. I've found a couple of wiki's about doing this but they seem contradictory so I'm taking that slowly. The lack of the /home/mark directory seems to get in the way of pretty basic stuff: mark@lightning / $ java-config -L [blackdown-jre-] "Blackdown JRE" (/etc/env.d/java/20blackdown-jre- [blackdown-jdk-] "Blackdown JDK" (/etc/env.d/java/20blackdown-jdk- * mark@lightning / $ java-config -s blackdown-jre- jc_options: Cannot write to ${HOME} mark@lightning / $ If I create the directory by hand I suspect I'll create problems. 6) I am not sure I'm happy with the way the wiki set up my chrooted environment. From the 64-bit environment I now see: mark@lightning ~ $ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 9614148 8224572 901200 91% / udev 255204 292 254912 1% /dev /dev/sda6 3850292 1437408 2217296 40% /usr/src /dev/sda7 11543016 1773832 9182816 17% /mnt/gentoo32 shm 255204 0 255204 0% /dev/shm none 255204 0 255204 0% /tmp/jack /dev 255204 292 254912 1% /mnt/gentoo32/dev /dev/shm 255204 0 255204 0% /mnt/gentoo32/dev/shm /usr/portage 9614148 8224572 901200 91% /mnt/gentoo32/usr/portage /tmp 9614148 8224572 901200 91% /mnt/gentoo32/tmp myth14:/video 225373664 120268192 93657152 57% /video It seems these mount -bind steps have hidden my normal disk partitions.... Anyway, that's my quick status. Thanks in advance for all your help. Cheers, Mark -- gentoo-amd64@g.o mailing list


Subject Author
[gentoo-amd64] Re: chrooted environment not available to users Duncan <1i5t5.duncan@×××.net>
Re: [gentoo-amd64] chrooted environment not available to users Billy Holmes <billy@××××××.net>