unixware 2.0


 
Thread Tools Search this Thread
Operating Systems SCO unixware 2.0
# 1  
Old 11-06-2008
unixware 2.0

High,
I have a simulator application running on unixware 2.1, there are no original installation CDs for the application. is it possible to copy directories and configuration files, related to the installed application, from unixware 2.1 to other system running Unixware 7.1.1 (replacing Unixware 7.1.1 directories).
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. SCO

UnixWare 2.x needed

Anyone here using Unixware 2.x? I want to try some binary testing on this system regarding DG/UX binaries. (4 Replies)
Discussion started by: dgux
4 Replies

2. SCO

Unixware Crash ...

Hi, I need help, one of our servers is down, and all data in that Server are critical: The Scenario: ------------- I have a computer with the next architecture: architecture=IA32 bus_types=PCI2.10,ISA,PnP1.0 hostname=xxx.xxx.xxx (the real name is hidden) hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
2 Replies

3. News, Links, Events and Announcements

Are the UnixWare 7.1.1 sources available?

So, I was browsing groklaw.net, and I was surprised to read that Pamela Jones was reading the copyright notices in the UnixWare 7.1.1 source code files... Groklaw - Santa Cruz Listed Novell as Owning the Copyrights in 1999 How can that be? Are the UnixWare 7.1.1 sources available to the... (1 Reply)
Discussion started by: pepinox
1 Replies

4. SCO

Installing UNIXWARE 7.1.1

I want to install unixware 7.1.1 on a server which does not have a on board floppy drive. I have got a USB floppy drive. Can anybody please help me...how could I provide HBA disk using this USB floppy drive???? (0 Replies)
Discussion started by: siddhartha7m
0 Replies

5. SCO

Unixware 7.11 cannot telnet

Hi all, I recently re-installed a Unixware 7.1.1 system for a customer. It installed correctly, I can ping the server but I cannot telnet to it. I did check and telnetd is running. Am i missing something in the config? thanks for any help (0 Replies)
Discussion started by: RDP
0 Replies

6. SCO

Problem in Unixware 7

Hi, I need help for SCO UNIXWARE 7.1.0. During booting it is detecting the network card (Intel PRO 100B /100+) but it is giving error : "UX:S69inet:error". Hence network is not getting up. I have tried with another network card (D-Link DFE 538TX) but unable to get the proper driver for the... (1 Reply)
Discussion started by: hcl.rajat
1 Replies

7. SCO

Unixware problem

Dear All, I have a HP Netserver LH3 server which has unixware 7 os with oracle. Suddenly it shows a error message that " Raw Stack Dump beigns at 0xFFFDABIC... Generating Selective dump Storing system memory image for crash analysis.... #scanning memory....dumping to disk (Press any key to... (0 Replies)
Discussion started by: mr.chiranjib
0 Replies

8. UNIX for Dummies Questions & Answers

please help me about unixware 7.1.3

msg: vfs_mountroot:cannot mount root %%%%%% system don't start (0 Replies)
Discussion started by: hushboy
0 Replies

9. SCO

Performance issue from Unixware 2.1 to Unixware 7

Hello, I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0. My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls. What i hyave noticed is that after a... (0 Replies)
Discussion started by: Amith
0 Replies

10. IP Networking

Change ip on UnixWare 2.1.2

I changed the IP whit Ifconfig and I used ping to test the conetions the conection is rigth on my LAN (NetA) But, I have two networks for example: NetA route to NetB and vicevers On NetB ping to any machine on NetA, it is respons successfully. but I ping to UNIX server no respons. I... (1 Reply)
Discussion started by: lmena
1 Replies
Login or Register to Ask a Question
sasl_appname.conf(4)						   File Formats 					      sasl_appname.conf(4)

NAME
sasl_appname.conf - SASL options and configuration file SYNOPSIS
/etc/sasl/appname.conf DESCRIPTION
The /etc/sasl/appname.conf file is a user-supplied configuration file that supports user set options for server applications. You can modify the behavior of libsasl and its plug-ins for server applications by specifying option values in /etc/sasl/appname.conf file, where appname is the application defined name of the application. For sendmail, the file would be /etc/sasl/Sendmail.conf. See your appli- cation documentation for information on the application name. Options that you set in a appname.conf file do not override SASL options specified by the application itself. The format for each option setting is: option_name:value. You can comment lines in the file by using a leading #. The SASL library supports the following options for server applications: auto_transition When set to yes, plain users and login plug-ins are automatically transitioned to other mechanisms when they do a successful plaintext authentication. The default value for auto_transition is no. auxprop_plugin A space-separated list of names of auxiliary property plug-ins to use. By default, SASL will use or query all available auxiliary property plug-ins. canon_user_plugin The name of the canonical user plug-in to use. By default, the value of canon_user_plugin is INTERNAL, to indicated the use of built-in plug-ins.. log_level An integer value for the desired level of logging for a server, as defined in <sasl.h>. This sets the log_level in the sasl_server_params_t struct in /usr/include/sasl/saslplug.h. The default value for log_level is 1 to indicate SASL_LOG_ERR. mech_list Whitespace separated list of SASL mechanisms to allow, for example, DIGEST-MD5 GSSAPI. The mech_list option is used to restrict the mechanisms to a subset of the installed plug-ins. By default, SASL will use all available mechanisms. pw_check Whitespace separated list of mechanisms used to verify passwords that are used by sasl_checkpass(3SASL). The default value for pw_check is auxprop. reauth_timeout This SASL option is used by the server DIGEST-MD5 plug-in. The value of reauth_timeout is the length in time (in minutes) that authentication information will be cached for a fast reauthorization. A value of 0 will disable reauthorization. The default value of reauth_timeout is 1440 (24 hours). server_load_mech_list A space separated list of mechanisms to load. If in the process of loading server plug-ns no desired mech- anisms are included in the plug-in, the plug-in will be unloaded. By default, SASL loads all server plug- ins. user_authid If the value of user_authid is yes, then the GSSAPI will acquire the client credentials rather than use the default credentials when it creates the GSS client security context. The default value of user_authid is no, whereby SASL uses the default client Kerberos identity. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) SunOS 5.10 14 Oct 2003 sasl_appname.conf(4)