OpenBSD Journal

Wanted: Your Stories

Contributed by deanna on from the content-makes-puffy-happy dept.

Reminder: The OpenBSD Journal exists to publish news and information by and related to the OpenBSD community. As seen on the sidebar, we are constantly on the lookout for stories about how you put OpenBSD to work. Here are a few publishing guidelines that may help.

Original Content

We prefer original content -- that means written by you. Appropriate topics are case studies, personal hacks and original uses, ideas and opinions, advocacy and much more. If you're unsure, just ask, via the submit story form or through email to the editors.

Format

Please make your stories at the very least a couple of paragraphs. The more in-depth, the better. If you feel your story is too long, it may be submitted and published in parts (see the recent PF articles for reference). In special cases, your article may include images such as diagrams; mail the editors for more information.

Credit

We believe in giving credit where it is due. Feel free to submit a short bio about who you are, where you work, what you do, your cat's name, or how you discovered OpenBSD. Keep it to one or two sentences, please.

We look forward to reading your stories!

(Comments are closed)


  1. By Anonymous Coward (213.118.21.137) on

    http://unduli.bsws.de/papers/nanog36/mgp00043.html
    I would like to see some updates about those production servers :-)

  2. By Anonymous Coward (218.75.87.37) on

    Something about how to get started with and all the details about running snapshots and testing the diffs posted to tech@ would make a nice article.

  3. By Leon Yendor (218.214.194.113) on

    An overview of AltQ from the perspective of choosing between the types of queueing seems like a desirable topic.

    misc@ is not exactly being swamped with questions about it but they do pop up from time to time and I wonder just what approach I would take if I had a need for queueing.

    I feel that I could use a guidance document to judge where I should concentrate when reading the respective man pages and I think I'm not alone in that.

    1. By Anonymous Coward (193.63.217.208) on

      > An overview of AltQ from the perspective of choosing between the types
      > of queueing seems like a desirable topic.
      >
      > misc@ is not exactly being swamped with questions about it but they do
      > pop up from time to time and I wonder just what approach I would take if
      > I had a need for queueing.
      >
      > I feel that I could use a guidance document to judge where I should
      > concentrate when reading the respective man pages and I think I'm not
      > alone in that.

      This sounds like a good topic, especially if there's any good tips on CBQ queuing fast network interfaces (100Mbit included) with only a 100Hz granularity from the kernel tick.

  4. By Anonymous Coward (128.171.90.200) on

    I'm sure, as with coding, it's better to write something rather than hang out here saying what you want people to write

    1. By Anonymous Coward (84.57.136.82) on

      > I'm sure, as with coding, it's better to write something rather than hang out here saying what you want people to write

      ACK!

      1. By Anonymous Coward (70.179.123.124) on

        > > I'm sure, as with coding, it's better to write something rather than hang out here saying what you want people to write
        >
        > ACK!
        >
        >

        RST!

  5. By Anonymous Coward (89.59.160.112) on centroid.eu

    I maintain a small website/blog that has OpenBSD content. Since my only OS at home is OpenBSD this comes natural. Whenever I figure out a new feature or send in a new patch to gnats@ it probably gets mentioned on this blog. http://centroid.eu -p

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.]