I get errors trying to load debian.

Code:

$ su # bootdeb bootdeb: not found # _

If I follow this advice: masterjedidan wrote:

QUOTE:
When installing and running Debian, simply typing in 'bootdeb' in order to boot the system didn't work for me. I renamed the 'bootdeb' file to 'bootdeb.sh' and ran 'sh bootdeb.sh' in the terminal in order to start debian.

I get the following:

Code:

$ su # sh bootdeb.sh sh: Can't open bootdeb.sh # _

What's going on?

I finally got it to work!!! Yay me!

@jook

cd into the debian directory that the bootdeb file is in. If it is still called bootdeb.sh remove the .sh.
(Run su at this point. I noticed in your post that the line started with $ and not #. Starting with $ means you haven't invoked root, # does.)
Then run

Code:

modprobe ext2

followed by

Code:

su bootdeb

Keep in mind that even though you've already invoked root with 'su', you must still include it in the launch command. Something else I noticed is that these guides don't use modprobe when I think I would work much better because it already has these modules incorporated. But then again, there's probably something I'm not seeing. (Input from the community to confirm/deny this would be very appreciated.) One problem I'm having. I'm still trying to make the file system for the debain image available under android, but when I run

Code:

mount -t unionfs -o dirs=$mnt/etc=rw:/etc=ro unionfs /etc

I get

Code:

mount: mounting unionfs on /etc failed: invalid argument

Can I get some help here?

actually, I copied bootdeb and made a spare one called bootdeb.sh. Seemed more efficient than constantly mounting the memory card to change a filename and try something else.
Anyway, your advice worked. Am I going to need to modprobe each time? or was I just missing the cd /sdcard/debian/ ?

jook wrote:

QUOTE:
Am I going to need to modprobe each time? or was I just missing the cd /sdcard/debian/ ?

Yes and no.

The cd command simply (If there is a dev reading this and can explain it better, PLEASE do so) changes the directory that the terminal is paying attention to. When the terminal emulator starts fresh it looks at the / (aka root ) directory. This directory hold various files/folders that make up android. Among those is /sdcard, which is where the sdcard's files are shown in the file system's hierarchy. However commands than run continuously (like telnetd for example) will persist even when the emulator closes (my definition of close is not even running in the background ). When it comes to actually launching debian, you can use two different options.

A:
su
cd /sdcard/debian
su bootdeb

or B:
su
su /sdcard/debian/bootdeb


As for modprobe, you will only need to reuse it after you turn you phone off. Until then you can skip that step.
I'm gonna try a little experiment. I'll edit this post after I've tried. Should be done about 10 minutes after the timestamp of this post.

DONE!!!
First download Text Edit from the market.
Use it to open the file /sdcard/debian/bootdeb.
Look for the line that says, busybox insmod ext2
Edit it to read busybox modprobe ext2 (be sure to save!)
Launch it.
This edit will silently use the modprobe that I mentioned earlier.
I have another idea. Give me another 10 minutes.

EDIT:
Idea was to place a script that would trigger the bootdeb script in the / directory. The system won't let me. Oh well.
I still want to make the debian files visible to android, but I'll try again another day.

I've got debian booting now, seems my problem was just not going to /sdcard/debian/ first, I suppose. Now I want a GUI, since I don't have any experience with linux anyway, and a command-line interface isn't that useful to me.
Honestly, I dunno why I'm doing this anyway. No idea what there is to gain. We'll see.

I'm getting space errors trying to install GUIs though. I suppose I need a bigger memory stick.