ghah. did it again. <br><br><div><span class="gmail_quote">On 10/12/07, <b class="gmail_sendername">Bob Hartmann</b> <<a href="mailto:bob.hartmann@gmail.com">bob.hartmann@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="e" id="q_11596beb6435ecab_0"><br><br><div><span class="gmail_quote">On 10/12/07, <b class="gmail_sendername">Andrew Zbikowski</b> <<a href="mailto:andyzib@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
andyzib@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/12/07, Elvedin Trnjanin <<a href="mailto:trnja001@umn.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">trnja001@umn.edu</a>> wrote:<br>> Are you experienced enough with that firewall or any software, that
<br>> you're confident the implementation of it will go smoothly? Would you be
<br>> able to train others to be competent enough to maintain it? I've found<br>> (albeit in my limited experience) that those two things are more<br>> important and decisive than any case study you can present.
<br><br>Without a doubt. Corporate firewalls are very important these days, so<br>a commercial firewall isn't necessarily a bad thing. Depending on the<br>size of your company and your requirments, there are many commercial
<br>products that run embedded OSS. Watchguard Firebox products and Astaro<br>Security Gateway run their own embedded versions of Linux. (At least<br>the Fireboxes used to, I haven't looked at one in a few years so<br>
things may have changed.)<br><br>Anything new in IT generally starts in your server room/data<br>center/infrastructure, not on the client side. Where is OSS going to<br>fit in in your environment? A internal web server, perhaps running a
<br>Wiki (Dokuwiki is nice for quick technical documentation) to document<br>your IT infrastructure/coding project/etc. is an easy sell. A Nagios,<br>Big Brother, or similar network monitoring package is also a good<br>project if you don't already have something for that role. Find
<br>problems/issues that can be solved with OSS, going OSS just for the<br>sake of going OSS is going about things in the wrong direction.<br><br>If you want an OSS project to be successful, pushing it as free, OSS,<br>Linux, etc. ins't the way to go. As with any solution you implement in
<br>IT, it must be the right tool for the job. Just because it is Open<br>Source and Free doesn't make it the right tool for the job, but when<br>it is the right tool those factors are great added bonus.<br><br>--<br>
Andrew S. Zbikowski | <a href="http://andy.zibnet.us" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://andy.zibnet.us</a><br>SELECT * FROM users WHERE clue >0;<br>0 rows returned<br><br>_______________________________________________
<br>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<br><a href="mailto:tclug-list@mn-linux.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">tclug-list@mn-linux.org</a><br><a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br></blockquote></div>
<br><br></span></div><span style="color: rgb(91, 16, 148);">That was awesome, andyzib. Great advice. <br>Throwing up a Wiki where none exists will be very popular. I did it many years ago when the average Joe didn't know what a Wiki was. Once you get 'em hooked, just keep saying "no, it has to be on Linux, man."
<br>Then use that same box to introduce even more sedition. :) <br><br></span>
</blockquote></div><br>