Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 11 and Version 12 of FAQ


Ignore:
Timestamp:
2014-12-18T19:07:15Z (5 years ago)
Author:
Martin Decky
Comment:

small fixes

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v11 v12  
    2121
    2222'''Q:''' '''Is it based on Linux? Is it UNIX-like?'''[[BR]]
    23 '''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 {{{fork()}}}.
     23'''A:''' No. HelenOS is based on original code, from the ground up. It is based on the original SPARTAN microkernel. 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 {{{fork()}}}.
    2424
    2525'''Q:''' '''What does it do, from an end-user's perspective?'''[[BR]]
     
    2727
    2828'''Q:''' '''What do you aim for with HelenOS?'''[[BR]]
    29 '''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.
     29'''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.
    3030
    3131'''Q:''' '''How is HelenOS development organized?'''[[BR]]
     
    3535'''A:''' HelenOS source code is managed with [http://bazaar.canonical.com/en/ 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.
    3636
    37 '''Q:''' '''How is HelenOS different from Unix?'''[[BR]]
     37'''Q:''' '''How is HelenOS different from UNIX?'''[[BR]]
    3838'''A:''' See our [wiki:DiffFromUnix page] which describes some design differences between HelenOS and Unix-like systems.
    3939
     
    4545
    4646'''Q:''' '''Why don't you work on ''insert your favorite OS project'' instead?'''[[BR]]
    47 '''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 {{{^_^}}}.
     47'''A:''' While HelenOS currently has some gaps in end-user 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 {{{^_^}}}.
    4848
    49 '''Q:''' '''After so many years of development, HelenOS still cannot do XYZ?'''[[BR]]
     49'''Q:''' '''After so many years of development, HelenOS still cannot do ''XYZ''?'''[[BR]]
    5050'''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.[[BR]]
    5151'''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.