10 More Discussions You Might Find Interesting
1. Solaris
In Solaris 10 it was easy, a simple grep through modinfo output and you'd have the version of any loaded module, including your NIC drivers. In my career I've seen many people relying on this information in their scripts. Now I'm on Solaris 11, and where have the version numbers gone? The... (0 Replies)
Discussion started by: cambridge
0 Replies
2. Linux
Hi All,
I am trying to make rpm package for unixODBC driver manager 2.3.0 using below spec file. During rpmbuild i am getting the error. Can you pls advice how we can overcome this issue
%define name unixODBC
%define ver 2.3.0
%define prefix /usr
%define sysconfdir /etc
%define libdir... (2 Replies)
Discussion started by: kamauv234
2 Replies
3. Programming
Hi, all:
My writed NIC driver for rtl8139d adapter on linux 3.0.4 cannot send and recieve simultaneously but is able to send or recieve in parallel respectively. As soon as it send and recieve at the same time, the transmmition rate on both directions gradually decrease to zero b/s and report... (1 Reply)
Discussion started by: liklstar
1 Replies
4. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
5. UNIX for Advanced & Expert Users
Hi, all:
How can I know whether the packets recieved from network by my own NIC driver are transmitted to upper layer(IP layer) or not?
How can I know if the packets come from upper layer are passed to my own NIC driver and go out further?
Is there any shell command or utility show... (9 Replies)
Discussion started by: liklstar
9 Replies
6. Red Hat
Guys,
Can you help me how to verify the current installed NIC driver version in RHEL5.3?
Thanks.:D (1 Reply)
Discussion started by: shtobias
1 Replies
7. SCO
hi
I have a fresh installation of SCO 5.0.6 and I have download a NIC driver for Intel Pro 1000:
ftp://ftp.sco.com/pub/openserver5/507/drivers/eeG_5.0.7g/VOL.000.000
Howto install it using floppy?
---------- Post updated at 04:02 PM ---------- Previous update was at 02:18 PM... (0 Replies)
Discussion started by: ccc
0 Replies
8. IP Networking
Hi
I need to know how a driver for a network interface card works, I want to learn the basic principles since I know that every driver has its specific implementation.
For example when we speak about the scheduler, we can read an operating system book and learn general design concepts e.g.... (0 Replies)
Discussion started by: Puntino
0 Replies
9. UNIX for Advanced & Expert Users
Hi:-
I am trying to install a device driver for Intel NIC card on TurboLinux, but getting following errors,
cc -O -Wall -o eepro100-diag eepro100-diag.c
eepro100-diag.c:72: unistd.h: No such file or directory
eepro100-diag.c:73: stdio.h: No such file or directory
eepro100-diag.c:74:... (1 Reply)
Discussion started by: s_aamir
1 Replies
10. UNIX for Dummies Questions & Answers
I'm way confused. I loaded RH 7.1 on an old P-75 Compaq. IT has an EtherExpress pro/100 card in it and I have that attached to the optional port on our firewall with a crossover....I can't seem to get the card to negotiate with the firewall...it's currently 100Meg at Half duplex. I'm at a loss... (3 Replies)
Discussion started by: kwalter
3 Replies
clone(7) Miscellaneous Information Manual clone(7)
NAME
clone - opens a major and minor device pair on a STREAMS driver
DESCRIPTION
The driver is a "pass through" device driver that allows other drivers to select unique minor device numbers on each In effect, the driver
passes an open operation through to the other driver. This mechanism allows for multiple instantiations of a driver, each with a different
minor number, through a single device file.
When the driver is opened, it is passed a major and minor device number by the operating system. The major number is the driver's major
number (72), and the minor number is the major number of the driver the user wishes to clone (referred to here as the target driver). The
driver calls the open routine of the target driver with the flag which specifies a clone open. The target driver's open routine allocates
an unused minor number. The target driver must use to make a new device number for the newly created device, and must set to the new
device number returned by The new device number is returned to the open through The open then returns to the user a file descriptor that
points to the new instantiation of the target driver.
The driver is an example of a clonable driver.
Notes
It is not possible to do multiple opens of a device with the same major and minor number using the driver. This is because the driver is
only given the major number of the driver to be cloned, and that driver will then select a minor number which has not been opened.
When called with a pathname which corresponds to the clonable driver, will return different results than when it is called on a file
descriptor returned from of the same clonable driver pathname.
RETURN VALUES
If the driver is given an invalid minor number, or if the driver indicated is not a clonable driver, the fails and is set to [ENXIO].
SEE ALSO
open(2), fstat(2).
clone(7)
