Debian Applications On Sharp Rom

[Meanie]

I've been toying with the idea of being able to run Debian apps (.deb packages) directly on the Sharp ROM without going through chrooted Debian. I've setup X/Qt to be able to run X and written a script that can convert a .deb file into a .ipk file. The only thing remaining is the library support since Sharp ROM uses glib 2.2.x whereas Debian uses 2.3.x. I've assembled the necessary standard C libraries and created a ipk package to upgrade them. If this works, then I will be able to download debian packages, convert them to sharp rom compatible packages and run them. This would then potentially allow me to run OpenOffice from Sharp ROM with X/Qt installed. I will know if this works when I test the glib package. I am currently on the road so cannot backup my Z to test it so watch this space when I return

[adf]

excellent!   keep us posted

[lardman]

I've assembled the necessary standard C libraries and created a ipk package to upgrade them. If this works,

Hmm, I tried upgrading libc once upon a time. It didn't work and I needed a reflash to recover. I've always wondered whether it was actually possible.

A couple of points - can the Sharp's flashROM be made rw so that you can perform the update?

Why not just install the libc files elsewhere and alter LD_LIBRARY_PATH when you run a debian app?


Si

[ken]

I've been toying with the idea of being able to run Debian apps (.deb packages) directly on the Sharp ROM without going through chrooted Debian. I've setup X/Qt

gpsdrive would be very interesting to run.  So far I haven't found ipk's for the following gpsdrive requirements (not that I've looked very hard):

pcre, xdevel (X11 development), gettext, libcrypt, glibc

I think that, and kstars would be the 2 applications I'd be very interested in seeing run on X/Qt ...

[Cresho]

GIVING MEANIE SUPPORT HERE


interested as well since c1000 has a very small onboard memory.

[omro]

This would then potentially allow me to run OpenOffice from Sharp ROM with X/Qt installed.[div align=\"right\"][a href=\"index.php?act=findpost&pid=92437\"][{POST_SNAPBACK}][/a][/div]

Would this help it to run faster?

[Meanie]

This would then potentially allow me to run OpenOffice from Sharp ROM with X/Qt installed.[div align=\"right\"][a href=\"index.php?act=findpost&pid=92437\"][{POST_SNAPBACK}][/a][/div]

Would this help it to run faster?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=92759\"][{POST_SNAPBACK}][/a][/div]

That was indeed one of the drivers for making me want to do this. I've purchased a 4 GB CF card and hope that running Debian on it directly using ext2 fs would make OO run faster and potentially, if I could eliminate Debian altogether, it should speed things up a bit too. Memory is the biggest bottleneck  There is only 64MB RAM available, but OO needs much more and hence a large swap file is required but swap is slow because its disk IO.

[evade]

It shouldn't be necessary to convert packages or launch into a full debian system running an X server.

One should be able to maintain a working Debian chroot environment but only launch the application you want and have it connect to the X/Qt server running in QTopia?  

I do somthing similar with my AMD64 System and an x86 chroot.

the process is described in detail here : https://alioth.debian.org/docman/view.php/3...o.html#id271773

 /proc /home and /tmp should be mounted within the chroot.  tmp is so that the chroot can connect to the local X server. The entries in /etc/fstab would look like this:

#debian-chroot
/home           /hdd3/debroot/home none  bind            0       0
/tmp            /hdd3/debroot/tmp none   bind            0       0
proc            /hdd3/debroot/proc proc  defaults        0       0


now to launch a program into your X/Qt server would be as simple as starting X and type this in a terminal:

chroot /hdd3/debroot
su - zaurus
export DISPLAY=:0
openoffice


or if dchroot is installed and configured you could just type this.
dchroot -c debian -d openoffice

maybe make a shortcut like this:

xlauncher dchroot -c debian -d openoffice

This should elimintate the overhead (but not the space) involved in running the entire debian system but still allow you to use aptitude to update software and solve dependencies.

I haven't tested this yet but intend to shortly on my SL-C3100

[Meanie]

It shouldn't be necessary to convert packages or launch into a full debian system running an X server.

One should be able to maintain a working Debian chroot environment but only launch the application you want and have it connect to the X/Qt server running in QTopia? 

I do somthing similar with my AMD64 System and an x86 chroot.

the process is described in detail here : https://alioth.debian.org/docman/view.php/3...o.html#id271773

 /proc /home and /tmp should be mounted within the chroot.  tmp is so that the chroot can connect to the local X server. The entries in /etc/fstab would look like this:

#debian-chroot
/home           /hdd3/debroot/home none  bind            0       0
/tmp            /hdd3/debroot/tmp none   bind            0       0
proc            /hdd3/debroot/proc proc  defaults        0       0


now to launch a program into your X/Qt server would be as simple as starting X and type this in a terminal:

chroot /hdd3/debroot
su - zaurus
export DISPLAY=:0
openoffice


or if dchroot is installed and configured you could just type this.
dchroot -c debian -d openoffice

maybe make a shortcut like this:

xlauncher dchroot -c debian -d openoffice

This should elimintate the overhead (but not the space) involved in running the entire debian system but still allow you to use aptitude to update software and solve dependencies.

I haven't tested this yet but intend to shortly on my SL-C3100
[div align=\"right\"][a href=\"index.php?act=findpost&pid=94884\"][{POST_SNAPBACK}][/a][/div]

this is basically what i am doing at the moment, but space is the issue.

xlauncher debian soffice would launch openoffice and it loads much faster now that it runs off a CF card, but the problem is that I cant use my CF wifi while my CF flash is in there.  well, i got a usb eth network...

anyway, after some testing it appears the only way to update libc libraries is by flashing the Z with a zImage.