Sponsored Content
Full Discussion: TCP in sco unix 3.2
Operating Systems SCO TCP in sco unix 3.2 Post 302387909 by edfair on Monday 18th of January 2010 11:19:02 PM
Old 01-19-2010
What version of TCPIP works with either 3.2 or Xenix? I have a couple of packages but never installed since I took the customers to OServer before I got around to networking at the earler version.
How would you do the transfer, assuming that one of the packages fit the needs?
 

10 More Discussions You Might Find Interesting

1. IP Networking

TCP/IP printing on SCO 2.1.3

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

SCO TCP/IP runtime System for SCO Unix

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

TCP/IP in c (unix)

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

SCO UNIX "TCP/IP not licensed error"

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

all tcp are CLOSED on SCO Unix on VMWARE

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

/dev/inet/tcp not listening in SCO 6.

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

load sco xenix and sco unix binary ?

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

SCO TCP/IP ?

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

SCO TCP/IP 1.2.0. floppys needed

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

Sco Openserver Starting TCP/IP Services

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
yumdb(8)																  yumdb(8)

NAME
yumdb - query and alter the Yum database SYNOPSIS
yumdb [command] [packages ...] DESCRIPTION
This command is used to query and alter the yum database, which is a simple key value store used in conjunction with the rpm database. Any installed package can have arbitrary data in the yum database, however the main use case is to store extra data about packages as they are installed. yumdb commands are: yumdb get <key> [pkg-wildcard]... This command will get the value for the given key, limiting to any specified packages. yumdb set <key> <value> [pkg-wildcard]... This command will set the value for the given key, to the given value, limiting to any specified packages. yumdb del <key> [pkg-wildcard]... This command will delete the given key, limiting to any specified packages. yumdb rename <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, noth- ing happens. yumdb rename-force <old-key> <new-key> [pkg-wildcard]... This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new- key is deleted. yumdb copy <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, nothing happens. yumdb copy-force <old-key> <new-key> [pkg-wildcard]... This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-key is deleted. yumdb search <key> <wildcard>... This command will search all packages for the given key, against any of the given wildcard values. yumdb exist <key> [pkg-wildcard]... This command will print any packages which have the given key, limiting to any specified packages. yumdb unset <key> [pkg-wildcard]... This command will print any packages which do not have the given key, limiting to any specified packages. yumdb info [pkg-wildcard]... This command will display all the data stored in the yumdb, limiting to any specified packages. yumdb sync [pkg-wildcard]... This command will add any missing data to the yumdb from the repositories, limiting to any specified packages. This is useful to run if you have had any aborted transactions (and thus. missing yumdb data). Note that "yumdb sync" cannot know all the information that would have been put into the yumdb at the time. yumdb sync-force [pkg-wildcard]... This command will replace any data in the yumdb from the repositories, limiting to any specified packages. EXAMPLES
List all the packages which don't have a from_repo key/value: yumdb unset from_repo List all the packages which were installed as dependencies: yumdb search reason dep WELL KNOWN KEYS
Note that there is no limit to the number of keys that can be created or what they may contain (for installed packages only). However this is a list of well known keys, and what they store. checksum_data checksum_type These keys store the createrepo checksum, and it's type, of the available package yum installed. Note that these are used by "yum version" to calculate the rpmdb version. command_line This key stores the entire command line, of the yum command (if it was called). from_repo from_repo_revision from_repo_timestamp These keys take values from the available package yum installed, and store the repo id, it's revision and timestamp. reason This key stores either "user" or "dep", currently. To mark if the user requested the package to be installed, or if it was brought in automatically as a dependency. Note that this is kept over updates. releasever This key stores the value of releasever, when the package was installed. installonly If this attribute has the value "keep" then this package will not be removed automatically by the installonly process (and does not count towards the installonly_limit). SEE ALSO
yum (8) rpm (8) AUTHORS
James Antill <james.antill@redhat.com>. James Antill 8 April 2010 yumdb(8)
All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy