|Version 10 (modified by 9 years ago) ( diff ),|
Frequently Asked Questions
Q: What is HelenOS?
A: HelenOS is an open-source microkernel-based multiserver operating system written from scratch. It runs on several different CPU architectures (IA-32, x86-64, SPARC V9, IA-64, PowerPC, ARM, MIPS). HelenOS prides in portability, modularity, clean design and coding style.
Q: What is SPARTAN?
A: SPARTAN started as a small kernel written by Jakub Jermář for his university assignments. Later it was open-sourced and adopted as the kernel of the HelenOS operating system. Now we either call it just the kernel or SPARTAN. The SPARTAN kernel gives HelenOS a very solid and well-developed base to build on. It supports multi-tasking, virtual memory and symmetric multi-processing. It also implements the HelenOS IPC, upon which HelenOS userspace services are built.
Q: What is HelenOS used for?
A: Some people fiddle with HelenOS simply as a hobby. HelenOS is also used as a platform for school assignments for the Operating Systems course at the Faculty of Mathematics and Physics, Charles University, Prague, as well as for the students' bachelor and master theses.
At this point we don't consider HelenOS usable for something different than development and research, but we're getting very close to the point where it will be.
Q: What license is HelenOS released under?
A: All original HelenOS code is covered by a BSD-like license. Some specific third-party components are covered by the GPLv2.
Q: Is it based on Linux? Is it UNIX-like?
A: HelenOS is based on original code, from the ground up. It is based on the original SPARTAN micro-kernel. It does not mimic any existing system and it is not meant to be POSIX-compliant or UNIX-like at all. Just as an example, HelenOS does not support
Q: What does it do, from an end-user's perspective?
A: We have a command line which allows you to manipulate files, run applications and mount file systems from disks and disk images. You can play Tetris or edit text files. HelenOS supports multi-national text throughout thanks to using UCS (i.e. Unicode).
Q: What do you aim for with HelenOS?
A: Mainly two things. One is to create a fully usable operating system. (I.e. a system that could be used for at least some everyday task such as router, server, PDA or desktop). The other is to have fun.
Q: How is HelenOS development organized?
A: HelenOS development is community-driven. The primary communication medium for developers is our mailing list. Since most developers are currently based in Prague (or vicinity), we hold developer meetings in Prague once every month. Minutes are usually published on the mailing list.
Q: Where is HelenOS source code kept?
A: HelenOS source code is managed with Bazaar VCS. We have a central repository which is considered as the most current code base. Several developers also have their private development branches which are publicly viewable.
Q: How is HelenOS different from Unix?
A: See our page which describes some design differences between HelenOS and Unix-like systems.
Q: Oh, yet another operating system?
A: No, not at all. There are definitely many more various content management systems, office suites or web browsers out there than there are microkernel-based multiserver operating systems like HelenOS.
Q: Why don't you work on insert your favorite OS project instead?
A: While HelenOS currently has some gaps in user-space functionality (such as system tools and applications), from many points of view we consider it more advanced than any comparable project. Microkernel is just a label and there are as many ways to write a microkernel system as there are many ways to write an operating system. HelenOS pursues many interesting ideas not found in other projects. HelenOS is portable, clean and modular. And last, but not least, writing HelenOS is fun
Q: After so many years of development, HelenOS still cannot do XYZ?
A: We are developing a new operating system from scratch as compared to a mere cloning an existing system with an established API. This forces us to figure out and design everything ourselves, which takes time.
A: The HelenOS development process can be characterized as breadth-first rather than depth-first. Breadth-first here denotes the fact that we are writing code which runs on half-dozen processor architectures and is highly multiplatform and portable. This is in strong contrast with the depth-first development model, in which a project quickly gains a lot of desktop features on only one architecture (typically x86) but its poor design prevents it from being ported to more platforms.
Q: Why don't you use Clang as your primary compiler?
A: Well, we strive to support Clang as an alternative compiler for some architectures, but the thing is that Clang does not currently support all CPU architectures that HelenOS supports, so we must use GCC to build HelenOS.