On Tue, Jan 3, 2012 at 7:45 AM, Graham Lawrence <[email protected]> wrote:
> I thank you all for your help, but I really can't use your > recommendations without screwing up something else on my system. I > have a script which runs automatically on system startup which > immediately references this ntfs drive, so I must have this drive > automount on startup like my internal HD, or the script will fail. It > runs for several hours, during which I can't unmount and remount the > drive. > > The initial mount command assigns the drive to ROOT:ROOT with rwx > permissions for all users. These cannot be changed with chown, chmod, > chgrp as explained at > http://ubuntu.swerdna.org/ubuntfs.html > As this is an ubuntu site this behavior is not specific to my distro, > slackware. I assume it is standard behavior for the kernel, ntfs-3g > and the core utilities. > > I appreciate that one can get vim to write to this drive by having it > use a different linux command to do so, and am already doing that. > But I often forget to use it because my vim shutdown script > automatically writes out any altered buffers; but then it fails if it > tries to write to this ntfs drive. The only feasible solution for me > is to elaborate my shutdown script to choose the appropriate write > procedure for each buffer. > > I think this is a bug in vim. The ownership of the file should not be > an issue, only the permissions, which are as they should be. This is > the standard adhered to by all other apps except, as far as I know, > only vim. > > I checked this on my Ubuntu 11.10 system with the default version of Vim that comes with it. It looked exactly like your setup... example: $ ls -l total 56 drwxrwxrwx 10 root root 4096 2011-12-31 21:23 ./ drwxr-xr-x 24 root root 4096 2011-12-31 12:26 ../ . . . drwxrwxrwx 1 root root 8192 2012-01-02 12:00 xp-c/ $ cd xp-c $ ls -l drwxrwxrwx 1 root root 4096 2012-01-03 08:56 Temp/ $ cd Temp $ ls -l -rwxrwxrwx 2 root root 21 2012-01-03 08:51 BoiseNetWiz.txt* I was able to edit this file with vim/gvim with no problem, either with editing nor with creating the temp file. I guess the reason I changed the permissions on my system were not to give me access, but to make the files not writable to all. If nothing else, I don't like having all the file coloring as shown on my system with these settings. I never meant that you need to unmount/remount the drive just to use Vim, at least not normally. I only said to do that for debugging to get the right mount command, then you would leave whatever works in your fstab file for startup. But if you are convinced that this is a Vim problem, then I guess you don't want to bother. Sorry nobody has been able to tell you the answer. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
