Background information

http://www.dd-wrt.com/wiki/index.php/Linksys_E2000

http://www.dd-wrt.com/wiki/index.php/Installation

Steps Taken

- 30/30/30 Reset
- Upload dd-wrt.v24-18024_NEWD-2_K2.6_mini-e2000.bin via Linksys firmware upgrade page from ftp://ftp.dd-wrt.com/others/eko/BrainSlayer-V24-preSP2/2011/12-20-11-r18024/broadcom_K26/
- Wait 5 minutes after upload completed.
- Web interface for DD WRT appears.
- Do a 30/30/30 reset again.
- Wireless > Advanced Settings enter 50 in the Tx Power entry. This should make for less Tx/Rx Errors and help the unit run cooler.

General:

- Initital DD WRT firmware flash must be a trailed build. A trailed build has “*e2000.bin” in its name. Following flashes must have “*e2k-e3k.bin” in their name.

This can be done by adding the following lines to the junit task:

<junit fork="true">

		<!-- For remote debugging from Eclipse -->
		<jvmarg value="-Xdebug" />
		<jvmarg value="-Xnoagent" />
		<jvmarg value="-Djava.compiler=NONE" />
		<jvmarg
value="-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y" />

This will make the task wait for an incoming debug connection on port 8787. It is necessary to have the fork attribute on the junit task set to true, because the jvmarg values can only be given to a starting Java virtual machine.

Result

Finding files by date: http://www.cyberciti.biz/faq/howto-finding-files-by-date/

Windows

• Recuva – Excellent at recovering data from Windows partitions and free to boot.
• UFS Explorer – Not free, but is able to recover from linux partitions (Recuva is better for FAT/NTFS)
• explore2fs – Access linux partitions from Windows. Free.
• HFSExplorer – Access Mac partitions from Windows

Linux

• Hiren’s Boot CD – Contains an impressive lineup of programs for computer forensics, but its legal status is often debated.
• Trinity Rescue Kit – A live distro with backup programs, Midnight Commander, testdisk, shell and other good stuff. Legal!

will throw the ClassCastException.
The trick is to use the overloaded version of toArray(), which takes an array as parameter. This the javadoc description of the method

The solution is therefore to do this:

Lightrooms data files can roughly be put into two categories: The catalog file(s), which contain meta data about your images such as their location and the actual image files.

Lightroom does not permit having the catalog files on network attached storage, so you will have to keep those on your workstation. However, you can choose to have Lightroom backup your catalog files to the NAS so they are stored together with your images. This can be configured by going into Edit > Catalog Settings in Lightroom.

The following steps explain how to move your images from your workstation to a location on the NAS.

• Locate your catalog file (you can find it in Edit > Catalog Settings) and make a backup of it. Just as a safety precaution.
• Locate the folder containing your images and copy it to the NAS
• Rename the local image folder to something like ‘images_OLD’
• Open Lightroom
• In Library mode, there should now be question marks on the folders, since we renamed the image folder to images_OLD
• Right click on each folder and select its new location on the NAS
• Once all folders have been resolved, do a quick check, that all images are there

If something goes wrong you can always replace the catalog file with the backup from step 1 and rename the images_OLD back to using your local image folder.

Performance

As to be expected, there is a slight performance drop, by having the images on a network share instead of a local harddisk. In order to quantify the difference I picked 10 test photos (RAW) and measured the the time it took to zoom in on the image in Library mode. Zooming in on an image forces the actual image to be loaded into memory instead of just showing a preview.

• Avg. zoom time Local: 6 seconds
• Avg. zoom time NAS: 6.9 seconds

Not much of a difference and hardly noticable. I have not timed any other operations, but it appears, that the main loading happens only once. I.e., there is no lag when cropping or fixing white balance, since the image has already been loaded into memory.

• A standby signal is sent to the disk.
• Wait until a process wakes up the disk and then prints out name of that process.
• Repeat.

The following link contains a list of daemons and configurations known to cause random disk activity: Standby Mode FAQ
Older versions of Squeezebox Server caused lots of disk activity, but fortunately that has been resolved in version 7.5.1.
What is jdb2 and flush?
Sometimes the processes “jbd2″ and “flush” are waking up the harddisk. As I understand, these processes are responsible for doing delayed writes to the disk in order to optimize performance. In other words, they are writing to the disk on behalf of other processes which makes it difficult to find the culprit(s). In my case, it was the samba daemon accessing the disk. As long as a PC or media streamer on your network has an open view on any of your samba shares, it will cause the disks to wake up.

• Do an fdisk /dev/sdv
• type d to delete any existing partitions.
• Type n to create a new partition.
• Make it primary and first
• Go with the defaults when prompted for start and end cylinder
• Press t to change the filesystem to linux (number 83)
• Type w to write the changes to the disk and exit

Finally, format the partition with the ext3 filesystem:

Now the partion is formatted and it can be mounted again:

The USB drive is now ready for use

Every script in that directory represents a daemon, which can be started, restarted and stopped manually using the following syntax:

If, for example, I wanted to restart an nzb-get daemon due to changes in its configuration files, I would type

After issuing the command, the daemon will usually print some lines to the terminal indicating what it is doing, e.g.: ”Starting NZB-Get Daemon” or “Shutting Down“.

If you want to make sure whether a daemon is running or not, you can grep for its name in the list of running processes. If I wanted to see if the nzb-get daemon was really started, I could do the following grep:

If the daemon is running, this will produce a result like:

The first line is the daemon. Notice the “–daemon” at the end of the line. The second line is the grep process we just ran to find the daemon.