<?xml version="1.0" encoding="UTF-8"?>
<schedule>
  <conference>
    <title>BSDCan 2014</title>
    <subtitle>The Technical BSD Conference</subtitle>
    <venue>University of Ottawa</venue>
    <city>Ottawa</city>
    <start>2014-05-13</start>
    <end>2014-05-18</end>
    <days>6</days>
    <release>Final</release>
    <day_change>09:00</day_change>
    <timeslot_duration>00:15</timeslot_duration>
  </conference>
  <day date="2014-05-13" index="1">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
    </room>
    <room name="Montpetit 202">
    </room>
    <room name="Montpetit 207">
    </room>
    <room name="Morisset 211">
    </room>
    <room name="Morisset 212">
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
      <event id="519">
        <start>17:00</start>
        <duration>06:15</duration>
        <room>Royal Oak Pub</room>
        <slug>goat</slug>
        <title>Goat BOF</title>
        <subtitle></subtitle>
        <track>BOF</track>
        <type>other</type>
        <language>en</language>
        <abstract>This is a BOF.</abstract>
        <description>About goats.</description>
        <persons>
          <person id="214">Allan Jude</person>
          <person id="1">Dan Langille</person>
          <person id="6">Michael W. Lucas</person>
        </persons>
        <links>
          <link href="https://twitter.com/dlangille/status/462732293686452224">Twitter announcement</link>
          <link href="http://goo.gl/maps/zHr2P">Google Map to Royal Oak on Laurier St</link>
        </links>
      </event>
    </room>
    <room name="Out and About">
    </room>
    <room name="Hacker Lounge - L140">
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
    </room>
    <room name="University Center 301">
    </room>
  </day>
  <day date="2014-05-14" index="2">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
      <event id="476">
        <start>09:00</start>
        <duration>03:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>IPv6 Tutorial</title>
        <subtitle>How to get rid of legacy</subtitle>
        <track>Tutorial</track>
        <type>workshop</type>
        <language>en</language>
        <abstract>With the IPv4 depletion closer and closer, there is a rising need to be able to work with IPv6 in our everyday life. This tutorial aims at putting the audience with their hands on the new protocol, creating a test network and managing applications running on top of it. The tutorial is divided in small theory sessions, and a series of hands-on sessions right after them, where lessons learned will be applied in a real life environment.

NOTE: this tutorial requires use of a VM which attendees must install themselves before arriving at the tutorials.  Details will be mailed out before the tutorial.
</abstract>
        <description>We all know that IPv4 is running out faster than we could ever predict, and everybody should start getting acquainted with IPv6, a protocol ? or better a suite of protocols ? that has been available and usable for more than ten years but never got the right level of audience. Being ahead of the majority of the people will give those who were smart enough a lead over those that underestimated the ?threat?.

This tutorial is intended for people wanting to get a greater grasp on the technology and implications of running IPv6, and will be presented along with a series of lab session to get running in this somewhat new world. There will be an introduction shedding light on key concepts and features, preparing the attendees for the rest of the session, focusing on putting hands on an IPv6-only network and connecting it to the world at large.

Focus will be on a hands-on approach, where the participant is requested to act and work on configuring services over a real network after a brief theoretical introduction to highlight key concepts. Topics of the tutorial include IPv6 subnetting, protocol implementation for different common internet services like www, mail, dns, along with digressions over routing protocols and implementations such as DS-LITE and NATx4

At the end of the session, participants should be able to set up an IPv6-enabled network with no hassle, and with the required know-how to migrate services to the new protocol, transition mechanisms and procedures, and everything else needed.

The tutorial is supported by a remote lab where every participant will be given a series of virtual machines to configure following the topics presented in the theory sessions, and will also have to relate to others to complete the required exercises, like setting up web services and interacting with other groups to test their communication on the live internet. Every participant will also be given a three week period over which the virtual machines will still work, so that he can keep on trying out IPv6 to strengthen key concepts outside of the class.</description>
        <persons>
          <person id="39">Massimiliano Stucchi</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="453">
        <start>13:00</start>
        <duration>03:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Building The Network You Need With PF, The OpenBSD Packet Filter</title>
        <subtitle>Sane networking, matching your needs</subtitle>
        <track>Tutorial</track>
        <type>workshop</type>
        <language>en</language>
        <abstract>This session is aimed at experienced or aspiring network administrators who want to expand their knowledge of PF, the OpenBSD packet filter, and related tools.  A basic knowledge of Unix and TCP/IP network configuration is expected and required.  

The session will provide updates on the new PF syntax and features introduced in OpenBSD 4.7 (with samples presented in the old and new syntax where appropriate), with newer updates and previews of relevant new features such as the new traffic shaping system in the upcoming OpenBSD 5.5 release (planned release date May 1st).</abstract>
        <description>Topics potentially covered include

* Configuration on OpenBSD, FreeBSD and NetBSD
* PF ruleset basics and rule interactions: block, pass, match
* Writing maintainable rulesets
* Address families: IPv4 NAT vs IPv6
* Redirection, divert and services with odd dependencies (ftp-proxy, spamd)
* Adaptive rulesets (state tracking tricks)
* Traffic shaping with priorities and 'newqueue', OpenBSD 5.5 style
* Legacy ALTQ traffic shaping
* Per user filtering with authpf 
* High availability with CARP, relayd 
* Wireless vs wired networks
* Filtering bridges
* Logging and monitoring - pflog, pflow and others
* Testing, debugging, and optimizing your configuration

The session will provide updates on the new PF syntax and features introduced in OpenBSD 4.7 (with samples presented in the old and new syntax where appropriate), with newer updates and previews of relevant new features such as the new traffic shaping subsystem in the upcoming OpenBSD 5.5 release (planned release date May 1st). 

The available material (notes and slides) covers significantly more than the schedule allows for. To help make the session more targeted to your needs, I would appreciate if you, when you sign up for the session or soon after, send me an email to tutorial@bsdly.net description of what you would like to learn in this session, and to the extent you are allowed and feel it is appropriate, what your near or longer term future OpenBSD project is. 

Slides matching the latest version of the tutorial can be found at &lt;a href="http://home.nuug.no/~peter/pf/newest/"&gt;http://home.nuug.no/~peter/pf/newest/&lt;/a&gt;; updated slides will be made available to the general public after the present session has concluded. 

Timing and logistics allowing, copies of the third edition of Hansteen's The Book of PF will be available to purchase at the session. (Also see &lt;a href="http://nostarch.com/pf2.htm"&gt;The Book of PF, 2nd edition&lt;/a&gt;, No Starch Press November 2010). 
</description>
        <persons>
          <person id="19">Peter Hansteen</person>
        </persons>
        <links>
          <link href="http://home.nuug.no/~peter/pf/newest/">Newest presentation slides</link>
          <link href="http://bsdly.blogspot.com">Peter N. M. Hansteen's blog</link>
          <link href="http://nostarch.com/pf3">The Book of PF, third edition</link>
        </links>
      </event>
    </room>
    <room name="Montpetit 202">
    </room>
    <room name="Montpetit 207">
    </room>
    <room name="Morisset 211">
      <event id="498">
        <start>18:00</start>
        <duration>04:00</duration>
        <room>Morisset 211</room>
        <slug></slug>
        <title>Doc Sprints</title>
        <subtitle>Doc Sprints</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.</abstract>
        <description>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.

FreeBSD committers will be available to assist non-committers in getting started with the FreeBSD documentation set, learning the workflow and how to make changes, and to approve and commit patches. Committers will also work on closing doc PRs and discuss proposed changes to the documentation.

Feel free to drop by and help out!</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="Morisset 212">
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
    </room>
    <room name="Out and About">
    </room>
    <room name="Hacker Lounge - L140">
      <event id="487">
        <start>20:00</start>
        <duration>04:00</duration>
        <room>Hacker Lounge - L140</room>
        <slug></slug>
        <title>Hacker Lounge</title>
        <subtitle>meet, greet, hack</subtitle>
        <track>Social</track>
        <type>other</type>
        <language>en</language>
        <abstract>The hacker lounge is on the ground floor of residence.  Bring your laptop, enjoy.

This room is located just past the lobby.  You may need to ask for the key at the desk. </abstract>
        <description>Proper behaviour is expected, or you'll be asked to leave.  :)  If you must ask what proper behaviour is, well, it sounds like you shouldn't be there.

The starting time is flexible, so is the ending time.  Just show up.  wifi will be available.

In order to play nicely with others, please bring an extension cord / power strip.

Please keep this room tidy and clean.</description>
        <persons>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
    </room>
    <room name="University Center 301">
    </room>
  </day>
  <day date="2014-05-15" index="3">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
      <event id="454">
        <start>09:00</start>
        <duration>03:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Transition to OpenBSD 5.5</title>
        <subtitle>Transition from earlier OpenBSD releases or other Unix-like systems</subtitle>
        <track>Tutorial</track>
        <type>workshop</type>
        <language>en</language>
        <abstract>OpenBSD has been the source of a number of BSD innovations over the years, including but not limited to PF (the OpenBSD packet filter, now including a new traffic shaping engine), significantly improved IPSEC tools, OpenSSH (the free Secure Shell server and client), security enhancements including preemtive exploit mitigation, and various other advances of the art and engineering in various parts of the system.

This session intends to help you tackle the transition to the newest OpenBSD release from earlier releases or even coming from other Unix-like systems, highlighting enhancements in the new release and how to avoid any pitfalls that may turn up during the process.</abstract>
        <description>OpenBSD has been the source of a number of BSD innovations over the years, including but not limited to PF (the OpenBSD packet filter, now including a new traffic shaping engine), significantly improved IPSEC tools, OpenSSH (the free Secure Shell server and client), security enhancements including preemtive exploit mitigation, and various other advances of the art and engineering in various parts of the system. 

At the time of writing (mid-January 2014) the big news items for OpenBSD 5.5 seem to be the new traffic shaping system and the automated installer, but it's not set in stone yet and every release has enhancements that may not be immediately obvious until you start using the system. 

This session intends to help you tackle the transition to the newest OpenBSD release, highlighting enhancements in the new release and how to avoid any pitfalls that may turn up during the process.  

The intended audience or attendee profile is anybody who is considering making the jump to OpenBSD 5.5. You may be considering moving your systems wholly or partly to the new release from an earlier OpenBSD release or to move specific parts of your operation from a different Unix-like operating system to OpenBSD. 

To help make the session more targeted to your specific interests and needs, I would appreciate if, when you sign up for the session or soon after, send me an email to transition@bsdly.net with a brief description of what you would like to learn in this session, and to the extent you are allowed and feel it is appropriate, what your near or longer term future OpenBSD project is. 
</description>
        <persons>
          <person id="19">Peter Hansteen</person>
        </persons>
        <links>
          <link href="http://bsdly.blogspot.com">Peter N. M. Hansteen's blog</link>
          <link href="http://home.nuug.no/~peter/transition/bsdcan2014/">Slides for this talk</link>
        </links>
      </event>
      <event id="456">
        <start>13:00</start>
        <duration>03:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Sudo</title>
        <subtitle>You're doing it wrong</subtitle>
        <track>Tutorial</track>
        <type>workshop</type>
        <language>en</language>
        <abstract>Sudo is one of the most widely deployed system security tools. It's also widely misunderstood and frequently misapplied. This tutorial takes you through the proper application of sudo, its strengths and weaknesses, and how it can be used and abused. Based on the book "Sudo Mastery."</abstract>
        <description>Unix-like operating systems use a rudimentary access control system: the root account can do anything, while other users are peasants with only minimal access. This worked fine in UNIX&#8217;s youth, but today, system administration responsibilities are spread among many people and applications. Each person needs a tiny slice of root&#8217;s power.

Sudo lets you divide root&#8217;s monolithic power between the people who need it with accountability and auditability.

This course will teach you to:

* design a sudo policy rather than slap rules together
* simplify policies with lists and aliases
* use non-Unix information sources in policies
* configure alternate sudo policies
* manage shell environments
* verify system integrity and perform intrusion detection
* have a common sudo policy across your server farm
* manage sudo policies via LDAP
* log and debug sudo
* log and replay full sudo sessions
* use authentication systems other than passwords

</description>
        <persons>
          <person id="6">Michael W. Lucas</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="Montpetit 202">
      <event id="499">
        <start>19:00</start>
        <duration>03:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>Doc Sprints</title>
        <subtitle>Doc Sprints</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.</abstract>
        <description>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.

FreeBSD committers will be available to assist non-committers in getting started with the FreeBSD documentation set, learning the workflow and how to make changes, and to approve and commit patches. Committers will also work on closing doc PRs and discuss proposed changes to the documentation.

Feel free to drop by and help out!</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="Montpetit 207">
    </room>
    <room name="Morisset 211">
      <event id="505">
        <start>19:00</start>
        <duration>03:00</duration>
        <room>Morisset 211</room>
        <slug></slug>
        <title>Puppet BOF</title>
        <subtitle></subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>The Ottawa Puppet Users Group is holding their next meeting at PGCon 2014.</abstract>
        <description>If you use Puppet, or would like to learn more, this is your opportunity.  Don't miss this chance to mix and mingle with fellow Puppeteers and maybe even snag yourself some Puppet Labs swag!</description>
        <persons>
          <person id="255">Kenn Hussey</person>
        </persons>
        <links>
          <link href="http://www.meetup.com/Ottawa-Puppet-Users-Group">Ottawa Puppet Users Group</link>
          <link href="http://puppetlabs.com/">Puppet Labs</link>
          <link href="https://en.wikipedia.org/wiki/Puppet_(software)">Puppet (Wikipedia)</link>
        </links>
      </event>
    </room>
    <room name="Morisset 212">
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
      <event id="488">
        <start>15:00</start>
        <duration>04:00</duration>
        <room>Royal Oak Pub</room>
        <slug>register</slug>
        <title>Registration - pub</title>
        <subtitle>Pick up your registration pack, have a beer!</subtitle>
        <track></track>
        <type>other</type>
        <language>en</language>
        <abstract>Registration pick up</abstract>
        <description>Avoid the line ups of the first day! Pick up your registration pack early, at the pub. Sit back. Have a drink, some food. Enjoy the company.

A BSDCan tradition. :)</description>
        <persons>
        </persons>
        <links>
          <link href="https://www.bsdcan.org/">The map is linked to from the home page.</link>
        </links>
      </event>
    </room>
    <room name="Out and About">
    </room>
    <room name="Hacker Lounge - L140">
      <event id="502">
        <start>20:00</start>
        <duration>05:00</duration>
        <room>Hacker Lounge - L140</room>
        <slug></slug>
        <title>Hacker Lounge</title>
        <subtitle>meet, greet, hack</subtitle>
        <track>Social</track>
        <type>other</type>
        <language>en</language>
        <abstract>The hacker lounge is on the ground floor of residence.  Bring your laptop, enjoy.

This room is located just past the lobby.  You may need to ask for the key at the desk. </abstract>
        <description>Proper behaviour is expected, or you'll be asked to leave.  :)  If you must ask what proper behaviour is, well, it sounds like you shouldn't be there.

The starting time is flexible, so is the ending time.  Just show up.  wifi will be available.

In order to play nicely with others, please bring an extension cord / power strip.

Please keep this room tidy and clean.</description>
        <persons>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
    </room>
    <room name="University Center 301">
    </room>
  </day>
  <day date="2014-05-16" index="4">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
      <event id="464">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Forensic Timestamp Analysis of ZFS</title>
        <subtitle>Using ZFS Metadata to enhance timeline analysis and detect forged timestamps.</subtitle>
        <track>Security</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Exploring the use of the internal data structures of ZFS to provide extra sources of data for forensic timeline analysis. Several techniques to detect falsified timestamps on ZFS filesystems are demonstrated.</abstract>
        <description>During forensic analysis of disks, it may be desirable to construct an account of events over time, including when files were created, modified, accessed and deleted. "Timeline analysis" is the process of collating this data, using file timestamps from
the file system and other sources such as log files and internal file metadata.

ZFS uses a complex structure to store file data and metadata and the many internal structures of ZFS are another source of timeline information. This internal metadata can also be used to detect timestamps which have been tampered with by the touch command or by changing the system clock.

This presentation will discuss the internal data structures of ZFS, present new research illustrating how ZFS metadata changes over time, and demonstrate how this data can be used to detect falsified file timestamps.</description>
        <persons>
          <person id="244">Dylan Leigh</person>
        </persons>
        <links>
          <link href="http://research.dylanleigh.net">http://research.dylanleigh.net</link>
        </links>
      </event>
      <event id="480">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Porting OpenBSD on the MIPS64-based Octeon Platforms</title>
        <subtitle></subtitle>
        <track>Embedded</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>My work on the Octeon port made possible for OpenBSD to run on the D-Link DSR line of mid-range routers and also improved all supported models through the drivers I wrote for the hardware random number generator and the real-time clock. I'm continuing my work on improving the OpenBSD experience on the DSR products by adding support for the CF card in particular and the USB stack in general. This presentation summarizes the developments I brought and the obstacles I faced.</abstract>
        <description>OpenBSD/octeon began in 2010 with an SDK created by IIJ and donated to OpenBSD. Portwell CAM-0100 becoming self-hosting in April 2013. Support for EdgeRouter LITE Ethernet was added in September 2013, allowing the EdgeRouter LITE to be usable by NFS booting.

Somewhere around mid-2013 someone kindly donated me an unsupported Octeon-based DSR-500 from D-Link. By October 2013 the machine was usable through NFS boot. Since then I started improving the port by adding new drivers like octrng(4) and octrtc(4), working on supporting the CF card found on the DSR models and towards adding generic USB support.

Lack of proper hardware documentation and a crippled SDK license are slowing down the porting process and don't allow for the creation of sound and robust device drivers.</description>
        <persons>
          <person id="222">Paul Irofti</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="517">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug>mips</slug>
        <title>MIPS router hacking</title>
        <subtitle>lunch time BOF</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>Lunch session with hands on bring up of a Mips74k commercial router.</abstract>
        <description>pointers to how to construct a FreeBSD image, flashing images to routers, recovery upon failure, netbooting for initial bring up, and using qemu to build pkgng style packages.
</description>
        <persons>
          <person id="97">Sean Bruno</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="458">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Using BGP for realtime import and export of spam whitelist/blacklist entries</title>
        <subtitle>a year in the life</subtitle>
        <track>System Administration</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The results of using BGP for realtime import and export of spam whitelist/blacklist entries</abstract>
        <description>In early 2013, I introduced a new method to distribute spam whitelist/blacklist entries.  Now, I am able to present the results of 1 year of usage.

In the battle against Spam, many mail server admins collect and distribute IP addresses of systems that send them Spam. However, distribution of these lists are traditionally limited to 2 methods.

 * is periodically downloading this list from a source, usually a web server often causing massive load and slowness at the top of the hour.
 * is a real-time lookup against an external provider (such as dns-rbls) so your response time is dependent on how fast they respond or timeout.

This talk discusses a 3rd solution: using BGP to distribute the IP addresses in a real-time manner.
</description>
        <persons>
          <person id="235">Peter Hessler</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=i8UAVswpagA&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=21">video</link>
        </links>
      </event>
      <event id="451">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>OpenBGPD turns 10 years</title>
        <subtitle>Design, Implementation, Lessons learned</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The Border Gateway Protocol, BGP, is used on the internet between ISPs to announce reachability of networks. Routers build their routing tables using this information. The global IPv4 routing table has about 470000 entries today.
</abstract>
        <description>In 2004, I was upset enough with the implementation we were using back then, zebra, to start writing an own one. After showing an early  prototype other developers jumped in and helped. Quickly thereafter we had a working BGP implementation that not only I have used ever since then. We'll look at OpenBGPD's design and how it differs from other implementations, the frameworks established and later used for other purposes, and the lessons we learned over the last 10 years.
</description>
        <persons>
          <person id="127">Henning Brauer</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=cP8AW111IKg&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=19">video</link>
        </links>
      </event>
      <event id="484">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>BSD/ARM Kernel Internals</title>
        <subtitle>A Walkthrough of FreeBSD and NetBSD ARM Code</subtitle>
        <track>Embedded</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>In this talk, I'll discuss how BSD kernels interface with the ARM processor. I will cover the kernel internals of the FreeBSD and NetBSD ARM ports, focusing on ARMv7 primarily.</abstract>
        <description> I will discuss how booting, memory management, exceptions, and interrupts work using plenty of BSD code. This talk is meant to be a quick start guide for BSD hackers who aren't familiar with the ARM architecture.</description>
        <persons>
          <person id="250">Arun Thomas</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=ZAM7fqhGRr8&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=20">video</link>
        </links>
      </event>
      <event id="500">
        <start>18:00</start>
        <duration>04:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Doc Sprints</title>
        <subtitle>Doc Sprints</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.</abstract>
        <description>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.

FreeBSD committers will be available to assist non-committers in getting started with the FreeBSD documentation set, learning the workflow and how to make changes, and to approve and commit patches. Committers will also work on closing doc PRs and discuss proposed changes to the documentation.

Feel free to drop by and help out!</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="Montpetit 202">
      <event id="492">
        <start>09:00</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>Keynote</title>
        <subtitle>The opening session</subtitle>
        <track>Plenary</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>FlightWare has been using FreeBSD servers since they started.</abstract>
        <description>Karl will talk about some of the history behind FlightAware and various projects he has been involved with.</description>
        <persons>
          <person id="253">Karl Lehenbauer</person>
        </persons>
        <links>
          <link href="http://it.flightaware.com/about/code/freebsd.rvt">http://it.flightaware.com/about/code/freebsd.rvt</link>
          <link href="https://www.youtube.com/watch?v=13LiyjnTGsQ&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=12">video - keynote</link>
        </links>
      </event>
      <event id="478">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>In-kernel OpenvSwitch on FreeBSD.</title>
        <subtitle></subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>OpenvSwitch (OVS) is a very popular component for experimenting with Software Defined Networking.  OVS is especially useful for interconnecting virtual machines, as it eases VM migration and reconfiguration of routing in the hosting provider.

In this paper we will discuss how we ported the in-kernel OVS dataplane to FreeBSD, using the original linux code with minimal modifications and suitable wrappers to build a FreeBSD kernel module, parse netlink messages and convert skbufs and mbufs.

Our module equals or exceeds the performance of the Linux one (reaching 600-700 Kpps with TAP interfaces). Our approach eases retaining feature parity as the original OVS is updated. This also includes much faster versions of OVS which we have in the works, using netmap/VALE as a dataplane.

Our work will also help porting further network-related kernel modules from Linux to FreeBSD, and provides a useful starting point for a complete, BSD-licensed version of the OVS dataplane.
</abstract>
        <description>OVS has two components: a userspace control plane, available for multiple platforms including FreeBSD; and a data plane in charge of moving packets around, with both userspace and kernel implementations. The in-kernel OVS dataplane, required to efficiently interconnect virtual machines, is a linux-only kernel subsystem.

With the obvious desire to provide FreeBSD with such as useful component, we looked at how to implement in-kernel OVS for FreeBSD, by reusing the Linux kernel code and building suitable adaptation layers.

As a result of our effort, we achieved a working FreeBSD openvswitchkernel module with approximately 1500 lines of new code, mostly to implement generic netlink sockets and netlink message parsing, and to convert between skbufs and mbufs.  Modifications to the existing files were minimal and mainly to address compiler issues (unnamed unions; missing const qualifiers and printf format warnings) and disable a handful of unsupported features.

One might rightly question our approach: the original linux-OVS kernel code is only about 8000 lines, and a complete rewrite would be feasible and could be done under a BSD license.

However, we believe that our choice was appropriate for a number of reasons: our module will support updates with almost no additional work, does not incur any performance penalty, helps testing the correctness of the userspace component of OVS,
and provides a suitable starting point for a BSD-licensed version of the code for interested parties.

We are working with the OVS developers to integrate some of our changes, and we plan to release the code soon for use into FreeBSD, either as a port or as in-tree kernel component.

The full paper/presentation will discuss the internal architecture of the in-kernel OVS dataplane, including performance issues, and give more details on the porting infrastructure.</description>
        <persons>
          <person id="101">Luigi Rizzo</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=Lr5o1VQMtgA&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=15">video</link>
        </links>
      </event>
      <event id="465">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>NAND Flash and FreeBSD</title>
        <subtitle>An Overview</subtitle>
        <track>Embedded</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>And overview of NAND technology, its relevance to FreeBSD, and a discussion of the advantages and disadvantages of the NANDFS and other nand technology in FreeBSD. The first part of this talk will be generally about NAND flash, and is applicable to embedded, PCIe-based flash storage and SSD. The second part of the talk focuses on those technologies in FreeBSD to talk to raw NAND, what can be deployed today, and what additional work will be necessary in the future.</abstract>
        <description>NAND Flash technology continues to be important to some market segments in which FreeBSD is deployed. This talk will be in two parts.

The first part of the talk will discuss NAND flash generally. The second part of the talk will focus on NAND in a FreeBSD context.

In the first part, an overview of AND flash will be presented. Basics about NAND generations, NAND storage strategies (SLC, MLC, TLC), characteristics of NAND, and operational considerations will be discussed. An overview of the trends in NAND evolution and their implications will be presented. The talk will explore how these features apply to SSDs and PCIe cards. This part of the talk will be of interest to anybody using these technologies either directly attached, or in a storage product.

The second part of the talk will be more focused on embedding FreeBSD, running FreeBSD from NAND and an exploration of the currently supported technology. Kernel configuration, build parameter and other details necessary to build a system will be presented. Creating a system image is a bigger challenge with NAND flash, because blocks on the part wear out and need to be retired (some blocks come from the factory this way), and how to compensate. The additional features need to be developed to deploy the latest NAND parts may be discussed. The second part of the talk will be more focused more on FreeBSD embedded systems using NAND.</description>
        <persons>
          <person id="31">Warner Losh</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=lj0XAE6C6-k&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=16">video</link>
        </links>
      </event>
      <event id="486">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>Capsicum and Casper - more than a lipstick on a pig</title>
        <subtitle>Don't build security on hacks</subtitle>
        <track>Security</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Capsicum and Casper are FreeBSD proposal for a clean, robust and intuitive application compartmentalization. Today's sandboxing techniques build on top of existing technologies that weren't really designed for this sort of protection (like chroot(2), rlimit(2), setuid(2), Mandantory Access Control, etc.). Capsicum and Casper provide rich infrastructure for breaking applications into multiple useful sandboxes and thus significantly reducing Trusted Computing Base.</abstract>
        <description>Capsicum is a lightweight OS capability and sandbox framework implementing a hybrid capability system model. The Casper daemon enables sandboxed application to use functionality normally unavailable in capability-mode sandboxes.

The talk will discuss Capsicum framework, Casper daemon and its services. It will provide introduction based on already implemented examples to those new FreeBSD features. The talk will also present existing portable sandboxing implementations to give clear picture how hacky those solutions are.</description>
        <persons>
          <person id="252">Mariusz Zaborski</person>
          <person id="47">Pawel Jakub Dawidek</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=0la06FHbdvg&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=13">video</link>
        </links>
      </event>
      <event id="479">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>Migrating from Linux to FreeBSD as a backend data store</title>
        <subtitle></subtitle>
        <track>System Administration</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>In this talk I would like to discuss the process I went through in replacing a research file server&#8217;s OS from Linux to FreeBSD and that of its backup system. Initially, the system was hosting a custom 32bit Gentoo Linux instance and was able to host approximately 2.5TB of data over two file systems backed by a RAID-5 software RAID implementation. 

The solution I implemented allowed me to leverage all the installed disks as one large ZFSv2 data volume by booting the system as a diskless FreeBSD system.  I then utilized istgt (an iSCSI target software package) to offer a large disk to one of the group&#8217;s 64bit Gentoo Linux compute nodes whereby I could then launch autofs and racoon services.

I would like to present this material to the BSDCan attendees to share my experience with others and to show that others can accomplish the same task without spending a large amount of money on proprietary software.</abstract>
        <description>In this talk I would like to discuss the process I went through in replacing a research file server&#8217;s OS from Linux to FreeBSD and that of its backup system. Initially, the system was hosting a custom 32bit Gentoo Linux instance and was able to host approximately 2.5TB of data over two file systems backed by a RAID-5 software RAID implementation. 

Unfortunately, due to the physical layout of the software RAID instances, if a drive failed, it was easy to physically replace and to schedule a maintenance window. However, when it came time to insert the drive replacement back into the applicable RAID volume the performance penalty for rebuilding the RAID volume was rather high. This caused the system to become unresponsive when users were trying to query or engage the file server to launch new software instances.

The solution I implemented allowed me to leverage all the installed disks as one large ZFSv2 data volume by booting the system as a diskless FreeBSD system.  I then utilized istgt (an iSCSI target software package) to offer a large disk to one of the group&#8217;s 64bit Gentoo Linux compute nodes whereby I could then launch autofs and racoon services (which in the Linux world means using IPSec to securely allow client machines to access file server resources in a very secure manner). The driving force behind using diskless FreeBSD is that if the research group wanted to expand their data store through the acquisition of additional storage gear the new server(s) could be booted as a diskless client, its disks configured as a ZFS data volume; leveraging istgt an additional disk would be offered to the 64bit Gentoo Linux compute node.

I would like to present this material to the BSDCan attendees to share my experience with others and to show that others can accomplish the same task without spending a large amount of money on proprietary software.</description>
        <persons>
          <person id="226">Dwayne Hart</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=AVuF9eFeVWs&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=14">video</link>
        </links>
      </event>
      <event id="460">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>FreeBSD bmake and meta mode</title>
        <subtitle></subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The Junos "meta mode" build is the coolest thing since sliced bread.  The FreeBSD projects/bmake branch provides a proof of concept for the more general use of this technology.
</abstract>
        <description>The latest release of FreeBSD uses bmake by default, a prerequisite for the "meta mode" build. This talk will cover the adoption of bmake and how the projects/bmake branch differs from traditional FreeBSD build.</description>
        <persons>
          <person id="149">Simon Gerraty</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=4s0UY0sg6vI&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=17">video</link>
        </links>
      </event>
    </room>
    <room name="Montpetit 207">
      <event id="477">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>IPv6 Transitioning mechanisms on the BSDs</title>
        <subtitle>Keeping one foot in two socks</subtitle>
        <track>System Administration</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The growth pace of IPv6 adoption is still slow, but constantly increasing, as more providers and networks migrate.  There is one aspect of the adoption that is still underestimated, and it's transition mechanisms, enabling networks speaking different protocols to talk to each other.  In may 2013, Switzerland jumped on top of IPv6 utilisation in the world by just having its incumbent operator enable one of these for a large base of its users.</abstract>
        <description>This talk will first introduce a handful of different transitioning mechanisms in use, picking the most widely used amongst the plethora of ones available.  In the second part, a live demonstration will show the audience how to set up some of them using native tools on OpenBSD and FreeBSD.

This talk is useful for those IT administrators who would like to get a grasp on implementing IPv6 in their network without going full native, while still offering services on the new protocol.</description>
        <persons>
          <person id="39">Massimiliano Stucchi</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=jo8ObzR1tKQ&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=3">video</link>
        </links>
      </event>
      <event id="447">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Userspace Networking with libuinet</title>
        <subtitle>A portable and performant TCP/IP stack-in-a-box</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>libuinet is a userspace library version of the FreeBSD TCP/IP stack that also includes extensions to the base stack functionality that make it particularly useful in network infrastructure equipment.

This talk will cover its design goals, implementation, current and potential uses, and performance.</abstract>
        <description>libuinet was originally conceived as a way to bring highly scalable transparent proxy functionality to the free, portable TCP proxy WANProxy (http://wanproxy.org).  To this end, libuinet extends the base FreeBSD TCP/IP stack feature set to include 'promiscuous sockets', which allow listens to capture connection attempts across VLANs (including nested), any IP address, and any port, admit/ignore those attempts based on an application-supplied filter, and retrieve the complete L2 and L3 details of admitted connections.  Promiscuous socket functionality also allows active connections to fully specify their L2 and L3 identity.  In this mode, libuinet has been shown to scale to 1 million active connections concurrent with 1 million listen sockets, with those million connections distributed in multiple ways across the VLAN and 4-tuple TCP addressing space.

Implementation of another extension to the stack, 'passive sockets', is currently underway and targeted for completion by the end of 1Q2014.  Passive sockets provide for reassembly of both data streams in a TCP connection, along with a missing-frame notification mechanism, based on a copy of the packet stream flowing between the connection endpoints (e.g., via a SPAN port).

Packet I/O is accomplished via network interface drivers that plug into the bottom of the stack in the usual way, with a netmap interface being the current example.  Providing additional interfaces is a straightforward exercise.

Care has been taken in the implementation to make the library self-contained and straightforward to keep up-to-date via merging in later FreeBSD releases, as well as to make it reasonably portable to other UNIX-like systems (and beyond, although with some additional effort).

libuinet is a useful building block for network infrastructure devices, including security, monitoring and WAN optimization applications, and is a potentially useful tool for network protocol research.</description>
        <persons>
          <person id="236">Patrick Kelsey</person>
        </persons>
        <links>
          <link href="https://github.com/pkelsey/libuinet">libuinet source code</link>
          <link href="https://www.youtube.com/watch?v=LhIx8q8_7YY&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=5">video</link>
        </links>
      </event>
      <event id="516">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug>ipv6address</slug>
        <title>Developing an IPv6 addressing plan</title>
        <subtitle>lunch time BOF</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>Come along and learn some simple techniques which will simply your IPv6 addressing.</abstract>
        <description>Not using everything is key</description>
        <persons>
        </persons>
        <links>
        </links>
      </event>
      <event id="471">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Optimizing GELI Performance</title>
        <subtitle>reducing encryption overhead</subtitle>
        <track>Security</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Features, like encryption, need to have minimal overhead for them to be widely adopted.  If the performance is to slow, few people will use it.  The first iteration of AES-XTS using AES-NI in FreeBSD was not much faster than the software version of it.  The talk will describe why the AES-XTS algorithm was slow and what was done to improve it.  It will cover topics from intrinsics, adding them to gcc and advantages of using them over assembly to how to use HWPC that are included in most modern processors to evaluate performance to identify performance bottle necks.</abstract>
        <description>Optimizing code first starts with measuring the performance, but it also requires you to understand the parts of the system so that you can decide if increasing performance is possible.

It will cover:
1) Cipher modes and their performance impact
2) Processor performance, understanding pipelining, throughput and latency
3) Other SSE instructions used for XTS tweak factor calculations
4) Intrinsics and their use with GCC and CLANG
5) Using pmcstat and kcachegrind for understand performance.
6) Possible future work to increase the performance beyond what it is today.</description>
        <persons>
          <person id="239">John-Mark Gurney</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=2qicD0tv_tI&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=7">video</link>
        </links>
      </event>
      <event id="472">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Shellscripts and Commands</title>
        <subtitle>practical development method from large-scale academic research to mission-critical business system</subtitle>
        <track>Hacking</track>
        <type></type>
        <language>en</language>
        <abstract>Shellscripts and Commands: practical development method from large-scale academic research to mission-critical business system</abstract>
        <description>Universal Shell Programming Liboratory has developed many kinds of mission-critical business systems for many companies based on their own unique and innovative development method for SI and big-data processing. The main idea of that might be too simple to believe in: text files, commands and shellscripts. You can convert almost any kind of your data into text. Then the development method tells you how to organize your data in what directories. As a result, it realizes fast processing and easy coding. This method is applicable in many areas, from as small tools to larg-scale data processing. I describe their development method in a tangible way using Open usp Tukubai and FreeBSD.</description>
        <persons>
          <person id="229">Daichi GOTO</person>
        </persons>
        <links>
          <link href="https://en.usp-lab.com/">Universal Shell Programming Laboratory, Ltd.</link>
          <link href="https://www.bsdconsulting.co.jp/">BSD Consulting, Inc</link>
          <link href="https://www.youtube.com/watch?v=MsRu0xIawaA&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=9">video</link>
        </links>
      </event>
      <event id="450">
        <start>16:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Keeping Current</title>
        <subtitle>Maintaining an internal fork of FreeBSD</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Detailed discussion of tips, tools and strategies for maintaining internal software forks with a particular emphasis on FreeBSD and its use in EMC's Isilon Storage Division.</abstract>
        <description>Occasionally you need to fork a project. You probably still want to track the upstream version but you've got local modifications you need to maintain. The EMC Isilon Storage Division does this with FreeBSD in a big way.

This presentation will go through what happens when you don't keep up to date and how you can get back up to date in a way that can still mesh with your release process. It'll also go through tools you can use to help the process along and keep your project managers happy and strategies for making sure you don't get behind again. </description>
        <persons>
          <person id="237">Benno Rice</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=jZp-ciB6mAg&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=8">video</link>
        </links>
      </event>
    </room>
    <room name="Morisset 211">
    </room>
    <room name="Morisset 212">
      <event id="490">
        <start>10:00</start>
        <duration>06:00</duration>
        <room>Morisset 212</room>
        <slug></slug>
        <title>FreeBSD Dev Summit</title>
        <subtitle>public track</subtitle>
        <track>FreeBSD Developers Summit</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>This is a place holder.</abstract>
        <description>Individual talks will be added to the schedule closer to the conference dates.</description>
        <persons>
          <person id="1">Dan Langille</person>
          <person id="186">Justin T. Gibbs</person>
        </persons>
        <links>
          <link href="https://wiki.freebsd.org/201405DevSummit#May16th">List of talks and times</link>
        </links>
      </event>
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
    </room>
    <room name="Out and About">
    </room>
    <room name="Hacker Lounge - L140">
      <event id="495">
        <start>18:00</start>
        <duration>06:00</duration>
        <room>Hacker Lounge - L140</room>
        <slug></slug>
        <title>Hacker Lounge</title>
        <subtitle>meet, greet, hack</subtitle>
        <track>Social</track>
        <type>other</type>
        <language>en</language>
        <abstract>The hacker lounge is on the ground floor of residence.  Bring your laptop, enjoy.

This room is located just past the lobby.  You may need to ask for the key at the desk. </abstract>
        <description>Proper behaviour is expected, or you'll be asked to leave.  :)  If you must ask what proper behaviour is, well, it sounds like you shouldn't be there.

The starting time is flexible, so is the ending time.  Just show up.  wifi will be available.

In order to play nicely with others, please bring an extension cord / power strip.

Please keep this room tidy and clean.</description>
        <persons>
          <person id="1">Dan Langille</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
      <event id="489">
        <start>12:30</start>
        <duration>02:00</duration>
        <room>University Center 206</room>
        <slug>bsda2</slug>
        <title>BSDA</title>
        <subtitle>BSD Certification</subtitle>
        <track>Exams</track>
        <type>other</type>
        <language>en</language>
        <abstract>Take the BSDA certification.</abstract>
        <description>The BSD Certification Group Inc. is a non-profit organization committed to creating and maintaining a global certification standard for system administration on BSD based operating systems.

YOU MUST register and pay for this event.  See the link for details.</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
          <link href="https://register.bsdcertification.org/step-2-select-an-exam-event-or-testing-center">Register here</link>
        </links>
      </event>
      <event id="515">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>University Center 206</room>
        <slug></slug>
        <title>ZFS BOF</title>
        <subtitle></subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>nil</abstract>
        <description>nil</description>
        <persons>
          <person id="242">Matt Ahrens</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="University Center 301">
    </room>
  </day>
  <day date="2014-05-17" index="5">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
      <event id="459">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>new trends in mandoc</title>
        <subtitle>enhancing the modern toolbox for the classic documentation formats</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Since its first presentation at BSDCan 2011, the mandoc(1) documentation formatting system has gained a lot of traction in all four major BSD operating systems and beyond.  This talk will provide an update regarding recent feature additions, in particular the mdoc(7) to man(7) converter to produce high quality manual formatting for portable software packages, and the new SQLite3-based mandocdb(8) utility, a drop-in replacement for the traditional makewhatis(8)/apropos(1) combo, providing markup-sensitive search capabilities and flexible search result output formats.

I will give an overview of the adoption status of mandoc(1) and mandocdb(8) in OpenBSD, DragonFly, NetBSD, and FreeBSD as well as a few other free operating systems, comment on mandoc versus
groff usage in the OpenBSD ports tree including recommendations for handling manuals in packaging systems in general, and comment on possible future development directions.</abstract>
        <description>During its first three years of being the only documentation formatter in the OpenBSD base system, the mandoc(1) utility has matured considerably. While we certainly continue tuning mandoc to bring its output even closer to groff(1) output, development focus has shifted from implementating basic features and fixing bugs to extending its scope beyond the mere formatting of manuals.

After a brief introduction explaining the advantages of mdoc(7) as the markup language for writing manuals and of mandoc(1) as the manual formatter, this talk will focus on two features recently added to mandoc:

1. The mandoc -Tman output mode for converting hand-written mdoc(7) documents into autogenerated man(7) code.  The talk will explain how to use this to produce high quality documentation for portable software packages.  The portable sudo(8) distribution will be used as an example.

2. The usage, implementation, optimization, and performance of the SQLite3-based mandocdb(8) utility, a drop-in replacement for the traditional makewhatis(8) program, in concert with the SQLite3-based apropos(1) replacement.  These tools add markup-sensitive search capabilities and flexible output formats to the traditional apropos(1) functionality.  To name some examples, they let you specifically search for include file names, function and argument types, function argument names, variable types and names, preprocessor constants, error constants, environment variables, command arguments and flags, file system paths, kernel configuration directives, author names, standards, operating system releases and cross references across all manuals installed on the local machine.  They support complex search queries supporting "or" and "and" operators and parentheses, and they allow to show the contents of user-chosen macros in place of the usual (Nd) description line in the output.</description>
        <persons>
          <person id="146">Ingo Schwarze</person>
        </persons>
        <links>
          <link href="http://mdocml.bsd.lv/">mandoc homepage</link>
        </links>
      </event>
      <event id="469">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Taking the red pill</title>
        <subtitle>Charting the rabbit hole to improve FreeBSD performance on Xen</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The Xen hypervisor is a Open Source Type 1 hypervisor, it's widely used on production environments like Amazon EC2 and Rackspace. Since it's inception, one of the focuses of Xen was to be an OS agnostic hypervisor, allowing any kind of OS (with proper Xen support) to act as DomU/Dom0.

This talk will cover how the Xen community works, together with an explanation of the ongoing work in FreeBSD in order to improve Xen support.</abstract>
        <description>This talk will cover the following points:

- Basic Xen description and specific Xen concepts.
- How the Xen community works (compared to BSD communities).
- A look into new Xen features (PVH).
- Work being done in FreeBSD improving Xen support.
- Probably a small demo to highlight Xen features.</description>
        <persons>
          <person id="240">Roger Pau Monn&#233;</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=q6l9qtjlNXU&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=2">video</link>
        </links>
      </event>
      <event id="518">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug>ezjail</slug>
        <title>ezjail</title>
        <subtitle>lunch time BOF</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>ezjail is a great tool for managing jails on FreeBSD</abstract>
        <description>Come along and learn from others.</description>
        <persons>
          <person id="214">Allan Jude</person>
          <person id="1">Dan Langille</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="452">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Introducing ASLR in FreeBSD</title>
        <subtitle></subtitle>
        <track>Security</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>Address-space layout randomization (ASLR) has existed in many operating systems for a number of years. The most famous implementation is the PaX patch for Linux's kernel. This presentation introduces and announces an ASLR implementation based on PaX for FreeBSD/amd64. Details regarding how ASLR has been ported to FreeBSD and some advanced features will be presented.</abstract>
        <description>FreeBSD will soon be getting a port of PaX to 11-CURRENT/amd64. This presentation details changes to how ELF executables are loaded in memory and innovative workarounds for legacy applications that don't support (or misbehave) ASLR. Jails can have their own ASLR settings. Misbehaving applications can be run in a jail with ASLR turned off, while ASLR remains turned on in the other jails and in the host.</description>
        <persons>
          <person id="238">Shawn Webb</person>
        </persons>
        <links>
          <link href="http://0xfeedface.org/blog/lattera/2013-11-16/freebsd-aslr-progress">Current ASLR Status</link>
          <link href="https://www.youtube.com/watch?v=q6l9qtjlNXU&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=2">video</link>
        </links>
      </event>
      <event id="445">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Jenkins, BHyve, and WebDriver: Continuous Integration Testing on FreeNAS</title>
        <subtitle></subtitle>
        <track>Hacking</track>
        <type></type>
        <language>en</language>
        <abstract>During the software development lifecycle (SDLC), it is highly desirable that developers can rapidly work on new features, integrate their code into the main codebase, and not break existing functionality.

Continuous Integration (CI) is a technique where code is continuously integrated, built, and tested.  Jenkins ( http://www.jenkins-ci.org ) is a CI framework which is used by many software organizations
to do integration, building, and testing of code.  Jenkins is flexible and extensible by hundreds of plugins.
</abstract>
        <description>This talk will describe how the FreeNAS project uses Jenkins for doing automated software builds.  This talk will also cover how the BSD Hypervisor (BHyVe) is used for booting and testing FreeNAS images.  The talk will also discuss how WebDriver is used for automating some of the web-based testing for FreeNAS.</description>
        <persons>
          <person id="132">Craig Rodrigues</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="501">
        <start>18:00</start>
        <duration>04:00</duration>
        <room>Montpetit 201</room>
        <slug></slug>
        <title>Doc Sprints</title>
        <subtitle>Doc Sprints</subtitle>
        <track>BOF</track>
        <type>meeting</type>
        <language>en</language>
        <abstract>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.</abstract>
        <description>This doc sprint is open to both committers and anyone interested in helping to improve the documentation set (handbook, guides, man pages, website) for any of the BSD projects.

FreeBSD committers will be available to assist non-committers in getting started with the FreeBSD documentation set, learning the workflow and how to make changes, and to approve and commit patches. Committers will also work on closing doc PRs and discuss proposed changes to the documentation.

Feel free to drop by and help out!</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="Montpetit 202">
      <event id="462">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>The FreeBSD Test Suite</title>
        <subtitle>An introduction</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>FreeBSD has seen the birth of its test suite in 2013 and, while the result is heavily based on experience gained in the NetBSD project, there are significant differences between the two.

Come to this talk to learn what the FreeBSD test suite is by looking at the various design choices, the tools in use, the roadmap to the final product and, if you are into coding, some actual examples of tests and the process to plug them into the suite.</abstract>
        <description>FreeBSD has been in the need for an automated test suite for a long time. During the last few years, various alternatives have been investigated and, finally, the beginnings of a tangible test suite surfaced in 2013. The FreeBSD test suite is now a reality: the system builds and installs tests out of the box; the test suite can be trivially executed with a single command; the testing cluster is up and running, publishing results for test runs about twice per hour; and there is a lot of ongoing work to make the current setup better.

This talk will provide you with a general overview of the new FreeBSD test suite, both from the perspective of an end user and of a developer. We will cover many different areas, including but not limited to: the structure of the test suite, covering the use of Kyua as the run-time engine and the various "frameworks" available to implement test programs; the set up of the continuous testing cluster, to understand how its activity benefits developers; the differences between the FreeBSD and NetBSD test suites, and how the two will eventually converge; the future plans for the test suite, especially in the area of reporting and kernel-level testing; and, to conclude, we will get our hands dirty by seeing actual code for a bunch of simple tests. You will hopefully get a sense of the non-existent difficulty to start writing tests en-masse!</description>
        <persons>
          <person id="139">Julio Merino</person>
        </persons>
        <links>
          <link href="http://wiki.freebsd.org/TestSuite">FreeBSD Test Suite (project page)</link>
          <link href="http://code.google.com/p/kyua">Kyua (project page)</link>
          <link href="http://julipedia.meroh.net/2013/12/introducing-freebsd-test-suite.html">Introducing the FreeBSD test suite (bog post 2013-12-31)</link>
          <link href="http://goo.gl/1SCfgv">slides</link>
        </links>
      </event>
      <event id="473">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>The architecture of the new solver in pkg</title>
        <subtitle></subtitle>
        <track>FreeBSD Developers Summit</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>In the context of package management, the solver is an algorithm (or set of algorithms) to resolve dependencies and conflicts.  The solver must handle options, upgrades, multiple repos, locally installed software, as well as other factors. The upcoming 1.3 release of pkg will have the new solver that has some important consequences.

This talk is dedicated to the design concepts of the new solver in pkg management system (pkg-ng initially). In this talk, I describe the basic architecture of the solver, ideas used and the consequences of using this algorithm. Moreover, this talk describes the proposed pkg and ports architecture to simplify binary packages and ports using for all FreeBSD users.</abstract>
        <description>The proposed talk is oriented to the wide auditory of FreeBSD users and describes the architectural design of pkg and ports that is going to be implemented. I concentrate on the following topics:

- the interaction of ports and packages
- how pkg may be used for ports management
- what are the alternatives used by other packages management systems (yum/apt/zypper/MacPorts)
- the basic description of the SAT problem and how this algorithm can be applied to packages management
- multiple repos handling
- the improved support of custom options
- advanced conflicts and dependencies
- fine-grained packages distribution
- base system interaction
- the speed estimations

This talk is intended to improve the understanding of pkg internals and the future plans of FreeBSD packages and ports development.</description>
        <persons>
          <person id="249">Vsevolod Stakhov</person>
        </persons>
        <links>
          <link href="http://www.slideshare.net/VsevolodStakhov/new-solver-for-freebsd-pkg">The slides of ruBSD presentation</link>
          <link href="http://">http://</link>
        </links>
      </event>
      <event id="521">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>OpenBSD/LibreSSL</title>
        <subtitle>and related projects BOF</subtitle>
        <track>BOF</track>
        <type>workshop</type>
        <language>en</language>
        <abstract>There are a number of developers here, as well as foundation representation.</abstract>
        <description>Anyone interested in anything related to OpenBSD and/or LibreSSL can attend and ask us all questions and chat.</description>
        <persons>
          <person id="220">Bob Beck</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="449">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>Transparent Superpages for FreeBSD on ARM</title>
        <subtitle></subtitle>
        <track>Embedded</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The talk covers recent work on providing transparent superpages support for the FreeBSD operating system on ARM. The concept of superpages is a virtual memory system optimization, which allow for efficient use of the TLB translations, effectively reducing the overhead related to the memory management. This technique can significantly increase system's performance at the interface between CPU and main memory thus affecting its overall efficiency.</abstract>
        <description>The lecture focuses on presenting superpages mechanism supported by the FreeBSD in the context of its implementation for the ARM architecture. Principles of the virtual memory operations are briefly presented to illustrate the requirements and limitations standing before the related subsystem. The talk provides description of the virtual memory system architecture introduced in ARMv6/v7 compliant processors and the opportunities to take advantage of the superpages technique.

The primary focus of the presentation is to elaborate on how the superpages functionality was implemented on FreeBSD/arm and what are the results of its application. The talk presents real-life measurements and benchmarks performed on modern, multiprocessor ARM platforms. Hence, the actual achievements and areas of application are shown. Finally, the article summarizes the integration process to the mainline FreeBSD and discusses the areas of future work and improvements.</description>
        <persons>
          <person id="182">Zbigniew Bodek</person>
        </persons>
        <links>
          <link href="http://wiki.freebsd.org/ARMSuperpages">Wiki page on FreeBSD.org</link>
          <link href="http://community.arm.com/groups/processors/blog/2013/11/13/transparent-superpages-for-freebsd-on-arm">Article on ARM Blogs</link>
        </links>
      </event>
      <event id="461">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug></slug>
        <title>FreeBSD and Beaglebone Black, a robotic application.</title>
        <subtitle>FreeBSD and the ARM based Beaglebone Black board. Demonstrating a ROV with I/O and video streaming.</subtitle>
        <track>Embedded</track>
        <type>podium</type>
        <language>en</language>
        <abstract>An embedded ROV powered by FreeBSD and Beaglebone Black.  It demonstrates the usage of the flattened device tree (FDT) plus video streaming by WIFI and motor drivers remote control. Opencv features and power actuators by MOSFET drivers.</abstract>
        <description>This talk is about a remotely operated vehicle (ROV) with I/O management for sensors and motor drivers. The system runs FreeBSD and offers a webGUI over WIFI to control the movements and watch a video streaming from the onboard camera.
The platform used is the popular embedded board Beaglebone Black with a custom cape (shield) on top for the I/O connectivity. Beaglebone Black is an ARMv7 system with integrated RAM and flash memory for the root filesystem, it offers many more capabilities such as input/output pins ready to connect to sensors and actuators. BBB has enough processing power and speed for Opencv tasks, networking, web services and GPIOs I/O. This robot can be controlled remotely by a joystick or using the controls on the web GUI.  To manage GPIOs and the output for the motor drivers, it was used the FreeBSD flattened device tree (FDT). To keep the system reliable and fast, a custom kernel was compiled and the system environment was carefully prepared.

The list of features available:
-Remote control of the motors via WIFI (webGUI or Joystick)
-WIFI hotspot
-Video streaming from the onboard camera
-MOSFET actuators 
-Sensors collection to gather environmental data
-OpenCV video features
-Stepper motors to move a robotic arm and video camera
-webGUI with websockets</description>
        <persons>
          <person id="241">Fabio Balzano</person>
        </persons>
        <links>
          <link href="http://beagleboard.org/products/beaglebone%20black">http://beagleboard.org/products/beaglebone%20black</link>
          <link href="https://wiki.freebsd.org/FlattenedDeviceTree">https://wiki.freebsd.org/FlattenedDeviceTree</link>
        </links>
      </event>
      <event id="494">
        <start>16:15</start>
        <duration>01:00</duration>
        <room>Montpetit 202</room>
        <slug>close</slug>
        <title>Closing session</title>
        <subtitle>The wrap up</subtitle>
        <track>Plenary</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The closing</abstract>
        <description>Fun.  Games.  Awards.</description>
        <persons>
          <person id="1">Dan Langille</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=ryTLPEJ-1wc">video</link>
        </links>
      </event>
    </room>
    <room name="Montpetit 207">
      <event id="520">
        <start>10:00</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>LibreSSL</title>
        <subtitle>The first 30 days, and what the Future Holds</subtitle>
        <track>Security</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>LibreSSL is a recently started initiative by the OpenBSD project to fork and clean up the OpenSSL code base. We have been working on this rather intensively for about a month now.
</abstract>
        <description>I will be discussing the Origins of LibreSSL (The OpenBSD Fork of OpenSSL) - including why we decided to fork, what we are hoping to achieve, as well as a number of examples of the sorts of code changes we are doing, and the sorts of issues we have found in the code base and how we are changing things.  All who are potentially interested in something better than OpenSSL may find this talk of interest.
</description>
        <persons>
          <person id="220">Bob Beck</person>
        </persons>
        <links>
          <link href="http://www.libressl.org/">LibreSSL project</link>
          <link href="http://www.openbsd.org/papers/bsdcan14-libressl/">slides</link>
          <link href="https://www.youtube.com/watch?v=oM6S7FEUfkU&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=18">video</link>
        </links>
      </event>
      <event id="466">
        <start>11:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>OpenZFS: upcoming features and performance enhancements</title>
        <subtitle></subtitle>
        <track>Invited Talks</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>The OpenZFS project provides a common development hub for all platforms working with open source ZFS code. Currently, it is easy to pull changes from Illumos into FreeBSD, but it is more difficult to submit changes from FreeBSD to Illumos. </abstract>
        <description>This talk will discuss how OpenZFS will enable ZFS code and ideas to flow easily between the Illumos, FreeBSD and ZFS on Linux communities. In addition, I will present several important features and performance enhancements to ZFS in FreeBSD, and also discuss forthcoming enhancements that are in the planning phase.</description>
        <persons>
          <person id="242">Matt Ahrens</person>
        </persons>
        <links>
          <link href="https://www.youtube.com/watch?v=EjGqVdCOIhM&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=10">video</link>
        </links>
      </event>
      <event id="522">
        <start>12:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>NFSv4/pNFS</title>
        <subtitle>BOF</subtitle>
        <track>BOF</track>
        <type>other</type>
        <language>en</language>
        <abstract>NFSv4/pNFS BOF</abstract>
        <description>see above</description>
        <persons>
          <person id="1">Dan Langille</person>
        </persons>
        <links>
        </links>
      </event>
      <event id="448">
        <start>13:30</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Introduction to FreeNAS development</title>
        <subtitle>FreeNAS development</subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>FreeNAS has been around for several years now, however, development on it has been by very few people. Even with corporate sponsorship and a team of full time developers, outside interest has been minimal. </abstract>
        <description>Not a week goes by when a bug report or feature request is not filed. Documentation on how to develop on FreeNAS simply does not exist. Currently, the only way to come up to speed on FreeNAS development is to obtain the source code, read through it, modify it and verify it works. The goal of this talk is to create a simple FreeNAS application to demonstrate some of the common methods used when dealing with FreeNAS development, as well as showcase some of the API. </description>
        <persons>
          <person id="211">John Hixson</person>
        </persons>
        <links>
          <link href="http://www.freenas.org">FreeNAS website</link>
        </links>
      </event>
      <event id="483">
        <start>15:00</start>
        <duration>01:00</duration>
        <room>Montpetit 207</room>
        <slug></slug>
        <title>Features and status of FreeBSD's Ext2 implementation</title>
        <subtitle></subtitle>
        <track>Hacking</track>
        <type>lecture</type>
        <language>en</language>
        <abstract>While FreeBSD has been experiencing a huge momentum with ZFS and UFS2 continues to improve in exciting ways, another UFS variant has seen some advances: Ext2fs is trying to catch up with the new times.</abstract>
        <description>FreeBSD's ext2 implementation has a huge history: it started it's life as part of BSD-Lites for CMU's Mach. It got ported to FreeBSD and after some rust gathering it eventually got important merges from NetBSD's port so now it is completely GPL free and is supporting new features.

Ext2 uses many concepts that are based on UFS but, for good or for bad, Ext2 has never been considered important enough to compete with the local UFS filesystem in the BSDs.  Both filesystems have also taken different design decisions over the years and it is not always clear which developments are a clear win on either side.  The core of both filesystems is indeed very similar and that similarity has made it relatively easy to adopt in FreeBSD's Ext2fs many enhancements based on FreeBSD's UFS support.  Recent years have seen some developments based on successful Google Summer of Code Projects so FreeBSD's driver has support for the directory index and read-only support for extents.

This talk presents the recent developments in ext2fs for FreeBSD and attempts to compare the linux ext2/3/4 features with the typical UFS filesystem in the BSDs.</description>
        <persons>
          <person id="174">Pedro Giffuni</person>
        </persons>
        <links>
          <link href="https://wiki.freebsd.org/Ext2fs">FreeBSD's Ext2 wiki</link>
          <link href="https://www.youtube.com/watch?v=HMeTxViulgo&amp;list=PL2BmtSoZtRyBzTDkJRt3nXZOnj12vXQ3c&amp;index=11">video</link>
        </links>
      </event>
    </room>
    <room name="Morisset 211">
    </room>
    <room name="Morisset 212">
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
    </room>
    <room name="Out and About">
    </room>
    <room name="Hacker Lounge - L140">
      <event id="491">
        <start>18:00</start>
        <duration>05:00</duration>
        <room>Hacker Lounge - L140</room>
        <slug></slug>
        <title>Hacker Lounge</title>
        <subtitle>meet, greet, hack</subtitle>
        <track>Social</track>
        <type>other</type>
        <language>en</language>
        <abstract>The hacker lounge is on the ground floor of residence.  Bring your laptop, enjoy.

This room is located just past the lobby.  You may need to ask for the key at the desk. </abstract>
        <description>Proper behaviour is expected, or you'll be asked to leave.  :)  If you must ask what proper behaviour is, well, it sounds like you shouldn't be there.

The starting time is flexible, so is the ending time.  Just show up.  wifi will be available.

In order to play nicely with others, please bring an extension cord / power strip.

Please keep this room tidy and clean.</description>
        <persons>
        </persons>
        <links>
        </links>
      </event>
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
      <event id="493">
        <start>12:30</start>
        <duration>02:00</duration>
        <room>University Center 206</room>
        <slug>bsda1</slug>
        <title>BSDA</title>
        <subtitle>BSD Certification</subtitle>
        <track>Exams</track>
        <type>other</type>
        <language>en</language>
        <abstract>Take the BSDA certification.</abstract>
        <description>The BSD Certification Group Inc. is a non-profit organization committed to creating and maintaining a global certification standard for system administration on BSD based operating systems.

YOU MUST register and pay for this event.  See the link for details.</description>
        <persons>
          <person id="10">Dru Lavigne</person>
        </persons>
        <links>
          <link href="https://register.bsdcertification.org/step-2-select-an-exam-event-or-testing-center">Register here</link>
        </links>
      </event>
    </room>
    <room name="University Center 301">
    </room>
  </day>
  <day date="2014-05-18" index="6">
    <room name="Morisset 015">
    </room>
    <room name="Montpetit 201">
    </room>
    <room name="Montpetit 202">
    </room>
    <room name="Montpetit 207">
    </room>
    <room name="Morisset 211">
    </room>
    <room name="Morisset 212">
    </room>
    <room name="Morisset 250">
    </room>
    <room name="Royal Oak Pub">
    </room>
    <room name="Out and About">
      <event id="496">
        <start>10:00</start>
        <duration>06:00</duration>
        <room>Out and About</room>
        <slug>tourist</slug>
        <title>Tourist stuff</title>
        <subtitle>Spend some time exploring</subtitle>
        <track>Social</track>
        <type>other</type>
        <language>en</language>
        <abstract>Explore Ottawa</abstract>
        <description>This is a self-led tour.  Nobody will be there to guide you.  This is a suggested location where you can meet and decide where to go from there.

Ottawa has a large number of great attractions.  Spend some time looking around and explore.  Spend as much time as you want with us, or leave early.  We will walk everywhere we go.  Wear sensible shoes. Bring your camera.  We'll probably have lunch somewhere along the way.  Consider the weather (sun block, rain coat, umbrella, swim suit).

We will depart from the National Memorial at 9:30 AM *if the weather is good*.

If it's raining, we'll assemble in the lobby of Residence instead (same time).

If you have ideas/suggestions/plans, please let others know via the forum.  From that list, we'll decide what to do on the day.</description>
        <persons>
          <person id="1">Dan Langille</person>
        </persons>
        <links>
          <link href="http://maps.google.ca/maps/ms?ie=UTF8&amp;hl=en&amp;t=h&amp;msa=0&amp;msid=115376119403106089489.000468dc2232e50072e40&amp;ll=45.423094,-75.690479&amp;spn=0.029759,0.055189&amp;z=14&amp;iwloc=000468dc2480096f4f9f3">National Memorial</link>
          <link href="http://maps.google.ca/maps/ms?ie=UTF8&amp;hl=en&amp;t=h&amp;msa=0&amp;msid=115376119403106089489.000468dc2232e50072e40&amp;ll=45.424058,-75.690479&amp;spn=0.029759,0.055189&amp;z=14&amp;iwloc=000468dc248009063acf6">Residence</link>
          <link href="https://www.bsdcan.org/phorum/list.php?f=9">Forum</link>
        </links>
      </event>
    </room>
    <room name="Hacker Lounge - L140">
    </room>
    <room name="University Center 205">
    </room>
    <room name="University Center 206">
      <event id="497">
        <start>10:00</start>
        <duration>04:00</duration>
        <room>University Center 206</room>
        <slug></slug>
        <title>BSD Professional (BSDP) Certification</title>
        <subtitle>Take the BSDP Professional Beta Lab Exam</subtitle>
        <track>Exams</track>
        <type>other</type>
        <language>en</language>
        <abstract>The BSD Certification Group Inc. is pleased to announce the availability of the BSDP Beta Lab Exam.  This exam is a hands-on exam that will test your ability to configure up to three BSD systems according to a set of instructions.
</abstract>
        <description>Exam laptop workstations (with US keyboard layout) will be provided. 

Limited availability (10 seats) - first come, first served.

YOU MUST register and pay for this event.  

(Payment for this Beta Lab Exam is to help offset the cost of equipment rental.)

More information and registration are [here](https://register.bsdcertification.org/events/bsdp-lab-beta).
</description>
        <persons>
          <person id="133">Jim Brown</person>
        </persons>
        <links>
          <link href="http://www.bsdcertification.org/certification/certification/bsd-professional">You can read more about the BSD Professional exam here</link>
          <link href="http://www.bsdcertification.org/downloads/certreq-bsdp-en.pdf">The BSD Professional exam objectives</link>
        </links>
      </event>
    </room>
    <room name="University Center 301">
    </room>
  </day>
</schedule>
