Desire Debian

[Guest aaaloha]

Hi ther!

I am wondering if any of you Desire owners out here have managed to install/mount the debian image on their device.

We can have write access to the system path (/system) and basicly moving everything in the right position/permission would allow to execute the bootdeb shellscript.

Is there anyone that has experience with this?

Thanks for your time! :lol: :)

Aaaloha

Desire/Root/AuraxTSense/Busybox

Edited September 24, 2010 by aaaloha

[Guest DragosP]

Do you mean something like this?

[Guest mrshark]

and, except for the fact that eventually you can do it, what's the purpose? it's an OS not designed for these devices...

[Guest aaaloha]

Thankyou I didnt see that post before! useful :lol:

@mrshark: Because theres things you can do with linux, that you cannot do with android os.

and the other way around, thats why I want both B)

Edited September 24, 2010 by aaaloha

[Guest woti17]

and, except for the fact that eventually you can do it, what's the purpose? it's an OS not designed for these devices...

maybe to run a vlc? as streaming proxy to play all formats vlc can on your phone?

@original poster: i have it running (took the same link to install but modified the boot script a little to get it running)

but i don't think you get full-root (writeable /system), it runs in an chroot jail, you have the same drivers and kernelmodule for hardware as android, maybe im wrong here?

nevertheless its good to have, there are a lot arm-compiled programms for debian you can use that dont exist for android

[Guest aaaloha]

@Woti: :lol: can you post that modificated bootscript here? that would be nice

What I get when i run the bootdeb from that post is.

# su

su

# bootdeb

bootdeb

uid=0(root) gid=0(root)

←[H←[J

a888a

d888888b

8P YP Y88

8|o||o|88

8. .88

8 ._. Y8.

d/ 8b.

.dP . Y8b.

d8: ::88b.

d8 Y88b

:8P :888

8a. : _a88P

._/ Yaa_ : .| 88P|

\ YP | 8P \.

/ \._____.d| .|

--..__)888888P ._.|

Usage: mount [-r] [-w] [-o options] [-t type] device directory

/system/bin/bootdeb: cannot create /data/local/mnt/etc/resolv.conf: directory no

nexistent

mount: No such file or directory

mount: No such file or directory

mount: No such file or directory

mount: No such file or directory

mount: No such file or directory

mount: No such file or directory

Bad mode

mount: No such file or directory

Bad mode

mount: No such file or directory

Bad mode

mkdir failed for -p, Read-only file system

mount: No such file or directory

mkdir failed for -p, Read-only file system

mount: No such file or directory

mkdir failed for -p, Read-only file system

mount: No such file or directory

Android directories are mounted under /android/

Type exit to end session

Make sure you do a proper exit for a clean kill of Debian!

chroot: can't execute '/bin/bash': No such file or directory

Shutting down Debian........

#

[Guest woti17]

@Woti: :lol: can you post that modificated bootscript here? that would be nice

for the debian.img look at:

http://forum.xda-developers.com/showthread.php?p=7503343

script started with

root@localhost#> cd /sdcard ; sh aboot

(thats how i called the script "aboot")

btw: debian can't be exit, you have to reboot the phone, at least thats my knowledge from the time i last read the thread at xda, maybe there is a solution now

export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH

export TERM=linux

export HOME=/root

mkdir -p /sdcard/debian

losetup /dev/block/loop5 /sdcard/debian.img

mount -t ext2 /dev/block/loop5 /sdcard/debian

rm -rf /sdcard/debian/tmp

mkdir /sdcard/debian/tmp

mount -t devpts devpts /sdcard/debian/dev/pts

mount -t proc proc /sdcard/debian/proc

mount -t sysfs sysfs /sdcard/debian/sys

busybox mount /sdcard /sdcard/debian/root/sdcard

sysctl -w net.ipv4.ip_forward=1

chroot /sdcard/debian /bin/bash

[Guest aaaloha]

Thanks thats pretty straight forward.

Only problem I keep encountering is the error i get when i try to mount the loop:

# losetup /dev/block/loop5 /sdcard/debian/debian.img

losetup /dev/block/loop5 /sdcard/debian/debian.img

losetup: /dev/block/loop5

^no problems there.

# mount -t ext2 /dev/block/loop5 /sdcard/debian

mount: Device or resource busy

What ever I try when I want to mount it gives me that "device or resource busy".

Which makes me doubt that loop devices are enabled in the kernel build.

Trying a different rom soon, thanks for the help!

[Guest woti17]

Thanks thats pretty straight forward.

Only problem I keep encountering is the error i get when i try to mount the loop:

# losetup /dev/block/loop5 /sdcard/debian/debian.img

losetup /dev/block/loop5 /sdcard/debian/debian.img

losetup: /dev/block/loop5

^no problems there.

# mount -t ext2 /dev/block/loop5 /sdcard/debian

mount: Device or resource busy

What ever I try when I want to mount it gives me that "device or resource busy".

Which makes me doubt that loop devices are enabled in the kernel build.

Trying a different rom soon, thanks for the help!

kernel-config should show if loop dev is enabled

zcat /proc/config.gz | more

if devs exist, they should be seen

ls -l /dev/block/loop*

i don't think loop5 is a must, try an other number?

and/or reboot before running again

hope this helps, btw r9 kernel should have loop devices enabled

mount -a should show the mounted loop device

Edited September 26, 2010 by woti17

[Guest aaaloha]

Strange, "zcat /proc/config.gz | more" does show that loops is enabled (CONFIG_BLK_DEV_LOOP=y), everything seems normal apart from the fact that my loop devices are always "busy", so changing loop device number didnt matter much for me.

Trying with a new microsd soon, i read something about 16g not working and for those ppl with 4 gb it did work, which doesnt make any sense but im desperate enough to try it B).

Will update this as soon as i know more..

PS: Anyone with Neophyte360's roms got it to work?

mount shows:

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mtdblock3 /data/local/mnt/system_ro yaffs2 ro,relatime 0 0

/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0

/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev,relatime 0 0

tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0

unionfs /data/local/mnt/system_union fuse.unionfs rw,nodev,relatime,user_id=0,gr

oup_id=0,default_permissions,allow_other 0 0

unionfs /system fuse.unionfs rw,nodev,relatime,user_id=0,group_id=0,default_perm

issions,allow_other 0 0

/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,errors=continue 0 0

/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u

id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset

=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

is about normal right?

Thanks for your time :lol:

Edited September 28, 2010 by aaaloha

[Guest woti17]

Strange, "zcat /proc/config.gz | more" does show that loops is enabled (CONFIG_BLK_DEV_LOOP=y), everything seems normal apart from the fact that my loop devices are always "busy", so changing loop device number didnt matter much for me.

Trying with a new microsd soon, i read something about 16g not working and for those ppl with 4 gb it did work, which doesnt make any sense but im desperate enough to try it :lol:.

Will update this as soon as i know more..

16gb is allright

look into what app is on sd (preferences / applications / manage applications / apps on sd)

the resource busy comes from "new school" apps2sd,

remove the apps back to phone, you should be done

[Guest aaaloha]

16gb is allright

look into what app is on sd (preferences / applications / manage applications / apps on sd)

the resource busy comes from "new school" apps2sd,

remove the apps back to phone, you should be done

woti youre the best!

Thank you soo much

that was problem indeed, the apps on the sdcard were moved to the phone and voila!

resources became available

"localhost:/#"

:lol: B) B) :lol: :lol: :) :o

Thanks so much for sharing your wisdom. :o