![]() |
2010-05-21
, 17:00
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#51
|
![]() |
2010-05-21
, 17:21
|
|
Posts: 94 |
Thanked: 209 times |
Joined on Oct 2009
@ Germany
|
#52
|
Huh? You can always exit your chroot:ed evironment and use umount to unmount whatever has been mounted. Rebooting is ... just wrong.
![]() |
2010-05-24
, 21:08
|
Posts: 255 |
Thanked: 61 times |
Joined on Feb 2010
|
#53
|
![]() |
2010-05-29
, 09:19
|
Posts: 173 |
Thanked: 160 times |
Joined on Jan 2010
@ London, UK
|
#54
|
![]() |
2010-05-29
, 09:32
|
Posts: 173 |
Thanked: 160 times |
Joined on Jan 2010
@ London, UK
|
#55
|
First thank you again for your present work and the howto
Here is what i tried:
I downloaded your qemu-Build and registered it to run i386-binaries.
I tried to run a static linked i386-binary and a dynamic linked binary, they both worked but for the dynamic linked one i had to execute qemu explicitly:
becauseCode:../qemu-386 ./ld-linux.so.2 --library-path `pwd` ./otrdecoder
just gave me: ./ld-linux.so.2: line 1: syntax error: "(" unexpectedCode:/ld-linux.so.2 --library-path `pwd` ./otrdecoder
otrdecoder is a closed source downloader/decoder for an internet tv recorder service: www.onlinetvrecorder.com).I can execute them and the tell me about their command line arguments but they complain that they can't connect to the server. I guess that's because qemu doesn't provide network access.
Did you leave out the networking functionality of qemu in your build or did i just not configure it properly?
I just missed a few networking libraries (libresolv, libnss*), now i can run & use otrdecoder on the n900.
I did not create a full chroot environment with wine yet. Collecting all the libraries for the dynamically linked binary was enough work for me. So i can't say if that part of your howto works.
Edit: i'm doing this right now
The Following 3 Users Say Thank You to damion For This Useful Post: | ||
![]() |
2010-05-29
, 09:43
|
Posts: 173 |
Thanked: 160 times |
Joined on Jan 2010
@ London, UK
|
#56
|
"
The hardest part will be to "fill" up your chroot environment. You need an old i386 linux installation with a working xserver and wine (like i. e. slackware 10.2) and copy all the stuff that is necessary to run the xserver and wine (/etc /usr/lib /usr/X11/lib /usr/X11/bin /usr/bin /lib /bin /sbin).
My tip: Don't be a chicken and try it out. Make a backup before you start in case you need to reflash.
Put your chroot directory in /opt and be careful not to overwrite anything (like /dev on your phone or /etc). If you don't accidentally overwrite anything you just need to reboot your phone to revert the changes you made by chrooting and mounting.
![]() |
2010-05-29
, 11:05
|
|
Posts: 94 |
Thanked: 209 times |
Joined on Oct 2009
@ Germany
|
#57
|
You do not need an xserver, you should be able to talk to the existing one. In fact given time I'd investigate what the easy arm debian chroot is doing.
Good luck. One thing I mean try try is touching a file before testing on a normal x86 system, then using find / -anewer /fileyoutouched
to create a list of files for a very minimal chroot.
strace xterm 2>&1 | grep 'open("' | grep -o '"/.*",' | grep -o '[^"]*' | sort | uniq | grep -v "/dev" | grep -v "/proc" > list_xterm.txt
![]() |
2010-05-29
, 13:45
|
Posts: 173 |
Thanked: 160 times |
Joined on Jan 2010
@ London, UK
|
#58
|
![]() |
2010-05-29
, 15:26
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#59
|
![]() |
2010-06-05
, 14:18
|
Posts: 36 |
Thanked: 11 times |
Joined on Nov 2009
|
#60
|