Labels

css (1) jQuery (7) linux (38) mac (70) php (29) python (1) svn/git (9) trac (4) ubuntu (1) virtualbox (6) vista (2) windows (14)

Monday, 25 January 2010

Hiding OSX dock icons

If you have a program that runs all the time but you don't want to see it's dock icon do the following:

Right click the app, click show package contents, then open the Contents folder, open the info.plist file and add a new key called LSUIElement and set it to value 1 then restart the app.

Sunday, 24 January 2010

Multi user git and websites

As you may know I use GIT for version control.

Recently a client asked me to allow them and others access to the site (uh oh this should be fun!)

Now currently I edit locally, commit to git, and upload files via sftp (makes sense). Now this isn't ideal for the multi user situation because of the following...

1) You need a remote repo to push to
2) Teaching people how to use sftp (not hard I know but it's something extra do to)
3) What happens if they upload via sftp but forget to commit to git?! Oh crap is what happens.

So after some googling I found the following:

http://joemaller.com/2008/11/25/a-web-focused-git-workflow/

It works wonders, with a few tweaks of course which are:

1) For multi-user access add each user as a linux user with git-shell
2) Add them all to the same group let's call it "git"
3) Make the git repo and the website group writable
4) chmod 06770 the .git directory so it's sticky this allows users to write to the files if they have the group permission bit and it makes new files retain the parent directories group

That way no SFTP and the only way to edit the site is via a git push so everything is logged.

Monday, 18 January 2010

Mac Reindex Spotlight


I recently used Onyx to clean up my mac, one of the things was rebuilding the spotlight index, oh boy was that a bad idea, spotlight which was uber quick and my main access to applications became slower than a moron convention. 

To fix it I tried the apple support idea of adding it to privacy then removing it, that did absolute squat, after googling I found this http://davecoyle.com/documents/leopard-when-spotlight-wont-reindex.htm worked a treat, here are the commands:

sudo rm -r /.Spotlight-V100
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
sudo mdutil -i on -E /

Note this is on Snow leopard the .Spotlight-V100 folder might be named something else in different versions.

Saturday, 16 January 2010

Mac RAID


One of my external hard drives might be on it's last legs (it's rather louder than usual and has been disconnecting itself randomly) so I've migrated most of the data to my next biggest drive, which brought to mind the idea of RAID, I've done it under windows and it wasn't the most pleasant procedure (ironically my mother board failed shortly after I did that). On a mac it seems quite simple an interesting article that explains it is found here http://www.frozennorth.org/C2011481421/E20060221212020/index.html

Here is the contents just incase that page ever goes missing and I want to use it



Our Mac G4 Cube finally bit the big one this week, so on Wednesday I went out and bought a brand-new Mac Mini (and a cheap flat-panel monitor).
Let me begin by saying that the Mini is probably the most amazing computer I've ever owned. It is an astonishingly capable machine, and until you see on in person, you just don't understand how tiny they really are. Imagine a stack of about six CD jewel cases: that's the size of the entire computer.

As had been my practice for the last few dead-Mac transitions, the first thing I did was extract the hard drive from the old computer, put it in an external USB case, and transfer the contents to the new computer. Mac makes it so utterly simple to transfer your life from one computer to another (literally two clicks) that it is truly a joy--especially if you've ever had to go through the pain and agony (as I have, several times) of doing it under Windows.

But I have a problem. Not a let's-call-my-geeky-friend kind of problem, but an I-should-enroll-in-a-12-step-program kind of problem. My problem is that every so often I see how utterly cheap hard drives are, and I can't resist buying a 250GB external drive for ten Cheerios boxtops plus $2.50 postage, or whatever the price happens to be that day. Never mind that I don't have a use for all that storage: it is just so cool that you can get so much for so little that I have to have it.

So combine that problem plus my practice of putting the hard drives from old computers into external cases, and I have this accumulation of external hard drives sitting around basically doing nothing.

Then the obvious idea hit me: Why not build a RAID array from all these external drives? At least then I'd have something coherent (a giant virtual disk with a goodly fraction of a terabyte) instead of a whole bunch of external drives.

I'd always known that Mac OS X comes with built-in RAID capability, but I never had the excuse to explore it.

RAID stands for Redundant Array of Inexpensive Disks (some people use the word "Independent" instead, but either is correct). It was originally designed by cash-strapped researchers to take advantage of the plunge in consumer-grade disk drive prices back in the 90's in order to build bigger, more-reliable virtual hard drives than they could actually afford, by binding together multiple small, unreliable drives.

In fact, a RAID array can provide a bigger, faster, and more reliable storage device than anything you could get from a single drive (no matter how much you wanted to spend), using cheap off-the-shelf drives. It is now the standard way to build large storage systems.

The RAID capability in OS X is relatively easy to set up (as such things go), but it is still a little geeky. It is hidden inside the "Disk Utility" program, and gives you three modes: "Mirrored" which lets you combine multiple drives into a single redundant drive with the capacity of the smallest drive of the set. Each drive contains the entire contents of the array, and if any one drive is functional, then the virtual drive works properly. In other words, you can combine three 80-GB drives into a single 80-GB drive, but any two of the three can break before the virtual drive stops working. "Mirrored" mode is for creating highly reliable virtual disks.

"Striped" combines multiple drives into a single larger drive, spreading the contents of the array across all drives in the array. This gives you both a bigger drive and faster access (since data is read from multiple disks simultaneously). But there's no redundancy: if any one drive in the array fails, the whole thing goes down.

"Concatenated" also combines multiple drives into a single larger drive, like the "Striped" mode, except that a given block of data is only written to a single drive. This has the advantage of letting you add new drives to the array after it is set up, so you can grow the array as needed, and you can combine drives of different sizes without wasting any space.

Right now, the built-in RAID doesn't include more sophisticated modes like N+1 redundancy (where, for example, five drives can be combined into an array with the capacity of four of the five drives, and any one of them can fail without taking the array down). But it does do a couple of other nifty tricks.

One is that you can set up the RAID using individual partitions on a given drive. For example, if you have an 80-GB drive and a 120-GB drive, and you want to set up a mirrored array (which has the capacity of the smallest drive in the array), normally you would lose 40 GB of capacity from the 120-GB drive. But under OS X, you can set up an 80-GB partition on the larger drive for the RAID, and leave yourself with an extra 40-GB partition to use for something else.

The other neat trick is that you can create hybrid arrays, where you combine arrays of arrays. Suppose, for example, that you had a bunch of drives sitting around of random sizes, and you wanted to create a single big array. Normally you would use the "Concatenated" type, but that has the disadvantage of being unreliable: if any drive in the array goes down, the entire array is toast. If you want reliability, too (sacrificing half the capacity), you can create two "Concatenated" arrays which are approximately the same size, then combine those two arrays into a single "Mirrored" array. Then if any one drive fails, the virtual array continues to function normally.

This is not as efficient (in terms of storage space) as N+1 redundancy, but it wins hands-down on flexibility, especially if your basic problem is not building a highly redundant data center, but simply making good use of a bunch of random hard drives sitting around.

So I'm setting two RAID arrays on our Mac Mini. One is a Mirrored array combining the Mini's internal drive and an 80-GB partition on an external drive. This is the boot disk, and has all our precious data like Quicken files, family photos, and the like. If we're careful, we should never lose important stuff.

The other array will be a Concatenated array which will probably have about 600GB capacity. Since this is unreliable storage, it is essentially a giant scratch disk for things we could afford to lose: backup images of CDs, working files for editing home video, and so forth.

So we'll have a small(-ish) virtual disk which will be highly reliable, and a huge virtual disk which will be unreliable.

Now I just need to go find some data.

Friday, 15 January 2010

Redis


I'm currently reading up on Redis as a nice way to store information as key value pairs in memory (instead of using memcached), and this tickled me.

Values can be strings (including binary data) of every kind, for instance you can store a jpeg image inside a key. A value can't be bigger than 1 Gigabyte.

Since this is an in-memory database (it does store on disk as well but everything is also in memory) I think 1 gig should be sufficient for everyone's needs

Monday, 4 January 2010

VMware Fusion OS X Guest Disk Size

By default VMWare fusion sets OS X guest disk size to 40GB, why I don't know I only use it for testing and have a bare OS X install which is no where near that in size. To reduce it find the *.vmdk file which is associated with the image, open it in a text editor (I like text wrangler) and remove excess lines under # Extent description the more you remove the smaller the disk.