11-06-2008
Not sure why the system assigned them in that order, but to solve it read man path_to_inst
Quote:
/etc/path_to_inst records mappings of physical device names
to instance numbers.
The instance number of a device is encoded in its minor
number, and is the way that a device driver determines which
of the possible devices that it may drive is referred to by
a given special file.
In order to keep instance numbers persistent across reboots,
the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by
add_drv(1M) and devfsadm(1M).
Note that it is generally not necessary for the system
administrator to change this file, as the system will main-
tain it.
The system administrator can change the assignment of
instance numbers by editing this file and doing a reconfi-
guration reboot. However, any changes made in this file will
be lost if add_drv(1M) or devfsadm(1M) is run before the
system is rebooted.
So, you can change /etc/path_to_inst, then do: touch /reconfigure; init 6.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
what are the basic steps/command to configure a new nic (2nd) on Solaris 9? :eek:
10x N. (4 Replies)
Discussion started by: nadav
4 Replies
2. SCO
Hi guys,
I am a newbie in SCO UNIX, and I am having problem in installing a NIC for my machine:
My machine: UnixWare scou 5 7.1.4 i386 x86at SCO UNIX_SVR5
My NIC is dLink DFE-538TX, I got the driver from:
http://support.dlink.ca/ProductView.asp?ProductModel=DFE-538TX
The driver... (1 Reply)
Discussion started by: Voldi
1 Replies
3. Shell Programming and Scripting
how can I know the Network Interface Card physical address? (4 Replies)
Discussion started by: nokia1100
4 Replies
4. HP-UX
how can I determine which NIC card is virtual NIC Card
which condition can make a decision
Does HP UX have Virtual Network Adapter Concept
if ,it has
where I can Find if I Install Virutal Network Adapter
or which command that i can get it
or which software can generate
thanks (2 Replies)
Discussion started by: alert0919
2 Replies
5. 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
6. IP Networking
I am new in squid proxy.
My question is how to (and if it's necessary) to set one NIC for inbound traffic (http requests) and one NIC for outbound traffic (http answers)?
Thank you in advance! (4 Replies)
Discussion started by: aixlover
4 Replies
7. Red Hat
Dear All
I want tune my NIC's rps, rfs and xps value.
In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1).
Here is the question? Which device should I modify ?
eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0)
Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies
8. HP-UX
Hello,
I need to configure a second NIC on my HP UX, B.11.31 U ia64 ...if it is helpful.
I see a good thread to start on:
Configuring NIC
https://www.unix.com/hp-ux/15589-configuring-nic.html
I have started reading the man pages listed. Without having to know every last detail is there... (3 Replies)
Discussion started by: KmJohnson
3 Replies
9. Linux
Hello Admins,
My ask is how can I add two different subnet IPs to same box with two different gateways?
The issue is I can connect to the box when I am on ethernet LAN, but I am not able to connect to the same IP when I am on wifi. The server is RHEL 7 VM on vmware.
How can I get connected... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
LEARN ABOUT FREEBSD
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device.
This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1: Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst
SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future
release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.10 2 Nov 1995 path_to_inst(4)