Well I might as well joing the uber-fun. I'd really like to post my screenshot of Bash running on my OS, but I lost it and it doesn't run atm (writing my ATA and EXT2 drivers is taking a while, and I decided to totally rewrite my entire syscall and IPC interface and as you know it takes a lot longer to rework an interface than a module...)
Right then here we go
Jimix after boot, running my super-mini shell. keys F1-F4 change tty from tty1-tty3,/dev/console. All of this is running in user mode by the way - four processes running: /init, /udev, /tty, /shell.
The boot sequence into tty mode is currently far too fast for me to screenshot so I stuck it in serial mode (default kernel output is directed to a serial port instead of the monitor) and put it in debug mode (There are three levels, debug, verbose and spam). Debug mode is essentially an strace.
OK, then we have JTED (Jimix test execution daemon), my automated testing software. It's still in development and can currently run automated builds and (just about) train tests interactively. It's what I use to exorcise (deliberate spelling) the evil web-dev in me!
Home page:
A listing of all the builds/tests in one 'batch run'. The 'auxiliary builds' are programs that tests may use but don't live in the source tree, such as memory consistency checkers or the all-important 'hello world' app.
Finally an in-depth view of a build, to show it actually does stuff
If you're wondering what the 'speaker' in shiny colours is there for - each batch is assigned not only an ID but a random word as well - helps with remembering which one's which. I learned that trick from my work
Sorry for spamming with images...