And if not, he may end up being the mayor of Bartertown.
> When you close your account, we will immediately destroy all your personal information and won't keep any backup.
I'd love to hear how you're purging users from your backups, and how long you keep backups.
To my knowledge (and I may have missed something) Linode is one of the first VPS providers to do IPV6. So I thought this was awesome.
If lots of other VPS providers start doing IPV6, and don't charge for a /64, or charge less than Linode does, Linode will have to change their fees or lose customers. But until that happens, why bash Linode for an as-yet unspecified charge?
The vendor decrypts this, and marks it as fixed in your database by submitting "decrypted" text that says "I like ponies."
Highly recommended.
http://www.amazon.com/Practice-System-Network-Administration...
We started in 2005, are venture-funded, and are not yet profitable. We're raising our 2nd round of venture funding right now. All employees get stock options, and we have medical, dental, and vision coverage.
We're looking for people who will work out of our Santa Monica, CA office. It's a casual office environment with really good coffee, and people often bring their dogs in to work. Today there's a Neapolitan Mastiff (http://twitpic.com/cwjfl) and a Chihuahua here.
Our touchscreen appliance (visible in the picture at the link above) runs Ubuntu Linux, and most of our infrastructure is Linux-based, with a few Windows (SQL Server) and OS X boxes. Our GUI software is written in REALbasic, and our system administration scripts are BASH and Python.
We're also in the process of developing a software-only installable product that will run on OS X and Windows.
Our desktops are OS X or Linux (your choice) with two big-ass monitors per person. We do well (but not 100%) on the Joel test, and are always looking for ways to make our work more efficient and productive.
Our biggest need right now is for someone in a combined Linux System Administration and QA Automation role. This would entail everything from installing and configuring Postfix to automating install testing for our Windows product.
We're also looking for QA Engineers for the Windows/OS X Product, and for additional support people, again, with Windows and OS X experience. Linux experience for both the QA Engineers and the support people is a huge plus.
To avoid getting put in the "Craigslist" mountain of resumes, send a cover letter and resume directly to me: schof at dakim.com
Posting things on the public Internet that reflects poorly on the candidate shows a judgment issue that is a valid reason for rejecting a candidate.
In the case I'm thinking of, a cursory Google search on a candidate I would otherwise have hired showed that he had at least one job that he had quit without notice; this job was not listed on his resume. In addition, this first-person blog stated that he had shown up to work so hungover he could barely see, on more than one occasion.
Should I have hired this person, given the red flags I found via Google and that there were other equally-qualified candidates who did not have those red flags?
1) It's actually pretty easy to install, once you get past the whole "it's different" bit. I had no real trouble.
2) Updating/upgrading is a PITA. Having to upgrade by patching source code -- WTF?
What do you do if you have a fleet of 100s of OpenBSD machines? I may be spoiled by apt, but I can upgrade the several hundred machines I'm responsible for in an almost trivial manner. (And updating a single machine with apt is absolutely trivial.) That doesn't seem to be possible with OpenBSD. (I suppose you could write a custom shell script to do the update, and distribute that to your machines, but...certainly not trivial.)
What's more, I would be willing (if not completely comfortable) to update a remote Ubuntu/Debian box to the next release -- that doesn't seem like a good idea (or even possible under some circumstances) with OpenBSD.
This seems even stranger when you consider the security reputation of OpenBSD, and how important updates are for security, even for something as well-audited and well-written as OpenBSD.
Am I missing something here?
[1] http://kerneltrap.org/mailarchive/openbsd-misc/2009/2/8/4924...
It seems there are two characteristics that would make an area ripe for this -- companies needing it badly, and some (real or perceived) barrier to entry that keeps legions of geeks from learning it.
Any other likely candidates?
What I'm managing (context is important): We develop a hardware appliance running Linux (we buy the hardware and write the software); this involves config changes to open source stuff and a number of our proprietary programs that must work together. We have six developers, and a number of artists, writers, etc. whose work mostly isn't but sometimes is a dependency for the stuff I'm...
Now I'm thinking about French.
Highly recommended, professional, and cheap. But a little on the BOFH side -- will refer to you to a FAQ instead of actually answering your dumb question. Since I'm a BOFH myself, we get along great.