Installing Dokuwiki on Mac OS X (Mavericks)

For the first time I was successful in installing Dokuwiki on my mac (Its a MacBook Air running Mavericks).

I used info from a combination of these weblinks (almost in that order)
http://machiine.com/2013/how-to-install-apache-and-php-on-a-mac-with-osx-10-8-mamp-part-1/
http://machiine.com/2013/how-to-setup-mysql-on-a-mac-with-osx-10-8-mamp-part-2/
http://machiine.com/2013/how-to-setup-phpmyadmin-on-a-mac-with-osx-10-8-mamp-part-3/
and
https://www.dokuwiki.org/install:macosx
and
http://metadata.mx/personal-wiki/

Please remember you have use some common sense in implementing this. For example I didnt use MAMP or Fluid. But some info like use: http://localhost/~username/dokuwiki/doku.php to access the dokuwiki, etc. 

Shrink Preview PDF files without ruining image quality

The following instructions at the given link are pretty useful.

http://www.macworld.com/article/1168311/shrink_preview_files_without_ruining_image_quality.html

If you are not satisfied with results of the Reduce File Size filter (which we use to make PDFs small enough to send by e-mail, etc), follow these steps:

Go to the folder /System/Library/Filters, and open the XML file: Reduce File Size.qfilter

Now rename (copy) that into three files: Reduce File Size Good.qfilter, Reduce File Size Better.qfilter, and Reduce File Size Best.qfilter. Then change the parameters of each file: 0.25, 0.5 and 0.75 for Compression Quality (respectively) and 842, 1684, and 3508 for ImageSizeMax (ditto). (The first is A4-size at 72dpi, the second A4 at 144dpi, and the third A4 at 300dpi).

Finally, change the default string for the Name Key at the end of each file—which is what displays in the Export menu—to match its file name. 

You will have 3 versions of PDF quality filters, when you "export" files to PDF next time. 

CUDA Clang Error on Mac OSX 10.8

If you got the following error in compiling CUDA sample codes on your Mac OSX 10.8

clang: error: unsupported option '-dumpspecs'
clang: error: no input files

The best solution lies here: devtalk.nvidia.com forum link 

This is what is been suggested and that worked for me: 

I had the same problem, thanks to martindeveloper. I found the 
findcudalib.mk but didn't have llvm-g++ (tried to install it but lost 
like 2 hours for nothing, because it doesn't come anymore with XCode and 

compiling it from llvm.org didn't work). Tried with gcc/g++ but nothing
 worked



Finally, I changed GCC ?= g++ to GCC ?= /usr/bin/clang (on findcudalib.mk) 

and everything worked fine (even if clang support is beta)

To find out lines of codes in a source code directory

Use:

find ./name-of-dir '*.php' | xargs wc -l

OR

( find ./name-of-dir -print0 | xargs -0 cat ) | wc -l 

ref: link 

Start and access Amazon EC2 micro ubuntu instance.

Logon/sign in: http://aws.amazon.com/ec2/

Start an ubuntu micro-image, Eg:
ebs/ubuntu-images-milestone/ubuntu-oneiric-alpha2-amd64-server-2011*** (ami-00b14b69)

create a keypair:_ something.pem

change the permission of something.pem to 400:
sudo chmod 600 something.pem

create security group:
- open ssh, tcp - in the security group, by editing/adding rules.

access the virtual machine using ssh, using public DNS of instance:
For ubuntu machines, default user is ubuntu:

So, access it like:
ssh -i something.pem ubuntu@ec2-67-202-**-***.compute-1.amazonaws.com

To install gcc/openmpi

sudo apt-cache search make g++ libopenmpi-dev openmpi-bin openmpi-doc build-essential gcc-multilib libstdc++6
sudo apt-get -y update
sudo apt-get -y install make libopenmpi-dev openmpi-bin openmpi-doc build-essential gcc-multilib libstdc++6

iweb parsing error - fix

If there is a Parse error: syntax error, unexpected T_STRING, etc in publishing a website developed using iweb on web hosting servers, try the following. I got it fixed.

• create a file named ".htaccess", where you put "index.html" (or folder called "public", some say - I havent tried this).

• Add either of the following line to that file:
• php_flag short_open_tag off
  -- OR -- 
• php_value short_open_tag 0

That should fix the problem. I got the tip from the following link. It works for me.

http://answers.yahoo.com/question/index?qid=20081022040450AAY1T8u

BACKUP USING RSYNC & CRON

(I'm only copying the content from the link given below. Just for your convenience, if at all the link disappears, at some stage)

 

Submitted by Daniel on Thu, 05/08/2008 - 08:00 

I wanted to backup my home directory using rsync to a separate drive, and to make it happen automatically.
I spent ages doing research into the various commands, and found everything I needed to know, but not all in the same place. While it was fun for me, others may just want to know how to do it immediately.  So here goes!
The rsync command
sudo rsync -av --progress --delete --log-file=/home/your-username/Desktop/$(date +%Y%m%d)_rsync.log --exclude "/home/your-username/.gvfs" /home /media/HomeBackup
the -av bit: 'a' means archive, or copy everything recursively preserving things like permissions, ownership and time stamps. The 'v' is verbose, so it tells you what its doing, either in the terminal, or in this case, in the log file.  --progress gives you more specific info about progress.
--delete checks for changes between source and destination, and deletes any files at the destination that you've deleted at the source. --log-file saves a copy of the rsync result to a date-stamped file on my desktop.
--exclude leaves out any files or directories you don't want copied. In my case, the .gvfs directory in Hardy Heron was a pain as even with sudo it errored and wouldn't copy properly, so I excluded it (Its not necessary to copy it anyway)  If you don't use Hardy yet, or any distro using the latest Gnome, skip this line, or upgrade!
/home is the directory I want copied. /home copies the directory and its contents, /home/ would just copy the contents
/media/HomeBackup is the separate drive.  Change this to whatever your backup location is. You can actually have this drive off-site and use ssh, but that will be a tutorial for another day!
The bash script
I was just pasting this command into Terminal each day, but wanted something automatic, so step one was a bash script.
Very easy, just open a new document in your favourite text editor, and type #!bin/bash followed by the command itself on a new line. So:
#!/bin/bash
sudo rsync -av --progress --delete --log-file=/home/your-username/Desktop/$(date +%Y%m%d)_rsync.log --exclude "/home/your-username/.gvfs" /home /media/HomeBackup
Save that as rsync-shell.sh on your Desktop and make it executable by typing
sudo chmod +x /home/your-username/Desktop/rsync-shell.sh   
or by right-clicking the file, select Properties, Permissions and then checking the Execute box
You can now double click that .sh file, choose 'Run in Terminal', it will ask you for your password and run, then leave a log file on your desktop.
or, you can make a cron job to do it for you!
The cron job
My biggest obstacle with this was the sudo bit. rsync won't be able to backup all files, or delete any, without root privileges. I didn't want to have to be there when it runs to type in my password, but after a bit of searching I found out how to make a root cron job.
Copy your .sh file to /root by typing
sudo cp /home/your-username/Desktop/rsync-shell.sh /root
Then type
sudo crontab -e
You'll see a line which reads:   # m h  dom mon dow   command
Under that type
0 22 * * * /root/rsync-shell.sh
What this all means is:
1. The number of minutes after the hour (0 to 59)
2. The hour in military time (24 hour) format (0 to 23)
3. The day of the month (1 to 31)
4. The month (1 to 12)
5. The day of the week(0 or 7 is Sun, or use name)
6. The command to run
So at 22:00 (10pm) every day root will run the shell script, without prompting you for sudo password (because its running as root already)
Now press Control-X, then type Y, then press enter.
You'll see   crontab: installing new crontab
And you're done!
 
"I hope this helps!" <--- I borrowed this line from Verbal, but I am sure he's made it Creative Commons!

The original quoted link:

http://www.linuxbasement.com/content/backups-using-rsync-bash-cron

Follow this link to create loginless ssh:

http://blogs.sun.com/jkini/entry/how_to_scp_scp_and