Skip to content

Commit

Permalink
[MISC] Update some docs
Browse files Browse the repository at this point in the history
  • Loading branch information
PeyTy committed Apr 29, 2024
1 parent 2fc8e91 commit af70179
Show file tree
Hide file tree
Showing 6 changed files with 14 additions and 16 deletions.
2 changes: 1 addition & 1 deletion Developer-Guide/CI.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Almost every change is built and tested. Thus, it makes it possible to have an e

#### When does the build take place?

* When a developer makes changes to the GreenteaOS/Kernel repository
* When a developer makes changes to the GreenteaOS/Tofita repository
* When the contributor sends a request to merge changes (Pull Request)
* When the contributor makes commits to his pull request

Expand Down
16 changes: 7 additions & 9 deletions Developer-Guide/Roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,26 +5,24 @@ The main idea of the project is to quickly and efficiently create a compatible e
### Planned features and improvements

* CPU
* [x] BIOS boot
* [x] UEFI boot
* [x] [x86-64-only mode (**dropping x86-32**)](x64.md)
* [ ] Multicore HAL and scheduler
* [x] UEFI boot
* [x] USB boot fixes
* GPU
* [ ] [Software Vulkan](../User-Guide/Vulkan.md)
* [ ] Hardware Vulkan
* [ ] OpenGL
* [ ] D3D
* Kernel
* [x] [New kernel in Hexa](../User-Guide/Hexa.md)
* Engine
* [x] [New one in Hexa](../User-Guide/Hexa.md)
* [x] Stable memory manager
* [ ] GUI for OS installer
* [ ] [Moving to a journaling filesystem](../User-Guide/Greentea-FS.md)
* [x] LiveCD/USB
* [ ] Stable networking
* [x] Initial .exe support
* [ ] Full .exe support
* [ ] Linux subsystem (only software)
* [ ] Unix subsystem (only software)
* [ ] Android subsystem
* [ ] [Easy system updates](../User-Guide/Rolling.md)
* Visuals
Expand Down Expand Up @@ -53,16 +51,16 @@ Features, like ARM support, aren't really useful in any real manner *right now*,
Features, like LPT printing, has so small applicability (LPT ports in 2018 anyone?),
so can't be considered in any manner real target for Greentea OS team and use case for our users.
Also, multiply that by a *enormous* number of bugs, hacks and workarounds, which we should fix now,
to at least make kernel non-academic project! And then improve implementations, **the real things**.
to at least make non-academic project! And then improve implementations, **the real things**.
Otherwise it is a waste of time.

---

### Feature timings

Features are highly dependent of Kernel API version.
Features are highly dependent of the API version.
Also, the ecosystem defines it's own distribution rules.
For example: while it *is* possible to run Vulkan API over virtually any (even 20 years old) operating system,
no hardware or middleware (LunarG) distributors actually did it.
Some features also, like native Wi-Fi or BLE support, were non-existent on old versions.
So we need to declare timings and dependencies for each feature.
So we need to declare timings and dependencies per feature.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Some releases may be provided in the [Greentea LOAD](https://t.me/greenteaos_off

Visit out [Issues](https://github.com/GreenteaOS/Greentea/issues) section to dive into development process! You are free to read and share anything important (well, actually bugs), but talking in chat rooms is in prefer.

## Kernel
## Internals

System's source code is hosted inside [Tofita](https://github.com/GreenteaOS/Tofita) repository. Feel free to make pull requests!

Expand Down
6 changes: 3 additions & 3 deletions User-Guide/Frequently-Asked-Questions.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,12 +17,12 @@ Nope. Greentea is funded solely by [donations](https://greenteaos.github.io/dona

#### Is Greentea OS a GNU/Linux distro?

No. It is an independent OS, without Linux kernel.
No. It is an independent OS, and isn't based on top of Linux.

#### What makes Greentea OS so unique?

***From developer perspective:*** safety-first OS, aimed at strict isolation and code verification.
To achieve those goals, we created new kernel for it — Tofita, and programming language - Hexa.
To achieve those goals, we created new engine for it — Tofita, and programming language - Hexa.

***From user perspective:*** apps cannot break the system or make it slow. System updates are fast and not annoying.

Expand All @@ -35,7 +35,7 @@ Visit [our Telegram news channel](https://t.me/s/greenteaos_news) and check [com

#### What is Tofita?

[Tofita](https://github.com/GreenteaOS/Tofita) is *the* Greentea OS kernel, the core, the heart of the system.
[Tofita](https://github.com/GreenteaOS/Tofita) is *the* Greentea OS engine, the core, the heart of the system.

#### Where I may download it?

Expand Down
2 changes: 1 addition & 1 deletion User-Guide/Protection.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
## Built-in protection mechanisms (antivirus, stability, isolation and snapshots)

Independent isolated copies of software allows user to safely run apps with more limited privileges, compared to classic "everything but kernel stuff" concept. Removable devices are not touched until explicit user permission granted.
Independent isolated copies of software allows user to safely run apps with more limited privileges, compared to classic approaches. Removable devices are not touched until explicit user permission granted.

[Rolling release](Rolling.md) model ensures that core files are kept untouched and are impossible to infect.
2 changes: 1 addition & 1 deletion User-Guide/Rolling.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
## Monolithic rolling-release updates of the system

Basic idea is to download a single system image via p2p-sharing (and do integrity checks, of course) and place it packed to the system partition as-is. Images a kept unchanged, and unpacked on-demand into RAM. They should contain kernel, common drivers and built-in apps.
Basic idea is to download a single system image via p2p-sharing (and do integrity checks, of course) and place it packed to the system partition as-is. Images a kept unchanged, and unpacked on-demand into RAM. They should contain internal components, libraries, common drivers and built-in apps.

This will gave nearly instantaneous updates with improved system resilience.

0 comments on commit af70179

Please sign in to comment.