Quote:
Originally Posted by UnknownUser
So I created a Debian image file and am trying to set it up as a chroot system on the KT. I tried both creating my own image, and using someone elses image from somewhere on these forums.. can't remember exactly where.
The problem came up when I try to use apt. It seems to lock up the entire filesystem somehow. for instance, running apt-get update will freeze in the middle of stuff (not always at the same point mind you...). Anytime any process trys to access parts of the filesystem, they hang as well. for instance, after apt hangs, I can call "ls /" fine, but "ls /mnt/us" will freeze... If I try to access a book from the kindle UI, the UI freezes... only thing I can do is a hard reset to fix it.
Seeing as how other people seem to have gotten this to work already, I'm kinda stuck as to why this is happening. Any advice here would be greatly appreciated!
|
You need to give a lot more detail of what you have done.
Normally, it would not be possible to "see" parts of the file system outside of the chroot.
So as an example of the missing information:
Did you try the reported "ls" commands from inside of the chroot?
If so, have you done some filesystem commands that make you think you should be able to see the file system outside of the chroot?
What all have you done to start the chroot prior to entering it?
Use this link for reference:
http://www.gerv.net/hacking/how-to-ask-good-questions/