11-22-2015
I'm aware that the link refers to UnixWare 7 but does it not also apply to Openserver V?
We all know that USB support on Openserver was lacking for a long time until particular maintenance packs arrived. However, after that the USB ports were recognised by the kernel and can be used.
Once the USB ports have device nodes (in /dev) that work (and you can test with, say, a memory stick) then can't a USB printer be attached in the way described using scoadmin?
Last edited by hicksd8; 11-23-2015 at 06:23 AM..
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 CENTOS
usb_make_path
USB_MAKE_PATH(9) Host-Side Data Types and Macro USB_MAKE_PATH(9)
NAME
usb_make_path - returns stable device path in the usb tree
SYNOPSIS
int usb_make_path(struct usb_device * dev, char * buf, size_t size);
ARGUMENTS
dev
the device whose path is being constructed
buf
where to put the string
size
how big is "buf"?
RETURN
Length of the string (> 0) or negative if size was too small.
NOTE
This identifier is intended to be "stable", reflecting physical paths in hardware such as physical bus addresses for host controllers or
ports on USB hubs. That makes it stay the same until systems are physically reconfigured, by re-cabling a tree of USB devices or by moving
USB host controllers. Adding and removing devices, including virtual root hubs in host controller driver modules, does not change these
path identifiers; neither does rebooting or re-enumerating. These are more useful identifiers than changeable ("unstable") ones like bus
numbers or device addresses.
With a partial exception for devices connected to USB 2.0 root hubs, these identifiers are also predictable. So long as the device tree
isn't changed, plugging any USB device into a given hub port always gives it the same path. Because of the use of "companion" controllers,
devices connected to ports on USB 2.0 root hubs (EHCI host controllers) will get one path ID if they are high speed, and a different one if
they are full or low speed.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 USB_MAKE_PATH(9)