I have installed below samba pkgs while installing CentOS 5.

[root@mail ~]# rpm -qa |grep samba samba-3.0.23c-2.el5.2.0.2 system-config-samba-1.2.39-1.el5 samba-common-3.0.23c-2.el5.2.0.2 samba-client-3.0.23c-2.el5.2.0.2

but, no smbmount is found.

instead of smbmount (mount -t smbfs) command, I used the command mount.cifsas folows . It worked properly.

pls see below.

mount.cifs //csbserver/mail_backups /mnt/mailmonthly -o ip=192.168.5.225 ,username=mailbackup,password=secret

---------- Forwarded message ---------- From: Steven Haigh netwiz@crc.id.au Date: Jun 29, 2007 10:21 AM Subject: Re: [CentOS] where is smbmount on centOS 5 To: centos@centos.org

Quoting Indunil Jayasooriya indunil75@gmail.com:

I am searching smbmount command on centOS 5.

On, CENTOS 4.4, I used it as follows to backup data to a window PC. I want to do it on CentOS 5 now.

mount -t smbfs -o ip=192.168.5.225,username=mailbackup,password=secret //server/mail_backups /mnt/maildaily

I can not issue such command on centos 5. When I try , It gives below error.

[root@mail ~]# mount -t smbfs -o ip=192.168.5.225,username=mailbackup,password=secret //server/mail_backups /mnt/maildaily mount: unknown filesystem type 'smbfs'

yum install samba-client

-- Steven Haigh

Email: netwiz@crc.id.au Web: http://www.crc.id.au Phone: (03) 9017 0597 - 0404 087 474

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

On Thu, 28 Jun 2007, Akemi Yagi wrote:

smbfs has been depreciated. See this wiki for mounting Windows shares:

http://wiki.centos.org/TipsAndTricks/WindowsShares

Akemi

On Fedora6, I have noted the folowing problems when using cifs to connect to NT shares:

- cp -vip does not copy mtime; tar x does copy mtime (it seems setting modtime by fname does work, setting by handle does not) - when there is a share mounted from a NT/2000 server which is not used for long time mounting another share from the same servers reliably fails ; touching the already mounted share (ls is OK) allows the mount so succeed. - when using vim to edit a file on the share and trying to write it, vim often says that the file has been modified in the meantime - perhaps most annoying: somtimes modifying a file located on NT 4 Workstation share with vim, it becomes permanently unavailable until NT is rebooted. It happens rarely, I do not know how to trigger it on demand.

Those problems did not happen when using smbfs from CentOS 4.4.

I am wondering if CentOS 5 has these problems? Anyone using cifs from CentOS 5 to access NT-exported share, would care to comment?

Thanks,

Wojtek

On 6/29/07, Akemi Yagi amyagi@gmail.com wrote:

On 6/29/07, Wojtek.Pilorz wpilorz@bdk.pl wrote:

...

On Fedora6, I have noted the folowing problems when using cifs to connect to NT shares:

• cp -vip does not copy mtime; tar x does copy mtime (it seems setting modtime by fname does work, setting by handle does not)
• when there is a share mounted from a NT/2000 server which is not used for long time mounting another share from the same servers reliably fails ; touching the already mounted share (ls is OK) allows the mount so succeed.
• when using vim to edit a file on the share and trying to write it, vim often says that the file has been modified in the meantime
• perhaps most annoying: somtimes modifying a file located on NT 4 Workstation share with vim, it becomes permanently unavailable until NT is rebooted. It happens rarely, I do not know how to trigger it on demand.

Those problems did not happen when using smbfs from CentOS 4.4.

I am wondering if CentOS 5 has these problems? Anyone using cifs from CentOS 5 to access NT-exported share, would care to comment?

Thanks,

Wojtek

I believe some of the issues you mentioned have been addressed in newer versions of cifs. For example, the vim/timestamp problem was reported and has been fixed in recent kernels. See:

http://lists.samba.org/archive/linux-cifs-client/2007-June/002014.html

However the CentOS kernel (2.6.18) uses cifs 1.45 and the current FC6 kernel (2.6.20) probably has cifs 1.47. Unless upstream/RH backports patches in their kernel, CentOS will not get them. One could compile cifs.ko from the source as a possible solution. If the problem is a severe one, it will be worth doing it.

Akemi

It looks like the upstream is going to update the cifs module to version 1.48 in the next release, RHEL 5.1. I am having some problem getting their test kernel to work, but at least it will get a newer (but not the latest) version of cifs.

Akemi