Archive for the ‘rants’ Category
I recently started using FreeNAS again after exploring other options that existed, such as openfiler, and now that I’ve returned, ZFS seems to be the cool thing to do. After reading, watching videos and playing with ZFS I’m sold on all the features it offers. However, I must ask, is there a compelling reason to use ZFS over UFS for a single disk? I’d really like to see some comments on this.
When using email, you should always keep the following rules suggestions in mind. Most of these apply to mailing lists, but could just as easily make any email communication (and maybe even instant messaging) better.
First, don’t top post. Not only is top posting counter-productive it is annoying. Also, if the person before you sucks at life, don’t follow with it. Remove everything but the relevant parts, and post under that. It makes life better for everyone.
Along with the last one, don’t include unnecessary posts in your reply. More than likely, most people will choose not to follow the first suggestion, so lets alteast remove the parts of the message that are unneeded. If you’re reply to a long message, break it apart. Put your replies inline, so others can better read them..
Keep the signature short. If you feel you must include a 12 line signature complete with pictures, color and blink tags, only do so once. A simple sig is great. A simple sig 24 times is annoying. Don’t do it. Any mailer worth using allows you to configure when to add a sig, so don’t add one on replies.
Stay on topic. If the current thread has sparked a new topic, start it elsewhere. Threads and topics enjoy having an exclusive relationship, so keep it that way. If you’re changing the thread, atleast warn people (New Thread Topic (WAS: old thread)).
That’s all for now. (actually, that’s just the 4 things that annoyed me while checking my mail tonight) I’ll expand as more annoying things come to light.
I was reading this story on lifehacker today and just wanted to drop my comments on the subject.
Quite often, I’ve had this conversation with people..
Me: What’s your backup scheme?
Them: Oh, we have RAID.
Me: Nice. So what’s your backup scheme?
THe problem with is this, if you havn’t figured it out yet… RAID is NOT a method for backing up data. Now, sure it is useful for protecting data (in some forms) or speed up access to data (in other forms) but it is not, in any way, a method for protecting data.
If nothing else, the journalspace incident proves this. They were using RAID for backups. Well, their RAID did exactly what RAID is meant to do. Protect the data on the drive. In their case, the data on the drive was the problem. Having the mirror simply copied all the bad data across their drives.
During this post, I’ve been trying to think of a funny, sarcastic, or otherwise memoriable way of saying this, but I’ve come up blank, so I’ll just say it… Having a RAID array IS NOT a backup! Taking this furthur, you should never trust one form of technology to fill the role of another.
The next time you’re asked to implement a backup stragety, remember RAID is not your answer.
I assume you’ve had your hands on at least one set of administrative credentials in your life. I’d also make the assumption that you’ve used that account as your everyday account. You know, the one we use to check mail, surf the web, update facebook, download porn… you know, that kind of stuff.
That’s a bad idea.
Why, you might ask. Doing so, opens yourself up for quite a lot of trouble.
Time to take a step back…. Let’s imagine for a moment that you’re just another user. What kind of access would you have on the network? Hopefully you’ve just said ‘as little as possible’ or ‘only what you need’ or similar. Well, why is that? Security. The idea of least access says that I can do only what I need to do to complete my job.
Whoa! But I’m the admin! I need access to everything!
This may be true, but probably not. Think about your average day. What do you really do? Occasionally you install some software, create user accounts, update systems… the list can go on. Now, let’s really think about that… How often do those tasks happen and where do you perform them. Know that you’ve answered those questions, let’s move on.
Everyone on your network should have a user account. That is, a limited account with least access to the resources they need. For an administrator, this means you have an account with very limited access to install software, run updates, make system changes and the like. Just like everyone else. This is the account you work with daily. You log in, surf the web, read the news, send email, check blogs, etc… all that work stuff.
BUT WAIT
You also create an account for yourself with administrative rights. This account, is used whenever you need to perform an administrative task.
Have this account separate account means that any time you want to do something that requires administrative access you MUST think “Do I really want to do this”? I bet you find yourself saying “no, not really” quite a lot after this. Separate accounts also gives you a nice way of monitoring changes on your network. By having separate logins, you can see when (and who) is making administrative changes on your network.
I’m tired..
