similar to: Compiling Samba 2.2.0-alpha3 on SCO Openserver 5.0.6

Displaying 20 results from an estimated 1000 matches similar to: "Compiling Samba 2.2.0-alpha3 on SCO Openserver 5.0.6"

2001 Mar 08
1
Error linking 2.2.0alpha2 smbd on Solaris 8
Hi all, I just downloaded the most recent 2.2.0alpha2 from samba.org and am trying to compile it on a Sun Ultra 5 running Solaris 8. I'm getting the following error when smbd is being linked: Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c Compiling smbd/oplock_linux.c Compiling smbd/notify.c Compiling smbd/notify_hash.c Compiling smbd/notify_kernel.c Linking
2002 May 09
2
Samba 2.2.4 and SCO Openserver 5.0.6
I have problems installing the latest release of Samba on Caldera (SCO) Openserver 5.0.6 I have downloaded the source and ran "./configure" fine. I get an error " line 664: Syntax error " when I run "make". If I run " ./configure --with-winbind", then run "make", I get the error "Compiling smbd/server.c include/includes.h, line 885:error:
2002 Jul 22
1
impedence mismatch between openssh 3.4p1 and openssl 0.9.6d on SCO OpenServer 3.2 5.0.6
Hi, I have been trying to build openssh 3.4p1 on SCO Open Server xxx It requires the libcrypto.a library produced by OpenSSL. So, I downloaded and installed OpenSSL 0.9.6d. As part of the configure process for OpenSSH, 'configure' checks for version of libcrypto.a with RAND_add(). RAND_add is defined in rand_lib.c and during the build of OpenSSH, I can see that rand_lib.c is compiled
2001 Jan 04
0
Problems/Modifications compiling SAMBA 2.2-alpha1 on SCO Openserver 5.0.5a
Hello, after one small modification I was able to compile samba. I have not yet tried to use it, but at least swat is working. It would be nice if anyone could modify the current code to resolve the specified problems. Mike The Problems: Only a nuisance: uid_t and gid_t are unsigned: /GNU-Source/samba-2.2.0-alpha1/source/smbd/sec_ctx.c: In function `initialise_groups':
2018 Sep 12
0
smbclient for SCO OpenServer 5.0.7
On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: > Looking back in the samba mailing list archives, I see not soancient requests > for samba on ancient SCO OpenServer systems. > > Recently faced with a situation where a Windows Server upgrade to 2012 R2 and > broke an smbclient upload from a SCO OpenServer 5.0.7 system. Directory > listings and file
2018 Sep 12
1
smbclient for SCO OpenServer 5.0.7
On 09/12/18 16:56, Jeremy Allison via samba wrote: > On Wed, Sep 12, 2018 at 03:27:37PM -0500, Kevin R. Bulgrien via samba wrote: >> Looking back in the samba mailing list archives, I see not soancient requests >> for samba on ancient SCO OpenServer systems. >> >> Recently faced with a situation where a Windows Server upgrade to 2012 R2 and >> broke an smbclient
2015 May 22
3
SCO OpenServer
Does anyone know the most up to date version of Samba that will run on SCO OpenServer 5.0.7? Kind Regards Dave Nolan Anchor Technology
2015 May 22
1
SCO OpenServer
I think what I need is a prebuilt package. I currently use Samba 2.2.12 running on SCO OpenServer 5.0.6 but I am in the process of upgrading to 5.0.7. Can't move to SCO version 6 because our application isn't guaranteed to work on it. Regards Dave -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Mauricio Tavares
2007 Jul 21
0
compiling samba 2.2.12 on Solaris (x86)
I am trying to build Samba 2.2.12 on Solaris 10 x86 with gcc. I am not able to successfully build it, however. I get a linker error for an undefined symbol VA_COPY. How can I fix this problem? Linking bin/smbd Undefined first referenced symbol in file VA_COPY lib/snprintf.o ld: fatal: Symbol referencing errors. No
2000 Nov 09
2
SCO Openserver Patch
I downloaded the Openssh-2.3.0p1 file and ran configure only to have it fail reporting the lack of libz. I found that configure was failing beacuse the test program did not include the libtinfo and libm which are needed to resolve references in libprot. I made changes to the configure script to add those libraries for SCO Openserver and then tried to compile the programs only to run into another
2015 May 22
3
SCO OpenServer
If you upgrade to sco 5.0.7, you get samba 3.0.20 5.0.6 had samba 3.0.14. so im wondering why your using samba 2.2.. samba 3.0x. is on the supplimental discs. Gr. Louis >-----Oorspronkelijk bericht----- >Van: dave at anchor-tech.co.uk >[mailto:samba-bounces at lists.samba.org] Namens David Nolan >Verzonden: vrijdag 22 mei 2015 14:12 >Aan: 'Mauricio Tavares' >CC:
2015 May 23
0
SCO OpenServer
On Fri, May 22, 2015 at 8:31 AM, L.P.H. van Belle <belle at bazuin.nl> wrote: > If you upgrade to sco 5.0.7, you get samba 3.0.20 > 5.0.6 had samba 3.0.14. so im wondering why your using samba 2.2.. > samba 3.0x. is on the supplimental discs. > > Gr. > > Louis Been there, done that. Samba 2.2 was built into the base release, supplements weren't always stable or well
2005 May 20
2
Samba3 on SCO Openserver
Dears Sirs; I'm tryng to compile and install samba 3.0.14a on a SCO Openserver 5.0.6 server (i want to use some shared printers from MS server2003 on a customer network, but with samba SCO ver 2.2, i can't obtain the authorization from the domain controller to use shared resources), but i'm havig a lot of trouble. I had dowloaded samba-3.0.14a.tar.gz fro Samba.org. I had put all the
2001 Nov 05
0
Compile problem with 2.2.2 with SCO OpenServer 506 after rs506a installed
I never have had a problem compiling Samba until 2.2.2 after installing a SCO patch 506a on OpenServer 5.0.6. I noticed the following message when running configure that does not normally appear: WARNING: No automated network interface determination make output: Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DLOGFILEBASE ="/usr/local/samba/var"
2018 Sep 12
4
smbclient for SCO OpenServer 5.0.7
Looking back in the samba mailing list archives, I see not soancient requests for samba on ancient SCO OpenServer systems. Recently faced with a situation where a Windows Server upgrade to 2012 R2 and broke an smbclient upload from a SCO OpenServer 5.0.7 system. Directory listings and file deletions did not fail, but all upload attempts produced empty files on the Windows server (this due,
2001 Mar 11
0
Problems with sftp under SCO OpenServer (fwd)
This is the final results of sftp on SCO OpenServer. ---------- Forwarded message ---------- Date: Mon, 26 Feb 2001 12:27:51 -0700 From: Greg Jewell <gjewell at cnnxn.com> To: mouring at etoh.eviladmin.org Subject: RE: Problems with sftp under SCO OpenServer > -----Original Message----- > From: mouring at etoh.eviladmin.org [mailto:mouring at etoh.eviladmin.org] > Sent: Monday,
2008 Feb 06
1
Has anyone gotten SCO Openserver working under Xen?
So far, I''ve only found references to success under VMware. But has anyone managed it, with either the open source or commercial versions of Xen? I like Xen and have worked with it extensively for RHEL and CentOS, but it could save me a whole lot of hardware money if I can decommission some OpenServer hardware and store working OS''s under virtual images.
2002 Oct 28
0
Port to SCO Openserver with PAM enabled
Hi all, I'm writing to you becuase I have compiled PAM in SCO (now Caldera) Openserver 5.0.x, and when I tried to use SSH with PAM enabled, y realized that OpenSSH depends on the user to exist en the /etc/passwd, and /etc/shadow databases, or equivalent ones (it uses getpw...() functions to determine validity of the user). In Linux, the simlpe solution is to use nsswitch, but it seems to hard
1999 Sep 22
0
SAMBA digest 2243 / 2.0.5 and SCO Openserver 5.0.5
James A. Mutter wrote: >Does anyone know of any issues with 2.0.5 and SCO Openserver 5.0.5? A >friend told me that he had "real problems", but couldn't elaborate. >Is there something I should be aware of before I try this? >Thanks, >Jim Hi, As far as I know there are no problems with running Samba on a SCO system, beside the normal Samba configuration problems.
2002 Jan 02
1
SCO OpenServer password issue
If SCO OpenServer is configured for large passwords, i.e. u_pwseg is greater than 1 in /etc/auth/system/default, then user authentication in auth-passwd.c will fail for users whose passwords are longer than 8 characters. The "traditional" level of security installs with u_pwseg#1, so most users would never encounter this problem. This has been an issue in openssh since I started using