<commit_before># arm-rust-clust
A bare-metal operating system for a cluster of small ARM boards, like the Raspberry Pi or CHIP.

## Goal
This is an etude in Rust and operating system development, with a focus on a single address 
space (SASOS) approach. I would like to put a statically-typed lisp as the OS's second 
language after Rust.

## How to begin
Start with the makefile.

## What is good (so far)
1. It think the test setup is good. Unit tests are run on the host. Rust integration tests are run under QEMU.
1. The arch abstraction is good, which helps the policy abstraction.
1. The use of Rust is more complete than most. We start the processor in Rust, and really only need global_asm
for exception handler entry.
1. Documentation and test coverage are significantly improved in this second try.

## What could improve
1. Reducing unsafe code even further, and justifying the necessary use of unsafe.
1. Would be good to build the x86 kernel in tandem, but I have avoided xbuild for arm, so I'll wait.
1. I am not sure enough of traits, monomorphisation and statics to be confident in module interfaces.

## Influences and thanks
* [<NAME>](http://jvns.ca/blog/2014/03/21/my-rust-os-will-never-be-finished/)
* [<NAME>](https://skillsmatter.com/skillscasts/4484-build-your-own-lisp-for-great-justice)
* [<NAME>](http://os.phil-opp.com/) Rust and great, but x86-centric
* [<NAME>](http://interim-os.com/) We follow in his footsteps!
* [<NAME>](https://github.com/dpc/titanos) And Dawid's too!
* [<NAME>](https://github.com/rust-embedded/rust-raspi3-tutorial) And cortex-a crate.
* [rCoreOS](https://github.com/rcore-os/rCore) Multi-arch
* [<NAME>](https://lowenware.com/leos/) <commit_msg>Updating what I like about my solution.<commit_after># arm-rust-clust
A bare-metal operating system for a cluster of small ARM boards, like the Raspberry Pi or CHIP.

## Goal
This is an etude in Rust and operating system development, with a focus on a single address 
space (SASOS) approach. I would like to put a statically-typed lisp as the OS's second 
language after Rust.

## How to begin
Start with the makefile.

## What is good (so far)
1. It think the test setup is good. Unit tests are run on the host. Rust integration tests are run under QEMU.
1. The arch abstraction is good, which helps the policy abstraction.
1. The use of Rust is more complete than most. We start the processor in Rust, and really only need global_asm
for exception handler entry.
1. Documentation and test coverage are significantly improved in this second try.
1. My implementation of map_translation handles blocks and contiguous ranges.

## What could improve
1. Reducing unsafe code even further, and justifying the necessary use of unsafe.
1. Would be good to build the x86 kernel in tandem, but I have avoided xbuild for arm, so I'll wait.
1. I am not sure enough of traits, monomorphisation and statics to be confident in module interfaces.

## Influences and thanks
* [<NAME>](http://jvns.ca/blog/2014/03/21/my-rust-os-will-never-be-finished/)
* [<NAME>](https://skillsmatter.com/skillscasts/4484-build-your-own-lisp-for-great-justice)
* [<NAME>](http://os.phil-opp.com/) Rust and great, but x86-centric
* [<NAME>](http://interim-os.com/) We follow in his footsteps!
* [<NAME>](https://github.com/dpc/titanos) And Dawid's too!
* [<NAME>](https://github.com/rust-embedded/rust-raspi3-tutorial) And cortex-a crate.
* [rCoreOS](https://github.com/rcore-os/rCore) Multi-arch
* [<NAME>](https://lowenware.com/leos/) 
{'fraction_non_alphanumeric': 0.10644977168949772, 'fraction_numerical': 0.013984018264840182, 'mean_word_length': 4.154411764705882, 'pattern_counts': {'":': 0, '<': 17, '<?xml version=': 0, '>': 17, 'https://': 10, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4343174', 'n_tokens_mistral': 1140, 'n_tokens_neox': 1057, 'n_words': 454}