Here are some Hurd boxes that users have made available to the public:
| Hoster | Name | Distribution | Machine Specs | Comments |
|---|---|---|---|---|
| bddebian | blubber | Debian GNU/Hurd | Celeron 2.2 GHz; 222 MiB | Xen domU on zenhost; for experimental stuff |
| bddebian | clubber | Debian GNU/Hurd | PIII 1 GHz; 384 MiB | |
| bddebian | flubber | Debian GNU/Hurd | Celeron 2.2 GHz; 666 MiB | Xen domU on zenhost |
| bddebian | foobar | Debian GNU/Hurd | Celeron 2.2 GHz; 160 MiB | Xen domU on zenhost; web server |
| bddebian | gnubber | Debian GNU/Hurd | PII 733 MHz; 384 MiB | |
| bddebian | goober | Debian GNU/Hurd | ? | |
| bddebian | grubber | Debian GNU/Hurd | Celeron 2.2 GHz; 222 MiB | Xen domU on zenhost; for experimental stuff |
| bddebian | zenhost | Debian GNU/Linux | Celeron 2.2 GHz | Xen dom0 for several hosts |
To request an account on the bddebian machines either contact bddebian or tschwinge (other people might also be able to help) in IRC or send email to hurd-shell-account@gnu.org. Also use these contact addresses for requesting support with respect to software installations, etc.
For easy access, you should append your public SSH key(s)
to ~/.ssh/authorized_keys on the remote machine.
Also, add the following stanza to ~/.ssh/config of the machine you're
connecting from:
Host blubber.bddebian.com blubber
HostName blubber.bddebian.com
Host clubber.bddebian.com clubber
HostName clubber.bddebian.com
Port 2251
Host flubber.bddebian.com flubber
HostName flubber.bddebian.com
Port 2250
Host foobar.bddebian.com foobar
HostName foobar.bddebian.com
Host gnubber.bddebian.com gnubber
HostName gnubber.bddebian.com
Port 2254
Host goober.bddebian.com goober
HostName goober.bddebian.com
Port 2255
Host grubber.bddebian.com grubber
HostName grubber.bddebian.com
Host zenhost.bddebian.com zenhost
HostName zenhost.bddebian.com
Port 2260
Host blubber.bddebian.com blubber foobar.bddebian.com foobar grubber.bddebian.com grubber
ProxyCommand ssh zenhost socat - TCP4:%h:%p
Host *.bddebian.com blubber clubber flubber foobar gnubber goober grubber zenhost
CheckHostIP no
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
User [username]
The CheckHostIP statement is for not having to worry about the machines's IP
addresses changing (due to dial-up connection), and the UserKnownHostsFile
one together with the StrictHostKeyChecking one are for not having ot worry
about the host keys changing (when the machines are re-installed). Of course,
this undermines SSH's security system, so you may disagree about these.