Oclug 2010
Upcoming SlideShare
Loading in...5

Oclug 2010



My presentation for December OCLUG meeting.

My presentation for December OCLUG meeting.



Total Views
Slideshare-icon Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Oclug 2010 Oclug 2010 Presentation Transcript

    • BSD For Linux UsersDru LavigneCommunity Manager, PC-BSD ProjectOCLUG, December 7, 2010
    • This presentation will cover...What exactly is BSD?How is it different from Linux?Does release engineering matter?Any features unique to BSD?Additional Resources
    • What exactly is BSD?
    • aka What exactly is Linux?
    • kernel?
    • distro?
    • What is BSD?Began as a series of patches andcontributed applications for Unix from theUniversity of BerkeleyForked into several projects when Berkeleystopped working on BSDTwenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributablehttp://oreilly.com/catalog/opensources/book/kirkmck.html
    • What is BSD?Projects originally differentiated by focus:NetBSD: clean design and portability (57supported platforms)FreeBSD: production server stability andapplication support (22,431 apps)OpenBSD: security and dependablerelease cycleDragonfly BSD: filesystem architecturePC-BSD: anyone can install and use BSD
    • How is BSD different from Linux?
    • Gnome on Ubuntu
    • KDE on PC-BSD
    • device names
    • startup (no runlevels)
    • one config file philosophy
    • kernel configuration
    • consistent layout (man hier)
    • BSD vs GNU switches
    • working examples
    • Release Engineering?
    • Release EngineeringComplete operating system, not kernel +distro: one source for security advisories,less likelihood of incompatible librariesIntegration of features not limited bycopyleft: e.g. drivers and features are built-inHigh “bus factor”Consistent separation between operatingsystem and third party and between BSDand GPLd code
    • Release Engineering● commit bit indicates write permission to code repository● FreeBSD 446 commit bits● NetBSD 264 commit bits● OpenBSD 132 commit bits● plus thousands of contributors for software, docs, translations, bug fixes, etc● Linux has 1 committer, 638 maintainers
    • Release EngineeringPrinciples used by the BSD projects reflecttheir 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
    • 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 dont result in library incompatibilities (safe for production)● documentation considered as important as code
    • Features unique to BSD?
    • securelevels
    • FreeBSD jails
    • NetBSD build.sh
    • pkgsrc
    • PC-BSD PBIs
    • VuXML and portaudit or pkg_admin audit for pkgsrc systems
    • NetBSD veriexec
    • binary emulation
    • FreeBSD netgraph
    • ZFS support
    • FreeBSD dtrace suport
    • CARP
    • FreeBSD superpages
    • OpenBSM
    • FreeBSD snapshots
    • ALTQ
    • DragonFly HAMMER
    • Automated Testing Framework
    • Non-GPLd Toolchain
    • Additional ResourcesHow the FreeBSD Project Workshttp://2007.asiabsdcon.org/papers/P08-slides.pdfFreeBSD Developmenthttp://www.freebsd.org/projects/index.htmlThe NetBSD Wayhttp://www.fosslc.org/drupal/content/netbsd-way-0NetBSD Developmenthttp://www.netbsd.org/developers/
    • Questions?http://www.slideshare.net /dlavigne/oclug-2010 dru@freebsd.org