Aesthetically screen shots would be really ugly. It's nothing but a terminal box, that can support up to 3 different terminals.
Even giving you a runnable copy would be a pain in the ass, since we used virtual emulators (QEMU) to debug, test, develop, and run because of the constant bugs where we crash our kernel.
We implemented pretty much everything - loading up the GDT, the IDT, Paging, Syscalls, keyboard driver, multiple terminals, RTC driver, PIT driver, PIC driver, file system, and round-robin scheduling.
A lot of things you take for granted is so complex - by far the hardest thing to do was to do our execute and halt to run a program. So many godamn context switches, pcbs, kesps, aaarrgh. We implemented in C and x86.
more like "unless you like text output, I don't imagine an OS made for a class would be very fun to look at".
It depends solely on what you define funny:
My OS class actually HAS and OS for itself. Ported by the professor for it's own processor.
We got the source and had to see how it worked ~ totally awesome.
OS the most difficult?
I beg to differ:
It could be the most complex one for sure because there is a bit of everything.
Every 4 students in our class has their own OS, that they personally built from scratch. Systems OS programming is by far the hardest class I've taken, and is probably the hardest I'll take in my undergrad career. I do have to make my own processor in another class, but it's a lot easier conceptually IMO.
Also, lolz CS. ECE get on my level.