README 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142
  1. ********************************************************************************
  2. __ ___ ___ __ __ _
  3. / |/ /___ ____ ____ / (_) /_/ /_ (_)_ ______ ___
  4. / /|_/ / __ \/ __ \/ __ \/ / / __/ __ \/ / / / / __ `__ \
  5. / / / / /_/ / / / / /_/ / / / /_/ / / / / /_/ / / / / / /
  6. /_/ /_/\____/_/ /_/\____/_/_/\__/_/ /_/_/\__,_/_/ /_/ /_/
  7. ********************************************************************************
  8. Monolithium is a 32-bit operating system for x86 PCs. It is not a Unix-like
  9. system, and shares almost nothing with the Unix architecture. Written
  10. completely from scratch, it is completely incompatible with other operating
  11. systems. Currently, only the Monolithium kernel is implemented. The other major
  12. components, the "system library" and "system manager", are still missing.
  13. Monolithium wasn't implemented according to any existing design, it was more or
  14. less designed as it was implemented, so the current interface may not be
  15. consistent. During this phase of its development, its kernel module interface
  16. and application programming interface are not stable and subject to major
  17. changes.
  18. FREQUENTLY ASKED QUESTIONS
  19. 1) Why write another OS from scratch?
  20. Most software development today is focused on assembling software from existing
  21. "building blocks", using libraries and high-level programming languages, which
  22. are designed to be complex and generic because they need to cover a lot of use
  23. cases. Simplicity is a very useful trait that is often overlooked. Monolithium
  24. is one of the few operating system projects with simplicity as its primary goal.
  25. 2) Why is there no development history?
  26. I started this project in 2011, before I understood how VCS systems work and why
  27. they're important. I made backups at regular intervals, but since I didn't use
  28. git, there are no commits before the first release.
  29. 3) Will the interface ever become stable?
  30. Having a stable interface, which will not change to the extent that later
  31. versions break software running in userspace, is one of the end goals of
  32. the project.