With the above configuration, it seems that the init.d/bcrypt script on startup first removes the /dev/bcrypt[0-15] nodes: start() { ebegin "Initializing BestCrypt" declare -i status=0 rm -rf /dev/bcrypt?* 2>/dev/null Then checks to see if this is a 2.2 kernel, and creates the nodes if it is: if [ $KERNEL_VERSION = "2.2" ]; then mknod -m 666 /dev/bcrypt0 b 7 128 ....snip.... mknod -m 666 /dev/bcrypt15 b 7 143 if not, then it checks to make sure there is no /dev/.devsfd character device: else if [ ! -c /dev/.devfsd ] If there is NOT, it would create the /dev/bcrypt nodes: mknod -m 666 /dev/bcrypt0 b 188 0 ...snip... mknod -m 666 /dev/bcrypt15 b 188 15 Next it loads the bestcrypt modules. (which all load fine btw) The problem I am seeing is that because I am NOT running a 2.2 kernel, and I DO have the /dev/.devsfsd character device node, the initscript does not create ANY device nodes that the bcmount command understands, and as such bestcrypt does not work, and I am not able to mount any containers. The fix I have found to work is to simply create a symlink: /dev/bcrypt0 -> /dev/bcrypt/disc0/disc where /dev/bcrypt/disc0/disc is: brw-rw-rw- 1 root root 188, 0 Mar 26 16:31 disc I would be happy to help with any updated scripts, or with any other information to help resolve this. Thanks! Reproducible: Always Steps to Reproduce: 1. emerge bestcrypt, rc-update add bcrypt default 2. restart system 3. try to mount a bestcrypt conatiner 4. create symlink: ln -s /dev/bcrypt/disc0/disc /dev/bcrypt0 5. mount bestcrypt conatiner works fine.
I'd suggest going to udev but any script improvements would be appreciated.
files/bestcrypt.devfs is ment for devfs to create nodes. I know it isn't pretty but I don't know devfs well enough to fix it. bc-1.6_p1 added too for testing.
I assume you've fixed this with udev. I'm sure there's a devfs way to fix this and I've tried before and failed (cause I didn't care enough).
