diff options
| author | namilsk <namilsk@namilsk.tech> | 2026-01-10 16:17:21 +0300 |
|---|---|---|
| committer | namilsk <namilsk@namilsk.tech> | 2026-01-10 16:17:21 +0300 |
| commit | d114acb6103706e56f7d2090569c354987033d7e (patch) | |
| tree | 903840d0fa893370a33bddb0abf4cbe678d08f57 | |
| parent | 620e092c927d04d454c2efd94b7beaf448133531 (diff) | |
Fixed parts naming
| -rw-r--r-- | Cargo.toml | 2 | ||||
| -rw-r--r-- | README.md | 8 | ||||
| -rw-r--r-- | vigilctl/Cargo.toml (renamed from vegilctl/Cargo.toml) | 0 | ||||
| -rw-r--r-- | vigilctl/src/args_dispatcher.rs (renamed from vegilctl/src/args_dispatcher.rs) | 0 | ||||
| -rw-r--r-- | vigilctl/src/main.rs (renamed from vegilctl/src/main.rs) | 0 |
5 files changed, 5 insertions, 5 deletions
@@ -1,5 +1,5 @@ [workspace] -members = ["init", "vegilctl"] +members = ["init", "vigilctl"] resolver = "3" [workspace.package] @@ -11,14 +11,14 @@ The development is based on the Unix philosophy: - **"The UNIX system is characterized by: [...] A unified view of I/O, and a hierarchical file system. A small number of kernel primitives, augmented by a rich set of user-level tools."** - Ritchie & Thompson, «The UNIX Time-Sharing System» -`vegil` strives to be indestructible, something that even in the case of most errors will boot you into the system. If not, then go to rescue mode with all the tools installed. +`vigil` strives to be indestructible, something that even in the case of most errors will boot you into the system. If not, then go to rescue mode with all the tools installed. # Development -This repo contains the source code of the `init` executable itself and `vegilctl`, for managing the initialization system. +This repo contains the source code of the `init` executable itself and `vigilctl`, for managing the initialization system. At the moment, the init binary itself is a priority for development. # Usage -All operations are logged and start with `*` and looks like `* <Operation> <Data>`, it has three colors: +All operations are logged and start with `*` and looks like `<Status> <Operation> <Data>`, it has three colors: - Red (`\x1b[31m`) - This means that a mission-critical operation has failed, and you will most likely go into rescue mode. - Yellow (`\x1b[33m`) - It means that the operation specified by the user in the configuration or not critical has failed, the system will start, but it is better to pay attention to it. -- Green (`\x1b[32m`) - Everything is in order.
\ No newline at end of file +- Green (`\x1b[32m`) - Everything is in order. diff --git a/vegilctl/Cargo.toml b/vigilctl/Cargo.toml index 0a89458..0a89458 100644 --- a/vegilctl/Cargo.toml +++ b/vigilctl/Cargo.toml diff --git a/vegilctl/src/args_dispatcher.rs b/vigilctl/src/args_dispatcher.rs index e69de29..e69de29 100644 --- a/vegilctl/src/args_dispatcher.rs +++ b/vigilctl/src/args_dispatcher.rs diff --git a/vegilctl/src/main.rs b/vigilctl/src/main.rs index 08ff37c..08ff37c 100644 --- a/vegilctl/src/main.rs +++ b/vigilctl/src/main.rs |