OK so I fixed my BIOS clock and have returned to the present day.... Remember that the chroot command is looking for /bin/bash in the NEW root, not the current root. So from your live environment you have to check with this command: ls -l /mnt/hd/bin/bash
It's like when we were looking for init, but this time for the shell program. This MUST exist for all of this to work. On Sat, Nov 24, 2018 at 6:16 PM Dick Steffens <[email protected]> wrote: > On 11/24/18 5:56 PM, Tomas K wrote: > > chroot command simply sets different root directory for a command - > > thus that command: > > a) sees different root directory > > b) cannot access anything outside that directory (aka chroot jail) > > > > Example: > > 1. Imagine you just mounted: > > mount /dev/sda2 /mnt/hd > > 2. Executing: > > sudo chroot /mnt/hd /bin/bash > > will execute bash from inside /mnt/hd (running /mnt/hd/bin/bash) > > as if you would have booted from there > > > > What Ben, most likely, wants to guide you through is running lilo as if > > booted from the disk mounted on /mnt/hd - thus updating the Lilo > > config. > > > > I will not guess further because I forgot most things about Lilo long > > time ago. The Linuxes I use boot using Grub for long time and/or boot > > using UEFI directly these days. > > > > Hope it makes sense. > > Tomas > > Makes sense, but isn't working. I'm logged in as root, so I didn't use > sudo, but otherwise, I ran it the same: > > chroot /mnt/hd /bin/bash > > and got : > > chroot: failed to run command '/bin/bash': No such file or directory > > -- > Regards, > > Dick Steffens > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
