Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everybody. I've been trying to solve this problem on my own for a while and I haven't found any satisfactory solutions.
I'm currently using Slackware 10 with kernel 2.6.7-ck6. (Downloaded from kernel.org and patched.) I've downloaded and patched to my liking kernel 2.6.10 but I can't get captive-ntfs to work with it. The same goes for kernels 2.6.8 and 2.6.9. The simple answer would be that LUFS is no longer supported and thus the later kernels don't work with it, and since captive requires LUFS it won't work either. This is not satisfactory or entirely true from what I've gathered.
http://www.jankratochvil.net/project/captive/ says that while LUFS is kind-of buggered there's an alternative method that's supposed to get captive-ntfs working again. I just can't figure it out. Does anybody know how to do this? I would REALLY like to move on to the latest-and-greatest kernels and still have read/write access to my NTFS partitions.
Thanks for the link, Keefaz! I'm not sure exactly what to do with all that diff stuff. Did he get an old version of signal.c from somewhere or rewrite it or what? Sorry if I'm being dense! :-)
Does anybody have any idea what to do with this bit of code? The link above says something about patching the kernel, I don't understand how to use this text to do it.
Quote:
Looking into the kernel sources revealed that kill_proc_info was
exported in kernels prior to 2.6.10, but isn't any more. I didn't
investigate further why this change was made but instead made the
following change which did the job:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.