I've submitted this back to lensfun so hopefully this will appear in the lens db soon. For now here it is

My setup is a laptop with 2 hard drives. The second hard drive was pulled out of my older laptop so it was also encrypted with luks.

1. configure your wireless device through the network manager as usual so you can start it normally once logged in. Make sure Connection automatically and Available to all users is selected.
2. edit your /etc/init.d/network file and change the line "chkconfig: - 24 90", basically you need network to start after NetworkManager
3. run "chkconfig --del network", then "chkconfig --add network" (to reset the start order). then
   "chkconfig network on"

Now hopefully it works... it did for me.

The two main sources of noise are

1. Fan
2. Hard Drive

To slowdown the fan.... create a file /etc/modprobe.d/thinkpad_acpi.conf, it needs 1 line "options thinkpad_acpi fan_control=1". Then do "echo level 1 > /proc/acpi/ibm/fan" to change the speed to the slowest speed (with out stopping it). As usual I put that in my favourite startup script... /etc/init.d/cpuspeed. The level depends on your usage, I suspect 1 is fine for most people. It is enough to decrease the temperature to about 42C. When you use the cpu it will go up, but when it's mostly idle it will come back down. If you're using the cpu a lot like for games or as a production server then this won't do. For people who's cpu is idle most of the time, this will be quiet and cool.

To slow the hard drive down... "hdparm -M 128 /dev/sda". As always I put that in /etc/init.d/cpuspeed as well.

Now it's almost dead quiet. I can still heard the HD spinning slowly but the only way to get rid of that would be to buy an SSD which is still too expensive at this current time.

If you're resizing a partition, you just unmount it and use the partition manager and specify the size.

If it happens to be your root partition, you need to boot off of usb stick or something as the partition should not be mounted.

1. boot off a usb disk like the net install image on a usb stick.
2. drop to the friendly command line
3. "modprobe dm-crypt" to load the encryption module
4. "cryptsetup luksOpen /dev/sda1 crypt1" to unencrypt the partition where /dev/sda1 is your encrypted luks partition
5. "lvm vgscan --mknodes" and "lvm vgchange -ay" to activate the encrypted partition
6. "e2fsck -f /dev/mapper/vg_tedst410-lv_root" to check the partition
   
7. "resize2fs -p /dev/mapper/vg_tedst410-lv_root 200g" to resize that file-system to 200 gigs (yes that's the file system only, not the partition)
8. "e2fsck -f /dev/mapper/vg_tedst410-lv_root" to check to make sure it's still ok
9. "lvreduce -L 200G /dev/vg_tedst410/lv_root" to resize the partition to 200 gigs.

I wrote this after I ran all the commands so double check the parameters before running it.

I needed a long remote shutter release for my E-P1. This is the details :

The first thing you need to know is the pins to release the shutter. The pins are pointed out in green. From some postings on the internet, they refer to the top pin as "pin 11", the bottom pins from left to right is "pin 4" and "pin 3" respectively.

pin 11 + pin 3 = half press i.e. focus.
pin 11 + pin 3 + pin 4 = full press i.e. shutter release.

You can hard wire pin 4+11 together if you never want to pre-focus. This means when pin 3 is added, it will focus then shutter.

(After further investigation, it appears pin 3 & 9 can be used interchangeably, maybe it's just the ground?)

So the question is, where do you get such a plug. The answer is... that video out cable you never use. Take the video out cable and cut the plastic cover off the plug.

Once you remove the cover you will be left with a plug which you can pull off the cable. There's a bunch of metal contacts sticking out. Here you have 2 choices, yank them all out, or yank them all out except pins 3/4/11. If one of those pins came out with the cable, you'll have to put one of the other pins into the spot. You now need to solder a wire to the contacts, so either solder the wire to the contacts sitting in the plug, or solder a wire to the pins and then put them into 3/4/11 of the plug.

This is a picture of me testing the pins... I just stuck the plug into the camera and hot wired the pins to test.

For the wire, I used a telephone cable. It's cheap and has 4 wires, I only really needed 3 of the wires.

Once the plug is soldered to the wire, just blob a ton of hot melt glue over it to make it a solid piece.

On the other side, I bought 2 press button switches. One switch activates the focus, the other activates the shutter. The plan is to tape the two buttons together so pressing it will cause it to focus and shutter.

The picture is the finished result. 2 metres long and works like a charm.

I need to put this command some where so I can find it in the future... so it's going to go right here :


you need the sync in there to flush the buffer, then you need to calculate the time manually, i.e.

... 1073741824 bytes (1.1 GB) copied, 293.588 s, 3.7 MB/s ...
... real    4m56.374s ...

4*60+56 = 296 seconds
1073741824 bytes = 1024 MB
1024/296=3.45 MB / second (a.k.a. in sd card terms class 3.45 :) )

I tried to install windows xp in kvm on fedora 12. The result was a very very slow windows xp virtual system. After some tinkering, I think I found my problem. My fedora 12 is x86_64 so the virtual machine defaulted to emulating x86_64. When creating the virtual machine instance, change it to i686 instead under the advanced settings. Everything ran 10 times faster once I reinstalled the virtual machine instance like that.

Task	Command
Partition your media	fdisk /dev/sdb
Set the raw partition as encrypted	cryptsetup luksFormat /dev/sdb1
Create a temporary mapping so you can format partition for usage. I'm calling the temp mapping "temp".	cryptsetup luksOpen /dev/sdb1 temp
Format the encrypted partition	mkfs.ext3 /dev/mapper/temp
Set the label of the partition. I'm calling my partition backup.	e2label /dev/mapper/temp backup
un-map the temporary mapping	cryptsetup luksClose /dev/mapper/temp

At this point you will have an encrypted drive. If you unplug it and plug it back in it will automatically prompt you for the password and mount it. If you use the GUI to unmount the partition everything will work fine. If you accidentally umount it from the the command line or unplug the drive with out unmounting it, you will receive an error the next time you try to mount it. To fix that, you need to run the "cryptsetup luksClose" command on /dev/mapper/xxxxx where xxxxx is the mount point it complains about when it tries to mount it.

• If you install F12 with ext4 the system is slow, if you do the exact same install with ext3 it is quick.
• If you test with an external HD, you get mixed results, sometimes it was quick on external usb drives even when formatted with ext4.
• If you make a spare partition on your main HD, you can see the results by making it ext3 / 4 and restarting your MySql.
• It's not simply and ext4 overall performance problem though, a test of zipping a slew of small files (source code) showed ext4 was running faster than ext3.
• Another way to notice the problem but not as severely was to import a mysql database. An imports seemed to take 33% longer than previously.
  

My final solution was to re-install F12 using ext3 as the file system. This resolved all my problems.

For reference, I was also using encryption on the HD but I also tested it with out encryption with similar slow down results. I also played with turning on and off selinux with no real effect.

-----

Upon further investigation it appears that it has to do with write barriers. http://kernelnewbies.org/Ext4#head-25c0a1275a571f7332fa196d4437c38e79f39f63 allegedly if you mount the FS with barrier=0 it will run a lot faster. There are integrity ramifications though.

-----

Update for Fedora 14 :
Installed Fedora 14 today and unfortuntely the problem still exists.

Here's a few snippets from my ext3 system running FC12:
 
Here's the same on ext4 using defaults running FC14:

As you can see it's roughly 10x slower... than ext3 on FC12.

Here's ext4 after setting barrier=0 in /etc/fstab on FC14


The performance is still about 3x worst than ext3 on FC12.

Here's ext3 and defaults on FC14 :


The performance is still 2x worst than ext3 on FC12.

Here's ext4 and noatime,nodiratime,barrier=0,data=journal,commit=30 on FC14 :


Performance is now about 1.5x worst than FC12 & ext3.

Here's ext3 and noatime,nodiratime,data=journal,commit=30 on FC14 :


YAYAYA!! kind of. It's still about 10% slower than FC12 & ext3 but that's acceptable for me - for now.

The kickers is that I had to enable data=journal which wasn't enabled on my FC12 system it was using the default writeback. For fun... I went back to the FC12 system and enabled journal. As expected it was slower... by about 20% (the unexpected result is that journalling was faster in FC14...).