mercury
/
book
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Activity

Minor additions

main
~erin 2023-04-18 23:52:16 -04:00
parent 064988574a
commit 4cce6065b0
Signed by untrusted user: erin
GPG Key ID: 9A8E308CEFA37A47
2 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/development/design/README.md
View File

@ -37,8 +37,9 @@ All of the code will take place in seperate repositories.
Information on actually commiting, pulling, etc. is in the [Workflow](/development/workflow.md) chapter. Information on actually commiting, pulling, etc. is in the [Workflow](/development/workflow.md) chapter.
Most of the code will be implemented as libraries, enabling for them to be used across systems, and worked on separately. Most of the code will be implemented as libraries, enabling for them to be used across systems, and worked on separately.
Similarly drivers will be libraries in `git submodules`.
- [ferrite](https://git.lavender.software/mercury/ferrite-kernel) - The core microkernel code - [ferrite](https://git.lavender.software/mercury/ferrite-kernel) - The core microkernel code w/ bootloader
- [hermes]() - The package manager - [hermes]() - The package manager
- [meteor]() - The [actors](/development/design/actor.md) library/implementation - [meteor]() - The [actors](/development/design/actor.md) library/implementation
- [gravitas]() - The library for working with [storage](/development/design/filesystem.md) - [gravitas]() - The library for working with [storage](/development/design/filesystem.md)
@ -49,7 +50,7 @@ Most of the code will be implemented as libraries, enabling for them to be used
### Connections ### Connections
```mermaid ```mermaid
erDiagram erDiagram
ASM ||--|| KERNEL: runs BOOTLOADER ||--|| KERNEL: runs
KERNEL ||..o{ GRAVITAS: uses KERNEL ||..o{ GRAVITAS: uses
KERNEL }|..o{ METEOR: uses KERNEL }|..o{ METEOR: uses
GRAVITAS }|..o{ HAL: uses GRAVITAS }|..o{ HAL: uses
@ -63,7 +64,7 @@ erDiagram
### Startup Flow ### Startup Flow
```mermaid ```mermaid
flowchart TD flowchart TD
ASM --> kern(Kernel) [[Bootloader]] --> kern(Kernel)
kern --> disk(Read Disk) --> kern --> disk(Read Disk) -->
parse(Parse Configuration) --> run(Run Startup Programs) parse(Parse Configuration) --> run(Run Startup Programs)
parse -.-> sh([Interactive Shell]) parse -.-> sh([Interactive Shell])

2
src/development/design/filesystem.md
View File

@ -39,7 +39,7 @@ If the saved data exceeds past a single chunk, the `extends` flag is set.
Additionally, it has a **UUID** generated via [lolid](https://lib.rs/crates/lolid) to enable identifying a specific chunk. Additionally, it has a **UUID** generated via [lolid](https://lib.rs/crates/lolid) to enable identifying a specific chunk.
```rust ```rust
const CHUNK_SIZE: u16; // Example static chunk size const CHUNK_SIZE: u64; // Example static chunk size
struct Chunk { struct Chunk {
checksum: u64, checksum: u64,