David Latham

Challenges: MySQL only allows a single location to be specified as the default data store for all databases. Consider the following typical scenario: A database server running one instance of MySQL has its datastore located at /mysql/databases. This server will contain multiple databases for multiple applications. The database tables are a mixture of InnoDB and MYISAM storage engines. The storage is provided by a SAN and separate storage volumes (iSCSI targets) are provisioned for each database. In this scenario, you would want all your MYISAM files (*.MYI, *.MYD, *.frm) and all your InnoDB table spaces to be contained on the same iSCSI volume on a per-database basis. Solution: This is easily achieved by mounting the iSCSI target on a sub-folder of /mysql/databases. For example: Mount iqn.openfiler.com:2006-06:blog-db-storage on /mysql/databases/blog Here is a sequence of steps that need to be carried out to make this work. in /etc/my.cnf set datastore=/mysql/da

MUST FOLLOW PROCESS.... MUST FOLLOW PROCESS... Starting with the premise that we need our customers to be happy with us, what do we need to do as an organisation to keep them that way? We are working through steps to improve our customer satisfaction at work by carefully considering how our daily work routines, processes and actions impact our customers. Consider this fairly typical example of how an organisation might respond to a customer request: [NOTE: This is a little bit (A LOT) satirical and not meant to in anyway be a real representation of an actual process. It's designed to highlight how strict adherence to process can lead to unhappy customers.] A customer needs a new type of widget. Your organisation sells gadgets that are very similar to widgets so they approach you to design and build one for them. They are willing to pay for the service but they need this new widget to work for them. Luckily your organisation has a process to handle this type o

I have to reblog this article in it's full just in case the original author removes it. Here is the original. http://bashscript.blogspot.com/2010/03/unixlinux-advanced-file-permissions.html Here in plain text to ** FORCE ** it into my rubbish layout. UNIX/Linux Advanced File Permissions - SUID,SGID and Sticky Bit After you have worked for a while with Linux you discover probably that there is much more to file permissions than just the "rwx" bits. When you look around in your file system you will see "s" and "t" $ ls -ld /tmp drwxrwxrwt 29 root root 36864 Mar 21 19:49 /tmp $ which passwd /usr/bin/passwd $ ls -l /usr/bin/passwd -rwsr-xr-x 1 root root 22984 Jan 6 2007 /usr/bin/passwd What is this "s" and "t" bit? The vector of permission bits is really 4 * 3 bits long. Yes there are 12 permission bits,not just 9.The first three bits are special and are frequently zero. And you almost always learn about the trailing 9 bits fir

I recently installed the latest version of Google Desktop. I found, however, that when searching either from the sidebar searchbox or the Ctrl Ctrl popup box, GD would always select Search Web by default. This can now be changed using a small registry edit on Windows XP it is: HKEY_CURRENT_USER\Software\Google\Google Desktop\Deskbar\ change search_type to "Search Desktop" That's it. Hopefully this will save some of you some time.

This is a very simple post. I found these principals very useful in solving a problem I have with a particular project I am currently working on... http://en.wikipedia.org/wiki/Unix_philosophy 1.Small is beautiful. 2.Make each program do one thing well. 3.Build a prototype as soon as possible. 4.Choose portability over efficiency. 5.Store data in flat text files. 6.Use software leverage to your advantage. 7.Use shell scripts to increase leverage and portability. 8.Avoid captive user interfaces. 9.Make every program a filter. Have a read. It's well worth remembering these guidelines. Even if you have read them before, it might be useful to refresh your memmory.