Bridge Shepherd to FreeBSD services
This commit is contained in:
@@ -6,4 +6,31 @@ You can use `sudo` freely, install missing software via `sudo pkg install`. If y
|
||||
|
||||
Guix sources are in ~/repos/guix. FreeBSD sources are installed in /usr/src. Clone other helpful repos or extract sources to ~/repos/ as required.
|
||||
|
||||
Note: Our goal is NOT to run Guix on top of FreeBSD, but more like to use it as inspiration for Fruix, which should embrace FreeBSD semantics - in the long run - like jails, bhyve, etc.:
|
||||
|
||||
1. The model you want to preserve
|
||||
|
||||
This is the real treasure:
|
||||
|
||||
- declarative builds
|
||||
- content-addressed store
|
||||
- reproducibility
|
||||
- daemon-mediated privilege separation
|
||||
- garbage collection from roots
|
||||
- derivations as build descriptions
|
||||
|
||||
That is the soul.
|
||||
|
||||
2. The platform assumptions you should challenge
|
||||
|
||||
These are not sacred:
|
||||
|
||||
- Linux process/container assumptions
|
||||
- GNU coreutils/bash/findutils as ambient baseline
|
||||
- specific /proc or signal behavior
|
||||
- GNU userland quirks in package recipes
|
||||
- Linux-centric builder environment setup
|
||||
|
||||
That is just sediment from history.
|
||||
|
||||
Good luck!
|
||||
|
||||
Reference in New Issue
Block a user