Pedigree Live Demo

[pcmattman]

Hello all,

I've set up a VM running Pedigree on a VPS that anyone can SSH into and play with. The system is set up with a watchdog timer, so if the system hangs or crashes, it will be automatically rebooted (and the kernel log will be preserved too, for post-portem investigation). No ISO to wait for an hour to download, no fiddling with emulator configuration, just a system already at your disposal.

Example:

Code: Select all

$ ssh -p 2222 [email protected]
Welcome to Pedigree.
This is Pedigree Unstable -- 0.1.3
Welcome to the Pedigree operating system.

Please don't feed the code monkeys - they bite.
[12:02:20] ~ $ make
gcc -O3 -o hello hello.c
[12:02:26] ~ $ ./hello
Hello, world!
[12:02:28] ~ $ make clean
rm -f hello
[12:02:31] ~ $ ls
Makefile  hello.c
[12:02:31] ~ $ ls ..
ssh  test
[12:02:38] ~ $ ls /
applications  boot  config  etc  include  keymaps  libraries  support  system  users
[12:02:39] ~ $ logout
Connection to build.pedigree-project.org closed.

So just point your favourite SSH client at build.pedigree-project.org, user 'ssh', port 2222, and give it a spin if you do so and find something broken, please reply in this thread, ideally with a transcript of what you did (and a timestamp+timezone ) to cause the issue.

Also, http://build.pedigree-project.org/livestatus hits a HTTP server running in Pedigree on the same VM, so if SSH isn't working right, check that the HTTP page renders properly. A HTTP 502 means the VM is down.

Note that currently http://pedigree-project.org is down; you can see the latest work at https://github.com/pcmattman/pedigree.

Happy testing!

[AndrewAPrice]

When I tried SSH'ing (authenticating as user 'ssh') I get:

Code: Select all

Welcome to Pedigree.
This is Pedigree Unstable -- 0.1.3

Then it disconnects. I'm using PuTTY on Windows 7.

On Linux, I can connect fine via SSH. Very cool.

I have a strange issue when I type. It echos back the first character (but doesn't seem to input it) and inputs the rest of the characters (without echo'ing it).

E.g. I can type:

5ls [enter]

and it prints:

"[14:59:25] ~ $ 5Makefile hello hello.c"

Anyway, just a minor issue. Great work!

EDIT: I tried reconnecting and now it works fine.

[Combuster]

Works from a linux client. Quite laggy though.

[bluemoon]

Code: Select all

$ ssh [email protected] -p 2222 -v
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/####/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: Connecting to build.pedigree-project.org [203.11.218.47] port 2222.
debug1: Connection established.
debug1: identity file /Users/####/.ssh/id_rsa type 1
debug1: identity file /Users/####/.ssh/id_rsa-cert type -1
debug1: identity file /Users/####/.ssh/id_dsa type -1
debug1: identity file /Users/####/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version dropbear_2013.58
debug1: no match: dropbear_2013.58
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA fd:dd:20:36:cd:85:8c:5d:1b:f6:14:eb:af:cd:1a:dc
debug1: Host '[build.pedigree-project.org]:2222' is known and matches the RSA host key.
debug1: Found key in /Users/####/.ssh/known_hosts:24
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
Welcome to Pedigree.
This is Pedigree Unstable -- 0.1.3
debug1: Authentication succeeded (none).
Authenticated to build.pedigree-project.org ([203.11.218.47]:2222).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Welcome to the Pedigree operating system.

Please don't feed the code monkeys - they bite.
[14:56:30] ~ $ ls
Makefile  hello.c
[14:56:36] ~ $ cat hello.c 
#include <stdio.h>

int main(int argc, char *argv[])
{
    printf("Hello, world!\n");
    return 0;
}

[14:56:40] ~ $ whoami
ssh
[14:56:49] ~ $ uname -a
Pedigree pedigree Foster 0.1 x86_64 Pedigree
[14:56:54] ~ $ make
gcc -O3 -o hello hello.c
[14:57:12] ~ $ time make
gcc -O3 -o hello hello.c
debug1: channel 0: free: client-session, nchannels 1
Connection to build.pedigree-project.org closed by remote host.
Connection to build.pedigree-project.org closed.
Transferred: sent 3784, received 3568 bytes, in 64.1 seconds
Bytes per second: sent 59.0, received 55.7
debug1: Exit status -1
$

Subsequent attemps

Code: Select all

Welcome to Pedigree.
This is Pedigree Unstable -- 0.1.3
debug1: Authentication succeeded (none).
Authenticated to build.pedigree-project.org ([203.11.218.47]:2222).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Write failed: Broken pipe

[Combuster]

Code: Select all

[14:58:18] ~ $ reboot
Connection to build.pedigree-project.org closed by remote host.

[sortie]

Glad to see your operating system is steadily improving.

Unfortunately, it still appears to be very unstable. In my latest try I couldn't even run ls without the shell eating the s and then complaining there was no l program.

[pcmattman]

Thanks for the testing!

Sortie - can I get a transcript of that happening, including the working directory? I can't immediately reproduce the behaviour.

bluemoon - it looks like the first disconnect was a watchdog action - I'll check the kernel log and I expect there'll be a fault. The reconnect seems to be around the same time Combuster rebooted the VM

MessiahAndrw - do you mean after a reconnect the shell worked as expected, or PuTTY worked and the weird shell behaviour remained?

BTW, shameless plug for #pedigree on Freenode IRC

[AndrewAPrice]

MessiahAndrw - do you mean after a reconnect the shell worked as expected, or PuTTY worked and the weird shell behaviour remained?

PuTTY on my Windows PC never held a connection, it always dropped off after printing two lines - I moved on to testing on Linux with 'ssh'. 2 out of the 3 times I ssh'd from Linux I had that weird shell behaviour (it echoed back but did not input my first character, then the rest of my characters were invisible) 1 time the shell worked as expected.

[Nable]

This command:

Code: Select all

ls -l /dev/

gives me ~reproducable ~scrambled output - some part of output misses \r characters, only \n.
I think that this problem has the same root as above described problems with character-eating shell (some kind of race condition in pipe/buffer implementation?).

Btw, 'chroot' binary is present but "Function not implemented", is this feature planned to be implemented in near future?

[thomasloven]

ls and make in ~ are killed by Segmentation fault
2014-06-26 CET 12:03

[pcmattman]

They should now work again (a minor regression that existed for a couple of days).

Thank you all for the reports - I have an interesting selection of bugs to work through!

The SSH server will continue to remain available.

[sortie]

The

Code: Select all

#!/bin/sh -

line in bashbug seems to not work, perhaps due to the -. I tried to edit it with vim over ssh, but that was an awful and buggy experience and I gave up.