dokuwiki thumbnail image to pdf

I recently had the requirement to make a kind of catalogue overview within our internal company wiki. After googling for a plugin I decided to do it the pragmatic way because our catalogues do not change that frequently.

  1. Save the pdf files to the wiki medi location (upload)
  2. open the pdf files and make images from the startpage, used as thumbnails later
  3. upload the images to the wiki
  4. create a link to the media using the image (see example syntax below)
  5. finished

Example Syntax:
[[http://<wiki url>/lib/exe/fetch.php?media=<wiki path to pdf file>|{{<one of the uploaded images in size M>?200|}}]]

So you will get a kind of thumbnailed pdf gallerie. If your content does not change that recently, the thumbnails are the work here, this will be fine.

 

Restoring a hanging osx system with all your data

Hi I had a problem recently with the osx system of my daughter. The SSD disk I built in 1 year ago started to get corrupted file systems. Long boot times (gray progress indicator), failing fck calls have been the result plus at last a system which won’t boot any more. I had no current backup of the system so there was also the problem of the data.

Luckily I had a ccc (carbon copy clone) of my own system. So all you need is the following:

  • usb disk/stick with a ccc clone of a working osx
  • usb disk/stick for the clone of the broken system
  • a little time at your hand
  1. Boot up the system holding the „shift“ key on startup. Afterwards you will get a list of volumes to boot from, select the ccc clone of your working system.
  2. When the system is booted open up ccc and create a recovery partition on the destination usb disk you will use for the clone of the broken system, remind to select the matching osx version.
  3. Clone the entire disk content using ccc from the broken system to your prepared destination usb disk, this may take a while regarding the amount of data you have on your broken system.
  4. After cloning succeeded, open up disk utility and reformat the disk of the broken system. Remind to check the GUID partition table option and use the journaled HFS filesystem type.
  5. Now open up ccc again and clone the content from the prior cloned broken system back to the new formatted harddisk of the system. After finishing this, reboot the system.
  6. Hold down „CMD“ + „R“ to boot into recovery mode. Once there select „Reinstall OSX“, this will again take a little time but afterwards you will be rewarded by a system working the same way as it has before stopping booting. No user data lost, no settings lost, everything is fine.

Corrupted OSX filesystem – mac constantly shutting down on startup

Hi if you have experienced the following behavior of you mac there has to be something wrong with your filesystem:

the grey progress bar is coming up on startup (fsck is running long in the background)

a little later (days, weeks) the mac is shutting down short after progress bar appears

you may have a corrupt BTree in your filesystem. This is normally a sign that your hard disk fails and will soon die. But you want to make a backup but can’t right?

Then do the following:

  1. Right after switching on press CMD + S for entering single user mode
  2. on the command line enter: fsck -f
  3. mount the filesystem: mount -uw /
  4. check what name your disk device has by entering: df -hl (there should be an entry like /dev/disk0s2, note it down)
  5. reboot into safe mode
  6. type the following: fsck_hfs -y -rc -d /dev/disk0s2 (what you noted down earlier)
  7. wait for the process to complete. If the message „The volume…. could not be repaired after 3 attempts“ appears repeat step 6 until you get the message „The volume…. was repaired successfully“
  8. reboot your system
  9. Voila

 

 

MacBook Air Battery Drain – LogMeIn

Hi. I have experienced a significant battery drain throughout the last months. I recently changed to a 2013 MacBook Air from my late 2010 Air and was disappointed because I thought the newer faster macbook took up more battery and therefore has less runtime. But I got curious when I saw the mds and mdworker processes come up in the activity monitor application with cpu load off 100% and higher. I therefore changed to the terminal application and used the lsof command to identify which files are currently in use and I found out that mds and mdworker are permanently using a file located in the LogMeIn Directory. LogMeIn is an application for remote access to you Mac. It is deactivated on my system currently but nevertheless recently updates a log file in this directory:

/Library/Application\ Support/LogMeIn/log

Not always but sometimes there are recent changes to the log file every few seconds and spotlight tries to add the changes to the index but has to do so every few seconds, what results in high cpu load for mds and mdworker process, what eats up your battery.

Simply add the following directories to the privacy area of the spotlight configuration in system settings panel:

/Library/Application\ Support/LogMeIn

/Library/Application Support/LogMeIn Plugin

You are done and you should not loose any battery any more on this issue.