• use the card reader to erase the Fat32 partition on your SD card and replace it by a small Fat32 one (32 MB should be enough) and a big Linux partition using fdisk (become superuser for it)
• format both partitions with mkfs.vfat (with -F 32) and mkfs.reiserfs
• mount both partitions (e.g. at /mnt/loox1 the FAT32 and /mnt/loox2 the reiserfs partition)

• quit superuser mode
• creat in your home dir a directory for all the stuff
  cd ~
  mkdir linuxloox
  cd linuxloox
• get the kernel image and HaRet stuff in order to boot Linux (from WinMobile) from here
• get the mini distro from here
• su to superuser and untar the kernel/booting stuff to the FAT32 partition of the SD card:
  tar xzf ./loox_boot.tgz -C /mnt/loox1
  
• untar the distro image to the raiserfs partition of the SD card:
  tar xzf ./loox_image.tgz -C /mnt/loox2
  (I ignored those timestamp warnings)
• do a sync
• umount both SD card partitions
• [OPTIONAL] Backup your loox before trying Linux.. it WILL wipe your looxs memory!
  (if your Loox isn't holding any data/programs as mine, skip that)

• put the SD card into the waiting Loox
• hard reset (to be safe - softreset while pressing POWER button for some secs)
• step thru the Fujitsu-Siemens welcome stuff and PDA setup and open the file manager
• change to the SD-MMCard (as the Linux partition isn't shown, you will land at the FAT32 partition)
• start HaRet
• Watch the penguin fly for the first time! (-:

• connect the Loox with the sync cable to your desktop box (will go to USB)
• now your desktop box should recoginze it, to check do ifconfig. There should be an USB network interface, normally it should be usb0 since most people don't have USB network devices (-:
• su to superuser and do ifconfig usb0 192.168.0.1
  (of course if necessary change usb0 to whatever it actually is on your system)
• quit superuser mode and ssh -lroot 192.168.0.2 and when asked for the password (might take some seconds), enter root
• [OPTIONAL] you can give 192.168.0.2 a nice host name like loox on your desktop by adding
  192.168.0.2 loox
  to /etc/hosts (use a text editor as superuser).
  instead scp some_file root@192.168.0.2:/some_dir it is now scp some_file root@loox:/some_dir (-:

Welcome to your Loox!

[RECOMMENDED]: set correct time/date to your Loox. This was necessary for me in order to successfully connect via OpenVPN.date MMDDHHMMYYYY (e.g.:date 092913252007 for September 29th 2007, 13h25min)

• in /root on your Loox, create a directory for the additional files and change to it:
  cd /root
  mkdir pnuke-updates
  cd pnuke-updates
  
• replace /etc/resolv.conf by http://www.postnuklear.de/linuxloox/files/resolv.conf
  (this one you cannot directly download with wget as you will need this file to actually resolve server names on the Internet) Either:
  • Save it onto your desktop box as resolv.conf, followed by
    scp resolv.conf root@loox:/etc/
  • or on the Loox (in console):
    cd /etc/ followed by pico resolv.conf
    delete all entries here (CTRL+k will erase the current textline) and paste the marked text into the window, hit CTRL+x (confirm with ENTER to save and exit
  (the old settings aren't valid anymore since the DNS servers mentioned there were close for external requests)
• wget http://www.postnuklear.de/linuxloox/files/hosts and copy (cp) it to /etc/
  (this will enable programs to resolve your Loox's hostname as the PDA hasn't an official worldwide known IP adress nor DNS entry)
• Masquerading will be used in order to let your Loox talk to the world using your desktop box and its connection.
  • Open a new console on your desktop box and become superuser
    (if so far you didn't use USB to talk to your Loox, follow instructions of above section first)
  • iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
    (if your desktop box is connected by a device [= network card or wifi or...] other than eth0 to the Internet change the iptables entry to match your configuration)
  • echo 1 > /proc/sys/net/ipv4/ip_forward

[RECOMMENDED]: change the password for the superuser on your Loox! You are now part of the Internet and therefore a possible victim of attacks. Enter passwd and change to a new password

You should now be able to do a ping www.firstloox.org

Next step: language support.
In order to let your Loox applications now talk in your own tongue, it is useful to install and configure the locales package. This software handles the settings for language support for texting, date, and so on depending on the country you live. A lot of programs come with locales files to display their messages in different languages. apt-get (-;

• in your Loox console type:
  apt-get install locales
  (ignore possible error messages about unset LC_ variables, this happens when you log in via ssh and have language settings on your desktop box properly set)
• after installation is done:
  dpkg-reconfigure locales
  this will bring up a menu oriented configuration program which lets you select support for languages and character sets you'd like to have, as well as setting the default language
• browse with the ARROW keys thru the first list, mark with SPACE all wanted sets. Note that there are more than one set for a specific natural language. For example I selected all de_DE stuff, that is German in Germany (-:. Additionally I selected all en_US entries. My idea: have some default fallback if a packages has no DE support (though not sure if this is necessary, am a newbie to LOCALES)
(make sure that the first entry for all languages is not selected. Otherwise you can go shopping or to sleep while all those locales are set up)
• When all you want to have is marked, hit TAB and ENTER
• From those languages you have previously selected, choose one default one by navigating with ARROW keys and selected the desired one with ENTER, letting your system being properly configured
• After dpkg-reconfigure is done, say Hello, Gooden Tag, Bienvenue or Willkommen to your apps, they speak your language now! (-:
  if the language of your desktop box was selected above, the annoying error messages will disappear)
• Well, actually not all of them, just those who support locales in those languages you selected

• apt-get install localepurge
• select the locales you want to keep, the chosen ones from above are preselected
• press TAB and ENTER

• apt-get install xserver-xorg-video-fbdev
  This will install the framebuffer video driver and all packages that it "depends" on. This is the way to go in order to get something to see on the Loox screen as far as I can see it (-:
  (Actually almost the whole basic X system is installed, as the video driver depends on those packages and those packages depend on and so on. To be honest, unecessary packages are also installed, as those dependencies try to provide a let's say "working everywhere" installation. This issue is handled later on)
  

  Note: at the end of package installation you are asked for the display resolutions to be set. Simply hit ENTER since we will replace the xorg.conf file anyways (-:

• apt-get install xfonts-base
  Ironically the package for basic fonts isn't covered by those X dependencies, maybe because you can also use remote font servers. Well, with above command, we install them (-:
• get the input driver for the touchscreen http://www.postnuklear.de/linuxloox/files/evtouch_drv.so (you remember? wget)
  There is also a debian package but it is unstable as far as I know and depends on different versions of the installed packages, so I compiled the source on the Loox.
  Home of this driver is http://stz-softwaretechnik.com/~ke/touchscreen/evtouch.html.
  
• Copy it to /usr/lib/xorg/modules/input

• backup the old xorg.conf file on your Loox:
  cd /etc/X11/
  and mv xorg.conf xorg.conf.orig
  
• next, download http://www.postnuklear.de/linuxloox/files/Xorg-Loox-Keys.tgz
  This archive contains the new xorg.conf as well as some keyboard related files to make the Loox keys functional
• Enter tar -xzf Xorg-Loox-Keys.tgz -C /
  (This will extract all files with / as top level directory)
- see README.keymap_mods.txt in /root after untarring -

• get http://www.postnuklear.de/linuxloox/files/z55_looxinput.rules to your Loox and copy it to /etc/udev/rules.d
  
• enter udevtrigger and check device setup with ls -l /dev/input
  There should be now a link touchscreen to one of the eventX files. Depending on hotpluggable hardware connecting and disconnecting, it is not guaranteed that a device will always be at the same event hook. With the udev rules you just installed there will always be a link touchscreen pointing to the correct /dev/input/event entry.
  
• now simply startx on your Loox
  after some seconds you should see the familiar X background checker, together with a single window telling you that X couldn't be started as no useful programs were found. Anyway this is enough for testing. Now touch the screen with your stylus and check that the mouse cursor follows the movements and you are able to close that dialog.
• calibrating the touchscreen - the new xorg.conf has some settings to adjust the touchscreen on my Loox. Those values might simply not really work for you.
  In this case
  • CTRL+c on your Loox to kill X
  • Get http://www.postnuklear.de/linuxloox/files/evtouch_values
    This is a simple program to find good Min/Max Values for the options section of the evtouch driver
    
  • do chmod u+x ./evtouch_values and start evtouch_values
    now touching the screen causes some output on your console
  • move the stylus along the sides of the screen, best is to follow the rectangular display border a few times
  • The program prints out the currently found min/max values. If those values don't change for some time while moving along the borders, write those values down and CTRL+c the program
  • in /etc/X11/ do pico xorg.conf and look for:
    

    Section "InputDevice" Identifier "touchscreen" Driver "evtouch" Option "CorePointer" Option "Device" "/dev/input/touchscreen" Option "DeviceName" "touchscreen" Option "MinX" "434" Option "MinY" "333" Option "MaxX" "3643" Option "MaxY" "3804" Option "SwapX" "true" # Option "ReportingMode" "Raw" # Option "Emulate3Buttons" # Option "Emulate3Timeout" "50" Option "SendCoreEvents" "On" EndSection

  • replace the Min/Max values according to those you wrote down
  • CTRL+x and answer the question for saving with y and hitting ENTER, leaving pico
  • try startx again and see if it helped
• At this point you should see X with a simple window that you can close by hitting the button with your stylus!
  
• If you want to rotate the X display (for desktop style screen view) add
  Option "Rotate" "DIRECTION"
  both to the Section "InputDevice" of the touchscreen and Section "Device" (where fbdev is specified). DIRECTION can be: CCW for counter clockwise and CW for clockwise rotation, UD for upside down.

• at the Loox console:
  apt-get install alsa-utils
  This will install some ALSA utilities. Actually because of the dependencies this package has, more is installed, in fact everyting that is needed to play a WAV file
• the main challange for you in order to get something to hear is to use a mixer program to adjust the soundcard settings. Go ahead, start alsamixer and see what I mean (-; (arrow keys for navigation, ESC to save settings and quit).
  For quick results however, download http://www.postnuklear.de/linuxloox/files/asound.state to your Loox and copy it to /var/lib/alsa/
• Enter: alsactl restore
  (asound.state is the configuration file for the sound device, used by ALSA. With alsactl restore those values simply are used to initial the soundcard)
• need a test file? Download http://www.postnuklear.de/linuxloox/files/kde_startup.wav.gz (300 kb)
• gzip -d kde_startup.wav.gz
• aplay kde_startup.wav

• Get additional kernel modules for Bluetooth support: http://www.postnuklear.de./linuxloox/files/bt_modules.tgz onto your Loox
• Extract them with: tar -xzf ./bt_modules.tgz -C /
• Enter: depmod -a
  (Ignore the warning about the cast6 module)
• do apt-get install bluetooth to get essential Bluetooth programs and libs.
  (also hcid and sdpd, daemons for handling Bluetooth devices, connections and services, are started and set to be run on startup)
• for a simple test:
  
  • activate Bluetooth on your cell phone (maybe give it also a nice name *g*) or any other working Bluetooth device, deactivate any hiding option
  • hciattach ttyS1 texas
    (the blue led should now blink) .
  • hcitool scan
    This should give you a list of Bluetooth devices your Loox can see right now
  • likewise you can scan for your Loox on those devices and should find loox720-0
  • to turn it off again do ps -aux, find the entry for hciattach look up their PIDs and do:
    kill -9 PID (with PID being the actual number)
    The blue LED should be off now (daemons still running though)
• To enable Bluetooth after booting, simply call hciattach ttyS1 texas
• In order to access devices using a PIN, you will need a key agent. Things are handled if you install the particular KDE or GNOME package, for now or, if you don't want to use those:
  • Get the http://www.postnuklear.de/linuxloox/files/passkey-agent and copy it to /usr/sbin/
  • before connecting with pand, do
    passkey-agent --default PIN &
    where PIN is the pin number the remote device accepts
    (there are plenty of more flexible ways to handle the passkey-agent issue, this is only a simple sample setting)
  • then you can do your pand call

Get http://www.postnuklear.de/linuxloox/files/powerbutton-agent as well as http://www.postnuklear.de/linuxloox/files/hibernate_loox.sh
• Do chmod 700 FILENAME for both files
• Copy the files to /sbin
• Get http://www.postnuklear.de/linuxloox/files/hibernate.tgz
  and do tar -xzf hibernate.tgz -C / this will install modified files under /etc to ensure that powerbutton-agent and hibernate_loox.sh will be started on boot time (old files are save as .old)
• if you don't want to wait till boot time to use the power button, do the following:
  • ps ax | grep -v grep | grep udev
  • kill PID where PID is the first number of above output
  • udevd --daemon (so basically a restart)
  • udevtrigger
    (I always thought, calling the trigger would do the job, but obviously the daemon has to be restarted first...)
  • call /sbin/powerbutton-agent /sbin/hibernate_loox.sh &
• Now pressing the power button should turn off the display, the wifi card and bluetooth. Additionally the CPU frequency is set to powersave, which is 104Mhz. On resuming all hardware that was on before hibernation will be turned on again (Note that nevertheless you might have to restart programs using them!)
• [EXPERIMENTAL]: To enable suspend mode for user processes (like X, etc...) open /sbin/hibernate_loox.sh and change doStopProcesses to on. When pressing the power button next time, additionally to hardware suspend a number of user started programs get the SIGSTOP signal. This also holds for any login, so after hibernating you can't do much on your Loox till you resume (-: actually, the connect should be continued without problems (as usual exceptions prove the rule). DO THIS ON YOUR OWN RISK!

• Remove superfluous packages, which came with the X installation
  (those packages were selected automatically by the dependance system but as setting up dependencies for such a complex piece of software as X is, it is far from being optimal. None of the following packages should actually break existing dependencies).
  call apt-get remove --purge with the following package names, separated by white space:
  • xserver-xorg-input-kbd
  • xserver-xorg-input-synaptics
  • xserver-xorg-input-wacom
  • xserver-xorg-input-all
  As you can see (?) the keyboard input driver is gone, as evdev is used for this Loox installation. However, mouse support is not handled this way, so the apropriate driver will be kept.

  Note: apt-get will ask you to confirm this step and display all packages that are actually going to be removed. Verify that only those packages mentioned above are marked for deletion!
  (For a fresh installation this shouldn't be a problem, however if you installed some stuff of your own, this new software might need one of the removal candidated. If you see more / other software marked for deletion, cancel and adjust the list for removing packages (-:)

• Get rid of (in my opinion) unecessary packages coming with the Loox image
  (this will not lead to broken dependencies so this shouldn't actually harm your system, worst case should be you will suddenly miss a program you used to use (-:)
  Again, verify that the list of packages to be removed is identical to the one you passed to apt-get remove --purge.
  Remove the following packages as done above:
  • aptitude
  • tasksel
  • tasksel-data
  • iptables
  • cpio
  • netcat
  • vim-common
  • vim-tiny
  • libconsole
  • dselect
  • ed
  • laptop-detect
  • info
  • libsigc++-2.0-0c2a
   
  
• a little hacking for more space, getting rid of python
  (This is a little tricky and I can't promise this won't cause any problems, however so far, all seems to work (-:)
  At the time of writing, alsa-utils depends on python2.4 a really big package. This is absurd, as only one little program is a python script. Even worse, actually the python-minimal installation already suffices to let this script run. I wrote this to the particular Debian package maintainers, and actually this false dependency has been fixed in the next package version of alsa-utils. However, right now it is in testing and no ARM packages are available, so you have to do this by hand:
  • on the Loox, do:
    pico /var/lib/dpkg/status
    (this file contains all information about all installed packages)
  • press CTRL+w and enter package: alsa-utils, hit ENTER
    This will bring you to the section referring to the alsa-utils package.
  • find the line starting with Depends: and change python to python-minimal
  • press CTRL+x, then confirm with y, hit ENTER for saving the modified file and leaving the editor
  • do apt-get remove --purge python2.4
    This will list two packages to be removed, the other one is python which is kind of a meta package, both aren't needed (in fact, one can't stay without the other)
  • don't do this if more packages are listed, this might happen if you installed some python depending software meanwhile!

  Possible effect: When doing an apt-get upgrade somewhere in the future, it might happen that alsa-utils is hold and not updated.
  This might be the case if dependencies of old and new package vary. You can tell apt-get with --ignore-hold to do the upgrade or in the end --force should do it (I am no APT expert, check the man page or the web if there are some problems).
  However, with the adjusted dependencies in the new release (1.0.15-1) this shouldn't be a problem (but who knows?)

• [EXPERIMENTAL] get rid of the APT working files
  (This will be a little bit exotic, but IMHO the gain is much bigger than the effort)
  APT maintains information not only of installed packages (using dpkg) but also of available packages on the net. As convenient this might be, as much space is needed for this. A temporary solution would be to delete those files, however, they will return with every apt-get call and thus you would have to reserve SD card space for them.
  The following approach uses some kind of ramdisk. Well actually it is not a ramdisk, but this isn't really important at this point (-:
  
  • cd to /etc/apt/ and wget http://www.postnuklear.de/linuxloox/files/apt.conf
    (there shouldn't be no older version of this file in this directory). With this settings, APT will not create archive files of the available packages (however this won't be enough to save space)
  • in the same directory edit sources.list with pico, comment the lines starting with deb-src with an # and save the modified file. Every line in there stands for a server which provides Debian packages and therefore needs space. By commenting the deb-src lines you won't retrieve information about source code packages, which you actually won't compile on the Loox anyways.
  • now change to /usr/sbin and use wget to retrieve http://www.postnuklear.de/linuxloox/files/loox-apt-session.sh
  • in /var/cache and /var/lib do rm -r apt
  • From now on, if you want to install packages using apt-get call loox-apt-session start first. This will get the information that APT needs in order to install packages, from the servers. When done with all apt-get install/remove jobs, call loox-apt-session stop, to free the RAM which was used to hold the files.
  Disadvantages:
  • installing software now takes longer since using the script APT will always retrieve information about all available software on the servers mentionend in the sources.list file. Normally, this wouldn't be necessary since information were stored on disk.
    However, if you sum up package installations, let's call it a session, instead of retrieving them every now and then, this shouldn't be that much of a problem (call the script with start once, do all installs/removals. call the script with stop)
  • RAM is used to store APT data. RAM is precious, thus the script currently reserves 64MB of the Loox RAM (you can adjust this in the script, look for the mount line and change the value), in order to let other programs still use some RAM while being able to store all APT data, most of the time at least. It might get a little tight if you have a big server list (/etc/apt/sources.list) and/or install a lot of software/ big packages/packages with huge dependencies. You can reduce the risk of running out of space (which would APT cause to stop installation I guess) by maintaining a small server list and, when installing a lot of packages, break the installation into more than one apt-get install calls and do a apt-get clean once in a while between them, to delete downloaded files of installed packages. This might be a little inconvenient, but don't forget, once you got all software you need, new installations should become rare...
   
  
• Trimming perl
  ...on Debian, X installation also installs defoma the Debian Font Manager. Though this is something good I guess, it has one big major drawback: it is perl scripted, which means: a lot of waste of space! Luckily it seems like Defoma only needs perl-base and perl-modules. These packages already eat up a lot of SD space, but at least we can get back ~10MB by getting rid of the perl package.
  (Note that this customizations might complicate later automatic upgrading of defoma and perl-modules!
  • open /var/lib/dpkg/status in a text editor
  • search for Package: Defoma
  • in line starting with Depends: change perl (>= 5.6.0-16) to perl-base (>= 5.6.0-16), perl-modules (>= 5.6.0-16)
  • search for Package: perl-modules
  • in line starting with Depends: change perl (>= 5.6.0-8) to perl-base (>= 5.6.0-8)
  • do apt-get remove --purge perl (don't forget loox-apt-session.sh start if you set it up ;) )
  Note: If apt-get lists more than the perl marked for deletion, you installed packages that depend on it: abort! AFAIK this shouldn't affect the working of defoma I called all scripts none referred to missing functions or similiar, however it is not 100% for sure this might break (I am no perl programmer). But installing another ttf-font which registers itself via defoma worked without any probs, for example...
  (I realised too late that those dependencies differ in version numbering... you should be save using the version numbers of actual installed perl-base and perl-modules)

At this point, this guide has found its end, basic software for hardware support has been installed (networking via USB or Wifi, Bluetooth, Audio, Loox keys and touchscreen under X, USB keyobard is working as well as USB mouse, again: under X (-: ).
However, if it comes to real usability, this setup doesn't do much yet. It is now uo to you to fill the blanks by apt-getting the programs you want to use on the Loox, starting with a tiny window manager (remember, it's a PDA, no desktop PC!) e.g. matchbox, maybe a light webbrowser like dillo up to GNOME or KDE if you really want to...basically the whole Debian distribution is available and waiting to be installed (-:.
To start, take a look at http://packages.debian.org/stable/ to browse the package sections.

Right now there is no Part 2 of From Dolphins and Penguins which covers a useful application installation setup, for this is quite depending on you the user, as well as a lot of installing, testing and basically messing up the system, which I don't have time for right now.