The cloop 1.2 ebuild has some small problems. The ebuild checks for kernel 2.4 and if found creates the needed /dev/cloop nodes. Kernel 2.6.12 howevr (and probably others) do not create the nodes themselves, but can be told to do so by the mknod command found in the ebuild. Maybe we should skip this step, and always create the nodes, or add the command to the start.local since it apears not be persistant. Also the ebuild checks for config_zlib_deflate, and asks the user to enable it, but doesn't mention the parent config options, puzzeling newbee kernel configgers. Reproducible: Always Steps to Reproduce: 1.emerge cloop (and if needed make sure kernel is configged with zlib-deflate etc) 2.notice the absense of /dev/cloop 3.mknod /dev/cloop 260 0 4.modprobe cloop /home/user/file 5.mount -o ro /dev/cloop /home/user/compressed 6.after reboot however the /dev/cloop is gone. Expected Results: create the nodes, or load, on emerge, or on boot. And thus allow the user to mount the just clooped file. i tried this on amd64, with kernel 2.6.12, and i think udev (which is the newest right? (udev/devfs)
It works for me, are you sure you have udev installed? ls /dev/.udev ?
(In reply to comment #1) > It works for me, are you sure you have udev installed? > > ls /dev/.udev > ? Yes i do. What kernel are you using? and how are you loading the module?
2.6.14-rc2-mm2 And I just do modprobe cloop and have plenty of /dev/cloop* after that
I cannot reproduce that, please give more info about your setup. Are you sure you are using the latest cloop version?
