I have what I believe to be a straight-forward question: is it possible to disable the NTFS kernel driver and if so, how does one do that ?
I just built the latest FUSE+NTFS-3g and it works well, so far. Like most kernels, my Slax (Slackware-based live CD distro-2.6.16) system has the NTFS kernel driver compiled in. I know this bec occasionally I see the following in my System log:
Jan 23 14:42:05 (none) kernel: NTFS volume version 3.1.
Using the NTFS kernel driver means the partition is mounted R/O, as opposed to R/W w/ NTFS-3g. (BTW, there is no ntfs.ko module.) When the NTFS partition is mounted via /etc/fstab using NTFS-3g:
Jan 23 14:59:02 (none) ntfs-3g: Version 0.20070118-BETA Jan 23 14:59:02 (none) ntfs-3g: Mounted /dev/hda1 (Read-Write, label "WINXP-NTFS", NTFS 3.1) Jan 23 14:59:02 (none) ntfs-3g: Options: noatime,rw,users,silent,allow_other,fsname=/dev/hda1,blkdev,blksize=4096
I can visualize two pos solutions. Somehow, explicitly map the NTFS fiilesystem to NTFS-3g+FUSE. That's what /etc/fstab is supposed to do, but some pgm has clearly discovered a some other code path around it. Actually, a KDE program is the culprit. Alternatively, one could disable the NTFS kernel driver. With NTFS-3g installed effectively I have a different filesystem. Practically its the same data structures, but obsolete code is getting in the way.
I've searched hi-and-low for answers to this issue, but no joy. Given the flexibility of Linux, it seems there should be a text config file (or two) to tweak to resolve this. I hope my theory is correct. TIA....Jet
Is the ntfs driver a module, or is it compiled into your kernel statically? In the latter case all you can do is compile a new kernel, in the first case just disable the ntfs module in /etc/modules.
You can find out in the kernel configuration file in the /boot directory if it's a module or not.