I'll wait until we work out what to do in regards to using a virtual keyboard with Open Office, then I'm in like Flyn

Your step by step in that post is hard to follow

-Where to I place the image?"check if the content of "/home/user/.chroot" is correct (pointing to the debian image file, etc)"

-How do I set .chroot to that image.
-Where you say to add to PATH - how?"- add "/usr/sbin" to the the PATH by adding the line: export PATH=/sbin:/usr/sbin:$PATH
to /home/user/.profile"
exactly what do I type into terminal?
Thanks

How come nobody's willing to write a detailed step by step on how to install/mount this thing for noobs.

I can follow step-by-step directions easily (as can most people), and with having open-mode kernel (e-yes's dual boot one) I think I should be able to get debian up and running on my 64G N9.

Please someone, write it up.......even better if
qole can do the writeup for open mode and
rcolistete for inception

Or whoever wants to....

I would greatly appreciate it.

With devel-su I get
BusyBox v1.20.0.git (MeeGo 3:1.20-0.1+0m7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ devel-su
Password:


BusyBox v1.20.0.git (MeeGo 3:1.20-0.1+0m7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # debian
Chroot dir specified: /.debian
/home/user/MyDocs/debian-m5-v3e.img.ext2 specified in ~/.chroot
Mounting...
using image file: /home/user/MyDocs/debian-m5-v3e.img.ext2
fs type is ext2
Using ext2 file system
/bin/qmount: line 203: modprobe: not found
mounting /home/user/MyDocs/debian-m5-v3e.img.ext2 on loop
Mount failure! /home/user/MyDocs/debian-m5-v3e.img.ext2 failed to mount on loop2 mount: mounting /dev/loop1 on /.debian failed: Device or resource busy
Cancelling chroot...
~ #

with opensh
~ # opensh


BusyBox v1.20.0.git (MeeGo 3:1.20-0.1+0m7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # debian
/bin/debian: line 30: can't create /dev/stderr: Permission denied
/bin/debian: line 49: can't create /dev/stderr: Permission denied
mount: permission denied (are you root?)
Mounting...
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
Using ext2 file system
/bin/qmount: line 203: modprobe: not found
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
Cancelling chroot...
~ #

like you can see...Im lost

Post 57 is clear as day, if those instructions are not clear enough for you then, trust me, you do not want to mess around that deep in the bowels of your phone.

Now please stop whining on this thread.

Yea......whatever

The wrong step is precisely in the first line of your code. devel-su doesn't grant you all of the available privileges, even though you may be running open mode. If so, please install opensh from here and you are good to go, use it instead of devel-su. If you are in normal mode, you need Inception and aegisctl, then install opensh through Inception then loosen Aegis security a bit
and try to mount the chroot as you have before.

I'm in open-mode

~ # opensh


BusyBox v1.20.0.git (MeeGo 3:1.20-0.1+0m7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # debian
/bin/debian: line 30: can't create /dev/stderr: Permission denied
/bin/debian: line 49: can't create /dev/stderr: Permission denied
mount: permission denied (are you root?)
Mounting...
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
Using ext2 file system
/bin/qmount: line 203: modprobe: not found
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
/bin/qmount: line 203: can't create /dev/stderr: Permission denied
Cancelling chroot...
~ #

OK, so now you are root with opensh. The problem seems to be that the script can't find some executables, in this case modprobe (which is used to insert modules in the kernel - the ext2 file system module, here, since N9 doesn't use that by default).
To start, the error you currently have comes from the qmount script. It says it can't find modprobe. By default, Linux systems store user-and-root-executable programs in the /usr/bin directory and only-root-executables in /sbin. Therefore, it is possible that since these scripts are a direct port from the N900, modprobe was in /usr/src on the N900, but it's in /sbin on the N9.
So, what you have to do is edit at least the closechroot, qchroot, qmount, qumount, synchroot and debian scripts and correct every path of a program that gives you an error when trying to chroot.
Here it clearly says modprobe, so, in the file qmount, replace modprobe with /sbin/modprobe. You could also look in /usr/sbin, some important programs are there instead.
And so on and so forth until you have corrected all the paths, which is when you'll have a fully functional chroot. Sorry for the lenghty post, I hope it helps.

I have update the post #57 with more detailed instructions about your above doubts. Read and follow the instructions.