Rules of OSDev

From OSDev.wiki
Revision as of 00:55, 29 October 2021 by Sebastian (talk | contribs) (Add the most important rule of life and anything else)
Jump to navigation Jump to search
This page is a work of humor.
It is not meant to be serious.
  • Rule of osdev #1469: never assume memory is zero'd - moondeck
  • Rule of osdev #1468: never assume indices are sequential - mniip
  • Rule of osdev #1470: don't divide when you can shift - glauxosdever
  • Rule of osdev #fbf89521-21f1-4a52-b5cb-a0bf0f761bb4: probably avoid collisions with globally unique identifiers - sortie
  • Rule of osdev #1985: Never try to build a GUI ontop of your DOS - bellezzasolo
  • Rule of osdev #0xB8000: Don't do arithmetic on video pointers. - m712
  • Rule of osdev #0xdeadbeef: If you think something is done for you, its not. - moondeck
  • Rule of osdev #0xF00F: Don't trust Intel, always check that cr1 access causes #UD. - aristos
  • Rule of osdev #(uint32_t)&kernel_sbrk: Do not negative-kernel-sbrk past your implementation of kernel-sbrk - franchufranchu
  • Rule of osdev #0xC10000000: Do not put something big on BSS before your full kernel is mapped (#PF here we come) - nexos
  • Rule of osdev #1984: Always use the superior boot protocol Stivale, instead of your 32-bit mentally deranged Multiboot - sebastian.
  • Add your rules here - name
Retrieved from "https://osdev.wiki/wiki/Rules_of_OSDev?oldid=20003"