01-19-2010
grep -i net /etc/path_to_inst
10 More Discussions You Might Find Interesting
1. Programming
Hi all,
I think that the title is explicit enough :) I would like in a C program to list the interfaces with a valid IP. Those that can permit to send something over a network.
Thanks ;) (7 Replies)
Discussion started by: brolon
7 Replies
2. Solaris
Hi Community,
I've a problem with IPMP: I have 2 physical interfaces, 1 "physical IP" and 1 VirtualIP.
My question is:
is it possible to have IPMP configuring 2 physical interfaces with the same "physical" IP Address?
for example:
ce0 10.10.10.10
ce5 10.10.10.10
and
VIP... (5 Replies)
Discussion started by: Sunb3
5 Replies
3. Solaris
Hello,
I have a SUN T5240 running Solaris 10 with Logical Domain Manager (v 1.0.3). You can use the "ldm" command to display current resources on the box. Is there away to display all the "physical resources" on the box(i.e.,used and unused). For example, "ldm ls" will tell me what the... (5 Replies)
Discussion started by: stephanpitts
5 Replies
4. AIX
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Discussion started by: jenish_shah
1 Replies
5. Solaris
After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks.
ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface
# ifconfig eg1000g0:2 plumb
ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface
# ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies
6. Solaris
Hi Al,
In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified.
1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Discussion started by: satish51392111
1 Replies
7. UNIX for Dummies Questions & Answers
Just wanted to understand what is the logic being used by Solaris(kernel) to transmit data/traffic on physical interfaces.
I have seen most of the time traffic is being sent to interface ce0 and sometime to ce1.
I have removed ip address from below command for some reason.
netstat -rn
... (3 Replies)
Discussion started by: nadeemahmed
3 Replies
8. Solaris
in AIX, we have lspv command to display details of physical volume like below:
lspv -l hdisk102
hdisk102:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
oradata112lv 1599 1599 320..320..319..320..320 /oracle/oradata11
Can you please tell how to... (2 Replies)
Discussion started by: sendtoshailesh
2 Replies
9. AIX
hi guys
We have a AIX Server with TSM installed.
This server has en0 for administration purposes and we have en1 for backup stuff.
en0 subnet 10.10.10.x
en1 subnet 10.10.20.x
The issue we are having is all of a sudden the LPARs we are backing up lose connectivity to the AIX-TSM Server.... (23 Replies)
Discussion started by: karlochacon
23 Replies
10. Solaris
How to list physical CPU on primary domain? Sparc SPARC T5-4
psrinfo -p
1
in ILOM I see
Processors:
4 / 4 (2 Replies)
Discussion started by: thomasj
2 Replies
LEARN ABOUT MINIX
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)