Displaying 20 results from an estimated 1000 matches similar to: "SCO OpenServer 5.0.5, issues with MAXPATHLEN and tty devices"
2000 Jun 12
1
Openssh on SCO Openserver Release 5
Yo Andrew!
What version of Openssh are you trying?
RGDS
GARY
On Mon, 12 Jun 2000, Andrew McGill wrote:
> Date: Mon, 12 Jun 2000 15:26:53 +0200
> From: Andrew McGill <andrewm at datrix.co.za>
> To: djm at ibs.com.au
> Cc: gem at rellim.com
> Subject: Openssh on SCO Openserver Release 5
>
> Hi there
>
> Your e-mail address appears in the README for openssh,
2003 Sep 05
2
3.6p1 bug on SCO OpenServer
SCO OpenServer 5.0.x
Openssh 3.6p1
loginrec.c writes incorrect data into the ut_id field of the utmp file.
This has been an issue since at least openssh 3.0.2 but I never bothered
to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects
the problem. Below is a brief patch to configure which does this. You
can observe the errant results in the "Line" column from the
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.
2001 Jan 04
0
'make' fails on SCO OpenServer 5.0.5
Hi folks,
I'm trying to install OpenSSH 2.3.0 on a SCO OpenServer Release 3.2 v.5.0.5
box.
I downloaded the tarball from the 'portable' directory and uncompressed.
./configure --with-egd-pool=/dev/random <-- works with no errors. Output attached here:
(See attached file: output.txt)
make displays:
root:/tmp/OpenSSH/openssh-2.3.0p1 # make
cc -g -I. -I.
2002 Mar 12
3
error compiling openssh-3.1p1 under SCO OpenServer 5.0.5
Trying to compile openssh-3.1p1 on SCO using:
export CCFLAGS='-L/usr/local/lib -I/usr/local/include'
./configure --sysconfdir=/etc/ssh --with-rsh=/usr/bin/rcmd
--exec-prefix=/usr
OpenSSH has been configured with the following options:
User binaries: /usr/bin
System binaries: /usr/sbin
Configuration files: /etc/ssh
Askpass
2000 Jun 06
0
SCO Openserver 5.0.5 ssh2 problem.
I just finished compiling openssh-2.1.0p3 on a SCO openserver system. I
generated the keys fine and genereated the host keys both rsa and dsa
without problems.
ssh (version1) works great.
I tried to use ssh (version 2) and after being prompted to login, it
quits. I am attaching a script file of...
ssh -v -2 root at sco to see if you can find the problem. Let me know how I
can help.
[root at
2001 Feb 22
3
Problems with sftp under SCO OpenServer
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
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
2000 May 19
1
Problem linking 2.0.7 under SCO OpenServer: uniarray_2_ascarray u ndefined
I'm having trouble linking Samba 2.0.7 under SCO OpenServer 5.0.5 and GCC
2.7.2.3. All the source files compile without errors. However, when I try
to link smbd, swat, or smbpasswd, I get the error message:
Undefined first referenced
symbol in file
uniarray_2_ascarray rpc_parse/parse_spoolss.o
I can't seem to find any
2000 Jul 20
0
SCO help
Hello,
I need some help. I have compiled openssh-2.1.1p3 on SCO 5.0.5. It
compiled without any complaints. My problem is the when someone tries to
connect to the sshd, they get the message
Warning: Remote host failed or refused to allocate a pseudo tty.
stty: tcgetattr failed: Bad address (error 14)
I have upped the pseudo ttys in the kernel and relinked but I still get
this error.
Could
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
2000 May 19
2
Solved: on Solaris, "couldn't wait for child '...' completion: No child processes"
> John Horne [SMTP:J.Horne at plymouth.ac.uk] wrote:
>
> Emanuel Borsboom <emanuel at heatdeath.org> wrote:
>> Trying to install the portable OpenSSH on Solaris 2.6. Compiling from
>> openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd
>> starts fine. First connection from another system works. Child sshd is
>> forked, but the parent dies
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
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
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,
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:
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.
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
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
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