Skip to main content

Pondering Operating Systems

For a long time, my goal has been to develop a higher-level, natively-compiled programming language, and then to develop a proof-of-concept kernel in it. Well, someone else beat me to the punch.

House is a proof of concept operating system written in Haskell. It has some simple graphics, a TCP/IP stack, etc. Naturally, it's just a research project, but achieving proof of concept was my goal too.

On that subject, I'm also keeping my eye on Microsoft's Singularity. It's a microkernel, and much of it is written in C#. Unlike most microkernels, the different components do not run in separate address spaces. The VM does protection in software, rather than hardware. I had been toying with this idea too, but my buddy Mike Cheponis informed me that VM/360 did it decades ago.

Is anyone other than me bummed that BeOS never took off? I'm sadly coming to the conclusion that Linux might not ever make it on the desktop. It's just not a priority. Too many great hackers use Linux on the server with Mac laptops. There's always hope that Haiku might recreate BeOS in a completely open source way, but it would have been a lot easier if Be had simply open sourced it in the first place.

In the meantime, SkyOS thinks that there is room for another easy-to-use, featureful, proprietary OS. Apple succeeded at this. BeOS failed. It's hard for me to get excited about a new proprietary OS. I'd sooner buy a Mac (although I still haven't been fully de-Stallmanized).

Speaking of which, has anyone else noticed how few non-UNIXy, open-source operating systems there are? Maybe it's true that Systems Software Research is Irrelevant.

Well, now that House has shown that you can write a kernel in Haskell, I think I need a new goal. Maybe I'll go solve world hunger. I've heard there's a little squabble going on in the Middle East that could use some attention. Maybe I'll go write an entire operating system in modern assembly; oh wait, it's already been done ;)


Noah Gift said…
Sounds like you need a way to find out how to be a part time scientist. I think you would be a good one.

I agree an OS in some other language than C would be very cool.

On the OS X front, I would recommend just doing it. When it is all said and done, the OS X desktop is just amazing. Leopard looks to be amazing as well, but I can't comment on whether it really is or not due to a NDA.

With the coming world of Virtualization, it becomes almost a moot point that linux can do X,Y,Z and Microsoft only runs the programs: A, B, C. VM Fusion is a great application and allows you to run a shell to any OS you want! Now you have the most productive UI in the world, and a shell to an almost limitless amount Operating Systems.

On the Virtualization front, the IBM AIX OS is quite an interesting beast. It has incredible virtualization technology that is allowing the world to head back into the realm of mainframes. There was just an article last week about it:
jjinux said…
Hey Noah,

Thanks for your comment. Something's wrong with that article. "139 football fields" worth of servers to service "350,000 users"? Must have been a typo ;)
jjinux said…
> I can't comment on whether it really is or not due to a NDA.

hahaha That's exactly the sort of stuff that keeps me running Linux! Not to mention, that I'm running it on a brand new $375 Compaq laptop ;)
Adam Ulvi said…
The article on systems research being irrelevant was quite disheartening, especially because in the 7 years since it was written, it's only become more and more true.

The computer industry continues moving away from public or university-funded R&D and keeping it all in-house under lock and key. Standards are ignored either to ensure vendor lock-in or because standards organizations take longer to make up their minds than commercial software feels like waiting. Tight, cohesive systems integration is still a dream, even getting something "industry standard" like Kerberos working is a big PITA. Why don't we have true working single sign-on, it shouldn't be that hard!

Personally, I'm fed up with closed-source software. Sorry to rant on your blog :-)
The L4 implementations Fiasco and Pistacio are GPL-licensed. And their certainly not purely research kernels. So don't trust Wikipedia too much.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p