Hey guys, nice to see you (well virtually speaking) all again.
I'm trying to accomplish another unusual thing, so, as one might naturally expected, I've run into a problem.
I just wanted to install the beta Fedora 17, but didn't have enough space on the only disk in my "slimline" HP computer.
So I installed on a USB stick, but running a distro from a USB stick is a nightmare... just driving me mad.
Well then I copied all the files into a chroot directory "/testing" and asked myself: Why not try booting into that chroot right from the start?? What is there which could prevent a system to boot from a different root?
So I'm using the kernel option:
,
which I borrowed from one guy who shared his experience with Debian.
This $mychrootinit is a custom script, which bind mounts the necessary stuff and than calls chroot command to chroot into /testing directory and
execute the init from that system
Here's the script:
Code:
#!/bin/bash
mount --bind /proc /testing/proc
mount --bind /sys /testing/sys
mount --bind /dev /testing/dev
mount --bind /tmp /testing/tmp
exec /usr/sbin/chroot /testing/ /usr/sbin/init 5
With all this stuff it boots fine, but then I can't login!
It just doesn't accept any login/password that has been created for the system in the /testing directory.
Sure enough, the /testing directory was created and all the files copied there as root.
I've checked and there ARE several virtual consoles, the graphical login runs on the 2-nd one, not on the 8th or 9th as usual. Unfortunately, I can't even check anything, cause I CAN'T LOGIN, ha-ha.
So please, what do you think could be wrong about it? Or maybe the very idea of booting into chroot is not that "smooth"?
Thanks in advance,
Kostya
