Please don't change Beastie to another crap logo such as NetBSD!!!

Greg Barniskis nalists at
Fri Feb 11 05:53:52 PST 2005

Bart Silverstrim wrote:

> Out of curiosity, is Beastie so terrible, a logo, that a business would 
> be stupid enough to base their server decisions based on it?  Would you 
> care if a business were that dumb...would you actually *want* them using 
> it?

The problem (from my point of view) really has a lot more to do with 
having to communicate about an OS after it is selected, rather than 
the act of selection (which is rightly based on technical merit). I 
need to communicate about ongoing server operations with boards of 
trustees, with my immediate customers, and indirectly with their 
customers. I can't use Beastie in these discussions because I can't 
afford the time to explain the multiple "inside jokes" re: 
daemon/demon, the tennis shoes, etc., over and over and over again, 
and I really, really can't afford to lose a debate about FreeBSD's 

While the amusing subtleties embodied in the Beatie emblem are 
indeed endearing to the IT community, they are a serious *drag* when 
communicating to the less clueful.

> Windows' logo isn't even a logo.  It's a flag of a window pane falling 
> apart in the breeze.  I associate windows with broken glass.  These 
> things don't seem to hinder Windows from getting massive market share.

My board of directors never looked at the Windows logo and said 
"What the f#$% is that!?". Argue all you like about the fact that 
people need to be more open and clueful, and how precious Beatie's 
legacy is (I agree it is), the bottom line is that some rather 
important people aren't very clueful, and many of them can't ever be 
expected to be clueful, and I don't have time to educate dozens of 
people every time I want to compare our organization's use of 
various OS flavors.

So, I limit myself to indicating "FreeBSD" by text only, and I know 
that the impact of that on the decision makers is somewhat lower 
than if I had a stylin' graphic suitable for use in official 
communications like uptime graphs, scope of use, service 
dependencies, project activities, etc.

OK, so now maybe I expect some flamage about bein' chicken, not 
standing up for what's right, etc. Well, horse hockey. I have a duty 
to my employer not to waste everyone's time with the deamon/demon 
discussion (over and over and over again). It would be one thing if 
we could do it once and get it over with, but that is clearly not 
the case.

Greg Barniskis, Computer Systems Integrator
South Central Library System (SCLS)
Library Interchange Network (LINK)
<gregb at>, (608) 266-6348

More information about the freebsd-questions mailing list