OpenBSD Journal

BSDTalk 90.

Contributed by sean on from the don't tell anyone I'm free dept.

In the first BSDTalk podcast of the year Will interviews an OpenBSD friendly sysadmin named Mike Erdely.

MP3: http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk090.mp3
OGG: http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk090.ogg

(Comments are closed)


Comments
  1. By Richard (24.37.236.100) on

    Really great talk!

    I highly recommend hearing this BSDTalk...

    I wish I could find a way of convincing my company to try and use OpenBSD in most places, just as you have done. My personal hobby is the same too, but the higher up admins are clueless... It drives me nuts!

    When I first discovered OpenBSD, I too thought it was nice and easy, nice, very clean and simply put *just makes sense*!

    - The 'Adbobe' Symbol... hehe, too true! ;-)

    Comments
    1. By Anonymous Coward (24.37.236.100) on

      > Really great talk!
      >
      > I highly recommend hearing this BSDTalk...
      >
      > I wish I could find a way of convincing my company to try and use OpenBSD in most places, just as you have done. My personal hobby is the same too, but the higher up admins are clueless... It drives me nuts!
      >
      > When I first discovered OpenBSD, I too thought it was nice and easy, nice, very clean and simply put *just makes sense*!
      >
      > - The 'Adbobe' Symbol... hehe, too true! ;-)
      >
      >

      Whoops, sorry for the typos.

    2. By sng (sng) on http://undeadly.org/cgi?action=search&sort=time&query=sng

      > Really great talk!
      >
      > I highly recommend hearing this BSDTalk...
      >
      > I wish I could find a way of convincing my company to try and use OpenBSD in most places, just as you have done. My personal hobby is the same too, but the higher up admins are clueless... It drives me nuts!
      >
      > When I first discovered OpenBSD, I too thought it was nice and easy, nice, very clean and simply put *just makes sense*!
      >
      > - The 'Adbobe' Symbol... hehe, too true! ;-)

      Bear in mind that I've not listened to this episode. But what I'm about to say applies in general.

      If you are trying to or have to "convince' anyone to use a given bit of software you have left the path of wisdom. Here is how you do it. You show up and do your job. You do it better than anybody else can do it. You get the reputation for being the guy who is always there, who always makes things right, you pull miracles out of your ass on a regular basis. You do what you do with the tools you're handed and you make your systems sing and bend them to your iron will. You do this till those around you know that you're damn good at your job and that you can be counted on to do it and do it well. At that point it will become a given that when you want to use a certain tool for a job that it's the best tool for the job and that's what should be done. Till you reach that point keep grinding and doing your job till you -are- good enough to command that kind of respect.

      Comments
      1. By Michael Erdely (merdely) on http://erdelynet.com/

        > Bear in mind that I've not listened to this episode. But what I'm about to
        > say applies in general.

        Maybe you should listen.

        > If you are trying to or have to "convince' anyone to use a given bit of
        > software you have left the path of wisdom. Here is how you do it. You show up
        <snip>
        > Till you reach that point keep grinding and doing your job till you -are-
        > good enough to command that kind of respect.

        I believe you think I tried to "convince" someone to use OpenBSD instead of something else. I've almost never had to make such an argument because of the reputation I have (earning it just as you described). The problem is when an intern starts, with no knowledge of my reputation for pulling miracles out of the air, and asks for Photoshop for the one or two graphics they have to work on. Do you just turn around a "do your job" by buying Photoshop or do you encourage or "convince" them to use Gimp?

        This example is quite extreme, but it's close to what happens. A lot of times people are comforted by the brand name even when there are free/open solutions that are basically just as good. I've used (older versions of) Photoshop quite extensively. Gimp is DEFINITELY a viable alternative and each time I use Gimp, I feel good that a no talent 'artist' (me) didn't waste $300+ on software.

        Comments
        1. By sng (sng) on http://undeadly.org/cgi?action=search&sort=time&query=sng

          > > Bear in mind that I've not listened to this episode. But what I'm about to
          > > say applies in general.
          >
          > Maybe you should listen.
          >
          > > If you are trying to or have to "convince' anyone to use a given bit of
          > > software you have left the path of wisdom. Here is how you do it. You show up
          > <snip>
          > > Till you reach that point keep grinding and doing your job till you -are-
          > > good enough to command that kind of respect.
          >
          > I believe you think I tried to "convince" someone to use OpenBSD instead of something else. I've almost never had to make such an argument because of the reputation I have (earning it just as you described).

          Excellent. That point was, of course, not directed at you but rathar at the first poster who said that was -just- what he was trying to do. So if that's not what you do then thank you for helping to make my point about how these things should be done.


          > The problem is when an intern starts, with no knowledge of my reputation for pulling miracles out of the air, and asks for Photoshop for the one or two graphics they have to work on. Do you just turn around a "do your job" by buying Photoshop or do you encourage or "convince" them to use Gimp?

          I hand them whatever the standard tool for that company is is since I have no knowledge of the tools they need to do their job and am thus, in no more of a position to advise them about the tool to use for their job then they are to advise me about the tools I need to do my job. Of course, I'm a net admin and not desktop support. So it would be more accurate to say that I ignore them. But if I was desktop support that's what I would do.

          >
          > This example is quite extreme, but it's close to what happens. A lot of times people are comforted by the brand name even when there are free/open solutions that are basically just as good. I've used (older versions of) Photoshop quite extensively. Gimp is DEFINITELY a viable alternative and each time I use Gimp, I feel good that a no talent 'artist' (me) didn't waste $300+ on software.

          Don't know. I don't work with graphics and have no talent in that direction. I have no more grounds to make that judgement than said graphics designer has making judgement calls about switches. It's all about knowing your tools. I don't know theirs. They don't know mine. The more we leave each other alone the better.


          Comments
          1. By Anonymous Coward (24.37.236.100) on

            > > > Bear in mind that I've not listened to this episode. But what I'm about to
            > > > say applies in general.
            > >
            > > Maybe you should listen.
            > >
            > > > If you are trying to or have to "convince' anyone to use a given bit of
            > > > software you have left the path of wisdom. Here is how you do it. You show up
            > > <snip>
            > > > Till you reach that point keep grinding and doing your job till you -are-
            > > > good enough to command that kind of respect.
            > >
            > > I believe you think I tried to "convince" someone to use OpenBSD instead of something else. I've almost never had to make such an argument because of the reputation I have (earning it just as you described).
            >
            > Excellent. That point was, of course, not directed at you but rathar at the first poster who said that was -just- what he was trying to do. So if that's not what you do then thank you for helping to make my point about how these things should be done.
            >
            >
            > > The problem is when an intern starts, with no knowledge of my reputation for pulling miracles out of the air, and asks for Photoshop for the one or two graphics they have to work on. Do you just turn around a "do your job" by buying Photoshop or do you encourage or "convince" them to use Gimp?
            >
            > I hand them whatever the standard tool for that company is is since I have no knowledge of the tools they need to do their job and am thus, in no more of a position to advise them about the tool to use for their job then they are to advise me about the tools I need to do my job. Of course, I'm a net admin and not desktop support. So it would be more accurate to say that I ignore them. But if I was desktop support that's what I would do.
            >
            > >
            > > This example is quite extreme, but it's close to what happens. A lot of times people are comforted by the brand name even when there are free/open solutions that are basically just as good. I've used (older versions of) Photoshop quite extensively. Gimp is DEFINITELY a viable alternative and each time I use Gimp, I feel good that a no talent 'artist' (me) didn't waste $300+ on software.
            >
            > Don't know. I don't work with graphics and have no talent in that direction. I have no more grounds to make that judgement than said graphics designer has making judgement calls about switches. It's all about knowing your tools. I don't know theirs. They don't know mine. The more we leave each other alone the better.
            >
            >
            >

            Thank you very much for the great advice! Just what I was hoping to hear from someone.

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