Difference between revisions of "Change root"

From ArchWiki
Jump to: navigation, search
(Example)
(48 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 
[[Category:System recovery]]
 
[[Category:System recovery]]
{{i18n|Change Root}}
+
[[es:Change Root]]
 +
[[fa:تغییر ریشه]]
 
[[fr:Chroot]]
 
[[fr:Chroot]]
 
+
[[ja:Change Root]]
Changing Root is the process of changing of the apparent disk root directory (and the current running process and its children) to another root directory. When you change root to another directory you cannot access files and commands outside that directory. This directory is called a ''chroot jail''. Changing root is commonly done for system maintenance for such tasks as reinstalling [[Grub#Bootloader_installation|GRUB]] or resetting a forgotten password. Changing root is often done from from a LiveCD or LiveUSB into a mounted partition that contains an installed system.
+
[[ro:Chroot]]
 +
[[zh-CN:Change Root]]
 +
[[Wikipedia:Chroot|Chroot]] is the process of changing of the apparent disk root directory (and the current running process and its children) to another root directory. When you change root to another directory you cannot access files and commands outside that directory. This directory is called a ''chroot jail''. Changing root is commonly done for system maintenance, such as reinstalling the bootloader or resetting a forgotten password.
  
 
== Requirements ==
 
== Requirements ==
  
* You'll need to boot to another working Linux environment (for example, to a LiveCD or USB flash disk).  For Arch install mediums there is both the [http://www.archlinux.org/download/ LiveCD and USB Flash disk].
+
* You'll need to boot from another working Linux environment (e.g. from a LiveCD or USB flash media, or from another installed Linux distribution).
  
 
* Root privileges are required in order to chroot.
 
* Root privileges are required in order to chroot.
  
* Be sure that the architectures of the Linux environment you have booted into matches the architecture of the root directory you wish to enter (i.e. i686, x86_64). You can find the architecture of your current environment by:
+
* Be sure that the architecture of the Linux environment you have booted into matches the architecture of the root directory you wish to enter (i.e. i686, x86_64). You can find the architecture of your current environment with:
  
uname -m
+
: {{bc|# uname -m}}
  
* If you need any kernel modules loaded in the chroot environment, load them before chrooting. It may also be useful to initialize your swap ({{ic|swapon /dev/<device-or-partition-name>}}) and to connect to your network before chrooting.
+
* If you need any kernel modules loaded in the chroot environment, load them before chrooting. It may also be useful to initialize your swap ({{ic|swapon /dev/sdxY}}) and to establish an internet connection before chrooting.
  
== Mounting the device ==
+
== Mount the partitions ==
  
The device or partition with the Linux system on it will need to be mounted. To discover the kernel name of the storage device name, type:
+
The root partition of the Linux system that you're trying to chroot into needs to be mounted first. To find out the device name assigned by the kernel, run:
  
  fdisk -l
+
  # lsblk /dev/sda
  
Create a directory where you would like to mount the device or partition, then mount it:
+
You can also run the following to get an idea of your partition layout.
  
  mkdir /mnt/arch
+
  # fdisk -l
mount /dev/<device-or-partition-name> /mnt/arch
+
  
== Changing Root ==
+
Now create a directory where you would like to mount the root partition and mount it:
  
Mount the temporary filesystems:
+
# mkdir /mnt/arch
 +
# mount /dev/sda3 /mnt/arch
 +
 
 +
Next, if you have separate partitions for other parts of your system (e.g. {{ic|/boot}}, {{ic|/home}}, {{ic|/var}}, etc), you should mount them, as well:
 +
 
 +
# mount /dev/sda1 /mnt/arch/boot/
 +
# mount /dev/sdb5 /mnt/arch/home/
 +
# mount ...
 +
 
 +
While it's possible to mount filesystems after you've chrooted, it is more convenient to do so beforehand. The reasoning for this is that you'll have to unmount the temporary filesystems after you exit the chroot, so this lets you umount all the filesystems with a single command. This also allows for a safer shutdown. Because the external Linux environment knows all mounted partitions, it can safely unmount them during shutdown.
 +
 
 +
== Change root ==
 +
 
 +
Mount the temporary filesystems as root:
 +
 
 +
{{Note|Using a newer (2012) Arch release, the following commands can be replaced with {{ic|arch-chroot /mnt/arch}}. You must have {{pkg|arch-install-scripts}} installed to run arch-chroot. The following commands may still be used if you're using a different Linux distribution.}}
  
 
  cd /mnt/arch
 
  cd /mnt/arch
Line 36: Line 53:
 
  mount -t sysfs sys sys/
 
  mount -t sysfs sys sys/
 
  mount -o bind /dev dev/
 
  mount -o bind /dev dev/
 +
mount -t devpts pts dev/pts/
  
Mount other parts of your filesystem (e.g. {{ic|/boot}}, {{ic|/var}}, {{ic|/usr}}...) that reside on separate partitions but which you need access to. For example:
+
If you have established an internet connection and want to use it in the chroot environment, you may have to copy over your DNS configuration to be able to resolve hostnames.
  
  mount /dev/<device-or-partition-name> boot/
+
  cp -L /etc/resolv.conf etc/resolv.conf
  
It's possible to mount filesystems after you've chrooted, but it's more convenient to do so beforehand.  The reasoning for this is you'll have to unmount the temporary filesystems after you exit a chroot so this lets you umount all the filesystems in a single command.  This also allows a safer shutdown.  Because the external Linux environment knows all mounted partitions it can safely unmount them during shutdown.
+
Now chroot into your installed system and define your shell:
  
If you've setup your network and want to use it in the chroot environment, copy over your DNS servers so that you will be connected to the network:
+
chroot /mnt/arch /bin/bash
  
cp -L /etc/resolv.conf etc/resolv.conf
+
{{Note|If you see the error {{ic|chroot: cannot run command '/bin/bash': Exec format error}}, it is likely that the two architectures do not match.}}
  
Now chroot to your installed device or partition and define your shell:
+
Optionally, to source your Bash configuration ({{ic|~/.bashrc}} and {{ic|/etc/bash.bashrc}}), run:
  
  chroot . /bin/bash
+
  source ~/.bashrc
 +
source /etc/profile
  
If you see the error, "{{Ic|chroot: cannot run command '/bin/bash': Exec format error}}" it is likely the two architectures do not match.
+
Optionally, create a unique prompt to be able to differentiate your chroot environment:
  
If you use bash, your root {{ic|$HOME/.bashrc}} will be sourced on login provided your {{ic|~/.bash_profile}} specifies it ({{Ic|source ~/.bashrc}}).  To source your chrooted, global bash configuration do:
+
export PS1="(chroot) $PS1"
  
  source /etc/profile
+
== Run graphical chrooted applications ==
  
If your bash configuration doesn't use a unique prompt, consider creating one to be able to differentiate your chroot environment:
+
If you have [[X]] running on your system, you can start graphical applications from the chroot environment.
  
  export PS1="(chroot) $PS1"
+
To allow the connection to your X server, you have to run the following from a terminal:
  
== Perform System Maintenance ==
+
# xhost +
  
At this point you can perform whatever system maintenance you require inside the chroot environment, some common examples being:
+
Then, to direct the applications to your X server, run:
  
* Upgrade or [[Downgrading_Packages|downgrade]] packages
+
# export DISPLAY=:0.0
* [[Mkinitcpio|Rebuild your initcpio image]]
+
* Reset a [[Password_Recovery|forgotten password]]
+
* Fix your [[Fstab|/etc/fstab]]
+
* [[GRUB#Bootloader_installation|Reinstall GRUB]].
+
  
== Exiting chroot ==
+
== Perform system maintenance ==
  
When you're finished with system maintenance, exit the chroot shell:
+
At this point you can perform whatever system maintenance you require inside the chroot environment. A few common examples are:
  
  exit
+
* Reinstall the bootloader.
 +
* Rebuild your [[mkinitcpio|initramfs]] image.
 +
* Upgrade or [[Downgrading_Packages|downgrade]] packages.
 +
* Reset a [[Password_Recovery|forgotten password]].
 +
 
 +
== Exit the chroot environment ==
 +
 
 +
When you're finished with system maintenance, exit the chroot:
 +
 
 +
  # exit
  
 
Then unmount the temporary filesystems and any mounted devices:
 
Then unmount the temporary filesystems and any mounted devices:
  
  umount {proc,sys,dev,boot...}
+
  # umount {proc,sys,dev,boot,[...],}
  
Finally attempt to unmount your hard drive:
+
Finally, attempt to unmount your root partition:
  
  cd ..
+
  # cd ..
  umount arch/
+
  # umount arch/
  
If you get an error saying that {{ic|/mnt}} (or any other partition) is busy, this can mean one of two things:
+
{{Note|If you get an error saying that {{ic|/mnt}} (or any other partition) is busy, this can mean one of two things:
  
 
* A program was left running inside of the chroot.
 
* A program was left running inside of the chroot.
* Or more frequently: a sub-mount still exists. For example, {{ic|/mnt/arch/usr}} within {{ic|/mnt/arch}}.
 
  
In the latter case, unmount the sub-mount mount point first. To get a reminder of all the current mount points, run {{Ic|mount}} with no parameters. If you still are unable to mount a partition, use the force option:
+
* Or, more frequently, a sub-mount still exists (e.g. {{ic|/mnt/arch/boot}} within {{ic|/mnt/arch}}). Check with {{ic|lsblk}} to see if there are any mountpoints left:
 +
 
 +
: {{bc|lsblk /dev/sda}}
  
umount -f /mnt
+
: If you are still unable to unmount a partition, use the {{ic|--force}} option:
  
After this you will be able to safely reboot.
+
: {{bc|# umount -f /mnt}}}}
  
== Resources ==
+
After this, you will be able to safely reboot.
  
* [http://en.wikipedia.org/wiki/Chroot Wikipedia] - for the introduction.
+
== Example ==
 +
This may protect your system from Internet attacks during browsing:
 +
{{bc|1=
 +
# # as root:
 +
# cd /home/''user''
 +
# mkdir myroot
 +
# pacman -S arch-install-scripts
 +
# # pacstrap must see myroot as mounted:
 +
# mount --bind myroot myroot
 +
# pacstrap -i myroot base base-devel
 +
# mount -t proc proc myroot/proc/
 +
# mount -t sysfs sys myroot/sys/
 +
# mount -o bind /dev myroot/dev/
 +
# mount -t devpts pts myroot/dev/pts/
 +
# cp -i /etc/resolv.conf myroot/etc/
 +
# chroot myroot
 +
# # inside chroot:
 +
# passwd # set a password
 +
# useradd -m -s /bin/bash ''user''
 +
# passwd ''user'' # set a password
 +
# # in a shell outside the chroot:
 +
# pacman -S xorg-server-xnest
 +
# # in a shell outside the chroot you can run this as ''user'':
 +
$ Xnest -ac -geometry 1024x716+0+0 :1
 +
# # continue inside the chroot:
 +
# pacman -S xterm
 +
# DISPLAY=:1
 +
# xterm
 +
# # xterm is now running in Xnest
 +
# pacman -S xorg-server xorg-xinit xorg-server-utils
 +
# pacman -S openbox
 +
# # for java we need icedtea-web which requires some fonts:
 +
# nano /etc/locale.gen
 +
# # uncomment en_US.UTF-8 UTF-8, save and exit
 +
# locale-gen
 +
# echo LANG=en_US.UTF-8 > /etc/locale.conf
 +
# export LANG=en_US.UTF-8
 +
# pacman -S ttf-dejavu
 +
# pacman -S icedtea-web
 +
# pacman -S firefox
 +
# firefox
 +
# # firefox is now running in Xnest
 +
# exit
 +
# # outside chroot:
 +
# chroot --userspec=''user'' myroot
 +
# # inside chroot as ''user'':
 +
$ DISPLAY=:1
 +
$ openbox &
 +
$ HOME="/home/''user''"
 +
$ firefox
 +
}}
 +
See also: [https://help.ubuntu.com/community/BasicChroot Basic Chroot]

Revision as of 10:38, 16 February 2013

Chroot is the process of changing of the apparent disk root directory (and the current running process and its children) to another root directory. When you change root to another directory you cannot access files and commands outside that directory. This directory is called a chroot jail. Changing root is commonly done for system maintenance, such as reinstalling the bootloader or resetting a forgotten password.

Requirements

  • You'll need to boot from another working Linux environment (e.g. from a LiveCD or USB flash media, or from another installed Linux distribution).
  • Root privileges are required in order to chroot.
  • Be sure that the architecture of the Linux environment you have booted into matches the architecture of the root directory you wish to enter (i.e. i686, x86_64). You can find the architecture of your current environment with:
# uname -m
  • If you need any kernel modules loaded in the chroot environment, load them before chrooting. It may also be useful to initialize your swap (swapon /dev/sdxY) and to establish an internet connection before chrooting.

Mount the partitions

The root partition of the Linux system that you're trying to chroot into needs to be mounted first. To find out the device name assigned by the kernel, run:

# lsblk /dev/sda

You can also run the following to get an idea of your partition layout.

# fdisk -l

Now create a directory where you would like to mount the root partition and mount it:

# mkdir /mnt/arch
# mount /dev/sda3 /mnt/arch

Next, if you have separate partitions for other parts of your system (e.g. /boot, /home, /var, etc), you should mount them, as well:

# mount /dev/sda1 /mnt/arch/boot/
# mount /dev/sdb5 /mnt/arch/home/
# mount ...

While it's possible to mount filesystems after you've chrooted, it is more convenient to do so beforehand. The reasoning for this is that you'll have to unmount the temporary filesystems after you exit the chroot, so this lets you umount all the filesystems with a single command. This also allows for a safer shutdown. Because the external Linux environment knows all mounted partitions, it can safely unmount them during shutdown.

Change root

Mount the temporary filesystems as root:

Note: Using a newer (2012) Arch release, the following commands can be replaced with arch-chroot /mnt/arch. You must have arch-install-scripts installed to run arch-chroot. The following commands may still be used if you're using a different Linux distribution.
cd /mnt/arch
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount -t devpts pts dev/pts/

If you have established an internet connection and want to use it in the chroot environment, you may have to copy over your DNS configuration to be able to resolve hostnames.

cp -L /etc/resolv.conf etc/resolv.conf

Now chroot into your installed system and define your shell:

chroot /mnt/arch /bin/bash
Note: If you see the error chroot: cannot run command '/bin/bash': Exec format error, it is likely that the two architectures do not match.

Optionally, to source your Bash configuration (~/.bashrc and /etc/bash.bashrc), run:

source ~/.bashrc
source /etc/profile

Optionally, create a unique prompt to be able to differentiate your chroot environment:

export PS1="(chroot) $PS1"

Run graphical chrooted applications

If you have X running on your system, you can start graphical applications from the chroot environment.

To allow the connection to your X server, you have to run the following from a terminal:

# xhost +

Then, to direct the applications to your X server, run:

# export DISPLAY=:0.0

Perform system maintenance

At this point you can perform whatever system maintenance you require inside the chroot environment. A few common examples are:

Exit the chroot environment

When you're finished with system maintenance, exit the chroot:

# exit

Then unmount the temporary filesystems and any mounted devices:

# umount {proc,sys,dev,boot,[...],}

Finally, attempt to unmount your root partition:

# cd ..
# umount arch/
Note: If you get an error saying that /mnt (or any other partition) is busy, this can mean one of two things:
  • A program was left running inside of the chroot.
  • Or, more frequently, a sub-mount still exists (e.g. /mnt/arch/boot within /mnt/arch). Check with lsblk to see if there are any mountpoints left:
lsblk /dev/sda
If you are still unable to unmount a partition, use the --force option:
# umount -f /mnt

After this, you will be able to safely reboot.

Example

This may protect your system from Internet attacks during browsing:

# # as root: 
# cd /home/user
# mkdir myroot
# pacman -S arch-install-scripts
# # pacstrap must see myroot as mounted: 
# mount --bind myroot myroot
# pacstrap -i myroot base base-devel
# mount -t proc proc myroot/proc/
# mount -t sysfs sys myroot/sys/
# mount -o bind /dev myroot/dev/
# mount -t devpts pts myroot/dev/pts/
# cp -i /etc/resolv.conf myroot/etc/
# chroot myroot
# # inside chroot: 
# passwd # set a password 
# useradd -m -s /bin/bash user
# passwd user # set a password
# # in a shell outside the chroot: 
# pacman -S xorg-server-xnest
# # in a shell outside the chroot you can run this as user: 
$ Xnest -ac -geometry 1024x716+0+0 :1
# # continue inside the chroot: 
# pacman -S xterm
# DISPLAY=:1
# xterm
# # xterm is now running in Xnest 
# pacman -S xorg-server xorg-xinit xorg-server-utils
# pacman -S openbox
# # for java we need icedtea-web which requires some fonts: 
# nano /etc/locale.gen
# # uncomment en_US.UTF-8 UTF-8, save and exit 
# locale-gen
# echo LANG=en_US.UTF-8 > /etc/locale.conf
# export LANG=en_US.UTF-8
# pacman -S ttf-dejavu
# pacman -S icedtea-web
# pacman -S firefox
# firefox
# # firefox is now running in Xnest 
# exit
# # outside chroot: 
# chroot --userspec=user myroot
# # inside chroot as user: 
$ DISPLAY=:1
$ openbox &
$ HOME="/home/user"
$ firefox

See also: Basic Chroot