1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
Here are some Hurd boxes that users have made available to the public:
[[table class="table_style_1" data="""
"Host Name","Operator","Access","Distro","Machine Specs","Comments"
"flubber.bddebian.com","[[Barry\_de\_Freese|bddebian]]","ssh; port 2250","Debian","PII 550 MHz; 384 MiB"
"clubber.bddebian.com","[[Barry\_de\_Freese|bddebian]]","ssh; port 2251","Debian","PIII 1 GHz; 384 MiB"
"gnubber.bddebian.com","[[Barry\_de\_Freese|bddebian]]","ssh; port 2254","Debian","PII 733 MHz; 384 MiB"
"hurd.nipl.net","[[AlastairPoole]]","ssh; port 24","GNU","AMD Sempron 2800 MHz","not sure if this machine is still alive"
"""]]
To request an account on the `*.bddebian.com` 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 the `hurd.nipl.net` host, please see <http://www.nipl.net/>.
To be able to use just `ssh [machine]`, you should append your public SSH key
to `~/.ssh/authorized_keys` on the remote machine.
And if you don't want to worry about the machines's IP addresses changing (due
to dial-up connection) or the host keys changing every now and then (when the
machines are re-installed), put something like the following into
`~/.ssh/config` of the machine you connect from:
Host clubber.bddebian.com clubber
HostName clubber.bddebian.com
Port 2251
Host flubber.bddebian.com flubber
HostName flubber.bddebian.com
Port 2250
Host gnubber.bddebian.com gnubber
HostName gnubber.bddebian.com
Port 2254
Host *.bddebian.com clubber flubber gnubber
CheckHostIP no
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
User [username]
|
