lexOS Documentation

Table of Contents

Getting Started with lexOS

Welcome to the lexOS documentation. Here you will find all the information you need to get started with lexOS, including installation guides, user manuals, and troubleshooting tips.

Installation Guide

Follow these steps to install lexOS on your machine:

0 Make a user named lex (on linux) and make it root (for more information why you need to do this read the github)

1 Download lexium VM and lexOS-image

2 Run lexium with normal settings (80% of your cpu will be used)

3 For running lexOS run the RUNER executable

4 The user will be lex and the password should be your user password and if that doesn't work try gulb12, i32, sun12, u32 or 1234

User Manual

The lexOS user manual provides detailed information on how to use and customize your lexOS system.

User Interface

its a simple CLI interface and in that way will remain :)

For commands type help in the OS

Package Management

we dont have but it has gcc vim and rustc (all of this are copies and then programed them to work on lexOS if you see any errors please go to lexOS-image issuse and report)

Troubleshooting

If you encounter any issues while using lexOS, report on lexOS-image github

System Configuration

system configuration will be big but in version 0.1 it only has a mini kernel editor but in the future i will add drivers editor a more complex kernel editor ,a CLi editor and a custom bare bone editor

to run the minkernel editor use the cd command to go to the root directory where minkernel folder is , cd into it and then cd into src and run "exec edit"

Network

to connect lexOS to wifi make sure you have the network driver and the minkernel version > 3

go into the minkernel folder and edit the netwifi.sync to your network

Minkernel customization

Lets go to the first customization

After you enter the minkernel customization

i or u

Why would you chose i:

1 i is used more in lexoterm which means that it will give a more flexible apps and interface for (in the next version of lexOS it will be switch to have more support for u for more information go to Progress report 0)

2 i is more faster at lower numbers so if you dont have many ram or a slower cpu i will be a better option than u

3 i is more functional

The i is more fast and functional at lower numbers like i8 or i16

Why would you chose u :

1 u is stable

2 you have a feature that makes your pc handles better tasks

3 the minkernel supports better u (in the next version of lexOS the support of i will be bigger)

4 u supports better higher numbers so if you have many ram and you have a good cpu , u can be your best option if you want a more stable system

If you chose u lexOS will be more stable and faster at numbers like u64 or u32 but in the futere the i and u are going to be more balanced

frenqency

For the next feature we have frenqency that isn't about the cpu frenqency but more of how much your pc can handle

Because lexOS uses more cpu you will have to decide yourself if your cpu is good enough to run 64 32 or 16

Some tips: if your cpu can run the 32 version but you want to be faster you could try the 16 version instead (same goes for the 64)

If your cpu is good and can run 64 with easy (like the most cpu) and you want to be faster you should not run it at 32 it will slow your pc down

BIT

BIT: just go with whatever your pc is 32bits or 64bits (even if you are on lexium virtual machine)

BUFFER

For buffer size it depends on how much ram do you have (the lexium virual machine uses all of your ram if it needs).

If you have 8GB or higher go with 8MB if you have below 8GB of ram go with 6MB (please do not go with the unlimited version it can breake your entier system)

Drivers

Drivers is your choice

Cpu cores

If you want to have a good experience use A normal usage but if you want to use lexOS in eco mode chose B liitel usage and BETA S zen it will run your cores at a much higher rate

Cpu frenqency

Cpu frenqency just go with normal

CPU zen

CPU zen: Firs the zen tehnology runs a test on your cpu to see what are the fastest Cores in your cpu and it will run some programs using that cores

zen mini use for testing and it will compile code faster and will run the system better

zen normal use for testing and it will compile and run the system more on that cores

BETA zen max use for running everything on that cores

GFX

gfx (if you chose i please dont chose anything)

use u64 if you have 16GB or more GB of ram (if you see any lag it can be from cpu or you have a very slow ram)

use u32 if you have 8GB or more GB of ram or if your cpu cant run u64 because of your cpu

use u16 if you have 4-8GB of ram

use u8 if you have 4GB of ram and you have an old cpu

More: you will see that in some cases you will see that u64 can be equal to u32 or u16 or even u8 because this project is started when i didnt know that much and i made some errors in support so yeah in future i will try to solve it if i see that the community grows

I size

i size (if you chose u please dont chose anything)

use i32 if your pc cant run cant run u64 and you want speed

use i16 instead of u16 just because after some benchmarks i saw that i16 is in general 8-12% faster than u16

use i8 if you want to try it (its the same speed as u8 so there is not a big diference)

C..

C.. coming soon if you chose anything it will not work

testing

testing coming soon if you chose anything it will not work

0

0

1

1

1

0

0

0