1 A minimal UNIX kernel project for x86 PCs

2 -----------------------------------------

3 Author: John Tsiombikas <nuclear@member.fsf.org>

4

5 License: GNU GPL v3 or any later version published by the free software

6 foundation. See COPYING for details.

7

8 About

9 -----

10 When the editor of the Linux Inside magazine asked me to write for his newborn

11 magazine, I leapt at the chance to start a series of introductory articles on

12 kernel programming.

13 For this reason I started writing a minimal, UNIX-like, operating system kernel

14 from scratch. It's not complete yet, but it already has user/kernel protection

15 levels, a virtual memory system with copy-on-write, processes, task switching,

16 etc.

17

18 The articles themselves (only in Greek at the moment unfortunately) can be found

19 at: http://nuclear.mutantstargoat.com/articles/kerneldev/index.html

20

21

22 Compiling & Running

23 -------------------

24 To compile kernel image (kernel.elf) just type make (or gmake, if your default

25 make tool is not GNU make). A script called "run" is supplied that will use qemu

26 to run the kernel in a virtual machine.

27

28 If you wish to boot up the kernel on your computer you need a multiboot

29 compliant boot loader like GRUB. Since you probably already have GRUB installed

30 if you're running a GNU/Linux distribution, just add an entry to the GRUB config

31 file (commonly /boot/grub/menu.lst) similar to this one and reboot:

32

33 title My kernel

34 root (hdX,Y) # where X is the disk number and Y the partition (first being 0)

35 kernel /path/to/kernel_code/kernel.elf # change this to the actual path

36

37 In case you are using GRUB 2 instead of the original GRUB, you'll have to

38 consult the documentation on how to modify the above into the GRUB 2 syntax.

39

40 Disclaimer

41 ----------

42 All programs contain bugs, and this sample code will undoubtedly have its share.

43 Running buggy kernel code on the real machine is very dangerous and may result

44 in data loss or even damage to your computer in extreme cases. The author

45 assumes no responsibility for any such eventuality. Run this code on your

46 computer at your own risk.

47

48 Contact

49 -------

50 For any comments or suggestions regarding the articles or this supplemental

51 code, please contact me at nuclear@member.fsf.org