11-20-2015
USB Printing for SCO UNIX OpenServer 5.0.7
Years ago I set up USB printing for SCO UNIX OpenServer 5.0.7 for a client--but I've misplaced my notes on how to do this! Maintenance Pack 5 is installed. I need step-by-step instructions to proceed. I've searched the SCO Knowledge Base site and found nothing there or elsewhere on the Web.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi everybody
I have got a set of sco unix open server release 3.0 flopyy disks series N1, N2, M1, P1...P43, Release notes..
ý did a fresh installation. but ý cant install ethernet card. when ý use netconfig-ad a chain -tcpip... there is a messge :
the sco contain TCP/IP driver. and ý... (2 Replies)
Discussion started by: kaygusuz
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am a new user to the Server SCO OpenServer(TM) Release 5.
Could you please advise any books for me to have a comprehensive view of how to administrate this Unix server.
Thanks (1 Reply)
Discussion started by: rogercko
1 Replies
3. SCO
I have a USB,can i use it in the sco unix 5.0.6? (1 Reply)
Discussion started by: fresh
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
We have a Unix 3.2v5.0.5.
I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts).
This is the configuration file :
Code:
root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies
5. SCO
Does anyone here have experience with running SCO UNIX OpenServer 5.0.7 on the Gigabyte GA-X58A-OC motherboard? Are there any problems? (2 Replies)
Discussion started by: Transpower
2 Replies
6. SCO
Hi everybody
I'm going to install svn client in sco unix openserver 5.0.7
where should I start ?
I have no Idea what to do ?
tnx (3 Replies)
Discussion started by: javad1_maroofi
3 Replies
7. SCO
My client has lost the SCO OS 5.0.5 install media.
However, they do have a working SCO 5.0.5 system, but is crumbling apart.
Where can I find the SCO OS 5.0.5 install media?
Or can I get a copy of the SCO CD as a ISO file?
Your help is much appreciated. (7 Replies)
Discussion started by: chedlee88-1
7 Replies
8. SCO
Has anyone here used eSATA drives on SCO UNIX OpenServer 5.0.7? SCSI host adapters and drives are getting harder to find, so I'm thinking about eventually switching to eSATA, but only, of course, if they will work with OpenServer. (2 Replies)
Discussion started by: Transpower
2 Replies
9. SCO
hi
How can I use my USB Flash memory in Sco 5.0.6
tanks (1 Reply)
Discussion started by: moein.mojtaba
1 Replies
10. SCO
Obviously, the client browsers which came with SCO UNIX OpenServer, Netscape and Mozilla, are horribly outdated now. Does anyone know of a relatively current browser which will work in their place? (2 Replies)
Discussion started by: Transpower
2 Replies
LEARN ABOUT MOJAVE
sasl_client_step
sasl_client_step(3) SASL man pages sasl_client_step(3)
NAME
sasl_client_step - Perform a step in the authentication negotiation
SYNOPSIS
#include <sasl/sasl.h>
int sasl_client_step(sasl_conn_t *conn,
const char *serverin,
unsigned serverinlen,
sasl_interact_t ** prompt_need,
const char ** clientout,
unsigned * clientoutlen);
DESCRIPTION
sasl_client_step() performs a step in the authentication negotiation. It returns SASL_OK if the whole negotiation is successful and
SASL_CONTINUE if this step is ok but at least one more step is needed. A client should not assume an authentication negotiation is success-
ful just because the server signaled success via protocol (i.e. if the server said ". OK Authentication succeeded" in IMAP sasl_client_step
should still be called one more time with a serverinlen of zero.
If SASL_INTERACT is returned the library needs some values to be filled in before it can proceed. The prompt_need structure will be filled
in with requests. The application should fulfill these requests and call sasl_client_start again with identical parameters (the prompt_need
parameter will be the same pointer as before but filled in by the application).
conn is the SASL connection context
serverin is the data given by the server (decoded if the protocol encodes requests sent over the wire)
serverinlen is the length of serverin
clientout and clientoutlen is created. It is the initial client response to send to the server. It is the job of the client to send it over
the network to the server. Any protocol specific encoding (such as base64 encoding) necessary needs to be done by the client.
RETURN VALUE
sasl_client_step returns an integer which corresponds to one of the following codes. SASL_CONTINUE indicates success and that there are
more steps needed in the authentication. SASL_OK indicates that the authentication is complete. All other return codes indicate errors and
should either be handled or the authentication session should be quit.
CONFORMING TO
RFC 4422
SEE ALSO
sasl(3), sasl_callbacks(3), sasl_errors(3), sasl_client_init(3), sasl_client_new(3), sasl_client_start(3)
SASL
10 July 2001 sasl_client_step(3)