trying to use a fuse-fs fails, although fuse is present: grep FUSE /usr/src/linux/.config CONFIG_FUSE_FS=y and the initscript started: /etc/init.d/fuse status status: started trying to mount anything fuse fuse: device not found, try 'modprobe fuse' first and ls /dev/fuse ls: cannot access /dev/fuse: No such file or directory Reproducible: Always Steps to Reproduce: 1. build fuse into the kernel 2. only tried with baselayout-2, don't know whether this is related 3. try mounting a fuse filesystem Actual Results: fuse: device not found, try 'modprobe fuse' first Expected Results: mount a filesystem I tried all the versions of fuse in the tree and all fail. works all right after creating the node "by hand": mknod /dev/fuse c 10 229 chmod o+rw /dev/fuse emerge --info (shorter version) Portage 2.1.4.4 (default-linux/amd64/2007.0/no-multilib, gcc-4.2.2, glibc-2.7-r2, 2.6.24-gentoo-r7 x86_64) ================================================================= System uname: 2.6.24-gentoo-r7 x86_64 AMD Opteron(tm) Processor 248 Timestamp of tree: Fri, 18 Apr 2008 06:45:01 +0000 app-shells/bash: 3.2_p33dev-java/java-config: 1.3.7, 2.1.6dev-lang/python: 2.4.4-r9dev-python/pycrypto: 2.0.1-r6sys-apps/baselayout: 2.0.0sys-apps/openrc: 0.2.2sys-apps/sandbox: 1.2.18.1-r2sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ABI="amd64" ACCEPT_KEYWORDS="amd64"
What udev version do you use (if you use it)?
(In reply to comment #1) > What udev version do you use (if you use it)? > I was using the stable version at that time, extract of emerge.log (I forgot how to read the time tag, sorry) 1198101688: >>> emerge (72 of 72) sys-fs/udev-115-r1 to / 1198101705: >>> unmerge success: sys-fs/udev-104-r12 1198101705: ::: completed emerge (72 of 72) sys-fs/udev-115-r1 to / 1208509651: >>> emerge (38 of 40) sys-fs/udev-120 to / 1208509670: >>> unmerge success: sys-fs/udev-115-r1 1208509670: ::: completed emerge (38 of 40) sys-fs/udev-120 to / 1208932192: *** emerge --tree --oneshot --verbose udev 1208932198: >>> emerge (1 of 1) sys-fs/udev-119 to / 1208932229: >>> unmerge success: sys-fs/udev-120 1208932229: ::: completed emerge (1 of 1) sys-fs/udev-119 to / 1208933463: *** emerge --tree --ask --verbose udev 1208933470: *** emerge --tree --oneshot --ask --verbose udev 1216086730: >>> emerge (25 of 321) sys-fs/udev-119 to / 1216086750: ::: completed emerge (25 of 321) sys-fs/udev-119 to /
please re-open if this is still an issue using a recent kernel and devtmpfs
