docs: Move and update Background page
This commit is contained in:
parent
86e41df561
commit
75708f9d77
@ -1,3 +1,13 @@
|
||||
---
|
||||
nav_order: 2
|
||||
---
|
||||
|
||||
# Background
|
||||
{: .no_toc }
|
||||
|
||||
1. TOC
|
||||
{:toc}
|
||||
|
||||
## Package systems versus image systems
|
||||
|
||||
Broadly speaking, software update systems for operating systems tend
|
||||
@ -5,27 +15,27 @@ to fall cleanly into one of two camps: package-based or image-based.
|
||||
|
||||
### Package system benefits and drawbacks
|
||||
|
||||
Benefits
|
||||
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
|
||||
Drawbacks:
|
||||
|
||||
* As package set grows, testing becomes combinatorially more expensive
|
||||
* Live system mutation, no rollbacks
|
||||
|
||||
### Image benefits and drawbacks
|
||||
|
||||
Benefits
|
||||
Benefits:
|
||||
|
||||
* Ensures all users are running a known state
|
||||
* Rollback supported
|
||||
* Easier to verify system integrity
|
||||
|
||||
Drawbacks
|
||||
Drawbacks:
|
||||
|
||||
* Many image systems have a read-only `/etc`, and writable partitions elsewhere
|
||||
* Must reboot for updates
|
Loading…
Reference in New Issue
Block a user