SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I have slack 12 installed on my system, I have some drives that are NTFS. When the system boots and mounts the drives, it says they are mounted as rw. I check the kernel and all filesystems I have on my system are compiled for rw. When I try to save a file or make a directory, it says filesystem is read only. I am confused.
When I try to save a file or make a directory, it says filesystem is read only.
If you want seamless access to your NTFS partitions, you might try downloading the latest kernel source and building it yourself. I am running Ubuntu 7.10 in a dual boot with Windows XP and I share the same e-mail directories between Ubuntu and Windows.
Just my 2€cents, the ntfs driver in linux kernel can write on an ntfs partition but this is very limited (especially the filesize must not increase). That's probably why it advertises read-write.
And there is no need special kernel requirement afaik. The only thing is fuse needs a kernel module which is not built by default now that it has been included with the linux kernel (only the kernel module part of course, FUSE_FS in "File Systems" when building a kernel).
How does that NTFS-3g work out anyway? I've been using for a few weeks now for reading NTFS partitions, but I'm still kinda scared if I write to them I'm gonna hose them.
It works well. It has been tested over a really, really long period of time.
I use it myself mostly for my data partition (the one that is 12 times bigger than others ;p ) but also the windows ones and have no problem.
Approximately one month ago though I had to back up my data partition and did it with ftp over gigabit ethernet. Transfer rates were ranging from 15 to 25MB/s and at some point which was caracterized by many small files, I was surprized that they were not higher and top told me ntfs-3g was using almost all the cpu cycles it could. Transfer rates were still high but not as high as they could.
However I had no corruption, only a slowdown.
Btw, I thought I could quote my source (and correct a statement) as well : from the linux kernel source, help for CONFIG_NTFS_RW,
Quote:
CONFIG_NTFS_RW:
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Note: While write support is safe in this version (a rewrite from
scratch of the NTFS support), it should be noted that the old NTFS
write support, included in Linux 2.5.10 and before (since 1997),
is not safe.
root@A6T-nix:~# mount
/dev/hdc6 on / type xfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw) /dev/hdc5 on /mnt/hdc5 type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
If the fuse kernel module is not present (default in slackware iirc), get [url=http://fuse.sourceforge.net/]fuse from sf[/ur], expand and run ./configure. Maybe the kernel module won't be enabled by default. If so, use ./configure --enable-kernel-module (or similar) then of course make && make install.
Now, get ntfs-3g, configure, make and make install.
Finally mount with "ntfs-3g <device> <mountpoint>".
I just think a whole kernel compile is unnecessary lengthy just to get ntfs write support especially since you'll need to install the fuse userspace tools and libs anyway.
I just think a whole kernel compile is unnecessary lengthy just to get ntfs write support especially since you'll need to install the fuse userspace tools and libs anyway.
I see a lot of Slackware posters clinging to old kernels, so I frequently suggest upgrading via building from source, because that is the way I like to do it.
However, I finally poked around on the Slackware site and I see that you can upgrade your kernel as a package. That would accomplish the same goal, presumably. Or are the Slackware folks dead set against enabling NTFS write support?
NTFS-3g has been used since at least 2.6.18 or 19, and is included in most distros that I've looked at. It works well and is easy to install with the scripts provided by SLACKBUILD.
hope this helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.