Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

i need this old version of fuse to work with siefs. i've tried to patch it just
like version 2.1 (with changing vfs-permission to generic-permission if
needed), but no success with that....

Created an attachment (id=47393) [details]
fuse-1.4-kernel-2.6.10.patch

just changing it like in fuse-2.1 worked for me .. strange

i've tried your patch and it doesn't work either. fuse is installed, but i
still have warning about this unknown symbol:

<root@CogES>/tmp: emerge --oneshot =sys-fs/fuse-1.4
Calculating dependencies ...done!
>>> emerge (1 of 1) sys-fs/fuse-1.4 to /
>>> md5 src_uri ;-) fuse-1.4.tar.gz
>>> Unpacking source...
>>> Unpacking fuse-1.4.tar.gz to /var/portage/tmp/portage/fuse-1.4/work
 * Applying fuse-1.4.patch ...                                            [ ok
]  < this is patch posted by you

[... all compiling and installing stuff...]

 * Checking kernel module dependencies
WARNING: //lib/modules/2.6.10/fs/fuse.ko needs unknown symbol vfs_permission
>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies ...                                       [ ok
]
>>> sys-fs/fuse-1.4 merged.

i've tried also always change vfs_permission to generic_permission (without the
"if ... else... endif" clause) in case my kernel isn't recognized corectly, but
that doesn't help either. it's strange, becouse greping for vfs_permission in
all fuse's sources shows only those two places in dir.c (so if i changed it
where can this warning comes from?;/ )

if you got any ideas what else i can try, please let me know....

BTW: i'm using vanilia 2.6.10, downloaded and configured manually (not handled
by portage)

i've found solution for it. it's about inconsequency in diffrent fuse version.
fuse-2.1 (which i've had installed by mistake at begginning) installs module in
 /lib/modules/2.6.10/fs/fuse.ko. then i've realized i need version 1.4 so i
simple emerge it, but while merging 1.4 it want's to install in
/lib/modules/2.6.10/kernel/fs/fuse/fuse.ko

in the other hand - portage will never remove /lib/modules/2.6.10/fs/fuse.ko,
even during deinstalation of fuse-2.1, couse this dir belongs to
$CONFIG_PROTECT (by default), so we've got two modules named fuse in kernel dir

i do not now why i had that warning with vfs_permision, since version 2.1 is
patched by default anyway and i can't reproduce it now, however as you can see
- it's impossible to automatically downgrade from fuse-2.1 to -1.4 and what's
worse - user'd think that he made it (well - i'm not sure which module'll be
loaded during modprobe fuse, but i assume it'd be the one from 2.1 version)

solution (or rather workaround) for that is manually remove module from 2.1
version. after that i was able to emerge 1.4 without warning (your patch
hovewer is still needed and shoulkd be included in portage)

I changed the old ebuild to also install in /lib/modules/$KV}/fs