Commit 32437cc4 authored by Glen De Cauwsemaecker's avatar Glen De Cauwsemaecker Committed by Jeremy Soller
Browse files

fix some mistakes I encountered while reading (#64)

parent 60257b2a
......@@ -8,7 +8,7 @@
* The commit hash of the code you used
* `git rev-parse HEAD`
* The environment you are running Redox in (the "target")
* `qemu-i386 -version` or your actual hardware specs, if applicable
* `qemu-system-x86_64 -version` or your actual hardware specs, if applicable
* The operating system you used to build Redox
* `uname -a` or an alternative format
4. Make sure that your bug doesn't already have an issue on Github. If you submit a duplicate, you should accept that you may be ridiculed for it, though you'll still be helped. Feel free to ask in the Redox [chat](./contributing/communication/chat.html) if you're uncertain as to whether your issue is new
......
......@@ -15,7 +15,7 @@ The steps given below are for the main Redox project - submodules and other proj
5. Alternatively, if you already have a fork and copy of the repo, you can simply check to make sure you're up-to-date
* Fetch the upstream:`git fetch upstream master`
* Rebase with local commits:`git rebase upstream/master`
* Update the submodules:`git submodule update --init`
* Update the submodules:`git submodule update --recursive --init`
6. Optionally create a separate branch (recommended if you're making multiple changes simultaneously) (`git checkout -b my-branch`)
7. Make changes
8. Commit (`git add . --all; git commit -m "my commit"`)
......
Microkernels
============
Redox's kernel is a microkernel. Microkernels stands out in their design by providing minimal abstractions in kernel-space. Microkernels have an emphasis on user space, unlike Monolithic kernels which have an emphasis on kernel space.
Redox's kernel is a microkernel. Microkernels stand out in their design by providing minimal abstractions in kernel-space. Microkernels have an emphasis on user space, unlike Monolithic kernels which have an emphasis on kernel space.
The basic philosophy of microkernels is that any component which *can* run in user space *should* run in user space. Kernel-space should only be utilized for the most essential components (e.g., system calls, process separation, resource management, IPC, thread management, etc).
......@@ -25,7 +25,7 @@ The above illustration ([from Wikimedia], by Wooptoo, License: Public domain) sh
A note on the current state
---------------------------
Redox has ~16,000 lines of kernel code. For comparison the Minix has ~6,000 lines of kernel code.
Redox has less then 9,000 lines of kernel code. For comparison Minix has ~6,000 lines of kernel code.
We would like to move parts of Redox to user space to get an even smaller kernel.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment