JR4/DV4 design change

Basically we have changed the chassis we use to one providing better cooling, and better OS drive access. In the case of the JR4, we should have better backplane fault isolation, at the cost of a few more wires to deal with internally (e.g. shouldn’t impact customers at all). Costs will be about the same, … Read moreJR4/DV4 design change

Treating partnerships as business investments

We’ve had issues in the past with ‘partners’ taking advantage of our willingness to work with them, in order to have everyone come out ahead … the customer, the partner, and us. This approach to partnership means all sacrifice a little, but everyone wins.
Unfortunately, it also requires that everyone behave in an honest manner, honor their agreements.
We are treating all discount requests as a partnership request. A customer wants a lower price on something. Fine. What are they willing to exchange for that lower price? Can we afford to give them the price? Will it so negatively impact our business that it becomes a bad decision to pursue? Basically we need to see the business justification for this action. Show us a model that will work for us, and we will consider it. Demand something for nothing? No, not gonna work.
For resellers and groups wanting to work with us to help grow their business, and help them differentiate their offerings (not many companies can do what we do), this is also an issue, but easier to codify in a reseller agreement. We can pre-define what happens in “if-then” scenarios. Provides something of a saner model.
But thats not what I am talking about here.

Read moreTreating partnerships as business investments

Docs wiki back up

That was annoying. The update/upgrade path effectively wrote over the old configs without telling me. Snapshot script is up, and we will set up for weekly snapshots, and then deletion of the same after 12 weeks. Did I mention that this was annoying? On another note, we’ve had requests to refine/update the documentation, and we … Read moreDocs wiki back up

dust just built and installed its first module, successfully, without issue

A few more things to do … we need a “make clean” like thing, and maybe a “make prepare” like thing. And we need to trigger a mkinitrd at the end when requested.
Major things are the init.d script, but all it does is call a

dust.pl –generate

Yeah, we are trying to make this really simple. Really really simple. And make sure it works. Really works.
Here is output with the –generate and –debug options. You can see that it pays careful attention to a number of things. I messed up a current working directory thing, but I can fix this fast.

Read moredust just built and installed its first module, successfully, without issue