fabiensiron/pyr0

Attempt to make a python based Operating System, it means that we use language feature to provide security instead of using hardware as in a classical operating system.

Python in ring 0 project (Pyr0)

Description

Pyr0 is an attempt to make a python based Operating System, it means that we use language feature to provide security instead of using hardware as in a classical operating system.

The project is composed of two different parts: the core (which is a classical kernel that manages memory, interrupts...) and the runtime (which manages tasks, user programs...).

Another great idea of this project, is to have a plain-text userland. Indeed, there is no binary in the root tree (except kernel :P), only python scripts.

Deps

• qemu (for emulation)
• libisoburn (for video)
• perl (for some scripts required by compilation)
• gcc/make (for compiling)

Build/Install

• ./configure
• make

Usage

For interpreter mode:

• make boot-i

For file mode:

• make boot

or if you want a specific python's script:

• make boot PYR0_ROM=path_to_python_script.py

Example: make boot PYR0_ROM=root/python/prime.py

Modules available:

Pyr0 stdlib

• math: very light math module (TODO)
• os: os information
• sh: shell builtins

Hardware information

• cpuinfo: cpu information
• smbios: various bios information
• pci: pci devices list

Debug

• mem: memory debug module

Misc

• morse: morse sound module (only on real hardware)

Real hardware:

To try on real hardware (with usb key or cdrom), just dd the iso:

• dd bs=4M if=pyr0s.iso of=/dev/your_device

Notes

There are quite a lot of bugs, but of course, if you find a bug, please just open an issue.

Community

IRC

To follow the project, discuss with us or contribute, please join us in #pyr0 on Rezosup (irc.rezosup.org).

pyr0's Issues

Custom bootloader

Write a custom bootloader for the project which must set-up the system before loading the core (video, 32 bits, command line ...).

Move compiler to C

The tinypy compiler is currently composed of 3 python's modules: tokenize.py, parser.py and encode.py.
The compiler is already boostrapped in bc.c under a array of tpc (tinypy bytecode).
If the compiler is moved in C, the speed is improved and the debugging is easier.
Plus, one can correct some grammar mistakes: empty file, one litteral...

Kernel threading

Add a simple kernel thread manager/scheduler.

VFS

A simple vfs have to be done. Basically, we need a read-only ext2 ramfs, a tmpfs, a devfs and maybe procfs.

Add boot test to travis

The goal is to avoid boot page-faulting.

Port pyr0 on ARM: Raspberry pi

I really want pyr0 to work on Raspberry (or same kind of stuff). The first step would be to divide the kernel into architecture dependant and non architecture dependant code. After that, let's port the kernel (memory, interrupts at less).

New memory manager.

Because of a bad utilization by tinypy and a not so good malloc implementation, we may want a better memory manager. Indeed, the current first fit has got a lot of fragmentation. Here are some ideas: replace the first fit by a buddy or do a classical memory manager with a vmm and a slab (http://sos.enix.org/wiki-fr/upload/SOSDownload/sos-texte-art5.pdf).

Pyr0 library

Rewrite the pyr0 library (include/ and lib/).
First step is to rewrite the code already written in a more homogeneous way.
Second step, is to add some functionalities (math, string etc...).
A "libc" or "pyro.lib" module can be written to test that.

EDIT: some data structures can be added. For example, list, hashtbl, ringbuff, refcnt ...