02-17-2002
Use netconfig command to setup networking for SCO Openserver.
Please be aware of something with SCO Openserver.
There are basically 2 versions available
1 - SCO Openserver (Host) edition. Which does not have networking built it. It's primarily used for terminals.. character based.
2 - SCO Openserver (Enterprise) edition. Which has networking built it.
If you try and run 'netconfig' and it fails, check to make sure you are running the Enterprise edition of SCO. If you aren't, then you will have to upgrade your O/S to the enterprise edition.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know of any good imaging tools that can be used to create an image of a Sco-Unix box? (2 Replies)
Discussion started by: gmrfh1
2 Replies
2. UNIX for Dummies Questions & Answers
Hi there!
We have a SCO UNIX box that uses a bunch of dumb terminals. We also have a workgroup of 5 stations Is there a way that we can network the UNIX box to the workgroup for dumb terminal.. A novice would think you could TCP the UNIX machine through a hub and use hypertermal as a dumb... (6 Replies)
Discussion started by: huilai
6 Replies
3. UNIX for Advanced & Expert Users
If I want to access unix box via VPN tunnel,from windows box.
What sould I configure on the windows client PC, and what should I enable on the Unix Server box ?
I am using Solaris V10 intel platform, and I am using windows XP, and 2003 for client (0 Replies)
Discussion started by: zillah
0 Replies
4. SCO
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
Discussion started by: fedir
0 Replies
5. UNIX for Dummies Questions & Answers
After having to replace a video card and having a corrupt root directory, I had to wipe out and reinstall my SCO OpenServer Enterprise System 5.0.2. because nothing would work for the root password. I am now trying to reinstall the Oracel Workgroup Server SCO v7.1.5.2 and it tells me I need to... (1 Reply)
Discussion started by: sheilaj1
1 Replies
6. UNIX for Dummies Questions & Answers
I am able to run the UNIX commands in a Windows box from a UNIX box through "SSH" functionality. But whenever the SSH connection is established between UNIX and Windows, password for windows box is being asked.
Is there a way to avoid asking password whenever the SSH connection is made? Can I... (1 Reply)
Discussion started by: D.kalpana
1 Replies
7. SCO
We have made numerous requests to our system administrator to add new employees at login screen ( passwords not required ) to no avail.
I can login into root but not sure how to proceed from there.
We have a 10 yr. old version of SCO
Can anyone help?
I know very few unix commands okay... (1 Reply)
Discussion started by: houseostyle
1 Replies
8. Shell Programming and Scripting
Hi
our unix admin has copied all files from one unix box to new unix box. We just need to confirm that all the file systems are copied properly. How to validate. (9 Replies)
Discussion started by: sravanreddym
9 Replies
9. Shell Programming and Scripting
Hello all !
I'm trying to write a shell script (bash) to ftp a file starting with particular name like "Latest_" that is present on a Windows box to UNIX server. Basically I want to set this script in the cron so that daily the new build that is posted on the Windows box can be downloaded to the... (2 Replies)
Discussion started by: vijayb4u83
2 Replies
10. UNIX for Advanced & Expert Users
Hello,
We run a mailing list and on our server sendmail is adding .org after some addresses, e.g. the first and third entries below in the process listingroot 1528 0.0 0.1 11764 6524 ? Ss Sep21 0:01 sendmail: ./p8NMgM0X031218 dimaventures.com.org.: user open
root ... (1 Reply)
Discussion started by: prautt
1 Replies
lib(3pm) Perl Programmers Reference Guide lib(3pm)
NAME
lib - manipulate @INC at compile time
SYNOPSIS
use lib LIST;
no lib LIST;
DESCRIPTION
This is a small simple module which simplifies the manipulation of @INC at compile time.
It is typically used to add extra directories to perl's search path so that later "use" or "require" statements will find modules which are
not located on perl's default search path.
Adding directories to @INC
The parameters to "use lib" are added to the start of the perl search path. Saying
use lib LIST;
is almost the same as saying
BEGIN { unshift(@INC, LIST) }
For each directory in LIST (called $dir here) the lib module also checks to see if a directory called $dir/$archname/auto exists. If so
the $dir/$archname directory is assumed to be a corresponding architecture specific directory and is added to @INC in front of $dir.
lib.pm also checks if directories called $dir/$version and $dir/$version/$archname exist and adds these directories to @INC.
The current value of $archname can be found with this command:
perl -V:archname
The corresponding command to get the current value of $version is:
perl -V:version
To avoid memory leaks, all trailing duplicate entries in @INC are removed.
Deleting directories from @INC
You should normally only add directories to @INC. If you need to delete directories from @INC take care to only delete those which you
added yourself or which you are certain are not needed by other modules in your script. Other modules may have added directories which
they need for correct operation.
The "no lib" statement deletes all instances of each named directory from @INC.
For each directory in LIST (called $dir here) the lib module also checks to see if a directory called $dir/$archname/auto exists. If so
the $dir/$archname directory is assumed to be a corresponding architecture specific directory and is also deleted from @INC.
Restoring original @INC
When the lib module is first loaded it records the current value of @INC in an array @lib::ORIG_INC. To restore @INC to that value you can
say
@INC = @lib::ORIG_INC;
CAVEATS
In order to keep lib.pm small and simple, it only works with Unix filepaths. This doesn't mean it only works on Unix, but non-Unix users
must first translate their file paths to Unix conventions.
# VMS users wanting to put [.stuff.moo] into
# their @INC would write
use lib 'stuff/moo';
NOTES
In the future, this module will likely use File::Spec for determining paths, as it does now for Mac OS (where Unix-style or Mac-style paths
work, and Unix-style paths are converted properly to Mac-style paths before being added to @INC).
If you try to add a file to @INC as follows:
use lib 'this_is_a_file.txt';
"lib" will warn about this. The sole exceptions are files with the ".par" extension which are intended to be used as libraries.
SEE ALSO
FindBin - optional module which deals with paths relative to the source file.
PAR - optional module which can treat ".par" files as Perl libraries.
AUTHOR
Tim Bunce, 2nd June 1995.
"lib" is maintained by the perl5-porters. Please direct any questions to the canonical mailing list. Anything that is applicable to the
CPAN release can be sent to its maintainer, though.
Maintainer: The Perl5-Porters <perl5-porters@perl.org>
Maintainer of the CPAN release: Steffen Mueller <smueller@cpan.org>
COPYRIGHT AND LICENSE
This package has been part of the perl core since perl 5.001. It has been released separately to CPAN so older installations can benefit
from bug fixes.
This package has the same copyright and license as the perl core.
perl v5.18.2 2017-10-07 lib(3pm)