smbfs & linux 2.1.79 still no go :(

David Burrows (snadge@gemcorp.com.au)
Wed, 14 Jan 1998 14:05:50 +1000 (EST)


I am using the mount tools from samba 1.9.18 which I have modified to
compile under glibc2. I have compiled SMBFS as a module, this time with
the win95 bug workarounds. This is what happens:

btw this is a win95 OSR2 box I am trying to connect to.. smbclient works
fine so its definately an smbfs problem.

using smbmount (the hacked version of smbclient with only mount support)

smb: \> mount shed -f 755
[root@bucket /mnt]# SMBFS: Win 95 bug fixes enabled
smb_newconn: state valid, pid=1264

[root@bucket /mnt]# cd shed
[root@bucket shed]# ls

smb_lookup: find //CDROM failed, error=-23
ls: CDROM: Too many open files in system
smb_lookup: find //Dave failed, error=-23
ls: Dave: Too many open files in system
smb_lookup: find //Games failed, error=-23
ls: Games: Too many open files in system
smb_lookup: find //Mouse failed, error=-23
ls: Mouse: Too many open files in system
smb_lookup: find //SB16 failed, error=-23
ls: SB16: Too many open files in system
smb_lookup: find //RECYCLED failed, error=-23
ls: RECYCLED: Too many open files in system
smb_lookup: find //COMMAND.COM failed, error=-23
ls: COMMAND.COM: Too many open files in system
smb_lookup: find //AUTOEXEC.BAT failed, error=-23
ls: AUTOEXEC.BAT: Too many open files in system
smb_lookup: find //IO.IDX failed, error=-23
ls: IO.IDX: Too many open files in system
smb_lookup: find //VBEAF.DRV failed, error=-23
ls: VBEAF.DRV: Too many open files in system
smb_lookup: find //IO.SYS failed, error=-23
ls: IO.SYS: Too many open files in system
smb_lookup: find //SYSTEM.1ST failed, error=-23
ls: SYSTEM.1ST: Too many open files in system
Audio My Documents SUHDLOG.DAT __ofidx.ffa
CONFIG.SYS Net Temp __ofidx.ffl
Download Program Files UTILS __ofidx0.ffx
MSDOS.SYS SBCD WINDOWS logo.sys

[root@bucket shed]# df
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hda1 1523318 1353167 91428 94% /
none 2096832 1294624 802208 62% /mnt/shed
[root@bucket shed]

(Oooh, something that works!) :)

ls -l shows the same output as ls except for the files and dirs which
"work" show up as ---------- and d--------- respectively (completely
ignoring the -f 755)

Oh well, I might have better luck the next time I have another go at
getting it to work.. I sure hope it will be ready for 2.2.

Regards,

Dave.