Fedora Core 6 and samba
 

Hi all!

I am trying to mount an sambashare from my fc6 computer.
The sambashare is served by an slackware server.
The share is user / password protected.

When mounting the share from an another slack computer I use this command as root:

mount -t smbfs -o username=xxx,password=xxx //ipaddr/share /home/user/mountpoint

In slack it askes for an another password confirmation, that is the password for the share.
Because I am not allowed to run mount as regular user I made an script that does this as root and because of the username and password option for samba it mounts it all correctly. But here comes fedora 6!

First of all, not allowed to run the command as regular user, ok.
Then, not any filesystem as smbfs it states, ok, trying cifs instead.
Ok, that mounts but now I can only view / write to the root of the share (as regular user), not in any of the underlaying folders..

Anyone got ideas for how to get this working?

EDIT:
I did try an chmod 777 /bin/mount now. That only changed the errormessage to must be super user

How can I get the right permissions back for this file?

your last question doesn't make much sense. Permissions back for _what_ file?

For the issues you're having with samba, good luck. Setting up a read-only samba share is easy; setting up a read-write samba share that you can only write to as root, is not very difficult; setting up read-write samba share that any user can write to with a user-mapping between linux and windows-share users without a domain controller? IMPOSSIBLE.

If this is just your desktop, either start hacking, or deal with having to 'su' to root every time you need to write to a share.

The file for the permission question is , sorry for the "now" after..

But it does not matter, this works without any problems in slackware 11, so I switched back to slack..

But, why does this command not work in fedora 6?

Even changing it to cifs instead of smbfs did not work..

The sambashare is mapped with an user and pass. When mounting this in slack with the correct user / pass I do get writepermissions for the folder this is mounted to (the share).

But when mounting it in fedora 6, I do not get write permissions for the mount, even still I have spessified user / pass for the share.. This is something I found a bit strange, but, it works in slack 11, so I do not see any reason to continiue working on this with fedora 6!

1) I don't know what CIFS is. That's some filesystem I've never heard of. It probably doesn't have anything to do with what we're doing here.

2) slackware, as I understand, is a pretty insecure and shakey operating system if its not configured correctly. They have pretty lax rules for setuid executables and other things, which may explain why this worked in slackware and not in fedora core. But this is not a feature of slackware, its a bug.

3) looking at my system, my /bin/mount is setuid root, so you may have broken it when you did 'chmod 777 /bin/mount'. You can fix that with this command (assuming /bin/mount is owned by root):

# chmod 4755 /bin/mount
# ls -l /bin/mount
-rwsr-xr-x 1 root root 77120 Nov 3 22:47 /bin/mount

(note the 's')

after that try mounting the share again. If it works and you get read/write access to the share as root, then you're at square one. You'll then have to figure out how to get the user access correct later.

Hmm.. Do not understand this..

If I use "smb://ipaddr/share" then it askes for an user / pass, when I input that correctly I get access..

I want fc6 to have that access for the same user, but in an folder in the users "home"

I can then use the "copy-to" command via kde-rightclick to move files around.. (to the share!)

I'm having problems with fedora core 6 and samba shares too.
It is only "samba" shares, i.e. shares coming from a linux machine running a samba server and not a windows machine. As smbfs has been replaced with CIFS (common internet file system for dombrowsky) in the mount command in fedora there are issues. The cifs mounter works fine with windows but not samba servers it would seem.
Use of smbclient allows connection to samba servers and in my case the samba server is a NAS HDD so I can't simply chose another distro for it. It's very frustrating and all because the fedora guys thought cifs was working perfectly, as far as I can tell it's not!

Check to see if an SELinux problem in FC. Try

setenforce 0

to turn in off, and

setenforce 1

to turn it back on. If SELinux is the problem, you can turn it off for ambd in security settings

I never use SELinux, causes too many problems for me

cifs bugs are being worked on by samba/cifs programmers. At least one known bug was fixed recently. But it will take a while before the patch is included in Fedora kernels. If you don't mind compiling the kernel, you can apply the patch to your running kernel to get going. See this Bugzilla:

https://bugzilla.redhat.com/bugzilla....cgi?id=211672