this-month 22/03: personal projects from phip1611 (#93)

* this-month 22/03: personal projects from phip1611

* this-month 22/03: linux-libc-auxv added

* wording

Author: phip1611

content/this-month/2022-03/index.md

@@ -114,6 +114,48 @@ In this section, we describe updates to Rust OS projects that are not directly r
 
 This month, ...
 
+### [`phip1611/simple-chunk-allocator`](https://github.com/phip1611/simple-chunk-allocator)
+
+<span class="gray">(Section written by [@phip1611](https://github.com/phip1611))</span>
+
+Philipp Schuster recently released an initial version of his [simple-chunk-allocator](https://github.com/phip1611/simple-chunk-allocator)
+crate. It focuses on being a very simple-to-use general purpose allocator that "just works" for various workloads 
+in `no_std` context. A bitmap is used for bookkeeping of used blocks/chunks. This enables a simple algorithm that is easy
+to understand. The allocator uses a combination of the strategies "next fit" and "best fit". It is usable as `#[global_allocator]` 
+and operates on static memory, i.e., no paging mechanism involved. The crate is suited to manage the heap inside a kernel 
+or in a similar `no_std` application. It is part of the roottask in [Philipp's Diplom (Master) Thesis](https://github.com/phip1611/diplomarbeit-impl) 
+where he wrote a runtime system for a Microkernel in Rust.
+
+
+### [`phip1611/linux-libc-auxv`](https://github.com/phip1611/linux-libc-auxv)
+
+<span class="gray">(Section written by [@phip1611](https://github.com/phip1611))</span>
+
+Philipp Schuster recently released an initial version of his [linux-libc-auxv](https://github.com/phip1611/linux-libc-auxv)
+crate. The crate enables the creation and the parsing of the initial Linux stack layout. This layout is a 
+special data structure that Linux prepares for applications before they start execution. The C runtime behind the 
+`_start` symbol of a libc implementation uses this to find program arguments, environment variables, and the 
+auxiliary vector. The layout is tricky to create because the creator must ensure that the layout is valid in the 
+address space of the target. However, `linux-libc-auxv` found a way to cope with this.  
+
+You can write a "freestanding" binary, i.e., without libc, with this crate, run it under Linux and parse the stack 
+layout yourself. This is similar to what the libc does, before Rust's runtime starts, that eventually calls the 
+main function of a Rust program.
+
+The crate is part of [Philipp's Diplom (Master) Thesis](https://github.com/phip1611/diplomarbeit-impl)
+where he wrote a runtime system for a Microkernel in Rust that can emulate Linux behaviour and run unmodified 
+Linux applications.
+
+### [`phip1611/diplomarbeit-impl`](https://github.com/phip1611/diplomarbeit-impl)
+
+<span class="gray">(Section written by [@phip1611](https://github.com/phip1611))</span>
+
+Philipp Schuster submitted his Diplom (Master) Thesis at TU Dresden where he build a policy-free system-call layer for 
+the Hedron microhypervisor. The project comes with a runtime system written in Rust for the microkernel and involves 
+a roottask that enables the execution of unmodified Linux binaries through an OS personality/Linux emulation. The 
+runtime system covers several interesting aspects of OS development, such as interaction with a kernel, system call
+emulation, and starting programs from ELF files.
+
 ## Join Us?
 
 Are you interested in Rust-based operating system development? Our `rust-osdev` organization is always open to new members and new projects. Just let us know if you want to join! A good way for getting in touch is our [gitter channel](https://gitter.im/rust-osdev/Lobby).