PDA

View Full Version : HOWTO: Captive-NTFS on 2.6.10-4



beefsprocket
March 21st, 2005, 03:28 AM
Right... Here it is (at least for me anyways).

Step 1: Install gcc and kernel source for whichever version you so choose (I went with 2.6.10-4)

Step 2: Patch your kernel source with the following (taken from mail archive on captive site (http://www.jankratochvil.net/pipermail/captive-list/2004-December/000645.html) )

diff -Naur kernel/signal.c.orig kernel/signal.c
--- kernel/signal.c.orig 2004-12-28 13:23:06.000000000 +0100
+++ kernel/signal.c 2004-12-28 13:24:59.000000000 +0100
@@ -1939,6 +1939,7 @@
EXPORT_SYMBOL(sigprocmask);
EXPORT_SYMBOL(block_all_signals);
EXPORT_SYMBOL(unblock_all_signals);
+EXPORT_SYMBOL(kill_proc_info); /* hcz */


/*

To patch you should copy and paste the above into a new file and save.
Execute the following from within your /usr/src/linux directory:

patch -p0 < /path-to-previously-created-patch-goes-here

Step 3: Download captive-ntfs .deb from here (http://www.kruyt.org/?sub_item=46) and install it.

Step 4: Compile your kernel and modules and reboot.

Step 5: Run captive-install-acquire and then try mounting your drive with mount -t captive-ntfs

Step 6: Write a reply telling me that I'm an idiot if this doesn't work for you ](*,)

vvu
March 23rd, 2005, 09:56 PM
This feature should be an option to install via apt-get or be integrated into the distro.

ember
March 23rd, 2005, 11:02 PM
Anyway I like to tick that Captive NTFS is really, really slow compared to the NTFS-driver in the Linux-Kernel, so if you don't depend on NTFS-write access stay with the open source driver.

kahping
March 24th, 2005, 02:40 PM
This feature should be an option to install via apt-get or be integrated into the distro.

in hoary, just add a new custom repository with deb http://www.kruyt.org/debian /

kahping

edit:

o yeah, and reload after adding it so it'll be listed for selection at your leisure :-P

edit2:

btw, i get stuck at the patching step, or at least it seems like it's stuck there. how long does it take to patch a file, normally? since it's just one file, i think it shouldn't be more than a few seconds(if at all) :confused:

cerbie
May 27th, 2005, 07:23 AM
newbie at step 6 :)


root@cerbuntu:~ # patch -p0 < /home/cerbie/patchy.txt
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -Naur kernel/signal.c.orig kernel/signal.c
|--- kernel/signal.c.orig 2004-12-28 13:23:06.000000000 +0100
|+++ kernel/signal.c 2004-12-28 13:24:59.000000000 +0100
--------------------------
File to patch:

This occurs with 2.6.10-5-386 and 2.6.10-5-k7 (the only kernels I have installed). I have the GCC (gcc-3.3, gcc-3.3-base), AFAIK, and the headers and sources for the kernels.

Now, I wasn't sure about the <, and that is probably wrong, but trying it as such:
root@cerbuntu:~ # patch -p0 < /home/cerbie/patchy.txtcauses the terminal to just sit there and not give the prompt back. No messages , no crazy CPU use or HDD access...nada. Unless it should take more than a couple hours to apply the patch, somethin' ain't right, there.

](*,)