being your own CIO?
Published 6 years, 9 months ago in leadership + management, small businessBeen working on our server for my new company a lot lately, and that’s taking a lot of time. As I work on it with our new sysadmin (who comes highly recommended by Scott Johnson) I’m starting to realize how little I really know about server administration, and for that matter network architecture.
I’ve always thought that I was just knowledgeable enough to be dangerous, while at the same time, smart enough to figure it out given the time, but I’m realizing more and more every day how precious my time really is. Thus, we’ve turned to someone else to set up our server the way that it needs to be set up, and with the speed that we need (and the price is right also).
It’s coming along nicely, but I also sort of fear that I/we are making decisions without having the time to research them, primarily because we’re already behind schedule (or so it feels). Decisions like sendmail vs. qmail? Apache 2.x vs Apache 1.x? MySQL 3.x or 4.x? What modules to include in apache? Bind?
I’m not knowledgeable enough to make an completely informed decision, and neither are any of my partners (yet). So, instead of holding up the project any more, we’re asking our friends what they think, and why, so that we can make a more imformed decision than we could before we asked them… but I still have a nagging feeling that I’ve got a lot (read a shit-load) of reading and tinkering, and asking to do this weekend…
The good news is that we should have FTP, http+php and mysql working by 9/19, and email up by 9/20 or so. So, things are progressing and our developer can get into the box and start tinkering.
Starting a business is tough. Being your own CIO when you know about as much as the Easter Bunny about the technology is just plain scary. But, I guess that’s what open-source is all about. Dive in head first and learn fast. Also, hire smart people to advise you, for those times when you just don’t have a clue, or the time to find one.
[later - ftp, httpd+php, mysql all done. Scott was right about the new sysadmin]
4 Responses to “being your own CIO?”
Leave a Reply
Search
Subscribe
Archives
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
- March 2003
- February 2003
- January 2003
- December 2002
- November 2002
- October 2002
- September 2002
- August 2002
- May 2002
Categories
- asides (508)
- baby (6)
- design + dev (143)
- email (1)
- for sale (7)
- get a job (12)
- investing (6)
- leadership + management (156)
- life stories (262)
- macintosh (322)
- marketing + advertising (228)
- Moveable Type (52)
- organization (6)
- photography + video (68)
- publishing + content (136)
- random (412)
- Saab (1)
- sales and selling (98)
- small business (148)
- startup (3)
- stuff (71)
- sysadmin (41)
- travel (43)
- Video (8)
- windows (69)
- WordPress (13)

Those are easy questions.
> sendmail vs. qmail?
If you are processing lots of mail; have users on the boxes; want it very modular; want it very secure - or any of the above - then choose qmail.
If you have barely any mail at all and simpler requirements (or really old (say uucp)) then choose sendmail.
Otherwise choose postfix.
I’m a qmail person.
> Apache 2.x vs Apache 1.x?
Static content: Apache 2.x.
Reverse Proxies (front end proxies): Apache 2.x
Dynamic anything: Apache 1.x.
> MySQL 3.x or 4.x?
MySQL 4.x is getting cooler and cooler. This depends really. Can you use the new features? Do you require more stability? Is it feasible to upgrade more frequently?
> What modules to include in apache?
As few as possibly; compile them all and load them as needed.
> Bind?
For recursive dns servers I like dnscache much better. It doesn’t crash. It doesn’t bloat to use all memory. It doesn’t have security problems left and right.
For authoritative dns servers I like tinydns much better. Very easy to write programs to deal with the data. If you run all your nameservers it makes it really easy to transfer the database consistantly.
If you need dynamic dns it’s not the right choice (for those domains anyway).
- ask (for hire too, but at first you might not think the price is right)
For hire? Gee, Ask… Word on the street is that you’ve already got your hands full at work?
Actually, I just like that line. “At first you might not think the price is right.” That says so many things. I should start using that. It occurs to me that I’m always “for hire” to some degree or another. Adam Goodman (publisher of Linux Mag) likes to refer to me as a free agent. He’s partly right.
> For hire? Gee, Ask… Word on the street
> is that you’ve already got your hands
> full at work?
What are you talking about? It’s only 4.30 and I am already on my way to bed. (Okay, so I didn’t work all evening…)
As you point out, it’s tricky to measure your availability sometimes.
I am plenty busy with big things to suck up the majority of my time (so the price for something like that would right now be really high as I otherwise wouldn’t be much interested).
However, smaller projects. Architecture reviews, recommendations, small but efficient sessions putting out fire, … that kind of thing. Well, that kind of thing is fun. And a limited scope makes it easier to find time and energy to pump into it.

- ask
I recently bought a server and stuck it in the rack at work. It has really taught me to appreciate the work a sysadmin does. It’s managing to run apache+mod_perl+sendmail+spamassassin+proftpd and keep my email and the couple of tiny websites I help admin going. I think in the end it took about 24 hours to get everything set up and running the way I wanted. I’d put myself in the “dangerous” category, but hopefully a bit more knowledgeable now