Hello
Compiling 2.2.8 and smbwrapper on Solaris 9,
I saw the following warnings:
Compiling smbwrapper/smbw.c with -KPIC
"smbwrapper/smbw.c", line 1258: warning: argument #4 is incompatible with prototype:
prototype: pointer to ullong : "include/proto.h", line
On Mon, Dec 23, 2002 at 03:53:08PM -0500, [EMAIL PROTECTED] wrote:
>> For the purposes of getting a browse list, connecting to port 139 is a
>> must. There are ways to get the equivalent of a browse list via AD, but
>> I don't think it's LDAP-only, so port 445 doesn't even do any good in
>> this
Steve Langasek <[EMAIL PROTECTED]> writes:
> For the purposes of getting a browse list, connecting to port 139 is a
> must. There are ways to get the equivalent of a browse list via AD, but
> I don't think it's LDAP-only, so port 445 doesn't even do any good in
> this regard.
>
> For the actual e
On Mon, Dec 23, 2002 at 02:51:08PM -0500, [EMAIL PROTECTED] wrote:
> My last known problem with smbwrapper on Linux is that sometimes hosts in a
> workgroup, or shares on a host, are not returned by the cli_Net*Enum()
> functions. On another list (debian.something), there is cu
My last known problem with smbwrapper on Linux is that sometimes hosts in a
workgroup, or shares on a host, are not returned by the cli_Net*Enum()
functions. On another list (debian.something), there is currently a
discussion of the fact that using port 445 can cause this problem, and in
fact
[EMAIL PROTECTED] wrote:
> So my questions are:
>
> 1. Are there LFS requirements for SMB/CIFS or can I just drop the high-order
>portion of 64-bit file offsets?
There was a previous dicussion of the LFS/glibc issues, including
some Samba ones, at
http://www.scyld.com/products/beowulf/softwa
-bit
functions into 64-bit functions.
As an example, I found cases where sizeof(struct stat) was different in the
calling application (ps in my test case) than it was in smbwrapper and
libsmbclient.
At least with the glibc environment, I found the paradigm used for smbwrapper
to be insufficient to
David Collier-Brown -- Customer Engineering <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>
>> It appears I've nearly got it solved (unless another big problem turns up
>> after I fix this one). Aside from my initialization routine not be called
>> early enough, thus providing some null
[EMAIL PROTECTED] wrote:
> It appears I've nearly got it solved (unless another big problem turns up
> after I fix this one). Aside from my initialization routine not be called
> early enough, thus providing some null function pointers,
Hmmn, In a different discussion group I once wrote:
---
x this one). Aside from my initialization routine not be called
early enough, thus providing some null function pointers, the big problem is
that sizeof(struct stat) differs in smbwrapper and the calling application.
smbwrapper is zeroing the structure. With the passed parameter being shorter
than the amount
Steve Langasek <[EMAIL PROTECTED]> writes:
> I suspect the key change in the Debian build is enabling of LFS support;
Could be, but I have reimplemented each of the LFS functions that were in
there originally in a manner that they should work with the current C library.
I have discovered missing
On Tue, Dec 10, 2002 at 01:54:52PM -0500, [EMAIL PROTECTED] wrote:
> > On Tue, Dec 10, 2002 at 01:27:07PM -0500, [EMAIL PROTECTED]
> > wrote:
> >> I have smbwrapper and smbsh working on Debian/woody with the Linux 2.4
> >> kernel and the default C library: libc-2.2.
Dan Kegel <[EMAIL PROTECTED]> writes:
> As a user, I welcome alternatives to smbfs.
Patch has been posted.
> (I'm also looking forward to trying out
> http://us1.samba.org/samba/Linux_CIFS_client.html)
I did minimal testing of it. It seems to work fine, as long as you don't need
to access anyt
[EMAIL PROTECTED] writes:
> On Tue, Dec 10, 2002 at 01:27:07PM -0500, [EMAIL PROTECTED]
> wrote:
>>
>> I have smbwrapper and smbsh working on Debian/woody with the Linux 2.4
>> kernel and the default C library: libc-2.2.5.so.
> Yes, I'm interested - please post p
[EMAIL PROTECTED] wrote:
On Tue, Dec 10, 2002 at 01:27:07PM -0500, [EMAIL PROTECTED] wrote:
I have smbwrapper and smbsh working on Debian/woody with the Linux 2.4 kernel
and the default C library: libc-2.2.5.so. ...
Based on search results that I've found, there's been almost
On Tue, Dec 10, 2002 at 01:27:07PM -0500, [EMAIL PROTECTED] wrote:
>
> I have smbwrapper and smbsh working on Debian/woody with the Linux 2.4 kernel
> and the default C library: libc-2.2.5.so. There is a problem that rears its
> ugly head with a few programs (segmentation violation
I have smbwrapper and smbsh working on Debian/woody with the Linux 2.4 kernel
and the default C library: libc-2.2.5.so. There is a problem that rears its
ugly head with a few programs (segmentation violation, presumably due to some
function which is not wrapped properly) but in general, and with
I tracked down a number of articles from the archives discussing the various
problems with smbsh for Linux. I am now getting much further than any of the
previous posters, but I could use some help.
Firstly, the problems with smbwrapper as shipped in Debian's package (2.2.3a)
are:
1. Alt
On Wed, Nov 13, 2002 at 10:38:08PM +0100, Stefan (metze) Metzmacher wrote:
> Hi Jeremy,
>
> smbwrapper is broken. by the global_* patches.
Fixed in HEAD and 3.0.
Jeremy
Hi Jeremy,
smbwrapper is broken. by the global_* patches.
metze
Linking bin/smbcacls
Compiling smbwrapper/smbsh.c
smbwrapper/smbsh.c: In function `main':
smbwrapper/smbsh.c:39: warning: initialization discards qualifiers from
pointer target type
Compiling smbwrapper/shared.c
Linking bin/
That's a likely culprit: if you have both fcntl; and fcntl64
showing up in strace, you may need to check this is turned
on in each of the smbwrapper files.
>
> According to Redhat,
>
> " It's the back door symbols _open, _read, _write which
> "Johnston, Christopher (DCSA)" wrote:
> Was curious.. does smbsh work in Linux.. I am having all sort of
> compilation issues with file locking.. I understand there was a bug
> in glibc 2.1 which caused havok with 64 bit locking.. I assume that
> has been fixed by now since I am running the late
Title: Message
All,
Was curious.. does
smbsh work in Linux.. I am having all sort of compilation issues with file
locking.. I understand there was a bug in glibc 2.1 which caused havok with 64
bit locking.. I assume that has been fixed by now since I am running the latest
and greatest glib
Hi,
where can I find docs for smbwrapper?
Is option --with-smbwrapper supported in Solaris?
Tian.
24 matches
Mail list logo
