Jump to content
Read the Funtoo Newsletter: Summer 2023 ×
  • 0

Installation, lost at "chroot"



Hi there!

I'm new to funtoo - to linux too to be honest... :-)

I tried an installation according to the section "install" at the website.

Everything worked until i came to the headline "chroot into Funtoo"; actualy in this part it's NOT

mentioned how to chroot in the new system EXACTLY.

I tried several approachses like "chroot /dev/sdc" because there would be my root directory, according

to the previous steps.. But it doesn't work a bit. I searched the net but found nothing that helped me.

Any suggestions?

Thanks for your help


Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

Following the install instructions to the letter.

Your target install partition /dev/sdc should be mounted to the working directory which is /mnt/funtoo

The period . after chroot is a shortcut for the working directory.

# env -i HOME=/root TERM=$TERM chroot . bash -l
Find your working directory with print working directory command:

If pwd outputs /mnt/funtoo then:

# env -i HOME=/root TERM=$TERM chroot . bash -l
is the same as

# env -i HOME=/root TERM=$TERM chroot /mnt/funtoo bash -l
Link to comment
Share on other sites

  • 0

I tried  install Funtoo according tutorial from official website  http://www.funtoo.org/Install

and this tutorial : 

and everything went very well , ... until chrooting 

i got answer : ... can not run ... bin bash, .. any error  ... ( ? )

and even appear change (before #) on (chroot) but later i couldn't do nothing

I also tried  apply above advanced commands ( # env ...  ... bash -1 )

and without succes too :-( 

I can join screens

Link to comment
Share on other sites

  • 0

What I did for my chroot is more in line with the Gentoo style.

mount -t proc /proc /mnt/funtoo/proc

mount --rbind /dev /mnt/funtoo/dev

mount --make-rslave /mnt/funtoo/dev

mount --rbind /sys /mnt/funtoo/sys

mount --make-rslave /mnt/funtoo/sys

chroot /mnt/funtoo /bin/bash

This works fine for me; doing it in accordance with the docs didn't maintain my network connection for some reason. Maybe this is a bad way to chroot, but I hope this helps someone.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...