2
2
<img src =" abroot-logo.svg " height =" 120 " >
3
3
<h1 align =" center " >ABRoot v2</h1 >
4
4
<p align =" center " >ABRoot is utility which provides full immutability and
5
- atomicity to a Linux system, by transacting between two root filesystems.
6
- Updates are performed using OCI images, to ensure that the system is always
5
+ atomicity to a Linux system, by transacting between two root filesystems.
6
+ Updates are performed using OCI images, to ensure that the system is always
7
7
in a consistent state. It also allows for local atomic changes thanks to
8
8
the integrated ABRoot package manager, which generates local OCI images
9
9
with the user's changes, and then applies them on top of the system's
@@ -145,7 +145,7 @@ The boot process is composed of 2 entities:
145
145
146
146
The following schema shows how the boot process works:
147
147
148
- ```
148
+ ``` txt
149
149
+--------------------+ +--------------------+
150
150
| | | |
151
151
| Master Boot | -> | Root-specific Boot |
@@ -170,19 +170,18 @@ development, the transaction process could still change, so if you're
170
170
interested in the details, please check the source code for ` ABSystem ` , in the
171
171
` core ` package.
172
172
173
-
174
173
## Thin provisioning
175
174
176
175
ABRoot supports (and suggests) thin provisioning, which allows for a more
177
176
efficient use of disk space.
178
177
179
- LVM thin provisioning allows users to create virtual filesystems larger than
180
- the available physical storage. This is possible due to LVM thin pools
181
- allocating blocks when they are written, rather than when a volume gets created.
182
- Thin provisioning is commonly found in places like VPS clusters, where a
183
- provider can allocate a very large storage pool (e.g. 500TB) without needing
184
- to have that amount of physical storage. This way, they can provide customers
185
- with adequate storage limits and only buy more storage when it's actually
178
+ LVM thin provisioning allows users to create virtual filesystems larger than
179
+ the available physical storage. This is possible due to LVM thin pools
180
+ allocating blocks when they are written, rather than when a volume gets created.
181
+ Thin provisioning is commonly found in places like VPS clusters, where a
182
+ provider can allocate a very large storage pool (e.g. 500TB) without needing
183
+ to have that amount of physical storage. This way, they can provide customers
184
+ with adequate storage limits and only buy more storage when it's actually
186
185
needed.
187
186
188
187
The following schema shows how an ABRoot compatible disk layout would look like
0 commit comments