How can I chroot to some partition?

cola · 01-14-2023, 01:30 AM

I have compiled and installed glibc, ncurses, bash in /mnt/lfs.
I have installed in this way:

Code:

./configure --prefix=/mnt/lfs/usr
make
make install

Now when I try to chroot /mnt/lfs /usr/bin/bash --login, I get error:

Code:

chroot: failed to run command ‘/usr/bin/bash’: No such file or directory

Why am I getting this error?

Running ldd command has the following output:

Code:

ldd /mnt/lfs/usr/bin/bash
	linux-vdso.so.1 (0x00007fffc70ab000)
	libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007fb0e6689000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb0e6683000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb0e64ae000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fb0e6818000)

hazel · 01-14-2023, 04:14 AM

If you are making an LFS system, you must make it step by step exactly as the book says. You can't just install a few packages and expect to be able to chroot.

With the current LFS release , you start chrooting in Chapter 7, by which time you have a lot more compiled than just glibc, ncurses and bash! And you need a more complicated chroot command with some preset environmental values. See https://www.linuxfromscratch.org/lfs...07/chroot.html.

btw I think this thread should be in the LFS forum. Try self-reporting and asking the mods to move it.

derguteweka · 01-23-2023, 09:45 AM

Moin,

Quote:

Originally Posted by cola

Why am I getting this error?

At least one of the libraries/files mentioned by your ldd command seems to be not present where suspected by ldd.
You might check that and copy them by hand to the desired locations. But even if you mange to run the bash binary in your chroot - there will be many other things missing, preventing you from doing something useful with your bash.

cheers,
WK

xlfs-0.2 · 01-29-2023, 06:52 PM

> chroot: failed to run command ‘/usr/bin/bash’: No such file or directory

If you check the source of chroot.c you find it prints that message on any failure.

I assume you already checked that /usr/bin/bash is installed (usually in /bin/sh btw).

Probably the failure is your /lib /lib64 are wrong (if glibc cannot load that binary you will get the message seen: try strace you'll see)

If your lucky, delete 'ld.so.cache', try again. maybe your cache is incorrect, so let ld search when loading.

TIP: try

$ chroot /foo path-to/ldconfig

Why try that? Because it is different from other binaries it doesn't need to (load libraries to run). If it runs it means your chroot is parly working but broken and strace can show what doesn't load. If it doesn't run: your chroot is totally broken if ldconfig cannot run - start over?