How to chroot from live session to #! on diskAssumption: #!
What does
mount -t proc none /proc
do inside the chrooted environment?
After doing that, when I run htop or ps aux inside the chrooted environment, I can see the actual root's processes.
Does it mean mount -t proc none /proc makes the chroot more insecure?
Thank you!
I've had this problem a few times, but I'm hoping somebody can shed some light on the matter.
I first experienced this when I first started remastering LiveCD's for 11.10beta1 to make a Gnome Shell default install instead of Unity.
I'm using a rescue-live-system (similar to a live-cd) to fix some issues with my Debian server, like that:
# mkdir -p /mnt/rescue
# mount /dev/md2 /mnt/rescue
# mount --bind /dev /mnt/rescue/dev/
# mount --bind /proc /mnt/rescue/proc/
# mount --bind /sys /mnt/rescue/sys/
Now I can chroot to /mnt/rescue - but after I'm done, how to unmount the filesystem again?
umount: /mnt/rescue: target is bu
I couldn't really find anything about this yet on ServerFault and I just hit this.
I'm trying to set up a build environment using chroot, but instead of downloading ubuntu base files, I want to use my live / as base files for the chroot and use c-o-w to redirect any changes made in the chroot to other folder.
Desde un live cd.
sudo mkdir linux
sudo mount /dev/sdXY linux/
sudo mount -t proc /proc linux/proc
sudo mount --bind /dev linux/dev
sudo chroot linux/
grub-install /dev/sda
el grub está aca
sudo gedit /etc/default/grub
As stated above, Tribe will not do what you want. You can try the following though.If you are on a running Chakra you can probably install it to usb with pacman.
I understand that /proc filesystem reflects the output of various processes. Unfortunately, I have a propietary (romdump) binary that expects the mount table to appear as /proc/mnt, while my Android device appears to output it as /proc/mounts.
I've tried creating a symbolic link, but clearly this only works for actual files or directories.
Email this page
