01-19-2010
Ed, I think the package was/is called TCP-IP version 1.2.1. There were several releases of the LLI package, especially as the PCI slot appeared about the same time.
10 More Discussions You Might Find Interesting
1. IP Networking
I am trying to set up TCP/IP printing to so we can remove the old novel server. The printer details have been added to the etc/hosts file correctly, and the printer added as a remote UNIX printer . However when a print job is issued lpstat -o displays the job, but it dosent move. Any help yould... (2 Replies)
Discussion started by: eel_king
2 Replies
2. Filesystems, Disks and Memory
Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies
3. IP Networking
I have written a client receive (TCP/IP) program which is up all the time. It connects to the server during Beginning of the day and stays alert and reads a message whenever one comes in.
the problem is after receiving a message, the client_receive program is getting a message with zero bytes.... (0 Replies)
Discussion started by: Rajeshsu
0 Replies
4. UNIX for Dummies Questions & Answers
I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based).
I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies
5. SCO
Hi folks,
First of all, sorry about my english, isn't the best and thks for advance.
Here es my problem...
I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies
6. SCO
While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out?
An early response will be appreciated.
Thank you
Regards
TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies
7. SCO
Hi
I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7.
I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies
8. SCO
Hello!
I tried to install an old version of SCO for test purposes, (3.2v4.0y), all fine,
but my TCP/IP disks are "unreadable" and I cant find them on the internetz.
Also, SCO doesnt respond to my request....is there any source for those images
available? I have license/activation key which... (5 Replies)
Discussion started by: doc_holiday
5 Replies
9. SCO
Hi,
every body, I have the same problem but with the SCO TCP/IP 1.2.0. I have the 3 floppy disks but I get an error on disk 3, unreadable. I have seen the closed post regarding the sco tcp/ip. Does anybody have those disks?
Thank you in advance
Mariano (8 Replies)
Discussion started by: locovich
8 Replies
10. SCO
Hi all,
I have a customer whose sco unix server wasnt power off correctly and when booting it up I noticed that the boot up takes a while to finish the " Starting TCP services: snmpd routed lpd". after that the server is ready for login, but you cannot ping anything from the server (apart from... (2 Replies)
Discussion started by: CharlL
2 Replies
LEARN ABOUT CENTOS
biosdevname
BIOSDEVNAME(1) General Commands Manual BIOSDEVNAME(1)
NAME
biosdevname - give BIOS-given name of a device
SYNOPSIS
biosdevname [options] [args]...
DESCRIPTION
biosdevname takes a kernel device name as an argument, and returns the BIOS-given name it "should" be.
OPTIONS
-i, --interface
Treat [args] as ethernet devs
-d, --debug
Enable debugging
-p, --policy [physical|all_ethN]
-P, --prefix [string]
string use for embedded NICs in the physical policy (default=em)
-x, --nopirq
Do not use $PIR table for mapping PCI device to slot. Some BIOS have incorrect values.
-s, --smbios [x.y]
Require minimum SMBIOS version x.y
POLICIES
The physical policy is the current default. However, when invoking biosdevname in udev rules, one should always specify the policy you
want, as the default has changed over time.
The physical policy uses the following scheme:
em<port>[_<virtual instance>]
for embedded NICs
p<slot>p<port>[_<virtual instance>]
for cards in PCI slots
The all_ethN policy makes a best guess at what the device order should be, with embedded devices first, PCI cards in ascending slot
order, and ports in ascending PCI bus/device/function order breadth-first. However, this policy does not work if your PCI devices
are hot-plugged or hot-pluggable, including the virtual functions on an SR-IOV device. In a hot-plug scenario, each separate udev
instance will be invoked in parallel, while the device tree is still being populated with new devices. Each udev instance will see
a different PCI tree, and thus cannot provide consistent enumeration. Use of this policy should be limited to only scenarios where
all PCI devices are present at boot (cold-plug).
EXIT CODES
Returns 0 on success, with BIOS-suggested name printed to stdout.
Returns 1 on provided device name lookup failure.
Returns 2 if system BIOS does not provide naming information. biosdevname requires system BIOS to provide naming information, either via
SMBIOS or sysfs files.
Returns 3 if not run as root but requires root privileges.
Returns 4 if running in a virtual machine.
SEE ALSO
http://linux.dell.com/wiki/index.php/Oss/libnetdevname
http://linux.dell.com/files/biosdevname/
git://linux.dell.com/biosdevname.git
RELATED PROGRAMS
The dmidecode package contains two tools useful for debugging BIOS features that biosdevname uses, specifically dmidecode to read the
SMBIOS Type 9 and Type 41 tables, and biosdecode to read the PCI IRQ Routing Table. Please include the output of each of these programs in
any bug reports.
AUTHOR
biosdevname was written by Matt Domsch <Matt_Domsch@dell.com>
This manual page was written by Rudy Gevaert <Rudy.Gevaert@UGent.be>, for the Debian project (but may be used by others).
Nov 28, 2010 BIOSDEVNAME(1)