CIFS woes (fwd)

[Paul D. Robertson]

Hi,

(If this isn't the right venue, can someone please cluebat me off-list and 
point me to the right place?)

I need to set up a server that allows chmod/chown stuff, so I'm using the 
CIFS code.  I've got a server set up using Samba 2.2.5, and it mounts from 
the local machine as a CIFS filesystem.  Here's my issue- I can't execute 
a binary file if it's on the share.  Doesn't mater if it's ELF or a.out 
format, or if it's static or dynamic.  

Scripts run just fine, but binaries give me:  "-bash: ./command: cannot 
execute binary file" along with "modprobe: modprobe: Can't locate module 
binfmt-464c" in syslog (which means the binformat isn't recognized 
AFAICT- noramlly an architecture or endian mismatch?)

I've tried compiling an executable on the CIFS filesystem, same results, 
moving the binary to a local filesystem works just fine, but once it's 
copied back, it won't execute, so it's not the contents of the file.

"file" on the dynamic ELF shows:

command: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), 
dynamically linked (uses shared libs), not stripped

I've tried calling the files with ./command as well as through the loader 
with the filename as a parameter- same results either way.

MD5 sums of the binary show identical if on the share or if on a local 
filesystem.

System is Linux, x86 with kernel 2.4.19 and the latest cifs client stuff 
as of a week or so ago.  Server and client are running on the same system 
during testing, and the base system is RH8 other than the kernel with all 
the UTF8 fun that entails.

Any ideas/pointers/clues would be most helpful at this point.

Thanks,

Paul
-
Paul D. Robertson  "My statements in this message are personal opinions
[EMAIL PROTECTED]  which may have no basis whatsoever in fact."

Re: CIFS woes (fwd)

[Urban Widmark]

On Wed, 30 Oct 2002, Paul D. Robertson wrote:

> the local machine as a CIFS filesystem.  Here's my issue- I can't execute 
> a binary file if it's on the share.  Doesn't mater if it's ELF or a.out 
> format, or if it's static or dynamic.  
> 
> Scripts run just fine, but binaries give me:  "-bash: ./command: cannot 
> execute binary file" along with "modprobe: modprobe: Can't locate module 
> binfmt-464c" in syslog (which means the binformat isn't recognized 
> AFAICT- noramlly an architecture or endian mismatch?)

"binfmt-464c is ELF -- it means your kernel came across an ELF
 executable and was unable to execute it so it tried to load the ELF
 binary format module. Since you have ELF compiled into your kernel
 already, this didn't work."
http://www.uwsg.iu.edu/hypermail/linux/kernel/0102.3/0006.html


> I've tried compiling an executable on the CIFS filesystem, same results, 
> moving the binary to a local filesystem works just fine, but once it's 
> copied back, it won't execute, so it's not the contents of the file.

AFAIK, ELF requires that the filesystem implements mmap in some form so
you are probably using a version that doesn't. For a.out, I think it
depends on the a.out type. Some are demand pageable, others are not.


> Any ideas/pointers/clues would be most helpful at this point.

You could try:
http://uranus.it.swin.edu.au/~jn/linux/smbfs/

/Urban