/dev/dump

I was forwarded the following infographic from OnlineCollege.org.  While I'm not normally one to just regurgitate someone else's posting (especially advertising), I think this one is worth looking at -- especially if you're at a point where you're contemplating future career or learning plans.

I'm pleased to announce that DEY Storage Systems, Inc. , along with Joyent  and other community members, is sponsoring the illumos and ZFS Day taking place in October 1st and 2nd at the Children's Creativity Museum in San Francisco.  My partners and I will be in attendance, along with a few other of my colleagues, and we'll be speaking on related topics. Additionally, Joyent is hosting the 2nd illumos hackathon at their facilities on October 3, and we will definitely be participating there.  We had a blast doing this last year (some excellent work came out of it), and we're looking forward to doing it again. If you can make, I hope you'll register.  The event itself is free, and while there will be online recordings of the material, its more fun to get together in person -- especially with a beer or three.  (Did I mention there will be a Solaris Family Reunion party on Monday night? In many ways, I view this event as a belated 2nd birthday party for illu...

With the recent announcement and discussion around OpenIndiana, I think its time to bring to the light of day an idea I've been toying with for a while now -- and have discussed with a few others in the community. illumos needs a reference distribution. Now just hold on there... before you get all wound up, let's discuss what I mean by a reference distribution. A reference distribution should be a base  for additional development, and testing.  It should support automated installation for mass deployment in test lab/QA/build farm scenarios. It must support "self-hosting" -- i.e. illumos-gate itself should be buildable on this distribution -- with as few additional steps as possible. It must be valid as a QA platform -- for example, it needs to support the packaging tools we use in order to validate the packaging metadata (manifests).  (Yes, this means it needs to support - and be packaged with - IPS -- in spite of my loathing of IPS itself.) It should be ...

[ Recently, Alasdair Lumsden announced his retirement as leader of the OpenIndiana community.  This is a copy of my response to that. ] Dear Alasdair, Here at the illumos Foundation, we are very sad to hear of your resignation as lead of the OpenIndiana distribution. You have demonstrated great leadership and have been a wonderful friend of the community. We understand that such projects can be very time consuming, and we wish you all the best in your other endeavors.  As a community, many of us share some of your frustrations. At times, progress does appear to be slow. At other times, there may appear to be a lack of interest from many of the former Sun employees. However, although you may feel that there is a lack of support or interest, many of us active in the community feel differently. While OpenIndiana served to carry on the banner of the OpenSolaris distribution, it was obviously a dead end because the desktop wars are over, and even the Linux co...

So, there has been some that have argued vehemently against the advertising policies of GoDaddy , and its ilk.  (See https://twitter.com/bdha/status/211210555577466881 for example of the complaints.) I have a different point of view.  What about sites that always picture a beautiful woman on a headset for their representation of tech support?  Should we also boycott them?  Would you prefer a site with an ugly  person answering the phone?  After all, it's a phone or text chat, so it shouldn't matter at all what the person looks like, right? Conversely, what about all the sites that use men  in their advertising? My hosting provider, bluehost.com , uses both .  Take a look .  Does the pretty blonde in glasses have anything to do with domain names or web hosting?  Of course not.  The guy wearing the headset for the tech support line isn't exactly hideous either, if you swing that way.  Are you likely to talk to this gu...

So, if you're like me, and you've been shopping for a new system lately because you're last one is dying or dead, you might see some fancy looking Intel E3-1200v2 Xeon systems.  (Why Xeon?  Because ECC memory is a good  thing.  I attribute some of my difficulty with my last system to using non-ECC memory.  Because its not ECC, I don't really know  whether the problem was in RAM or CPU, but I digress...) Great, so you pick out a E3-1240v2 Ivy Bridge CPU, and then you look for a System Board. I found the Supermicro X9SCA-F-O.  Looks like a sweet board.  The spec claims support for the E3-1200v2 cpus, and 1600MHz RAM.  It has a separate IPMI LAN support, as well.  Sweet!  (Look closer though....) So, package arrives from NewEgg, and you're ready to go. Assemble the kit.... if you're a software guy like me this might take a couple of hours. Power it on. Beep!  Beep!  Beep!  Beep! WTF does that mean!?  ...

So, I've been trying to setup a system that can build illumos-gate.  Because my old system had a memory DIMM fault, and isn't usable anymore. I thought, hmm... let me try something other  than OpenIndiana. Big mistake. Only OpenIndiana seems able to build vanilla illumos-gate right now. Why?  Because of external dependencies!   I tried building on OmniOS.  The stopper there -- Python 2.4!  On SmartOS, the dependency is IPS itself.  It seems only OpenIndiana is suitable for building stock illumos-gate. The problem is that our build is inherently very sensitive to the build environment.  It makes life incredibly unpleasant if you try to build on any system that is not configured exactly  as we specified. This, IMO, is an unacceptable situation. I will speak loudly against any  attempt to make changes that introduce further external dependencies.  The fact that some already exist is no excuse.  Every external depend...