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.
Hi:
I have an NTFS partition and cannot write to it. This partition was created by cfdisk with FS ID 07 (HPFS/NTFS). This is the ID windows XP writes in the partition table. The partition was formatted by the XP installer. Once within XP, I chose to make all files private (other than the adm no user can access them).
Now in linux (Slack 12.0) I cannot mkdir or cp on the NTFS mounted partition, although
Code:
# mount
/dev/hdaa4 on /hdaal type ntfs (rw)
and
Code:
# ls -ld /hdaal
drwx------ root root 4096 /hdaal/
# mkdir /hdaal/foo
mkdir: cannot create directory '/hdaal/foo'. Operation not permitted
Then I searched LQ and found this post, which made me look into the /extra/PACKAGES.TXT and I found the ntfsprogs package, which supposedly contains ntfsmount. To my great deception it does not, as looking in /var/log/packates/ntfsprogs-1.13.1-i484-1 shows. But there is the manual, which says its a module:
DESCRIPTION
ntfsmount is a FUSE module that rely on libntfs. You need FUSE to com-
pile it, xattr is recommended, but not mandatory.
And contrary to the other programs in the package, it speaks about compiling.
But I doubt I need this package, which nonetheless I installed, given that so many people has linux and windows in their machines, that it seems a little weird mount can't mount in such a way that I can write. The mount manual does not, however, mention any special circumstance when a file system can't be written to, and nothing special in the options for NTFS.
So, the question I do is: Do I have to rely on some /extra directory package (CD 3) or have I the means to write to an NTFS file system, given that I have done a full instalation (in slack 12.0 installing all packages from CDs 1 and 2 is considered a full install).
The Linux kernel is unable to write to NTFS volumes, it can only mount them in read-only mode. You haven't done anything wrong, this is just a limitation of the kernel.
If you want to get read/write access to NTFS, you need to use NTFS-3G, which should already be installed (it is in the "A" package set). You use the "ntfs-3g" command more or less like the normal mount command, just give it the device node and where you want to mount it.
Thanks for your post. It's unfortunate, I did 'grep -irl ntfs-3g /var/log/packages' and could not find it. In my system, this means ntfs-3g is nowhere. Perhaps slack 13. I'll look in slackbuilds.
As far as I can tell, ntfs-3g was first included in Slackware 12.1. I know it is part of 12.2 - I use it occasionally on one system that is still waiting for an upgrade.
If ntfs-3g won't build under 12.0, upgrading to 12.1 or 12.2 should make it available.
Thank you, Lirey. I have learned ntfs-g3 can charge the CPU up to a hundred per cent in old machines like mine. I always asked the winXP installer to use FAT32. This time, in a new installation, I decided in favor of NTFS, which was a mistake, as I now see, because then I have no comunication between ext2 and winXP.
Luckily, I have a large empty partition, which now I'll format in FAT32, and everything I create with XP I'll put it in that partition.
At equal CPU/DMA speeds, which makes file I/O faster? FAT32 or NTFS? Or for that matter, ext2 or ext3?
I didn't pay attention on CPU use by ntfs-3g before, but I just tried to mount ntfs volume with using ntfs and ntfs-3g and took a look on CPU use while copying big file from ntfs volume to my home directory and CPU use was almost the same, even it was a bit less for ntfs-3g.
So maybe just check if you have ntfs-3g support, and if CPU use will be acceptable for you. You can try to use ntfs-3g by mounting ntfs partition as root.
Code:
mount -t ntfs-3g /dev/sdc1 /mnt/hdd
Just change device and mount point according to your system.
Thanks. I'll do that. ALthough, given the fact my machine is old (kernel 2.6.21.5 running on Pentium III @1100MHz, 256MB RAM), I think the test will yield negative results.
I really don't see how NTFS-3G could have such a performance issue, especially on a machine that fast. I've run NTFS-3G on my router which has a 400 MHz CPU and 32 MB of RAM...so I'm not sure what you are worried about.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.