Anonymous user
What Order Should I Make Things In?: Difference between revisions
no edit summary
| [unchecked revision] | [unchecked revision] |
No edit summary |
No edit summary |
||
| (38 intermediate revisions by 12 users not shown) | |||
Line 2:
== For the starter ==
# Printing strings and integer numbers (both decimal and hex) on the screen is certainly a must. This is one of most basic ways of debugging, and virtually all of us have gone through a kprint() or kout in version 0.01.
# Outputting to a serial port will save you a lot of debugging time. You don't have to fear losing information due to scrolling. You will be able to test your OS from a console, filter interesting debug messages, and automatize some tests.
# Having a working and reliable interrupt/exception handling system that can dump the contents of the registers (and perhaps the address of the fault) will be very useful.
# Plan your memory map (virtual, and physical) : decide where you want the data to be
# The heap: allocating memory at runtime ('''malloc''' and '''free''') is almost impossible to go without. It should be implemented as soon as possible.
Line 11 ⟶ 14:
== Style Extremes ==
OSDev seems to have "archetypes" among the
=== Lino Commando ===
Line 19 ⟶ 22:
=== Nick Stacky ===
{{main|Nick Stacky}}
His test-machine has no keyboard and no screen (no one needs that). All he needs is NICs (Network Interface Cards)
=== James T. Klik ===
Line 32 ⟶ 35:
{{main|Alta Lang}}
Why would anyone want to write something as complex as an operating system in something as clunky and old as C? Alta wants something different for her system: a new language for a more elegant operating system. She spends at least as much time on language design as on system design, in the hopes that if she can design the language to be clean enough and powerful enough, the system will simply fall into place.
=== Stan Dard ===
{{main|Stan Dard}}
Stan knows how things should be. It's all nicely written down in standards. He sees how they fit together to form a beautiful system, well, if you disregard all the parts where the standard is stupid. He has a reasonably complete implementation of the areas he knows about and not-terribly-impressive code for the areas he is unskilled in.
=== Richard Theseus ===
{{main|Richard Theseus}}
Richard likes his current OS very much, except for one thing: it's not written by him. Bit by bit, he wants to replace the parts of his current OS with his own code. His ultimate aim is to have an identical copy of his host OS, but with his code.
=== Mister Perfect ===
{{main|Mister Perfect}}
Mister Perfect wants to write a perfect operating system, as he looks at all the flaws current operating systems have. He researches many design and implementation possibilities in order to decide what is better. He starts over multiple times in order to assure quality and perfectness.
=== Andy Microbaum ===
{{main|Andy Microbaum}}
Andy is a fan of small kernels who put much stuff done in a monolithic kernel into userspace.
=== Dizz Tracked ===
{{main|Dizz Tracked}}
Dizz gets distracted by unneccessary side projects.
=== Mono Lizzy ===
{{main|Mono Lizzy}}
Lizzy likes to put everything into one big kernel.
=== Ideas for new Archetypes ===
* '''Duct von Tape''' - Someone that reuses a lot of code and combines it into a horrible frankenstein of a project.▼
* '''Edward Scissorhands''' - Sounds like something designed on paper to do everything but completely broken in practice, I see architecture astronauts rather doing vaporware (e.g. you'd never get to see the Scissorhanded implementation the architecture would require)
* '''Real Man''' - Writes an entire operating system in
* '''Vizier Studio''' - Visual Studio people.
* '''Barry Pi''' - ARM people.
* '''Racing Carl''' - Does all in protected mode Assembler and rewrites the latest 3D library and tries to squeeze the last bit of speed out of the code.
=== Archetypes to avoid ===
* '''[[Cowboy Coder]]''' - Someone who eagerly jumps into coding without any plan.
* '''[[Dae Dreamer]]'''- Someone who spends all their time day dreaming and reading about operating systems, but hasn't yet started one.
▲* '''[[Duct von Tape]]''' - Someone that reuses a lot of code and combines it into a horrible frankenstein of a project. Or perhaps [[:Category:Lovecraftian|lovecraftian]]?
* '''[[Sir Dunning-Kruger]]''' - Someone overestimating his/her skills dramatically.
[[Category:OS Development]]
[[Category:FAQ]]
| |||