keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

docs/background: Fix benefits and drawbacks formatting

Browse Source 
The lists of pros and cons for each approach in the background section
of the manual use markdown formatting that is rendered as nested
lists. Separate the lists of benefits and drawbacks so that readers of
https://rpm-ostree.readthedocs.io/en/latest/manual/background/ and the
rendered markdown on github can understand which items are pros and
which are cons.

Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
This commit is contained in:
Doug Hellmann
2020-05-14 17:00:29 -04:00
committed by OpenShift Merge Robot
parent b7ff1612ea
commit d160ed181c
1 changed files with 25 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/manual/background.md
View File

@ -5,24 +5,34 @@ to fall cleanly into one of two camps: package-based or image-based.
### Package system benefits and drawbacks
* + Highly dynamic, fast access to wide array of software
* + State management in `/etc` and `/var` is well understood
* + Can swap between major/minor system states (`apt-get upgrade` is similar to `apt-get dist-upgrade`)
* + Generally supports any filesystem or partition layout
* - As package set grows, testing becomes combinatorially more expensive
* - Live system mutation, no rollbacks
Benefits
* Highly dynamic, fast access to wide array of software
* State management in `/etc` and `/var` is well understood
* Can swap between major/minor system states (`apt-get upgrade` is similar to `apt-get dist-upgrade`)
* Generally supports any filesystem or partition layout
Drawbacks
* As package set grows, testing becomes combinatorially more expensive
* Live system mutation, no rollbacks
### Image benefits and drawbacks
* + Ensures all users are running a known state
* + Rollback supported
* + Easier to verify system integrity
* - Many image systems have a read-only `/etc`, and writable partitions elsewhere
* - Must reboot for updates
* - Usually operate at block level, so require fixed partition layout and filesystem
* - Many use a "dual root" mode which wastes space and is inflexible
* - Often paired with a separate application mechanism, but misses out on things that aren't apps
* - Administrators still need to know content inside
Benefits
* Ensures all users are running a known state
* Rollback supported
* Easier to verify system integrity
Drawbacks
* Many image systems have a read-only `/etc`, and writable partitions elsewhere
* Must reboot for updates
* Usually operate at block level, so require fixed partition layout and filesystem
* Many use a "dual root" mode which wastes space and is inflexible
* Often paired with a separate application mechanism, but misses out on things that aren't apps
* Administrators still need to know content inside
## How rpm-ostree provides a middle ground