BSDCan2017 - 0722d
BSDCan 2017
The Technical BSD Conference
| Speakers | |
|---|---|
|
Sean Chittenden |
| Schedule | |
|---|---|
| Day | Talks #2 - 10 June - 2017-06-10 |
| Room | DMS 1140 |
| Start time | 13:30 |
| Duration | 01:00 |
| Info | |
| ID | 860 |
| Event type | Lecture |
| Track | System Administration |
| Language used for presentation | English |
Universal Userland
Why do we need to be different?
Walk through replacing the FreeBSD user land utilities from two different sets: a Go-based user land (https://github.com/aisola/go-coreutils) and more interesting a Rust based implementation (MIT licensed): https://github.com/uutils/coreutils . Why bother? What's interesting? What can be learned from non-C based user land utilities?
One of the things that irritates me is moving between operating systems and having my user land change. Both the layout, but most certainly the actual utilities themselves. In this talk I want to poke at the sacred cow and universally held belief that builtin utilities must be written in C and that they are operating system specific. What are the security benefits? What about the performance benefits? How do you package up a different userland effectively? Can the FreeBSD community partner with other OSes and distributions that also want a modern user land?