On 02/09/2016 00:56, Kai Krakow wrote:
Am Wed, 31 Aug 2016 02:32:24 +0200
schrieb Alan McKinnon <alan.mckin...@gmail.com>:
On 31/08/2016 02:08, Grant wrote:
[...]
[...]
You can't control ownership and permissions of existing files with
mount options on a Linux filesystem. See man mount.
So in order to use a USB stick between multiple Gentoo systems with
ext2, I need to make sure my users have matching UIDs/GIDs?
Yes
The uids/gids/modes in the inodes themselves are the owners and perms,
you cannot override them.
So unless you have mode=666, you will need matching UIDs/GIDs (which
is a royal massive pain in the butt to bring about without NIS or
similar
I think
this is how I ended up on NTFS in the first place.
Didn't we have this discussion about a year ago? Sounds familiar now
Is there a
filesystem that will make that unnecessary and exhibit better
reliability than NTFS?
Yes, FAT. It works and works well.
Or exFAT which is Microsoft's solution to the problem of very large
files on FAT.
Which NTFS system are you using?
ntfs kernel module? It's quite dodgy and unsafe with writes
ntfs-ng on fuse? I find that one quite solid
ntfs-ng does have an annoyance that has bitten me more than once. When
ntfs-nf writes to an FS, it can get marked dirty. Somehow, when used
in a Windows machine the driver there has issues with the FS. Remount
it in Linux again and all is good.
Well, ntfs-ng simply sets the dirty flag which to Windows means "needs
chkdsk". So Windows complains upon mount that it needs to chkdsk the
drive first. That's all. Nothing bad.
No, that's not it. Read again what I wrote - i have a specific fail mode
which I don't care to investigate, not the general dirty state flag
setting you describe
