I was running kernel 2.6.8-3-k7 but found it had a problem with IDE devices that kernel 2.6.8-3-686 fixed. But not I am unable to install fuse.


Why are 2 packages list but not installable ?
Thanks for reading.

Not sure about Debian or APT, but I got fuse working in FC6 with a custom compiled 2.6.18.1 kernel my manually compiling the package (i. e. by not using any form of package manager).

First, I recompiled the kernel and turned off fuse support, since it seemed the kernel had an old version of fuse imbedded. I then compiled fuse myself (the simple ./configure; make; make install; steps known to all) and installed it.

The fuse compile results in a kernel module file:

fuse.ko

You then just need to load this module into your running kernel:

insmod fuse.ko

in the directory where the fuse.ko module appeared after you finished your compile of fuse. You should then have fuse support.

Then of course you can use fuse with ntfs-3g to get read & write NTFS access to your Windows partition (or whatever):

/usr/local/bin/ntfs-3g /dev/hda1 /mnt/win (create the mountpoint first)

I. e. your best solution (at least from my viewpoint, since APT is not working) is to download fuse and compile and install it yourself, as I explained above.

If you still have trouble, post again, or if you need more help.

Yes, this thought crossed my mind, especislly with a fuse-source ackage being listed with apt-get.

But I don't understand why there wouldnt be a fuse module for a 686 kernel, yet a k7 kernel with same version has it.

Well I installed the fuse-source package which was a tarball that sat in /usr/src
I then needed to grab the kernel-headers of this kernel I am running now and then ran 'cd /usr/src && m-a a-i fuse' and got a kernel module.

I don't recall doing that in the k7 kernel, but perhaps I did, late at night, and dont recal now

That's the thing with any "package" type setup... if nobody have found it neccessary / worth their while to package a particular type of binary / module the way you need it, you're pretty much up a creek with no paddle. All you can do then is roll your own by using the source.

1)You forgot some architectures : http://www.debian.org/ports/
2)Also against which kernel should it be compiled? A module won't load if it is designed for another kernel.

You only had to launch m-a and then move in the menu.Update then Prepare and then Build and Install.
Not that complicated (and on newer kernels fuse is already in)

Ahh that explains it then. Makes sense now.

Cheers

I still find this odd.
Does this just means its listed, but shouldn't be in the repo's; its an old listing thats no longer supported in Sarge ?

For your error, you should get more information if you type this:
Probably you only have it in your local repository?

Anyway, this module has to be build.

You should have a binary module for your architecture and for sarge in /usr/src.
Install it with

m-a spits out

Not sure why, I just installed VMware-server on that needed the kernel source, header and kbuild packages.

It's a warning that probably the linux source that you have, has not been configured yet.
Running make menuconfig, saving and quitting in /usr/src/kernel-source-2.6.8 will remove this warning.

I should have been more explicit.

It says the module wasn't built properly and to check /var/cache/modass/fuse-source*buildlog*

But there's no log's in there starting with fuse-source*

I build this before a more manual way, but forgotten how now

Hahaha, if I only read back in this very thread I can see what I did. Ran that command and got more info in a more verbose ncurses window

"make[1]: dh_clean: Command not found"

So...

And then re-ran m-a a-i fuse (which I am guessing is the same as m-a install fuse) and all worked.

No. Doing this to create the .config didnt remove the warning. But all working now, so not a "show stopper" warning.