I'm trying to install an encrypted root filesystem originally using loopAES with the following tools:
1. Slackware 10.1
2. Kernel 184.108.40.206
However, i found that, it reboots when my ramdisk trying to run "init" command:
If i run the program manually myself on the console:
exec /usr/bin/chroot current-parition new-partition
i.e. : exec /usr/bin/chroot . loader
It shows error:
/usr/bin/chroot: cannot run command 'loader/': Permission denied
When i switched to the next screen. The error shows:
-sh: /dev/null: Read-only file system
stderr is not a tty - where are you?
The ramdisk im using busybox 1.0
I believe that it could be a bug in loopAES, therefore, i reimplement this encrypted root file system with dm-crypt which is readily available in kernel 220.127.116.11 with the following tools:
4. busybox 1.0
Any thing that i could have missed out?
It seems like the problem lies int the /sbin/init belonging to my real root filesystem. Once it's executed, it seems to do some processing 4 a while and KAPOOF-->
My system restarts AFTER MOUNTING /dev/loop0 to /mnt directory.