You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+63-29Lines changed: 63 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,68 +4,102 @@ TriOS is a Debian-based operating system designed for users who want a clean, sm
4
4
It ships with Debian’s full set of standard repositories and drivers (including non-free firmware) to ensure maximum hardware compatibility.
5
5
6
6
## Base Information
7
+
7
8
TriOS is based on **Debian 13 “Trixie”**, which will receive:
8
-
- Full security support until **August 2028**
9
-
- Long Term Support (LTS) until **August 2030**
9
+
10
+
* Full security support until **August 2028**
11
+
* Long Term Support (LTS) until **August 2030**
10
12
11
13
Bookworm-based releases and later Forky-based releases are being considered.
12
14
13
15
For more details, see the official [Debian release and support timeline](https://www.debian.org/releases/).
14
16
15
17
## Why TriOS?
18
+
16
19
I wanted a Linux distribution that was:
17
20
18
-
-**Minimal** – like Lubuntu, keeping the system lightweight and efficient.
19
-
-**Smooth** – like Linux Mint, with polish and usability out of the box.
20
-
-**Tailored to my workflow** – focused on game development, gaming, and creative studio work.
21
+
***Minimal** – like Lubuntu, keeping the system lightweight and efficient.
22
+
***Smooth** – like Linux Mint, with polish and usability right out of the box.
23
+
***Tailored to my workflow** – focused on game development, gaming, and creative studio work.
21
24
22
-
I am yet to find a disto that provides a balanced system that is easy to set up, stays out of the way, and supports both everyday use and demanding workflows.
25
+
I’ve yet to find a distro that offers a well-balanced system that’s easy to set up, stays out of the way, and supports both everyday use and demanding workloads.
23
26
24
-
I used to use Linux Mint to fulfill these needs, but the overhead of abstraction has made everyday usage difficult.
27
+
I used to rely on Linux Mint for this, but its growing abstraction layers have made everyday use feel sluggish and unnecessarily complicated.
25
28
26
-
Most distributions either prioritise developers or everyday users, but what if a you tried to optimise for both?
29
+
Most distributions either prioritize developers or everyday users, but what if you tried to optimize for both?
27
30
28
-
That's why I made TriOs.
31
+
That’s why I made **TriOS**.
29
32
30
33
## Features
31
-
- Debian-based
32
-
- Includes tools to install drivers for AMD, Intel, and NVIDIA hardware
33
-
- Minimal default desktop environment with room to customize
34
-
- Smooth out-of-the-box performance and experience
35
-
- Stable if used correctly
34
+
35
+
* Debian-based
36
+
* KDE Plasma desktop environment (minimal configuration, ready to customize)
37
+
* Includes tools to install drivers for AMD, Intel, and NVIDIA hardware
38
+
* Smooth, polished experience right out of the box
39
+
* Stable if used correctly
40
+
41
+
⚠️ **Note:** TriOS is currently in **beta**. It’s functional and stable in testing, but I **don’t recommend using it as your primary daily driver** just yet. Things are still evolving rapidly.
42
+
43
+
## Version Naming
44
+
45
+
TriOS version names follow a simple and consistent format:
46
+
47
+
> **[Debian Release Number][TriOS Codename]**
48
+
49
+
For example:
50
+
51
+
***13 Bepis** → Current beta release (based on Debian 13 “Trixie”)
52
+
***13 Tenna** → Planned first stable release
53
+
54
+
Future versions will continue this naming pattern, aligning with each major Debian release and a unique TriOS codename for clarity and identity.
36
55
37
56
## License
57
+
38
58
TriOS itself (custom scripts, configs, and branding) is licensed under the **MIT License**.
39
59
40
60
Please note:
41
-
- The operating system includes software packages from Debian, each under their own respective licenses.
42
-
- Non-free firmware and proprietary drivers are redistributed under the terms provided by their respective vendors.
43
-
- For full license information, see `/usr/share/doc/*/copyright` within the installed system.
61
+
62
+
* The operating system includes software packages from Debian, each under their own respective licenses.
63
+
* Non-free firmware and proprietary drivers are redistributed under the terms provided by their respective vendors.
64
+
* For full license information, see `/usr/share/doc/*/copyright` within the installed system.
44
65
45
66
## Downloads
46
-
TriOs was made for amd64. Future builds may also be available for i386 (32 bit) and arm64. TriOs hasn't been tested on arm64 or i386, but if you wish to try it anyway, you can build it yourself.
47
67
48
-
You MUST have a working internet connection when installing TriOs.
68
+
TriOS is built for **amd64**. Future builds may also be available for **i386 (32-bit)** and **arm64**.
69
+
TriOS hasn’t been tested on arm64 or i386 yet, but if you’re feeling brave (or stubborn), you can always build it yourself.
70
+
71
+
You MUST have a working internet connection when installing TriOS.
I spent **way too much time** getting this automatic build system to work, **for your convenience.**
85
+
86
+
But hey, if you want to take the hard road and rebuild it yourself just because you *can*, who am I to stop you?
87
+
Go ahead. I won’t judge (much).
88
+
89
+
### The elite Docker container in question
58
90
59
-
## Building the ISO from source
91
+
The Docker container lives in the `builder/` directory. It’s a standard container setup.
92
+
The `build-trios.sh` script only works if you’re running it as root and the repo is cloned to the root user’s home directory.
60
93
61
-
I spent way too much time getting this automatic build system to work FOR YOUR CONVENIENCE.
94
+
If you want additional customization, bind volumes to the `TriOs` and `TriOs_Output` directories.
95
+
`TriOs` should be a copy of the repo, and `TriOs_Output` should be an empty folder.
62
96
63
-
If you wish to discredit all of my hard work just because you feel like it, you can use the docker container. :)
97
+
If you’re developing for TriOS, I recommend using a separate copy of the repo rather than your working one.
98
+
Pull requests containing extra data generated by `lb build` or other temporary configs won’t be accepted.
64
99
65
-
### The elite docker container in question
100
+
### Testing the ISO (optional but recommended)
66
101
67
-
The docker container is in the `builder/` directory. It's a standard docker container. The `build-trios.sh` only works if you are running it as root and the repo is cloned to the root user's home directory. If you want additional customisation, you need to bind volumes to the `TriOs` and `TriOs_Output` directory. `TriOs` should be a copy of the repo and `TriOs_Output` should be an empty folder. If you are developer, I recommend using a copy of the repo and not the one you are currently working on. PRs with extra data created by `lb build` or other specific configs will not be accepted.
102
+
Boot the ISO in a VM or from a USB stick to verify functionality before distributing it.
68
103
69
-
### Test the ISO (optional but recommended)
104
+
But seriously, **please** test your builds before telling other people they’re safe to use.
70
105
71
-
Boot the ISO in a VM or from a USB stick to verify functionality before sending it out.
0 commit comments