Tag Info

Hot answers tagged


For network windows shares you need to specify the uid/gid that the drive should be mounted as and/or the file and directory modes to use since Windows doesn't understand Unix users and Linux doesn't understand Windows users or permissions. Right now, the share is probably writable but everything is owned by root so no other user can do anything. Try: ...


They're identical - both use ntfs-3g in (current) Ubuntu; the ntfs utils are just symlinked to ntfs-3g. # which mount.ntfs /sbin/mount.ntfs # which mount.ntfs-3g /sbin/mount.ntfs-3g # ls /sbin/mount.ntfs* -l lrwxrwxrwx 1 root root 13 2011-03-01 21:13 /sbin/mount.ntfs -> mount.ntfs-3g lrwxrwxrwx 1 root root 12 2011-03-01 21:13 /sbin/mount.ntfs-3g -> ...


That's right, NTFS won't enforce security if you physically connect the drive to another OS or system, nor will most filesystems out there. There's a range of options you can use, from encrypting your user dir to use TrueCrypt and other solutions to encrypt sensitive data. There's also drives with hardware encryption available, but that'll protect you only ...


The traditional NTFS kernel driver is read only. If you use ntfs in your fstab it will attempt to use that kernel driver, and mount your NTFS as read only The ntfs-3g is the newer FUSE driver (as you mention) and will mount the partitions as read-write is you use it in NTFS. Some distros have started treating them as one and the same, but as of about a ...


Mount the disks via labels or UUIDs. The label approach: Make sure you have ntfsprogs installed with apt-get install ntfsprogs. Then do ntfslabel /dev/sdb1 ntfsdisk1 ... repeat for all drives in /etc/fstab replace the /dev/sdx1 part of the respective lines with LABEL=ntfsdisk1 etc.


You can't. ntfs has no knowledge of Linux permissions and ownerships. The only weapons at your disposal are mount options.


The shell script should be: SOURCEWITHSPACES=( "${PREFIX}/Documents and Settings/." "${PREFIX}/electronic claims/." "${PREFIX}/billing statements/." ) for P in "${SOURCEWITHSPACES[@]}"; do echo "$P"; done


Try bs=32k, bs=64k, or even bs=1M: USB has significant turnaround time - and you use sync mount option. That kills write speed as it disables the write cache.


NTFS isn't a cluster-aware filesystem - it shouldn't be mounted on two systems at the same time. ntfs-3g could probably have some better handling for this situation, but it would just be a hackish workaround - the filesystem format simply wasn't built for this. Can you clarify what you're trying to achieve with this configuration?


I've noticed that checkinstall requires the command to be taken into quotes like this: checkinstall -D "make install"


You can't boot from an external drive so USB/CD repair is out...can't get network access...um...I don't know of anything that can outrightly fix it from Linux. NTFS support for anything other than reading and writing (and relatively speaking even write support was dodgy until fairly recently) is scant, as the attitude from the Linux community is that NTFS is ...

Only top voted, non community-wiki answers of a minimum length are eligible