similar to: CIFS on freebsd

Hello :) I have a current setup of apache serving websites for users, apache is using cgiwrap for all scripts so the filesystem needs to support chmod and chown stuff. This would all be good and dandy if everything was linux based, however, .. the whole setup needs the ablity to parse asp files as its needed for teaching ! I setup apache with something like this (ignoring all the php, perl,

Hi all, I've notice a strange behaviour in smbfs and I was not able to understand it, so I want to share it with some other We have some Solaris 7 machines with samba server and some linux workstations with Suse7.3 and SuSE 8.1 OS. When we mount on the linux workstation on share of the Solaris machine we see the file modification timestamp wrong by one hour. I was thinking about a problem

I've tried some internet and list searching, but I haven't been able to find anybody with the same issue. It's hard to search for "samba cifs force user problem" because it hits nearly every samba tech support question ever asked. The smbfs kernel module disappeared from the stock fedora kernels recently *crycry* Now my shares that were mounted via smbfs have to be mounted

Hello While the mounting process is successful, the behavior of remote directories and files is different under CIFS than SMBFS. Here are some of the issues I have encountered: 1) When doing a "file" on a file mounted under SMBFS, it gives a standard output depending on the file type. For the same file under CIFS, it gives the same information with "setgid sticky" before

>The smbfs kernel module disappeared from the stock fedora kernels >recently *crycry* Now my shares that were mounted via smbfs have to be >mounted via cifs. cifs is, apparantly, not a drop-in replacement for >smbfs however, as it behaves differnetly with the same configuration >options. Indeed, it does seem to be backwards in compatability as apposed to backwards compatable.

I periodically see smbfs questions get asked on this list, and they usually get one of two responses: 1. smbfs is a kernel module; this list is not the appropriate place to be asking smbfs questions. 2. You should be using cifs instead. (Please let me know if either if these is incorrect.) I was surprised to see, however, that the smbmount / mount.smbfs manpage makes no mention of cifs as being

I am attempting to troubleshoot a rather perplexing problem. Whenever I attempt to transfer a non-trivial amount of amount to a share mounted via the new CIFS kernel mod, my system will experience a hard lock requiring reboot. The setup linux client, running 2.6.3 (gentoo-dev-sources) with the preemptible kernel option enabled. Samba version as reported by smdb --version is 3.0.1. Using

Package: xcp-xapi Severity: important Version: 1.3.2-5 Tags: patch User: ubuntu-devel at lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch quantal Hello, the "smbfs" package has been deprecated for years, and finally removed last week: cifs-utils (2:5.4-1) unstable; urgency=low * New upstream release (Closes: #669327). - Version build dep on libwbclient-dev for

Hi all; When I access the data hosted in that share using others mount ways (except the smbmount/mount.cifs/mount -t smbfs/mount -t cifs) all works fine, downhere a benchmark: 1) Transfer a 500 mb file: netcat - 27 seconds ftp - 31 seconds smbclient - 38 seconds mounted (cifs) - 2:58 minutes I'm having a big problem with delay mounting a share using smbmount or mount -t cifs. First

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:16.smbfs Security Advisory The FreeBSD Project Topic: smbfs chroot escape Category: core Module: smbfs Announced: 2006-05-31 Credits:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:16.smbfs Security Advisory The FreeBSD Project Topic: smbfs chroot escape Category: core Module: smbfs Announced: 2006-05-31 Credits:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Suse Linux 10.1 X86_64 server that is destined to work with a mixed bag of OS/2, Windows and Linux clients. For this reason, I have again chosen to use the SMB protocol, which mandates the use of samba. I started with samba 3.0.22, but ran into some glitches so migrated to 3.0.23rc3. My Linux client is running Suse 10.1 X86_32 with samba

This may be sorta off topic considering this is probably regarding the linux kernel but I am hoping someone here will have the answer anyway. I am having the strangest problem when mounting a samba share with "-t cifs" as opposed to "-t smbfs" where, instead of mounting as the user I am logged in as, it is mounted as if I were logged on as a completely different user. For

Hello, I have the following Samba RPMs installed... samba-client-3.0.26a-0.5 samba-3.0.26a-0.5 samba-pdb-3.0.26a-0.5 yast2-samba-server-2.9.33-0.3 kdebase3-samba-3.2.1-68.62 samba-winbind-3.0.26a-0.5 yast2-samba-client-2.9.18-0.3 samba-python-3.0.26a-0.5 I used to be able to do a mount with -t smbfs, but not I get this message whenever I try it. Version

My LAN includes a server machine running FC4, with several shares mounted with Samba. Yesterday, I upgraded the packages on the FC4 machine, and these included Samba, which is now at 3.0.23a. Unfortunately, this seems to have broken the mounted shares for my Ubuntu 6.06 installation on my Acer 1682WLMI laptop. The cifs module on Ubuntu reports as version 1.39. The symptoms are that I can

Greetings, I think I may be having a slight configuration problem with Samba and FreeBSD-5.1. I'm trying to use FreeBSD's mount_smbfs(8) to mount a remote Samba share onto my local FreeBSD filesystem. With the configuration below, I can read all (almost; explained below) files and directories just fine. All permissions are correct. But whenever I try to write to the share, the write fails

After mounting a windows share via cifs I have came across the same issue as described here: http://lists.samba.org/archive/samba/2006-April/119813.html "While using vim on files mounted under CIFS, when trying to write an existing file you will randomly be warned "The file has been changed since reading it!!!". Normally, this only occurs when another user accesses and saves the

Hi I need to mount a windows share on a CentOS 4.5 box running stock kernel etc - I have tried using cifs and also smbfs My fstab looks like //share/name /mount/point smbfs username=user,password=password,uid=useridhere 0 0 or the same using cifs When i try and mount that i get the following errors depending on the share type smbfs: mount_data version 1919251317 is not supported CIFS

Hi all, when trying to mount a windows file share using the commands below, mount exits immediately with message "password too long" before even attempting the mount: mount -t smbfs -o username="a user",password="12345678901234567" "//server/share" "/mnt/target" mount -t cifs -o user="a

Hey, I've been working on making the Dovecot FreeBSD port resemble something which actually works this weekend, it's now much improved - one thing that I did notice is that Dovecot validates a users GID and will not accept a group id of 0. In FreeBSD the group wheel has a the id 0 and only members of the wheel group are allowed to use su and become root. Consequently there are non-root