Hello,
Following your idea, I pick the *chroot command (statically linked)
fromt tomsrtbt*, and put it on my trinux floppy.
It's sometime OK, sometime not:
1) trinux floppy, using new chroot:
mount -t ext2 /dev/hda2 /mnt
chroot /mnt /bin/du # OK, no more applet not found
# and results from du
chroot /mnt /sbin/lilo -v # No more applet not found, =
# but "Fatal: geo_comp_addr
# cylinder number is too big"
2) tomsrtbt floppy:
It seems to be a lilo problem, but with tomsrtbt and the same chroot
command, the same PC, the same /dev/hda2 , the same /sbin/lilo from
/dev/hda2, etc.
mount -t ext2 /dev/hda2 /mnt
chroot /mnt /bin/du # OK
chroot /mnt /sbin/lilo -v # *OK* too, no "Fatal: ..."
I thought that, the same chroot (statically linked) and the same
/sbin/lilo (the one from /dev/ha2) will give the same result.
Have you please any idea about the origin of this difference.
Thanks
Jean Cou=E9dic
--
Matthew Franz a =E9crit :
> =
> I'll go ahead and add the standalone binary to the one of the packages
> (probably baselib.tgz) vs. mucking with busybox and then the next time =
I
> rebuilt busybox I'll add it because I'm pretty sure it isn't compiled i=
n,
> even though it appears there is a symlink.
> =
> - mdf
> =
> > Hello,
> >
> > Do you know please what is needed to chroot command:
> >
> > chroot ...: applet ot found
> >
> > chroot is linked to busybox; other commands linked to busybox seems O=
K
> > (nslookup, reboot).
> >
> > ps: on Slackware chroot is included in sh_utils package, but i do'nt
> > find this package in Trinux packages.
> >
> > Thanks
> >
> > --
> >
> > Jean Cou?dic
> > E N P C - D I T
>
|
