le Fri, 25 May 2007 13:42:00 +0200 The MoonSeeker <[EMAIL PROTECTED]> a écrit:
> Hi, > > Is it to possible to chroot the after we create it (USE=-iconv > ACCEPT_KEYWORDS="**" ROOT="/tmp/minime" emerge -avkN uclibc busybox > baselayout-lite dropbear), because i get this error : > > chroot /tmp/minime/ > chroot: can't execute `/bin/bash': No such file or directory > I dunno where your bash comes from, but busybox embeds ash, a bash tiny ersatz. Normally sh is the most standard shell to ask for. So try chroot /tmp/minime /bin/sh. Two other possible reasons for this error: - either you're missing some dynamic libraries. In this case chroot or any shell don't even "see" the executable file. Use ldd /bin/ash to know which. - or if you made your chroot for x86 and try to launch from (non-multilib?) x86_64 system, you could catch some of those mysterious "No such file or directory". Hope it helps. If you're looking for a robust and not-often-changing miniroot, you could consider compiling busybox statically, still against uclibc. But the smart, easy, sure and efficient way to do this is emerge crossdev genkernel genkernel make all ( creates a new kernel and all relevant modules, and the miniroot I was talking about _if_ crossdev is present ) genkernel make initrd --lots-of-cool-options ( generates an initrd for the previously made kernel. Basically involves harddrives pilots, a statical busybox with few commands and modprobe. You can append your files very easily but overwriting some is an issue, as far as I remember. ) -- [EMAIL PROTECTED] mailing list
