Graham Lawrence 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.

One suggestion I haven't heard yet: Try changing the 'backupcopy'
setting.

Vim has some protection against doing bad things with root permission,
that might interfere with what you are doing.

-- 
Why isn't there mouse-flavored cat food?

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
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

Reply via email to