similar to: BUG #18

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

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"

Hi All, I've been having issues getting X forwarding to work on OpenServer for OpenSSH versions 3.4p1 and 3.5p1. I have compiled OpenSSH on Redhat Linux 8.0, Solaris 8, and OpenServer 5.0.6, but the OpenServer box is the only one that exhibits the problem. I've detailed everything below. I am using PuTTY for my ssh client under Windows. If I connect to the Linux or Solaris boxes, X

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

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:

You can download Ncurses for SCO OpenServer via ftp://ftp2.caldera.com/pub/skunkware/osr5/vols/ncurses-4.2-VOLS.tar This is a tar archive of media images suitable for installation with the SCO Software Manager (/etc/custom). Cheers, Ron Record rr@sco.com re: > Date: Wed, 26 Feb 2003 15:54:59 +0000 > From: Simon Hobson <shobson-lists@colony.com> > To: samba@lists.samba.org >

I''ve been dealing with SCO OpenServer 5.0.6 lately, and was forced to use VMware Workstation when I couldn''t get it working on Xen. That let me use it with IDE emulated drives, that avoided the whole intricate fun and games of installing compatible SCSI drivers. But VMWare ESX, which was not what I''d wanted to deal with, got selected for use, and since it

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

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

Good Morning, I understand you provide support for the Samba project. I am searching for some FREE help solving what I think is a very simple problem for an experience Samba professional. I am running Samba 2.2.12 on an old SCO OpenServer 5.0.6 box. I cannot update to a more recent version of Samba as this is the last version that will run on SCO OpenServer 5.0.6. I have some

Hi openssh-unix-dev subscribers :) I have found that ServerAliveInterval & ServerAliveCountMax have some bug. Basically the ssh-alive check function (that verify the peer is alive) is called only if no data at all gets into ssh (when it should work only for server channel).I am pretty sure developers know about this ..anyway I have tried to fix this issue. Here is the patch: diff -rNu

Hello, There appears to be a display issue when connecting to an OpenServer system using SSH2. I've compiled OpenSSH 2.5.1p1 on SunOS 5.7, HP-UX 11, and OpenServer 5.0.5. Whenever the destination is the OpenServer system, the display has a step-ladder effect. This behavior exhibits itself no matter what box the origination point is. A quick inspection revealed that the stty settings of

The attached patch adds an option (off by default to preserve current behavior) to set a timeout on the select() statement that waits for input in clientloop.c. This fixes a timeout issue for me (explained below) and probably also fixes the timeouts mentioned in last month's thread "Idle time out". The patch is also available by http from:

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.

Hi, I am trying to run sftp on SX-6 and it is giving me problem when I try to exit from sftp. On pressing ^D or entering "bye" on sftp prompt, sftp hangs. And I have to press ^C to quit. The versions are: - 1. openssh-3.1p1 on both client and server. 2. Both client (sftp) and server (sshd) are running on SX-6 It appears that the client and server are hanging on "select".

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:

Hello, I compiled OpenSSH 2.5.1p1 for SCO OpenServer 5.0.5, HPUX B.11.00, and SunOS 5.7. When I sftp into the HP or Sun box, everything works fine. However, whenever I sftp into the OpenServer box, all remote filenames are shown as "(null)". File sizes, owners, etc. display properly. This behavior is exhibited from all origination points. OpenSSH was configured with identical

We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix Openserver 5.0.5. I'm wondering if anybody else is using this version of Samba on SCO. I used an older version 3 years ago and rarely had a problem. I just installed this version and am experiencing an annoying problem: We use windows 95, 98 and NT4.0 (SP3/SP6) workstations. All passwords are set to clear text. The samba

Hello, We are trying to compile the samba 2.2.0-alpha3 source on a SCO Openserver 5.0.6 server. we ran configure with standard options no visible problems. On running make we get the following error ..... Compiling tdb/spinlock.c Compiling tdb/tdbutil.c Compiling printing/printing.c Compiling printing/nt_printing.c Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c

Denis Caron wrote: >>We seem to be experiencing some problems with Samba 2.0.6 on SCO Unix >>Openserver 5.0.5. >> >>I'm wondering if anybody else is using this version of Samba on SCO. I used >>an older version 3 years ago and rarely had a problem. I just installed this >>version and am experiencing an annoying problem: >> >>We use