Distributions

From OESF

(Difference between revisions)
Jump to: navigation, search
(→Ã…ngström)
Current revision (02:33, 26 December 2008) (edit) (undo)
(→Debian)
 

(20 intermediate revisions not shown.)

Line 1:

Line 1:

-
'''Overview of available software distributions from a user's point of view:'''
+
'''Overview of available software distributions from a user's point of view.'''
-
This page is intended for users new to the Zaurus community or those who never found the time try out alternatives.
+
 
 +
This article is aimed at explaining the different distributions in detail.
 +
 
 +
* Users new to the Zaurus community should take a look at [[Introduction to Alternative ROMs]].
 +
* [[Kernels]], most people don't compile their own but there are a lot of kernels ready available.
 +
* [[Dual Booting]] is somewhat difficult but still possible.
 +
* [[Recovery]] details some of the procedures for restoring a Zaurus after a bad installation.
 +
 
= Terminology =
= Terminology =
-
Any operating system consists of a kernel (linux) and a file system with user space software (applications). Both is usually stored on Zaurus' internal NAND memory while the user space part can be on a memory card or the C3x00 hard drive as well. People call the combination of a kernel and a (compressed) read-only file system a ''ROM'' for historic reasons. The procedure of installing a new ROM is called ''flashing''.
+
Any operating system consists of a kernel (Linux in our case) and a file system with user space software (applications). Both are usually stored in the Zaurus internal NAND memory while the user space part can be on a memory card or the C3x00 hard drive as well. People call the combination of a kernel and a read-only file system a ''ROM'' for historic reasons. The procedure of installing a new ROM is called ''flashing''.
-
A convenient way to install additional software are ''feed''s, that is internet sites providing binary packages. Those will be installed to a read-write partition on any form of storage available (internal NAND/HDD, CF/SD, USB key, network).
+
A convenient way to install additional software are ''feed''s, these are internet sites providing binary packages. Those will be installed to a read-write partition on any form of storage available (internal NAND/HDD, CF/SD, USB key, network).
We'll call the combination of ROM and feed a ''distribution'' in this document.
We'll call the combination of ROM and feed a ''distribution'' in this document.

Line 12:

Line 19:

= Software compatibility =
= Software compatibility =
-
Zaurus is a Linux PDA after all, so we can port any open source software and mix with whatever distribution we are running, right? Maybe. However (binary) interfaces differ a lot, so don't get too excited about mix and match; it won't match. If a program you want to use is not in your distribution (neither in the ROM nor in a suitable feed) and you want to install it, there's work ahead.
+
Zaurus is a Linux PDA after all, so we can port any open source software and mix with whatever distribution we are running, right? Maybe. However (binary) interfaces differ a lot, so don't get too excited about mix and match: it won't match. If a program you want to use is not in your distribution (neither in the ROM nor in a suitable feed) and you want to install it, there's work ahead.
The major issue here is the different kinds of GUIs used. Unless you are a software developer with some free time on your hand you probably want to choose a distribution that suits your needs. This page is to help you with that decision.
The major issue here is the different kinds of GUIs used. Unless you are a software developer with some free time on your hand you probably want to choose a distribution that suits your needs. This page is to help you with that decision.
-
pdaXrom, OZ/GPE, debian and pocketworkstation run on top of X. This is what all linux desktop GUIs use which makes porting software (such as from GNOME) possible but not trivial. OZ/OPIE, Sharp/Qtopia and Cacko use qt/embedded. qt is a free (partly as in speech, partly as in beer) toolkit to write GUIs for windows and X desktops, qt/embedded however differs from regular desktop qt, which again makes porting software (such as from KDE) possible but not trivial.
+
[[pdaXrom]], OZ/GPE, debian and pocketworkstation run on top of X. This is what all Linux desktop GUIs use which makes porting software (such as from GNOME) possible but not trivial. OZ/OPIE, Sharp/Qtopia and Cacko use qt/embedded. QT is a free (partly as in speech, partly as in beer) toolkit to write GUIs for windows and X desktops, QT/embedded however differs from regular desktop QT, which again makes porting software (such as from KDE) possible but not trivial.
-
All the Sharp Zaurus applications are binary compatible across distros, so as long as they don't require a GUI and are command line based, they should work, however, they have different library dependencies which is where the biggest compatability problem is. Sharp/Cacko and pdaXrom use GLIB 2.2.x whereas PocketWorkstation/Debian and OZ use GLIB 2.3.x. Applications that are not dependant on the latest GLIB features, usually can run on any Zaurus distro.
+
All the Sharp Zaurus applications are binary compatible across distros, so as long as they don't require a GUI and are command line based, they should work, however, they have different library dependencies which is where the biggest compatibility problem is. Sharp, Cacko and pdaXrom use GLIB 2.2.x whereas PocketWorkstation/Debian and OZ use GLIB 2.3.x. Applications that are not dependent on the latest GLIB features, usually can run on any Zaurus distro.
That said, the binaries may run, however, the package will not install because there are two different package formats for the IPK files as well. Sharp/Cacko and pdaXrom use an older IPK format that is in essence a tgz file containing tgz files. Debian and OZ use a newer format which the ipkg commands in the other distros cannot read and extract. There are tools around to convert between the package formats.
That said, the binaries may run, however, the package will not install because there are two different package formats for the IPK files as well. Sharp/Cacko and pdaXrom use an older IPK format that is in essence a tgz file containing tgz files. Debian and OZ use a newer format which the ipkg commands in the other distros cannot read and extract. There are tools around to convert between the package formats.

Line 28:

Line 35:

= Common distributions =
= Common distributions =
-
== Sharp retail ROM ==
+
== [[Sharp ROM]] ==
-
Sharp ships Zaurii with Japanese/English software based on Trolltech's Qtopia. The software differs from model to model. It's generally considered stable but lacks features found in other distributions. Due to Qtopia's commercial license it's not open enough for a true linux PDA.
+
Sharp ships Zaurus initially configured with Trolltech's Qtopia. The software differs slightly from model to model. It's generally considered stable but lacks features found in other distributions.
-
* uses qt/embedded 1.5
+
* uses Qtopia 1.5.4 and Qt/Embedded 2.3.2
* optimized for Zaurus screen resolution (PDA like environment)
* optimized for Zaurus screen resolution (PDA like environment)
* feeds with additional software are available
* feeds with additional software are available
 +
 +
== Crow ==
 +
 +
[http://www.schwag.org/~crow/ Cacko/Crow] is a ROM for the SL-5000/5500, placing /home on an MMC or SD card.
== Cacko ==
== Cacko ==

Line 44:

Line 55:

* supports most clamshell models: SL-C7x0/C860/C1000/C3100
* supports most clamshell models: SL-C7x0/C860/C1000/C3100
* 100% English
* 100% English
-
* uses qt/embedded 1.5 just like Sharp
+
* uses Qtopia 1.5.4 just like SharpROM
* optimized for Zaurus screen resolution (PDA like environment)
* optimized for Zaurus screen resolution (PDA like environment)
* Tetsu special kernel
* Tetsu special kernel
-
* Based on kernel 2.4.18, Anton back-ported many updates and drivers from the later 2.4 kernel
+
* Based on kernel 2.4.18, Anton back ported many updates and drivers from the later 2.4 kernel
-
* Many device drivers are included for hardware such as CF bluetooth & wifi, CF usb host, etc
+
* Many device drivers are included for hardware such as CF Bluetooth & WiFi, CF USB host, etc
-
* supports wifi networking very well, including WPA (if using a card with hostap drivers)
+
* supports WiFi networking very well, including WPA (if using a card with hostap drivers)
Cacko uses a compressed file system to store the main file system, and thus is quite space efficient; the downside is there are quite a few symbolic links in the read-write file system into the loopback-mounted cramfs file system in order to allow patching and changes.
Cacko uses a compressed file system to store the main file system, and thus is quite space efficient; the downside is there are quite a few symbolic links in the read-write file system into the loopback-mounted cramfs file system in order to allow patching and changes.

Line 55:

Line 66:

[http://my-zaurus.narod.ru/cacko.html]
[http://my-zaurus.narod.ru/cacko.html]
-
== pdaXrom ==
+
== tkcROM ==
 +
An interesting modified Sharp ROM. Certain apps stripped out, available as ipks. Home on SD but with a different method to the Cacko/Crow ROM. Also has recently been given a modified initrd to enable SD cards larger than 2 GB. See [[Available ROMs for the SL-5x00]] also.
-
* supports Zaurus SL-5000D/5500, SL-C7x0/7500/860, SL-6000, SL-C1000/C3100, SL-C3000 (experimental), x86 PCs, PhyCORE-PXA270
+
== [[pdaXrom]] ==
 +
 
 +
===pdaXrom current (r121 and later)===
 +
 
 +
* supports Zaurus SL-C7x0/7500/860, SL-6000, SL-C1000/C3100/C3200, C3000 (experimental), x86 PCs, PhyCORE-PXA270
* 100% open source, GNU GPL
* 100% open source, GNU GPL
 +
* Linux 2.6.x kernel
* X windows, GTK - use openbox as default window manager but can also use other window managers like xfce, kde, etc...
* X windows, GTK - use openbox as default window manager but can also use other window managers like xfce, kde, etc...
* crosscompiled desktop applications, not all optimized for Zaurus screen resolution (notebook like environment)
* crosscompiled desktop applications, not all optimized for Zaurus screen resolution (notebook like environment)
* Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc), SD cards, IR, and USB host/client
* Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc), SD cards, IR, and USB host/client
 +
[http://www.pdaxrom.org/], [[pdaXrom]]
[http://www.pdaxrom.org/], [[pdaXrom]]
-
== OpenEmbedded/OpenZaurus ==
 
-
OpenEmbedded is a not a distribution, it's a build system used by developers.
+
===pdaXrom beta1/beta3===
 +
 
 +
* supports Zaurus SL-5000D/5500, SL-C7x0/7500/860, SL-6000, SL-C1000/C3100/C3200, SL-C3000 (experimental), x86 PCs, PhyCORE-PXA270
 +
* 100% open source, GNU GPL
 +
* Linux 2.4.x kernel
 +
* X windows, GTK - use openbox as default window manager but can also use other window managers like xfce, kde, etc...
 +
* crosscompiled desktop applications, not all optimized for Zaurus screen resolution (notebook like environment)
 +
* Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc), SD cards, IR, and USB host/client
 +
 
 +
[http://www.pdaxrom.org/], [[pdaXrom]]
 +
 
 +
 
 +
===pdaXii13===
 +
 
 +
* supports Zaurus SL-C3000, SL-C1000/C3100/C3200, SL-C7x0/7500/860 (in a limited fashion)
 +
* based on pdaXrom beta1/beta3
 +
* X windows, GTK - use openbox as default window manager and can be easily switched to fluxbox and icewe
 +
* customised desktop applications optimized for Zaurus screen resolution (notebook like environment)
 +
* custom keyboard mappings for both Zaurus keyboard and USB keyboard
 +
* many bug fixes for beta1/beta3
 +
 
 +
[http://www.users.on.net/~hluc/myZaurus/pdaxii13.html], [[pdaXii13]]
 +
 
 +
===pdaXiiNG===
 +
 
 +
''Note: these are planned specs, this doesn't actually exist yet''.
 +
 
 +
* supports Zaurus SL-C3000, SL-C1000/C3100/C3200 (later)
 +
* based on pdaXrom latest rxxx with 2.6.x kernel
 +
* X windows, GTK - use icewm as default window manager
 +
* customised desktop applications optimized for Zaurus screen resolution (notebook like environment)
 +
* custom keyboard mappings for both Zaurus keyboard and USB keyboard
 +
 
 +
[http://www.users.on.net/~hluc/myZaurus/pdaxiing.html], [[pdaXiiNG]]
 +
 
 +
== Open Zaurus ==
-
OpenZaurus supports all Zaurus models (except SL-A300 which is very rare device). It's the only one distribution with 2.6 kernel for some models.
+
[[Open Zaurus]] supports all Zaurus models (except SL-A300 which is very rare device). It's the only one distribution with 2.6 kernel for some models.
Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc).
Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc).

Line 97:

Line 149:

* spelled Angstrom with °A=Å und "o=ö
* spelled Angstrom with °A=Å und "o=ö
-
* future of OpenZaurus
+
* future of Open Zaurus.
=== Hentges ===
=== Hentges ===
-
* based on OpenZaurus and maintained by Matthias Hentges
+
* based on Open Zaurus and maintained by Matthias Hentges
-
* Uses the OpenZaurus feeds
+
* Uses the Open Zaurus feeds
* installs and preconfigures many of the most popular applications
* installs and preconfigures many of the most popular applications
* [http://www.hentges.net/misc/ Hentges website]
* [http://www.hentges.net/misc/ Hentges website]
 +
 +
== Debian ==
 +
 +
There are several variants of Debian that can be run on Zaurus.
 +
 +
* Use familiar Debian concepts.
 +
* Instant access to 15000 binary packages compiled for your ARM processor from tons of Debian mirrors worldwide
 +
* Other advantages/disadvantages are not clear yet (''more experienced people should add details'').
 +
 +
See [[Debian/Zaurus]].
= Applications =
= Applications =
-
What matters to a user most is what applications are available and how good they run? This is a obviously a tough question and everyone holds an opinion about what's needed and what's good. Let's make a comparision table: '''(This needs work from people familiar with the distributions.)'''
+
What matters to a user most is what applications are available and how well they run? This is a obviously a tough question and everyone holds an opinion about what's needed and what's good. Let's make a comparision table: '''(This needs work from people familiar with the distributions.)'''
{| border="1" cellspacing="0"
{| border="1" cellspacing="0"

Line 494:

Line 556:

* Run Debian in a chroot environment
* Run Debian in a chroot environment
-
* Any debian ARM packages is available without porting.
+
* All Debian ARM packages are available without porting.
[http://wiki.debian.org/?PocketWorkstationXQT/]
[http://wiki.debian.org/?PocketWorkstationXQT/]
-
== Sharp-compat ==
+
== Sharp Compatibility ==
-
* librariers are available to support applications build for the Sharp ROM on other ROMs.
+
* libraries are available to support applications build for the Sharp ROM on other ROMs.

Current revision

Overview of available software distributions from a user's point of view.

This article is aimed at explaining the different distributions in detail.

  • Users new to the Zaurus community should take a look at Introduction to Alternative ROMs.
  • Kernels, most people don't compile their own but there are a lot of kernels ready available.
  • Dual Booting is somewhat difficult but still possible.
  • Recovery details some of the procedures for restoring a Zaurus after a bad installation.


Contents

Terminology

Any operating system consists of a kernel (Linux in our case) and a file system with user space software (applications). Both are usually stored in the Zaurus internal NAND memory while the user space part can be on a memory card or the C3x00 hard drive as well. People call the combination of a kernel and a read-only file system a ROM for historic reasons. The procedure of installing a new ROM is called flashing.

A convenient way to install additional software are feeds, these are internet sites providing binary packages. Those will be installed to a read-write partition on any form of storage available (internal NAND/HDD, CF/SD, USB key, network).

We'll call the combination of ROM and feed a distribution in this document.

Software compatibility

Zaurus is a Linux PDA after all, so we can port any open source software and mix with whatever distribution we are running, right? Maybe. However (binary) interfaces differ a lot, so don't get too excited about mix and match: it won't match. If a program you want to use is not in your distribution (neither in the ROM nor in a suitable feed) and you want to install it, there's work ahead.

The major issue here is the different kinds of GUIs used. Unless you are a software developer with some free time on your hand you probably want to choose a distribution that suits your needs. This page is to help you with that decision.

pdaXrom, OZ/GPE, debian and pocketworkstation run on top of X. This is what all Linux desktop GUIs use which makes porting software (such as from GNOME) possible but not trivial. OZ/OPIE, Sharp/Qtopia and Cacko use qt/embedded. QT is a free (partly as in speech, partly as in beer) toolkit to write GUIs for windows and X desktops, QT/embedded however differs from regular desktop QT, which again makes porting software (such as from KDE) possible but not trivial.

All the Sharp Zaurus applications are binary compatible across distros, so as long as they don't require a GUI and are command line based, they should work, however, they have different library dependencies which is where the biggest compatibility problem is. Sharp, Cacko and pdaXrom use GLIB 2.2.x whereas PocketWorkstation/Debian and OZ use GLIB 2.3.x. Applications that are not dependent on the latest GLIB features, usually can run on any Zaurus distro.

That said, the binaries may run, however, the package will not install because there are two different package formats for the IPK files as well. Sharp/Cacko and pdaXrom use an older IPK format that is in essence a tgz file containing tgz files. Debian and OZ use a newer format which the ipkg commands in the other distros cannot read and extract. There are tools around to convert between the package formats.

Hardware compatibility

If the distribution does not say it supports your Zaurus model it probably won't work. The hardware differs under the skin.

Common distributions

Sharp ROM

Sharp ships Zaurus initially configured with Trolltech's Qtopia. The software differs slightly from model to model. It's generally considered stable but lacks features found in other distributions.

  • uses Qtopia 1.5.4 and Qt/Embedded 2.3.2
  • optimized for Zaurus screen resolution (PDA like environment)
  • feeds with additional software are available

Crow

Cacko/Crow is a ROM for the SL-5000/5500, placing /home on an MMC or SD card.

Cacko

Cacko is an improved version of Sharp's ROM put together mainly by Anton Maslovsky. Cako means "Jewel" in Russian.

Cacko provides two ROMs, full or light, plus feed. Both offer the same applications if you take the feed into account.

  • supports most clamshell models: SL-C7x0/C860/C1000/C3100
  • 100% English
  • uses Qtopia 1.5.4 just like SharpROM
  • optimized for Zaurus screen resolution (PDA like environment)
  • Tetsu special kernel
  • Based on kernel 2.4.18, Anton back ported many updates and drivers from the later 2.4 kernel
  • Many device drivers are included for hardware such as CF Bluetooth & WiFi, CF USB host, etc
  • supports WiFi networking very well, including WPA (if using a card with hostap drivers)

Cacko uses a compressed file system to store the main file system, and thus is quite space efficient; the downside is there are quite a few symbolic links in the read-write file system into the loopback-mounted cramfs file system in order to allow patching and changes.

[1]

tkcROM

An interesting modified Sharp ROM. Certain apps stripped out, available as ipks. Home on SD but with a different method to the Cacko/Crow ROM. Also has recently been given a modified initrd to enable SD cards larger than 2 GB. See Available ROMs for the SL-5x00 also.

pdaXrom

pdaXrom current (r121 and later)

  • supports Zaurus SL-C7x0/7500/860, SL-6000, SL-C1000/C3100/C3200, C3000 (experimental), x86 PCs, PhyCORE-PXA270
  • 100% open source, GNU GPL
  • Linux 2.6.x kernel
  • X windows, GTK - use openbox as default window manager but can also use other window managers like xfce, kde, etc...
  • crosscompiled desktop applications, not all optimized for Zaurus screen resolution (notebook like environment)
  • Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc), SD cards, IR, and USB host/client

[2], pdaXrom


pdaXrom beta1/beta3

  • supports Zaurus SL-5000D/5500, SL-C7x0/7500/860, SL-6000, SL-C1000/C3100/C3200, SL-C3000 (experimental), x86 PCs, PhyCORE-PXA270
  • 100% open source, GNU GPL
  • Linux 2.4.x kernel
  • X windows, GTK - use openbox as default window manager but can also use other window managers like xfce, kde, etc...
  • crosscompiled desktop applications, not all optimized for Zaurus screen resolution (notebook like environment)
  • Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc), SD cards, IR, and USB host/client

[3], pdaXrom


pdaXii13

  • supports Zaurus SL-C3000, SL-C1000/C3100/C3200, SL-C7x0/7500/860 (in a limited fashion)
  • based on pdaXrom beta1/beta3
  • X windows, GTK - use openbox as default window manager and can be easily switched to fluxbox and icewe
  • customised desktop applications optimized for Zaurus screen resolution (notebook like environment)
  • custom keyboard mappings for both Zaurus keyboard and USB keyboard
  • many bug fixes for beta1/beta3

[4], pdaXii13

pdaXiiNG

Note: these are planned specs, this doesn't actually exist yet.

  • supports Zaurus SL-C3000, SL-C1000/C3100/C3200 (later)
  • based on pdaXrom latest rxxx with 2.6.x kernel
  • X windows, GTK - use icewm as default window manager
  • customised desktop applications optimized for Zaurus screen resolution (notebook like environment)
  • custom keyboard mappings for both Zaurus keyboard and USB keyboard

[5], pdaXiiNG

Open Zaurus

Open Zaurus supports all Zaurus models (except SL-A300 which is very rare device). It's the only one distribution with 2.6 kernel for some models.

Many device drivers are included for hardware such as CF cards (bluetooth, wifi, usb host, modems, gps etc). Supports wifi networking very well, including WPA (if using a card with hostap drivers and OZ 3.5.4).

Distribution comes in flavours:

[6]

OZ/Bootstrap

  • 100% open source
  • only console - no GUI at all

OZ/OPIE

  • 100% open source replacement for qtopia
  • uses qt/embedded
  • optimized for Zaurus screen resolution (PDA like environment)

OZ/GPE

  • 100% open source
  • uses X windows, GTK
  • optimized for Zaurus screen resolution (notebook/PDA like environment)

Ångström

  • spelled Angstrom with °A=Å und "o=ö
  • future of Open Zaurus.

Hentges

  • based on Open Zaurus and maintained by Matthias Hentges
  • Uses the Open Zaurus feeds
  • installs and preconfigures many of the most popular applications
  • Hentges website

Debian

There are several variants of Debian that can be run on Zaurus.

  • Use familiar Debian concepts.
  • Instant access to 15000 binary packages compiled for your ARM processor from tons of Debian mirrors worldwide
  • Other advantages/disadvantages are not clear yet (more experienced people should add details).

See Debian/Zaurus.

Applications

What matters to a user most is what applications are available and how well they run? This is a obviously a tough question and everyone holds an opinion about what's needed and what's good. Let's make a comparision table: (This needs work from people familiar with the distributions.)

legend
default (usually on basic ROM) available on extended/special ROM package available in (main) feed package available indirectly (through X/qt or Sharp-compat or additional feed) unsure
Sharp Cacko v1.23 pdaXrom OZ/OPIE OZ/GPE
PIM
qtopia
Ko/PI
qtopia
Ko/PI
Ko/PI desktop
KDEPIM
cal v3.5
fltdj v0.7
Ko/PI (=OPIE)
GPE
Office
Hancom Word/Sheet
vim
microemacs, zedit, yedit, qpdf2
Hancom Word/Sheet
vim
microemacs, zedit, yedit, qpdf2
SciTE 1.62, gnumeric v1.6
abiword v2.4
justreader v2.0J
nedit v5.4
vim v6.4
siag v3.6.0
xpdf v2.03
OPIE-Textedit, OPIE-Write
qpdf 2
justreader v2.0K
vim v6.4, micro-emacs
Hancom Word/Sheet, Abiword 2.4.4
abiword 2.4.4
gnumeric v1.6.2
vim v6.4
gpdf 2.10.0
web
netfront v3.1, Opera v7.25
apache/php/mysql
netfront v3.1, Opera v7.25
apache/php/mysql
dillo v0.8.5
Firefox v1.5, Minimo v1.7, Mozilla v1.7
apache/php/mysql
Konquerer
apache/php/mysql
Dillo, Firefox, Minimo
gpe-mini-browser
Dillo, Firefox, Minimo
apache/php/mysql
Email
qtopia
Kopie/Mail, mutt
msmtp
qtopia
Kopie/Mail, mutt
msmtp
sylpheed v2.0
thunderbird v1.0.7
msmtp, mutt
OPIE-Mail
sylpheed v2.0
thunderbird v1.0.7
mutt
sylpheed v2.0
thunderbird v1.0.7
mutt
IM, chat, VoIP
GAIM
KPhone/PI
bitchx v1.1-final
GAIM
KPhone/PI
bitchx v1.1-final
gaim v2.0
xchat
bitchx v1.1-final
KPhone/PI, OpieIRC
GAIM
network tools
gnupg, rsync, tar
wellenreiterII, kismet, aircrack v2.1-1
Access Point SNMP Utils for Linux
qtrdesktop, smbclient
gnupg, rsync, tar
wellenreiterII, kismet, aircrack v2.1-1
Access Point SNMP Utils for Linux
qtrdesktop, smbclient
gnupg v1.2.4, rsync, tar
kismet v2.6.0, wellenreiterII, wifi-radar
openssh v3.7.1p2, vpn
rdesktop v1.3.1, smbclient
x11vnc, tightvnc
WellenreiterII, OpieStumbler, Opie-rdesktop, Dropbear
wpa_supplicant
gnupg
kismet (console)
openssh
wpa_supplicant
Media
mencoder, mplayer
xmms
petitepeinture, GIMP
mencoder, mplayer
xmms
petitepeinture, GIMP
GIMP v2.3.6, tuxpaint v0.9.14
xmms v1.2.10
gqview v2.1.1
mad, mplayer v1.0pre3try2
Opie Media player, Drawpad
qpPhoto
Gimp
Gimp
software development
python, ruby, perl, miniscript, pocketscript
cvs
python, ruby, perl, miniscript, pocketscript
cvs
python v2.4.1, pygtk 2.5.3
ruby v1.8.1
tk v8.4.6
gcc v3.4.5
cvs
science, other
bc, maxima, neocal
qtplot
zroadmap
bc, maxima, neocal
qtplot
zroadmap
bc, dia, x48
bluefish, thunar
gpsdrive
stardict
grisbi

Get even more

X/qt

  • Using this X server running on top of qt/embedded you can use any X application provided it is compatible (ie. glibc compatible)
  • Sharp, Cacko, Crow? and OZ/OPIE ROMs

[7]

PocketWorkstation

  • Run Debian in a chroot environment
  • All Debian ARM packages are available without porting.

[8]

Sharp Compatibility

  • libraries are available to support applications build for the Sharp ROM on other ROMs.
Retrieved from "http://www.oesf.org/index.php?title=Distributions"
Personal tools