Help: FUSE installation problem

Hello,

My Linux is RHEL 3 with 2.4.21-47.EL kernel. I wanna install
ntfsprogs-2.0.0, so I need to install fuse-2.7.0 first. However, when I
use ./configure to operate, it stops with this error message:

checking kernel source directory... /usr/src/linux-2.4.21-47.EL
checking kernel build directory... /usr/src/linux-2.4.21-47.EL
checking kernel source version... Not found
configure: error:
*** Cannot determine the version of the linux kernel source. Please
*** prepare the kernel before running this script
configure: error: ./configure failed for kernel

The Linux source code is in /usr/src/linux-2.4.21-47.EL, I don't know why
it cannot go on configuring.

How to solve this problem? Is there any other NTFS read/write access
software? My system is RHEL 3.

Thank you very much~

Regards,

Amy Lee

Amy Lee staggered into the Black Sun and said:
> RHEL 3 with 2.4.21-47.EL kernel. I wanna install ntfsprogs-2.0.0, so I
> need to install fuse-2.7.0 first. However, when I use ./configure :
>
> checking kernel source directory... /usr/src/linux-2.4.21-47.EL
> checking kernel build directory... /usr/src/linux-2.4.21-47.EL
> checking kernel source version... Not found
>
> The Linux source code is in /usr/src/linux-2.4.21-47.EL, I don't know
> why it cannot go on configuring.

The "kernel source RPM" distributed with Redhat/Fedora isn't *really*
the whole kernel source. It's just the relevant headers and possibly
the .config file. If the .config file isn't there, "zcat
/proc/config.gz > /usr/src/linux/.config". These headers are there so
you can compile additional kernel modules. These may not be all the
things that ntfsprogs needs, though.

In Fedora, at least, if you need the actual source tree that corresponds
to the Redhat-patched kernel that you're using, you have to download the
vanilla tarball and a bunch of patches. Then there's a set of commands
you have to run. This is a complete pain, and it's one of the main
reasons why I always build a recent vanilla kernel after installing a
distro. Dealing with distro patches is far more trouble than it's
worth, and vanilla kernels tend to have fewer weird bugs.

> Is there any other NTFS read/write access software?

Not really. ntfs-3g works well, but it needs FUSE. If there aren't any
packages for ntfs-3g for your distro, then your distro is dropping the
ball. Trying to go around the package system is possible, but it can
also be a lot of trouble. HTH anyway,

--
One OS to rule them all, with DRM to find them
One OS to bring them all and with the EULA bind them
In the Land of Redmond where the shadows lie.
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see

--------------------------------------------------------------------------------

http://www.arabzwaj.com/welcome/viewtopic.php?t=2455

http://www.arabzwaj.com/welcome/viewtopic.php?t=2457


http://www.arabzwaj.com/welcome/viewtopic.php?t=2455
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://www.arabzwaj.com/welcome/viewtopic.php?t=2456



11
http://www.arabzwaj.com/welcome/viewtopic.php?t=2458

On Sat, 13 Oct 2007 15:41:34 GMT, Dances With Crows
wrote:

>Amy Lee staggered into the Black Sun and said:
>> RHEL 3 with 2.4.21-47.EL kernel. I wanna install ntfsprogs-2.0.0, so I
>> need to install fuse-2.7.0 first. However, when I use ./configure :
>>
>> checking kernel source directory... /usr/src/linux-2.4.21-47.EL
>> checking kernel build directory... /usr/src/linux-2.4.21-47.EL
>> checking kernel source version... Not found
>>
>> The Linux source code is in /usr/src/linux-2.4.21-47.EL, I don't know
>> why it cannot go on configuring.
>
>The "kernel source RPM" distributed with Redhat/Fedora isn't *really*
>the whole kernel source. It's just the relevant headers and possibly
>the .config file. If the .config file isn't there, "zcat
>/proc/config.gz > /usr/src/linux/.config". These headers are there so
>you can compile additional kernel modules. These may not be all the
>things that ntfsprogs needs, though.
>
>In Fedora, at least, if you need the actual source tree that corresponds
>to the Redhat-patched kernel that you're using, you have to download the
>vanilla tarball and a bunch of patches. Then there's a set of commands
>you have to run. This is a complete pain, and it's one of the main
>reasons why I always build a recent vanilla kernel after installing a
>distro. Dealing with distro patches is far more trouble than it's
>worth, and vanilla kernels tend to have fewer weird bugs.

[ a little OT ]

'Crows, this is a little different than my recollection of Fedora
kernel building. IIRC, the "kernel development package" is the
set of headers needed for building modules. The "kernel source
package" _is_ the (most of) the full tree needed to actually build
a kernel.

This _seems_ to agree with my recollection:

http://fedoraproject.org/wiki/Docs/CustomKernel

Slap me if I'm wrong.

I have built a few Fedora kernels - both stock and modified be
me - using this approach. One word to the wise: the configs
that come with the kernel source (the versions I have tried
anyway) have kernel debugging enabled. Makes for GIANT modules.

Bill
--
William D Waddington
william.waddington-at-beezmo.com
"Even bugs...are unexpected signposts on
the long road of creativity..." - Ken Burtch