They're on 24/7 so you are welcome to use them. They are:
Running the Atmark 2.4.27 kernel and busybox userland, bootstrapped into a Debian "etch" system ARM on a 1GB USB pendrive. The old system is accessible via telnet or on the serial console from guest using
$ minicom arma
Its /home is that of cluster.
Runs a web server, a forum and acts as an X terminal onto other hosts, is used for Debian old-ABI testing and as an access point from the net to other hosts on the local subnet.
You don't need to ask to use this; it is free to use over ssh as
arma.homelinux.net with user guest
and password friend.
In several years of free access
this account doesn't ever seem to have been abused.
$ minicom ts7250It runs Debian armel sid on a root filesystem served over NFS from cluster's /tftpboot/armel-sid There are notes on building this and its custom linux kernel.
Used for ARM EABI development, testing EABI software on armv4t hardware and for testing MaverickCrunch FPU floating point code generation and speed.
/home is that of cluster.
On USB host guest:
# ifconfig usb1 192.168.6.1 # iptables -t nat -A POSTROUTING -s 192.168.6.0/24 -j SNAT --to-source 22.214.171.124
On other local hosts:
# route add 192.168.6.0 netmask 255.255.255.0 gateway 126.96.36.199
On itself, put
nameserver 188.8.131.52in /etc/resolv.conf.
None. It just picks up the open wifi.
266MHz arm920t, 128MB RAM + swap, 500MB SD card,
GPS/GSM modem, USB network to guest.
OS: OpenMoko 2007.2, optionally hosting a chroot of Debian armel sid over NFS.
On guest, configure USB net and provide internet for the device:
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0 # iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j SNAT --to-source 184.108.40.206 # echo 1 > /proc/sys/net/ipv4/ip_forward
On other hosts and specially on the public/localnet gateway:
# route add -net 192.168.0.0 netmask 255.255.255.0 gateway 220.127.116.11
On the ADSL router/name server etc, add the same route.
Angstrom config on the device: put
nameserver 18.104.22.168in /etc/resolv.conf