On the X11 front, there appears to be more useful applications and games available for pdaXrom and it looks much prettier than GPE as well. OPIE is not a real choice since it lacks essential applications even though it looks nicer. For the SL-C, the choice is a bit different since there aren't many distros that really support it. There are also alternate boot loaders for the Zaurus other than the default one provided by Sharp. With the introduction of the 2.
OZ has simplified the pivot boot process with altboot and once kexec is integrated, it could be used to boot other distros as well. Using one of these bootloaders might be a way to boot and pivot the rootfs on the C to overcome the tiny 16M flash problem. However, the SL-C is a bit different since it got a tiny flash.
The choice for a distro for my SL-C is quite hard since none of the currently available distros are quite ready yet. However, neither of the two has gotten to a point yet where it is stable enough to use and includes sufficient useful applications and utilities. Both still have a lot of shortcomings.
Below is a discussion about why these two distros have potential and also where they fall short. Firstly, the OS needs to be able to boot and mount the internal MicroDrive as rootfs. OZ does that very well, however, pdaXrom does not officially support the C so it needs to be hacked to do that. Also, the perfect distro needs to fully support the SL-C hardware and its many powerful features. The SL-C has great hardware which more or less is supported by both distros.
Here is a quick summary of hardware and their level of support:. The main keys on the keyboard is mapped correctly on both distros, but is not very well documented on how to customise the keymaps. Some special keys are missing on both distros. Sticky keys can be enabled on pdaXrom which does not seem to be the case in OZ. Multi-key does not seem to work on OZ. OZ uses the matchbox window manager which looks quite ugly. Fluxbox is also available. It looks very nice.
There are also a host of alternate window managers available for pdaXrom such as icewm, xfce, fluxbox and kde. All those window managers can automatically resize the application window on load to fit the screen except for openbox which is the pdaXrom default window manager. The pdaXrom taskbar looks exceptionally pretty while OZ taskbar is rather dull. None of them have a docking view for minimised applications. However, OZ does not have a working applet for ejecting removable cards.
None of them have a swap management applet. The default theme on pdaXrom is quite pretty and can be customised through the theme config applet, but switching themes requires manual editing of the config file. The OZ theme, on the other hand can easily be switched and customised through its config applet, however, switching the theme on OZ results in some applications, namely abiword, to crash.
The config tools in both pdaXrom and OZ are a bit flakey and don't always work properly. You cannot use it to change the date or time. There is no applet in OZ to configure sound.
The pdaXrom sound applet has no effect while applications that use sound are active. Suspend and resume is a bit flakey on pdaXrom.
When it works, it works fine, but at times, it does not work reliably. Suspend works fine in OZ, however, resume sometimes behaves flakey. Screen capturing is an easy task in OZ, however, this feature is missing in the default pdaXrom install.
It can be added with contributed packages, although it is not as integrated as in OZ. There are more useful applications in pdaXrom. There may be more packages in OZ, but the number of truely useful applications is greater on pdaXrom although some are oversized and don't fit on the Z's screen.
A lot of the dialog boxes in both OZ and pdaXrom are also oversized. Some keys are incorrectly mapped in some of the applications.
Most applications depending on SDL libraries, for example, have wrongly mapped keys. Firefox also has many missing keys on OZ. Not only can it support many games through emulators, but there are also a lot of user contributed games of all sorts. Even a playstation emulator has been ported and optimised for pdaXrom. The default language of both pdaXrom and OZ is English. Support for other languages is provided via way of unicode fonts and input method support for entering extended characters using a virtual keyboard.
Now this is the biggest difference between pdaXrom and OZ. OE only runs on Linux and can target various platforms of which the Zaurus is one, but you will need a PC to build OZ packages and compile code. The native compiler which can compile code directly on the Zaurus itself is not very well supported on OZ. It has a pre-made and configured development image that can be placed onto the Zaurus which allows you to immediately begin building and compiling.
OZ developers are also concentrating more on developing PDA specific applications that works on other devices besides the Zaurus, ie they target devices with smaller screens and less storage. In essence, pdaXrom is about turning the Zaurus into a mini linux PC, whereas OZ is more about providing a bleeding edge and alternate open source operating system, as well as lightweight applications for PDAs. The OZ community is divided into two distinct groups, the developers and the end users.
OZ developer prefer to communicate through their mailing list which is very development centric and offer support on IRC for users. They also announce things through their website and through posts on OESF. Documentation was almost non existant or scattered until recently. The new OZ wiki is a start for documenting a few things, but bug reporting is still quite confusing and tedious since there are several bug reporting systems and repositories.
Support for pdaXrom is pretty much community driven. The pdaXrom users help each other and collect workarounds for common problems until they are fixed.
Bug reporting is much easier and simpler in pdaXrom, but the versioning scheme of pdaXrom is quite confusing since it does not adhere to a standard. Since neither pdaXrom nor OpenZaurus have sufficient features that would make them the distro of choice on a C, I have come to the conclusion that I would need to build my own custom distro for my C This custom distro would be based on either pdaXrom or OpenZaurus.
All current development is on the 2. GPE seems unfinished and looks rather plain. One option would be to continue work on pdaXrom beta3 and enhance its stability. I have decided to build pdaXii13 for my SL-C which is based on the C beta2 but much more polished. I have fixed all the shortcomings and bugs that annoyed me and now my C has a real stable and perfectly working distro.
See my pdaXii13 page on all the enhancements and features. There currently is a lot of work being done on creating newer and better distros for the Zaurus based on the 2. Work on pdaXrom is still ongoing and has progressed to version r It still is full of annoying bugs. OpenZaurus is no more.
It has been abandoned in favour of its successor, Angstrom. There has been some progress made in Angstrom which is also based on the latest 2. It is currently still in an unstable state. Debian has also been revamped and the new version is also using EABI and 2.
There is no Debian installer for armel build for Zaurus yet, but it is possible to boot Debian for the Zaurus using a combo of bootloaders and custom 2. The future for a 2. Binaries compiled for each should be binary compatible, but library dependencies will be an issue. It will retain the look and feel of pdaXrom but not be based on the pdaXrom code base and definately not use uboot.
No assurance is given to the accuracy of the information or instructions provided. You may use this as a guide but do not blame me if anything bad happens to your system or your data. Use anything described on this site at your own risk. If you have a C or C and you want to install Alice onto them instead of Sally, then this option will update your existing system which has to be pdaXrom beta3 or pdaXii13 Akita base to boot into the MicroDrive but will not update the kernel nor the rest of the system.
Once the installation has finished, you will need to extract the hdimage. Choose Option 4 for that and wait a while until it formats your first partition as ext3 and extracts the content of the tgz file onto the first partition of your MicroDrive. Then choose the last option Option 6 to reboot and pdaXii13 should be installed and boot into X windows. OpenBox will be the default X window manager just like in the default pdaXrom beta3.
During your first boot, your SSL private and public keys will be generated which will take a while. If you have used the recommended partition scheme or used your own custom partition layout, then you need to format those remaining partitions. During the initial boot, you will also be given a choice to format your second and third partition if you have them.
The second partition will be formatted as swap while the third partition will be formatted as FAT. Alternatively, you can do it manually as well. Start a terminal console and format the remaining partitions depending on what type of partitions you have created. For example:. Once your second partition is initialised, it will be automatically enabled as swap when you reboot. Installation files for pdaXii13 Spitz Alice can be downloaded from pdaXii13 files area on tyrannozaurus which contains a stable release version.
It is not guaranteed to work, and even if you managed to get it installed, there still may be some things that won't work. It is available as pdaXii13 base and pdaXii13 full. It is primarily available as pdaXii13 base only, but can be extended to pdaXii13 full on SL-C and SL-C by utilising the internal MicroDrive to store the entire hdd image from the Spitz install.
There is, however, an experimental feature for the SL-C to install the hdd image to a SD card instead. Installation instructions and installation files for pdaXii13 Akita Sally can be found at tyrannozaurus in the akita area. It is advised to resize the NAND root to during installation in order to utilize all of pdaXii13's features. You can also update an existing pdaXii13 installation with the same method. Just use the upgrade option in the pdaXii13 installer.
You can get the upgrade archive file pdaXiicustom. There also is an install script contained in the tarball which will copy all the patched binaries and scripts to the appropriate locations when you run the script if you prefer to manually upgrade or an installer is not available for your model.
To upgrade to pdaXii13 using the manual method, extract the tarball preferrably to a CF card rather than a SD card and run the install script install-fix-beta3. Make sure you make a NAND backup of your Zaurus before you apply the update in case something goes wrong, then copy pdaXiicustom.
This will give you something similar to the latest pdaXii13 base and works on all clamshell models. Below is a list of pre-installed applications that are part of the pdaXii13 full installation. The following packages are in addition to the applications installed by the default pdaXrom beta3. These applications are not all pre-installed on pdaXii13 base. There are many more packages beside the ones on the official feeds. Many user contributed packages exist and can also be installed. Some packages for pdaXrom beta4 and r will also work on pdaXii13 but be careful with those since some can also break pdaXii13 due to library version incompatabilities.
To create your own custom local feed, you can download the beta1 feed. You can then merge the two feeds and any additional ones onto your internal MicroDrive or one of the external cards. Just extract the files into a directory extract the 7x0 archive first and then the C one on top of it to eliminate the duplicates.
Then use ipkg-make-index to generate a new Packages file for the feed. You can also install individual packages without requiring a feed, but you will need to manually install dependant packages yourself. The pdaXii13 custom keyboard layout spitz. Below is a list of keyboard shortcuts and customisations that exists on pdaXii There are two types of changes to the keymappings. The first one are the essential fixes to make the keymap work, and the second ones are enhancements to make it more usable and similar to the keyhelper enhancements on the Sharp distro.
Use xev within X to determine the keycode for the keys. If you don't like my custom keymap, then use the original akita.
Sticky keys are automatically enabled and can be controlled with the ax command which controls all the AccessX functionality. For example, to produce A, simply press Shift followed by a. This is very nifty for one handed typing. Also the Caps Lock functionality has been disabled because of a conflict in the X server which needs to be patched to allow these features to function properly.
A patch has been applied to the X server to fix the silkscreens, but patching the Fn functionality for special dual function keys is a bit more complicated. Most keys are mapped as displayed on the keyboard except for some additional keys which have also been mapped but are not marked on the keyboard. Also some additional keys have been remapped as follows:. By defeault, there are also several predefined key combos which do the following in the default OpenBox window manager.
Other window managers have slightly different key combos:. The above changes can be done by modifying rc. In pdaXii13, those two locations are symbolically linked. The silkscreen and shortcut keys at the bottom of the keyboard can also be changed using the Input Setup tool.
When you plug in a USB keyboard, you can automatically remap the keys so that the keys on the external keyboard are mapped correctly, but it will result in the Zaurus keyboard being mismapped. When the external keyboard is unplugged, the keymapping for the zaurus keyboard is restored. This is handled by the hotplug subsystem.
It allows you to switch between the default Zaurus keymapping spitz. The following keys can be used to control XMMS:. Some of the sticky keys will also work outside of X as well.
Screen rotation works automatically on pdaXii Openbox will detect transformation between laptop mode landscape and PDA mode portrait and rotate the screen by calling rotate. You will end up with the taskbar at the correct location for the orientation you are in.
The currently running applications will also be resized to fit your orientation. In order for this to happen, the running applications will be maximized. The rotate option on the menu will also call rotate. A smarter script screencap has been written that mimics the capture behaviour on the Sharp distro, ie.
A shutter sound click. The filenaming and sequencing has been made to mimic the Sharp snapshot tool. See the screencap script. If scrot is installed it will use scrot to capture a png image, otherwise xwd is used instead and if ImageMagick is installed, then it will be used to convert the xwd image into a png image. In pdaXii13 full, an additional screencap icon is placed on the taskbar and once tapped will wait 10 seconds before taking a screenshot. Alternatively, you can also use gsnapshot which allows you to capture a specific area of the screen.
The desktop is by default managed by matchbox desktop in pdaXrom. You can manually replace the matchbox desktop with rox filer to get an integrated file manager and desktop manager in pdaXrom.
You can also specify whether to use matchbox desktop or rox pinboard in the pdaXii13 config file called pdaxii The wallpaper can be any png image file, but a resolution of x is ideal. There is also a command line tool called rox-bset which you can use to replace the background as well as enabling random backgrounds.
The GTK2 theme also controls the font size for those applications. The GTK Theme selector also allows you to just change the font without switching themes. Finally, in pdaXii13, the order of the icons on the toolbar can be changed with the Panel Manager tool. Other window managers use their own menu settings and may not use the. However, the pdaXii13 version of icewm has a conversion tool which converts all the.
There are quite a few applications which open up in a window that is way too big for the Zaurus. Some application can be tailored to a specific window size by editing their config files.
Other applications have the size hardcoded. You can either install my updated GTK2 package or replace libgtk However, it does not automatically resize applications that are oversized.
Suitable alternatives seem to be icewm and fluxbox which are also included in pdaXii13 full. The default window manager in pdaXii13 is openbox, just like in pdaXrom. However, once you exit X, you can use xselect to switch and make icewm or fluxbox your default window manager which will run when you start X again. If using a different window manager other than the default OpenBox, then there are various other config tools to configure those window managers.
IceWM and FluxBox have their own set of config tools. There is no default GUI file manager in the default pdaXrom, however, rox filer is a good candidate for this function and has been included in pdaXii In addition, emelFM2 is also a good file manager with two panels and has also been included in pdaXii Midnight Commander mc is a console based file manager that is by default installed in pdaXrom and has been updated in pdaXii Xdefaults if mrxvt does not have transparency enabled by default.
The Xdefault file enables transparency for mrxvt, rxvt, aterm and multi-aterm. You should always backup your system since that is the only way to recover if something goes wrong. You can also customise the bash prompt by creating or editing a file called.
You can change the bash prompt by changing the PS1 variable definition to something simple like zaurus-: or even something fancy with different colours. On the C it is only 4MB in size. It is physically located on the internal flash memory which is only 16MB in total on the C In addition, some applications also store their configuration and data into the zaurus home directory this is what linux apps are supposed to do , but it is not so ideal on the C On the C, however, the situation is slightly different.
Now you would think that the C won't run out of space so easily. Unfortunately, that is not the case. The rootfs is now allocated 32MB instead of 4MB which was what it was on the C, and remember, there is also the emergency rootfs smf. This isn't so bad after all you think, but wait, there is another surprise. We only have 89MB on the C Luckily, this 89MB is located on a jffs2 filesystem which has built-in compression so we could be able to install around MB of applications and stuff if we are lucky.
Still, we will run out of space eventually. Alternatively, you can install to SD or CF card, but some applications require to be installed to non-FAT partitions so you might need to reformat them.
On the C, it is an almost empty partition with a size of 9MB. It contains a file called hdimage2. On the C, it is also an empty partition with a size of 9MB.
It can be used to store data on files of any type, including relatively large files. There is also a tool called parted which allows you to resize your existing partitions without having to remove them.
This is certainly very useful tool, but remember to backup your hdd3 before resizing it if you have files on hdd3 that you want to keep. Although parted can resize the partition without wiping your data, it is not guaranteed. There may be instances where resizing could corrupt the partition so its always wise to do a backup first.
Also run fsck after using parted to verify that the partition has been resized successfully without corruption. Also you will need to create a startup script to mount hdd4 during bootup. You might also consider creating a small swap partition while you are at it. A swap partition is faster than a swapfile. A swap partition between 64MB and MB should be fine depending on your usage and applications.
In addition, it uses the same mechanism as qinstaller and thus applications installed with xipk can be uninstalled using the qinstaller. The MobileMapData part is in katakana. If you don't know Japanese, you probably want to hide the Contents tab. This can be done though the Appearance tool under the Settings tab. If you ever want it back, you can simply copy it from the third CD. Of course, after you do a factory reset, you will need to fix rc.
Alternatively, you could also update. Thus you can hack rc. This makes sense for the C where the applications and binaries are stored on the MicroDrive and there is a slight delay for the MicroDrive to spin up when it has gone into powersaving mode after some time of disk inactivity. However, for the C it would not make such a big impact on application performance since they actually are on the flash memory instead of the MicroDrive.
Make sure the Flash card you are using has a similar capacity to the MicroDrive 4GB would be good, 2 GB is managable and bigger ones should be better. However, make sure the Flash card you are using is faster than the current MicroDrive inside the Zaurus the Z has a 4GB Hitachi MicroDrive inside , otherwise you won't be gaining anything. You can d o this by inserting the Flash into the CF slot on the Zaurus and partition it ex actly like the MicroDrive using fdisk.
Then use the dd command to copy each partition, ie hdd1, hdd2 and hdd3. Unmount hdd2 and hdd3 before you copy them or remount them to read-only. The other partitions are located in the internal flash memory also called Nand. Alternatively, you can also use parted to copy the entire partition from one disk to another.
Once this is done, you can open up your Z and swap the two drives. This will void your warranty, so make sure you understand and know what you are doing. It is your own responsibility if you break your Zaurus or any parts of it. Finding replacement parts will be extremely difficult unless you live in Japan, so be careful and consider the consequences of your actions, or modifications.
Let me say it again. If you open your Zaurus up to replace parts, you void your warranty. If you break something during the process, then you are on your own since you just voided your warranty. You should always backup your system since that is the only way to recover if something goes wrong. The C and C come with a backup and restore tool which is located under the Settings tab. Use this application to backup your Zaurus. If you have automounter installed, you can unmount all the loop devices by running the following:.
Once you have backed up all the files on your Zaurus, you can remount all the loop devices by running the following:. A USB drive would be the best cheaper than CF drive and faster than Samba since its connected directly and not over a network unless you have got a fast network. This is much safer than the above approach while Qtopia is still running. You should, however, gzip the backup image to save some space.
Lastly,don't forget about backing up your SD and CF card also. They can get corrupted or fail without warning as well, so make sure you back them up to.
The same is not the case with the C so be very careful with what you flash your C with. A MB card should be sufficient. To do a Nand Backup or Restore, do the following:. If you manage to corrupt your Zaurus configuration so badly that you cannot boot it anymore or things just don't work any more, then you have several options to fix it. If you really messed up and just start over again without retaining anything, then just do a factory reset and the Zaurus will revert to its initial Japanese ROM state.
If you have a backup, you can restore your previous settings contained in your backup files. If you had to factory reset, then a restore can quickly get you to where you were before. This is by far the most advanced option. Please refer to Trisoft's C manual on how to do the above.
It would be a waste of my time to provide step by step instructions since they have it pretty much covered, and they even have emergency backup images for you to use in case you dont't have a system backup. This is the emergency partition that you usually don't see. You will need to manually mount the usual partitions if you want to access them. Don't forget to unmount the partitions after you have finished your changes or they will be rolled back and all the files remain unchanged.
Warning : Only flash your Zaurus with a ROM intended for your specific model and make sure you downloaded the complete files. Never ever flash your Zaurus with a ROM for another model. It will cause you many sleepless nights trying to restore it to a working condition.
There are several replacement kernels for the C and C which enhance the stock kernel that ships with Sharp's ROM. You can even build your own if you want and know how to. The kernel source is available on Sharp's developer website.
However, there are some smart people who already build and tested their own enhanced kernels. One of those is Tetsu's special kernel which has been build for optimised speed and also includes iptables and bluetooth modules.
It also makes the battery status more accurate and it has a few bug fixes too. Warning : The kernel is an important part of the Linux OS. A bad kernel can corrupt your Zaurus, so don't play around with it unless you know what you are doing and install the correct kernel for your model. Running fsck on a mounted filesystem is not recommended so the safest way to run it on the C is from the maintenance menu.
Unmounting the partitions on the MicroDrive is much easier on the C since it runs off the flash instead of the disk. You should also regularly fsck your SD and CF card. Please unmount them before fscking them. Enabling the wireless network was amazingly easy and straightforward.
Just plug in the Wireless CF card and the Zaurus automatically detects it. Then run the Network config applet and enter the network info and press connect. That's it. Way too easy. Not all CF Wifi cards are supported so your milage may vary depending on your card. However, you can also manually configure the network without using the Network config applet.
If for any reason the applet won't let you enter a value you want such as space in ssid , then you can edit the mentioned config files yourself.
Now this one was a bit trickier. Anyway, I cheated and googled for rtl Next I had to install this driver which was quite easy. Now came the slightly harder part, ie the automatic configuration of the device. The network applet seems to only work for the CF based cards so it completely ignored eth0 because it came from the USB interface.
After looking at how the usbdnet and wlan is configured by the hotplug mechanism, I extended the net. In addition I also wrote a script called net to change the stored network settings so I can easily switch between networks.
Some application such as NetFront insist on doing their own connection and disconnection to the network and ignore the fact that your USB network is already connected. As a workaround net has a refresh option to reset the network status whenever those programs mess with it. Simply run the following after you have launched NetFront:.
A lot of the USB network cards use either the rtl chipset or are compatible with the pegasus driver. Drivers for both are included with netswitch, so installing the netswitch package should enable your USB LAN device in most cases.
However, some network cards use other chipsets. You should be able to compile your own driver if you can find the driver source. See gcc section for further details. The Zaurus Software for the PC Windows does not use UniCode and hence displays garbage when run on an English version of Windows even if you have installed the Japanese language pack and your browser can display Japanese websites without problems.
To fix this, change the default Windows system locale to Japanese and restart Windows. This is the Zaurus USB network driver. You can use this driver to re-install the USB network or install it to another machine without having to run through the whole setup process again. Then once you installed the driver to the computer, it will believe that it is connected to the Zaurus via a network instead of treating the Zaurus as a dumb USB disk provided the Zaurus is in advanced USB mode.
Now, on to the Zaurus side of the configuration. By default, the Zaurus would be assigned an IP address of Assign an IP address in the same range to this new network adaptor, eg You should now be able to ping both ways unless you have a firewall blocking it or DDE service is not enabled. If you want the Zaurus to be able to access the internet as well, you could enable internet sharing on your Windows PC assuming it has internet connectivity and you trust Microsoft security.
Now that the route is configured, you should be able to ping servers by their IP addresses. Assuming your DNS is This method of networking your Zaurus would give you the slowest network speed and you usually would not use it if the other options were available to you.
Then you would need to make sure the chosen driver is enabled on both your Zaurus and your PC or Laptop. For IrDA connectivity, one machine has to be the host and the other the client. I will describe how to make Zaurus the host and the other PC or Laptop the client. The roles can also be easily reversed. I also did not bother with security since both machines would have to be physically in close range to each other in order for this to work. However, you would need to install a driver for Windows.
If you are running Windows and you have setup the direct connection using IrDA as client you can simply double click on the Direct Connection icon to connect. Once they are paired successfully, you can ping the other box from the Zaurus as The Zaurus would be You will need the IrNet module on the Zaurus and your other Linux box. However, it is already installed on Windows so all you need to do on Windows is to create a new Direct Connection using IrDA interface.
To install and enable IrNet on the Zaurus, you will need to copy irnet. It also provides an opie shell script to allow you to start and stop it from the Qtopia GUI or simply run irnet start to start it from the command line and irnet stop to stop it. However, the default Sharp ROM does not have bluetooth drivers or tools installed out of the box and you will need to setup and install those first before you can use bluetooth.
See the bluetooth section for more details. By default, a Samba service is already installed on the Zaurus. You can also manually start and stop the Samba service and allow it to go over your wireless and ethernet network instead of just the USB cable.
Remember to give it root access or else nothing will happen. Also you need to do the following to enable it to configure smb. Once you install SambaController, you can use it to start and stop samba, as well as modify smb. Note: you might need to hack the Windows registry to enable plain text password to make Windows compatible with Samba depends on the version of Windows you are running.
This configuration forces the samba user to be the zaurus. When giving access to the samba shares, all the access rights and file permission is that of the zaurus user. This will work fine on all FAT filesystems, however, if you change some of your partitions to ext2, then you might get some permission denied errors when trying to acces, create, modify, move or delete files. If that happens, make sure the file or directory in question has sufficient access rights for the zaurus user.
Make sure you use tcp wrapper as it is slightly more secure. Then enable tcp wrapper security by creating hosts. Alternatively, you can ftp to port on the Zaurus which is a very basic ftp service.
Alternatively, you can also enable the ftp daemon within inetd. You can run a vncserver on your Zaurus to enable remote access to its desktop. However, since the available fbvnc server packages were build for other models, it does not work reliably on the C and C I also managed to get the mouse pointer working through the vnc server as well as the keyboard.
However, some keys are still wrongly mapped. If you just want a read only vnc server without remote mouse and keyboard entry, then do the following to disable them:. Alternatively, you could also just restart Qtopia instead of rebooting the Zaurus. To do that instead do the following:. If you want to re-enable the keyboard and mouse, then just recreate the the symbolic link to fbvncinput and reboot your Zaurus:.
Vncserver is part of the Debian PocketWorkstation bundle and is intended as a loopback service to connect to the Debian instance locally.
However, there is nothing preventing it from being accessed remotely as well. It can also be installed under a webserver such as Apache. Simply make a directory such as vnc under the document root and copy index.
Or use the smbmounter GUI interface. Make sure you give it root access see Run as root section. For example if you have a hostname mylaptop mapped to an IP of You can also create the following simple script to automatically mount USB drives or use the more advanced usb-storage that I've written. Here is the simple version:. In addition, if you are using a USB Hub, then you will be able to attach and mount multiple devices, usually up to four disks.
I have created a more advanced script which can automatically mount up to four usb disks and also automount disks partitioned as primary or extended partitions. In addition to external harddisk enclosures with USB interfaces and memory sticks, most MP3 players, cameras and some mobile phones also have an internal storage that can be mounted on the Zaurus if they have a USB interface. Most of those devices will be recognised by the Zaurus as a Mass Storage device by default, however, some newer devices are not on the Zaurus' device list and you will need to update it to let the Zaurus know about the new device see SonyEricsson section for an example.
The automounter script only automatically mounts the first mountable partition. If you have multiple partitions, then you will need to manually mount the remaining partitions or modify the automounter script to also mount the remaining partitions.
You will need to copy ntfs. The SD and CF cards are automatically mounted when they are inserted. Furthermore, by default, the SD card script only attempts to mount the first partition. If you have multiple partitions, then you need to enhance the above mentioned script to automatically mount additional partitions on the CF or SD cards.
Some are also mounted as read-only. The following demonstrates how to configure a MB swap file on the C's harddisk. It even can manage the swapfile creation for you. This version can create a swapfile with a max. The created swap file is also called swapfile rather than.
However, some applications such as kismet or qpdf2 may require a bit more than just 1MB. Finally, you need to reboot the Zaurus in order for the change to take effect.
You can use a loopback filesystem which is a mounted filesystem image to do various things such as compressing files or overlaying a filesystem with another format. The cram filesystem is a read only compressed filesystem format. The following demonstrates how to configure cramfs to preserve some space. Only convert directories to cramfs if you are sure those directories are read-only, ie you are never going to change or add any files there.
You will need either [cramfs Here is an example for compressing and mounting the jre directory:. Note that mkcramfs stores the whole image in memory before writing it to disk, so make sure you have a sufficiently sized swap file enabled before running mkcramfs. Also, there are only 2 loop devices by default on the C and C, but you can create more loop devices.
You will need to recreate them each time you reboot, so it would be better to automate it in a start script which you can use to automatically mount the cram archives as well. You might also want to add an entry into fstab so the cramfs archives can be automatically mounted. At system shutdown or reboot, it will cleanup and unmount anything mounted as a loop device.
Similar to the cram filesystem is the squash filesystem which is appendable, ie you can add files to it. Alternatively, if you don't need a compressed filesystem but want a read and write access instead, then you can create an ext2 or ext3 formatted loopback filesystem.
You would need to pre-allocate a chunk of space for it and the files won't be compressed at all. However, doing this will impact on performance a little bit.
The overhead caused by the loopback filesystem and the speed of the MicroDrive are factors to consider and thus, choose files and directory that are not frequently used to be moved to the loopback filesystem.
Alternatively, instead of moving files manually after they have been installed, you can also just install files to the loopback filesystem directly. The default installer won't let you do it, but my xipk install script which is part of my ipktools package does allow it.
Then you can do the following to install applications to hdd Using the updated driver which is taken from the C, it is possible to use larger SD cards. Also, for 4GB SD cards, be very careful when ejecting the card. If you eject it while it is still mounted or while it is being written to, then you might corrupt the integrity of the device and might not be able to use it anymore. Since it is larger, it needs more time to flush the buffers and thus this problem occurs less on smaller SD cards.
If this occurs, however, even a fdisk or reformatting of the SD card won't work the smaller SD cards can be reformatted in some digital cameras but not many cameras can recognise the larger SD cards either so you cannot use them to reformat a broken SD card. To prevent this from happening in which case you need to claim a warranty replacement so make sure you got proper warranty when you purchase large SD cards, you can change the SD mount options to mount the SD card with the sync option and also increase the wait delay from 1 second to 3 or 5 seconds during the SD unmount process.
The Zaurus has an IrDa port build-in, but for security and power saving, it is disabled by default. You can temporarily enable it to receive files. Use the IR-Receive tool under the Settings tab and enable it to receive files. You should disable it once you finished receiving files. You can also send files via IrDa. For that, select the file you want to beam from the Files Tab and hold the stylus on it for a few seconds and select Send by beam The stock Sharp ROM does not come with bluetooth enabled.
In order to enable and use Bluetooth, you need to install a bluetooth stack such as bluez which includes the required kernel modules as well as needed command line tools. You can also add some plugins to the graphical Network config tool to enhance it to handle bluetooth connection types.
Once they are installed, you will see additional options in your Network config tool. The bluez package is essential while the others are optioanl.
If you find newer updated versions of those, then use them instead. Once you have installed the above packages, you can begin to setup and configure your bluetooth stack. There is also a bluetooth lite package which only contains the GUI scripts. The qshdlg package needs to be installed to use the bluetooth GUI. The first thing you need to do is check your config and make sure your bluetooth stack has initialised successfully.
Note that unless the other bluetooth devices are configured to be visible, you won't be able to find them. Write down their mac addresses. To find out the capabilities of those devices do the following with their corresponding mac address:.
0コメント