/etc/fstab:
----------
/dev/mapper/crypt-tmp           /tmp                    ext2            noatime                                                         0 1

/etc/conf.d/cryptfs:
-------------------
## /tmp
mount=crypt-tmp
options='-c aes -s 256 -h sha256 -d /dev/urandom'
source='/dev/hda9'
pre_mount='mke2fs ${dev}'
post_mount='chown root:root ${mount_point}; chmod 1777 ${mount_point}'

Error at boot:
-------------
Skipping invalid line in /etc/conf.d/cryptfs: mount=crypt-tmp
...
mke2fs 1.39 (29/05/2006)
fsck.ext2: No such file or directory while trying to open /dev/mapper/crypt-tmp
/dev/mapper/crypt-tmp: superblock could not be read
...
(try with command)
e2fsck -b 8193 <device>

Convo
-----
<Brain> fsck.ext2: No such file or directory while trying to open /dev/mapper/crypt-tmp
<Brain> hmn
<n3Cre0> yes because it skipped it
* [Brain] is away (away)
<Brain> what parameters is mke2fs called with then
<n3Cre0> any cmd to "create" it?
* [Brain] is away (away)
<Brain> like what does it do 
<n3Cre0> dunno
* [Brain] is away (away)
<Brain> to create it? sure
<Brain> cyptsetup -c aes -s 256 -h sha256 -d /dev/urandom create crypt-tmp /dev/hda9
<Brain> I think

Shell
-----
Gentoo theirman # ls /dev/mapper/
control  crypt-swap
Gentoo theirman # cryptsetup -c aes -s 256 -h sha256 -d /dev/urandom create crypt-tmp /dev/hda9
Gentoo theirman # ls /dev/mapper/
control  crypt-swap  crypt-tmp

When reboot: same error.

After reboot:
Gentoo theirman # ls /dev/mapper/
control  crypt-swap

Screen partitioning:
-------------------
http://img479.imageshack.us/img479/7858/gpartedgf8.jpg

Convo #2:
--------
<Brain> I just installed another system and get same problems, seems syntax has changed
<n3Cre0> Gentoo theirman # cryptsetup --version
<n3Cre0> cryptsetup-luks 1.0.4
<Brain> see /lib/rcscripts/addons/dm-crypt-start.sh
<Brain>   # check for the start of a new target/swap
<Brain>                 case ${targetline} in
<Brain>                         target=*|swap=*)
<Brain> so try target not mount
<Brain> in that version
<Brain> brb
<n3Cre0> I did that ;/
<n3Cre0> yeserday night I did
<n3Cre0> mount=tmp
<n3Cre0> target=crypt-tmp
<n3Cre0> options='-c aes -s 256 -h sha256 -d /dev/urandom'
<n3Cre0> source='/dev/hda9'
<n3Cre0> pre_mount='mke2fs ${dev}'
<n3Cre0> post_mount='chown root:root ${mount_point}; chmod 1777 ${mount_point}
<n3Cre0> didn't work
<Brain> mount=tmp
<Brain> no 
<Brain> remove that line
<n3Cre0> just target?
<Brain> think so
<Brain> when looking at the code
<Brain> target and options source pre_mount and post_mount
<Brain> that might work
<n3Cre0> k now I got:
<n3Cre0> target=crypt-tmp
<n3Cre0> options='-c aes -s 256 -h sha256 -d /dev/urandom'
<n3Cre0> source='/dev/hda9'
<n3Cre0> pre_mount='mke2fs ${dev}'
<n3Cre0> post_mount='chown root:root ${mount_point}; chmod 1777 ${mount_point}'
<Brain> well your version is unknown to me
<Brain> but that is my guess
<Brain> after checking the script that loads it
<n3Cre0>                 # check for the start of a new target/swap
<n3Cre0>                 case ${targetline} in
<n3Cre0>                         target=*|swap=*)
<n3Cre0>                                 # If we have a target queued up, then execute it
<Brain>                 # check for the start of a new target/swap
<n3Cre0> hehe
<n3Cre0> else:
<Brain> not                 # check for the start of a new mount/swap
<n3Cre0>  ewarn "Skipping invalid line in /etc/conf.d/cryptfs: ${targetline}"
<Brain> as it is in my old version
<n3Cre0> and that's what I get
<Brain> someone didn't update example config