Feeds

66540 items (51620 unread) in 130 feeds

Linux Linux
Gentoo Gentoo
Debian Debian
Fedora Fedora
Kde Kde
Gnome Gnome
Mandriva Mandriva
MySQL MySQL
Apache Apache
Redhat Redhat

rwhitby.net

  • Permalink for 'rwhitby.net/2007/12/31/Five_new_NSLU2_firmware_releases_in_five_days'

    Five new NSLU2 firmware releases in five days

    Posted: December 31st, 2007, 3:58am CET by Rod Whitby

    In the last five days, we have made five new NSLU2 firmware releases:

    2007-12-31 - Unslung 6.10-beta Release
    2007-12-30 - SlugOS 4.8-beta Release
    2007-12-29 - OpenWrt/NSLU2 Kamikaze 7.09 Release
    2007-12-28 - Angstrom/NSLU2 2007.12 Release
    2007-12-27 - Debian/NSLU2 Stable 4.0r2 Release

    All of these new releases are available at

    [www.slug-firmware.net]

    See [article.gmane.org] for
    an explanation of the pros and cons of each different firmware
    distribution, and the installable packages available for each.

    Thanks to everyone in the NSLU2-Linux, OpenWrt, Angstrom, OpenEmbedded
    and Debian projects who contributed to these releases.

    Remember, if you find any of the firmware or packages that the
    NLSU2-Linux project provides useful, feel free to make a donation to
    the project at

    [www.nslu2-linux.org]

    We are currently in need of about $500 to buy a RAID controller card
    and some disks for our autobuild machine to support all this new
    firmware with up-to-date package feeds …

  • Permalink for 'rwhitby.net/2007/11/13/Android_Internals'

    Android Internals

    Posted: November 13th, 2007, 7:06am CET by Rod Whitby

    Here are some links to various pieces of information (not published by Google) about the internals of the new Android OS:

    [benno.id.au]
    [benno.id.au]

    A script to list the contents of the root filesystem: [pastebin.ca]
    (Yes, this is almost unreadable perl, and the regexps were created by trial and error until there were no more unmatched lines.)

    The output of that script: [pastebin.ca]

    [benno.id.au]
    [benno.id.au]

    Graphical console programming: [groups.google.com]

    Dynamic linking: [groups.google.com]

    DEX format documentation: [groups.google.com]

    Dalvik VM benchmarking vs native code: [groups.google.com]

  • Permalink for 'rwhitby.net/2007/09/01/Setting_the_OpenMoko_timezone'

    Setting the OpenMoko timezone

    Posted: September 1st, 2007, 10:33am CEST by Rod Whitby

    If you want to set the timezone on your phone correctly, do the following:

    1. ipkg install tzdata
    2. ipkg install your desired tzdata-* packages.  For instance, I use “tzdata-australia“.
    3. Enable your desired timezone by symlinking it to “/etc/localtime“.  Adjust the following example command line for your locality.
      • ln -s /usr/share/zoneinfo/Australia/Adelaide /etc/localtime
    4. The “date” command should now show the correct time for your timezone.  If it is not correct, then install the “ntpclient” package, and use it to set your clock.

    Note that this technique should work on any OpenEmbedded-based Linux distribution.

    1. Permalink for 'rwhitby.net/2007/09/01/Intercepting_hotplug_on_the_Freecom_FSG_3'

      Intercepting hotplug on the Freecom FSG-3

      Posted: September 1st, 2007, 8:11am CEST by Rod Whitby

      The Freecom FSG-3 wireless storage router has four USB ports, and has support for hotplug built into the kernel.  This makes it ideal for use as a docking station for OpenMoko phones.

      Unfortunately, it does not have the normal hotplug agent scripts that you expect to find on a desktop Linux distribution.

      So you have to roll your own:

      1. Run “mv /sbin/hotplug /sbin/hotplug.freecom
      2. Create a new “/sbin/hotplug” shell script (the following is an example of how to automatically enable USB networking for an OpenMoko phone):
        #!/bin/sh
        
        case $1 in
          ( usb )
            case $PRODUCT/$INTERFACE in
              ( 1457/5122/212/2/6/0 ) # OpenMoko GTA01 cdc-ether
                case $ACTION in
                  ( add )
                    ifconfig usb0 192.168.0.200 up
                    ;;
                  ( remove )
                    ifconfig usb0 192.168.0.200 down
                    ;;
                esac
                ;;
            esac
            ;;
        esac
        
        /sbin/hotplug.freecom "$@"
        

      3. Run “chmod ugo+x /sbin/hotplug” to ensure that your new hotplug script is executable.
      4. See [linux-hotplug.sourceforge.net] for the list of environment variables you can use to distinguish different devices.
    2. Permalink for 'rwhitby.net/2007/09/01/Replacing_dropbear_with_openssh'

      Replacing dropbear with openssh

      Posted: September 1st, 2007, 7:57am CEST by Rod Whitby

      I prefer to use OpenSSH rather than Dropbear on my devices.  The main reason is to get sftp support (which is required by sshfs).  Another reason is to get better support for agent forwarding (which is essential for bouncing from one machine to another without leaving your private keys all over the internet).

      To do this on OpenMoko (or any other OpenEmbedded-based distribution for that matter, for instance SlugOS or Angstrom):

      1. Edit /etc/init.d/dropbear by replacing “DROPBEAR_PORT=22” with “DROPBEAR_PORT=2222” (or any other unused port).
      2. Run “ipkg install -force-depends openssh” to install openssh.
      3. Make sure you have set a root password before rebooting (use “passwd” to set it).
      4. Reboot (dropbear will restart on the new port, and openssh will start on the normal ssh port).
      5. Check that openssh is now serving on port 22 by logging into the device over ssh.
      6. Run “ipkg remove -force-depends dropbear” to remove dropbear.
      7. Then run “ipkg install openssh-sftp” to install support for the sftp protocol which sshfs uses.

    3. Permalink for 'rwhitby.net/2007/08/26/Debugging_gsmd_failures_on_OpenMoko'

      Debugging gsmd failures on OpenMoko

      Posted: August 26th, 2007, 2:29pm CEST by Rod Whitby

      If you’re having problems making phone calls on OpenMoko 2007.2, and wish to see what gsmd is doing, then look in /tmp/gsm.log for the gory details …
      Mine fails to register automatically, as documented in [lists.openmoko.org] - this seems to be a problem where libmokogsmd2 is not handling a GSMD_NETREG_UNREG_BUSY event correctly.

      Update: this problem with UNREG_BUSY has now been fixed with the patch that I submitted.

    4. Permalink for 'rwhitby.net/2007/08/25/Stopping_the_OpenMoko_startup_sound'

      Stopping the OpenMoko startup sound

      Posted: August 25th, 2007, 11:35am CEST by Rod Whitby

      OpenMoko 2007.2 makes a very loud startup sound.  To mute it, do the following:

      In /etc/pulse/session, replace:

       load-sample startup /usr/share/openmoko/sounds/startup_openmoko.wav

      with:

       load-sample startup /usr/share/openmoko/sounds/touchscreen_click.wav

      (or any other subdued wav file you wish to upload onto the device).

      Update: The OpenMoko team has sensibly replaced the load startup sound with a much more unintrusive sound.

    5. Permalink for 'rwhitby.net/2007/08/11/Connecting_a_Treo650_to_an_OpenEmbedded_based_firmware_distribution'

      Connecting a Treo650 to an OpenEmbedded-based firmware distribution

      Posted: August 11th, 2007, 11:29am CEST by Rod Whitby

      The following should work for an NSLU2 running SlugOS or Angstrom, or a device running OpenMoko.

      • Install the required kernel modules for bluetooth
        • ipkg install kernel-module-hci-usb kernel-module-l2cap kernel-module-rfcomm
        • depmod -a
        • ipkg install bluez-utils
      • Edit /etc/default/bluetooth to enable hcid and dund.
      • Change the pin and host settings in /etc/bluetooth/hcid.conf, and make sure that the class is 0×3e0100 (not the default value, which is for a PDA like a Zaurus, not a “Computer” device like the Neo which can accept and route tcp/ip network connections coming in over dund or pand on the bluetooth network)
      • Reboot and test with ‘hciconfig’ with a bluetooth dongle plugged in.
      • Install the required kernel modules for ppp
        • ipkg install kernel-module-ppp-async kernel-module-bsd-comp kernel-module-ppp-deflate
        • depmod -a
        • ipkg install ppp
      • Edit /etc/ppp/options as follows:

        noauth
        crtscts
        lock
        local
        proxyarp
        ktune
        192.168.1.XX:192.168.1.YY
        ms-dns 192.168.1.ZZ

        (edit the last two lines to suit your network topology, the first IP address
        is your gateway device, the second IP address will be assigned to the client,
        and the third IP address is your DNS server)
    6. Permalink for 'rwhitby.net/2007/06/28/Using_vncserver_on_the_Nokia_N800'

      Using vncserver on the Nokia N800

      Posted: June 28th, 2007, 2:09pm CEST by Rod Whitby

      There is a VNC Server available for the Nokia N800.

      • Install x11vnc from [mike.saunby.googlepages.com]
      • Select Extras->x11vnc to run it
      • Open VNC Viewer on your desktop and connect to <your-n800-hostname-or-ip-address>:0

      Some key bindings that I have found:

      • F3
        • Selects the Applications icon in the task navigator
      • F4
        • Opens the menu for the current application
      • F6
        • Toggles full screen mode
      • F7
        • Same as the + button
      • F8
        • Same as the - button
      • F9
        • Selects the application switcher (the >> button in the left hand bottom corner)

    7. ← Das Blog - Latest Entries hardy.dropblog →