After installing ntfs-config I've lost the ability to mount without sudo.
Tried "$sudo chmod u+s /bin/mount" but that seems to not be the problem. Purging ntfs-config doesn't seem to solve the problem either.
What do you think I should do? (ubuntu)
Printable View
After installing ntfs-config I've lost the ability to mount without sudo.
Tried "$sudo chmod u+s /bin/mount" but that seems to not be the problem. Purging ntfs-config doesn't seem to solve the problem either.
What do you think I should do? (ubuntu)
Try pmount, or add the entry to /etc/fstab (what I do).
Most people allow a group to mount (ie "storage") then chuck the user in the group.
BTW, what is the error? You can't use the mount executable?!
nope. I don't have privileges.
I could install pmount. But isn't there a way to get the rights back?Quote:
[mariof@jupiter:~ ]$ mount /dev/sda5
mount: only root can mount /dev/sda5 on /media/Backups
I tried to use "$ntfs-config -r" -- which apparently reverts any changes -- and then purge the package, but to no avail.
EDIT:
hmm... This is my fstab entry for that volume:
That ntfs-3g shouldn't be there should it? That's from the ntfs-config. My main ntfs volume sd1 -- which I can mount normally with no problems -- isn't even listed.Quote:
/dev/sda5 /media/Backups ntfs-3g defaults,locale=en_US.UTF-8 0 0
There really isn't a problem. It depends how you want to do things...
http://ubuntuforums.org/showthread.php?t=189783 could be a related problem.
nope. trying to mount it replies with:
mount: can't find /dev/sda5 in /etc/fstab or /etc/mtab
man fstab and look at the fourth field, particularly the "user" option.
Thanks rob, I will when I get a chance later today. But while that may solve the problem, I'm also interested in understanding why.
Particularly, my other ntfs volume is not present in fstab and I still can mount it with my unprivileged account.
Dunno. Perhaps if it's not in fstab, then it just matters if you have +x on mount.
I'm more curious why it worked in the first place as non-root.
This is my current fstab:
When booting Linux today, after yesterday troubles, I'm suddenly able to mount without sudo again. So probably purging ntfs-config required a reboot. I don't know. So the problem is pretty much solved. But I don't understand why.Code:# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda6
UUID=4503ecc6-deb2-4017-bb41-8af4f1d8ff5a / ext3 relatime,errors=remount-ro 0 1
# /dev/sda7
UUID=22c1c8b9-2b35-45f9-aa96-6fad5394984a none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
# /dev/sda5 /media/Backups ntfs-3g defaults,locale=en_US.UTF-8 0 0
This is the result of $mount for the two ntfs volumes after I mount them through Nautilus (I can't seem to be able to mount them with the CLI):
I notice it is using this 'fuseblk' and that there is a mount point (?) for it as well:Code:/dev/sda1 on /media/disk type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
/dev/sda5 on /media/Backups_ type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
Is this fuseblk taking over?Code:gvfs-fuse-daemon on /home/mariof/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=mariof)
fuseblk is the FUSE (Filesystem in User SpacE or something like that) block device driver, i.e. the kernel driver that communicates with the out-of-kernel ntfs-3g driver.
Ok, thanks. I was searching google for fuseblk lastnight and came up with that name. The linux lingo is still an issue and will be for some time. But at least I got my bearings.
It's the one in control apparently and doesn't support what it calls "old style mount":
$fusermount /dev/sda1
I'm also unable to mount with $mount because, as I now realize, I would need an fstab entry. So the issue was not really with $mount, but with $fusemount that was restricted to root when I installed ntfs-config. Removing this package and later rebooting solved the issue. I shall read about this fuse thing sometime later when I get the stomach for it.
...
I'm basically talking to myself on this post, I realize that. But also hoping if I'm saying something wrong you guys pick on it.