OpenBSD Journal

Slides from OpenCON Presentations Posted

Contributed by jolan on from the slide-slide-slippity-slide dept.

Slides are now available from all of the presentations which were given by OpenBSD developers at OpenCON 2005:
  • OpenBSD Hackathon Report by Peter Valchev
  • Exploit Mitigation Techniques by Theo (update of his old talk to include random malloc and mmap work)
  • OpenBSD Networking Update by Henning
  • OpenBSD Ports and Packages by Marc Espie
  • Porting OpenBSD by Niall and Uwe (PDF warning!)

    • Given the diverse parts of OpenBSD that the presentations all cover, there should be something to pique your interest, irrespective of whatever your interest in OpenBSD is.

    Also, lots of photos from the hackathon and OpenCON events have been posted. The gallery has an issue with some of the pictures where clicking the thumbnail reveals a smaller image. I'm told this will be rectified soon.

    (Comments are closed)

    Comments

    1. By Shane J Pearson (202.45.125.5) on

      is this the new Sun X2100?

      Comments

      1. By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on http://www.benzedrine.cx/dhartmei.html

        Yes, it is! :)

        Here's a picture of the open box and the rack.

        It's now running 3.8-stable (dmesg) and holding up very well (top(1), pfctl -si output). Full userland build is about 40 minutes.

        Many thanks to Kurt Seifried for his help with ordering and setting up the box. It's located in Edmonton, Alberta, Canada, at tera-byte.com.

        Page output appears to be quite fast, too, from here. Please let me know if you notice anything peculiar (or just that it's slower/faster now).

        Comments

        1. By SH (82.182.103.172) on

          Heh, isn't ksh(1) recommended as an alternative shell for users addicted to bash ;-) 

          load averages:  0.39,  0.42,  0.37                                                             05:49:43
23 processes:  22 idle, 1 on processor
CPU states:  0.0% user,  0.0% nice,  0.2% system,  0.0% interrupt, 99.8% idle
Memory: Real: 13M/101M act/tot  Free: 388M  Swap: 0K/2098M used/tot

  PID USERNAME PRI NICE  SIZE   RES STATE    WAIT     TIME    CPU COMMAND
....
28382 dhartmei  10    0  976K 2092K sleep    wait     0:00  0.00% bash

          Comments

          1. By Daniel Hartmeier (62.65.145.30) daniel@benzedrine.cx on http://www.benzedrine.cx/dhartmei.html

            Yes, you're right. I've been using bash simply because I want the same shell on all boxen (including non-OpenBSD ones), and haven't check on ksh in a while. Let's do a little experiment:

            # cat ~/.bashrc ~/.bash_profile >~/.profile
# chsh -s /bin/ksh
# pkg_delete bash-3.0.16p1
            On first and second glance, everything is the same. Line editing, PS1 placeholders, etc. work the same. Uses less memory, is BSD licensed, and doesn't require a package install. If I notice any difference, I'll let you know :)

        2. By Chris Snell (209.142.99.217) on http://chrissnell.com

          Are you doing anything RAID-wise with the disks? I can't wait for the SAS controller in the X4100 to be supported. I'm placing my order on the day I get a positive report. :) Chris

        3. By Anonymous Coward (81.57.42.108) on

          Please let me know if you notice anything peculiar (or just that it's slower/faster now). Well then: it's faster. Not that it wasn't fast enough before, for an undeadly.org user viewpoint.

    2. By Dan (212.199.205.65) on

      I got few question about the fast path idea: 1. Is is gonna happen in a single interrupt? 2. Compared to cisco, is it gonna be like CEF or like Netflow (netflow as a swtching path)? Sound very interesting, guess ip_input gonna be dulicated

      Comments

      1. By Tim (145.99.203.166) on

        How far did you progress with the OpenOffice.org port?

        Comments

        1. By Mitja (193.77.15.113) on

          Last I heard was that the port had 300 or so patches and still not building right.... A gigantic task.

          Comments

          1. By Anonymous Coward (193.63.217.208) on

            Will the changes be contributed back to OO.org? I'm assuming they will be...

            Anyone have a handle on how well projects receive patches from OpenBSD? Are they integrated? Rejected? Ignored? The new strict memory checks are great for finding bugs but if the original projects don't accept patches it only helps OpenBSD users. They are the only people that matter I guess ;) but it seems like a waste of valuable porter time to maintain patches (esp 300+) because the original project doesn't use the patches.

      2. By henning (213.39.134.228) henning@ on

        I got few question about the fast path idea: 1. Is is gonna happen in a single interrupt?

        no.
        that would be very very very stupid.
        you are way too limited in interrupt context. in int context, the mbufs are going to be placed in ipintrq, and everything else runs in softint context. then everything at once tho, unless another interrupt happens.
        plus, if you ran all this in int context (and thus high spl level), you'd block the machine for way too long. that leaves potential for very very very dangerous DoS atacks too.

        2. Compared to cisco, is it gonna be like CEF or like Netflow (netflow as a swtching path)?

        guess more like CEF, but I am not too familar with their internals.

        Sound very interesting, guess ip_input gonna be dulicated

        no, there is no need to duplicate ip_input

      3. By Daniel Melameth (63.228.76.214) daniel@melameth.com on

        Whoa. I overlooked the Networking Update piece and there is some VERY cool stuff in there. I really enjoyed the congestion indicator in stack and pf and crazy ideas for future releases slides--thanks for sharing Henning!

    3. By Confused (70.58.207.244) on

      I get the feeling I missed an inside joke. What is the "-F f*ck_henning" option referred to in the Ports foil #36?

      Comments

      1. By Anonymous Coward (82.197.192.49) on

        Yes. you are mising an inside joke.

        Comments

        1. By Miod Vallat (217.33.215.223) miod@ on

          Indeed. But we may keep this option (which is the default behaviour anyway).

    Latest Articles

    Credits

    Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]