1. BSD For Linux Users
Chair, BSD Certification Group
2. This presentation will cover...
What is this BSD you speak of? (frame of
How is BSD different? (will I like it?)
Release engineering? (behind the scenes)
Any features unique to BSD? (am I missing
out on anything cool?)
Books (some recommended reading)
3. What is this BSD you
4. aka What is this Linux
you speak of?
5. a kernel?
6. a distro?
7. If so, which one? Ubuntu?
8. Back to BSD....
Since we only have 45 minutes.....
We'll start with an overview of the BSD
Then concentrate on some of the
differences Linux users tend to notice on
9. Back to BSD....
Differentiated by focus:
NetBSD: clean design and portability (56
FreeBSD: production server stability and
application support (21,250+ apps)
OpenBSD: security and dependable release
Dragonfly BSD: filesystem architecture
PC-BSD: anyone can install and use BSD
10. How is BSD different?
11. Gnome vs.
13. device names
14. rc.conf instead of runlevels
15. one config file philosophy
16. kernel configuration
17. consistent layout (man hier)
18. BSD vs GNU switches
19. working examples
20. Release Engineering?
21. Release Engineering
Complete operating system, not kernel +
distro: one source for security advisories,
less likelihood of incompatible libraries
Integration of features not limited by
copyleft: e.g. drivers are built-in
High “bus factor”
Consistent separation between operating
system and third party and between BSD
and GPL'd code
22. Release Engineering
● While each BSD project has a separate
focus, the communities share ideas/code
● Mentorship process to earn commit bit
● FreeBSD 417 commit bits
● NetBSD 263 commit bits
● OpenBSD 127 commit bits
● plus thousands of contributors for
software, docs, translations, bug fixes, etc
● Linux has 1 committer, 196 maintainers
23. Release Engineering
Principles used by the BSD projects reflect
their academic roots:
● well defined process for earning a
“commit bit” includes a period of working
under a mentor
● code repository from Day 1 and can
trace original code back to CSRG days
● no “leader”, instead well defined release
engineering, security, and doc teams
24. Release Engineering
● development occurs on CURRENT which is
frozen in preparation for a RELEASE
● nightly builds (operating system and
apps) help ensure that upgrades and
installs don't result in library
incompatibilities (safe for production)
● documentation considered as important
25. Features unique to
27. FreeBSD jails
28. NetBSD build.sh
30. PC-BSD PBIs
31. VuXML and portaudit
32. pkg_admin audit
or pkg_admin audit
for pkgsrc systems
33. NetBSD veriexec
34. binary emulation
35. FreeBSD netgraph
36. ZFS support
37. FreeBSD dtrace suport
39. FreeBSD superpages
41. FreeBSD system snapshots
43. DragonFly HAMMER
Stop by the BSD booth to say hi and get a
free copy of PC-BSD!