Chroot, does it work on dreambox?

[jenkki700]

I'm trying to do a chroot in a telnet session on the dreambox, like
chroot /mnt/hdd
only to get
chroot: /bin/sh: No such file or directory

chroot /mnt/hdd /bin/ash doesn't work either.
It seems that chroot, sh and ash are all symbolic links pointing to busybox.
If chroot cannot be used on a dreambox, what is the point of having it in the busybox anyway?
-j

Dm500s, gemini 2.90

[noggie]

chroot works perfectly on a dreambox...

The error message you get, I would guess, is probably caused by not having a /bin/sh (or supporting shared libraries) installed in your new root (/mnt/hdd/bin/sh and/or /mnt/hdd/lib)

[CamouflageJJ]

Originally Posted by jenkki700

It seems that chroot, sh and ash are all symbolic links pointing to busybox

Choice when busybox compiled what linux cmds it can do, and those given a link to it instead of a binary. So some builds support some cmds, some not - choice of builder.

If bb binary was copied in from another build, then may be you have mismatch bb binary and links.

busybox --help

... shows what binary was actually compiled to do.

If you the builder, see line in script which adds chroot to bb config for a build I was testing ...

http://sat-industry.net/forums/showp...33&postcount=9

... and ...

http://www.busybox.net

[jenkki700]

chroot works perfectly on a dreambox...

The error message you get, I would guess, is probably caused by not having a /bin/sh (or supporting shared libraries) installed in your new root (/mnt/hdd/bin/sh and/or /mnt/hdd/lib)

Ok, this explains it. I was stuck thinking that chroot tried to load shell from old enviroment while it was in fact missing a library in the new enviroment.
Tnx m8s for your replies.