FS#8346 - smb4k - users cannot mount/unmount shares

Attached to Project: Arch Linux
Opened by sinister99 (sinister99) - Friday, 19 October 2007, 01:27 GMT
Last edited by Travis Willard (Cerebral) - Tuesday, 20 November 2007, 03:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Travis Willard (Cerebral)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When a user besides root tries to mount/unmount a smb share with smb4k, the following error pops up (on my computer)

mount error 1 = Operation not permitted
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

I discovered a fix for this on smb4k's website:
http://smb4k.berlios.de/handbook/trouble_shooting_mounting_unmounting.html#trouble_shooting_mount_cifs

You are trying to use mount.cifs(8) as normal user, but the SUID root bit is not set. The following (or a similar) command can be used as root to set the SUID bit:

$ chmod +s `which mount.cifs`

When I ran

chmod +s `which mount.cifs`
chmod +s `which umount.cifs`

the I could mount and unmount as a user.

If you don't see fit to package smb4k with this fix, can a post install message with these commands be included to notify users?
This task depends upon

Closed by  Travis Willard (Cerebral)
Tuesday, 20 November 2007, 03:10 GMT
Reason for closing:  Implemented
Additional comments about closing:  Post-install messages added to the smb4k package.
Comment by Ronald van Haren (pressh) - Monday, 22 October 2007, 09:41 GMT
If it is decided to add the install message you can use the one I created for pyneighborhood (to slightly reduce the workload :p) >> http://aur.archlinux.org/packages/pyneighborhood/pyneighborhood/pyneighborhood.install
Comment by Travis Willard (Cerebral) - Monday, 19 November 2007, 14:15 GMT
I'll correct the install notes tonight to detail what steps need to be taken.

We can't do this ourselves at post-install - the problem with such a method is that every time you upgrade smbclient, you'll need to re-run the chmod.
Comment by Travis Willard (Cerebral) - Monday, 19 November 2007, 14:37 GMT
Tpowa - I pulled you in on this because samba/smbclient are your packages.

Would this be a sane thing to do in the smbclient package, or should this be kept as a simple post-install message in the smb4k package?
Comment by Travis Willard (Cerebral) - Tuesday, 20 November 2007, 03:10 GMT
Post-install messages added to the smb4k package.

Loading...