07-13-2010
look for files called "path_to_inst" in /etc.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I ;ve a SUN x4600 running solaris 10. I want to connect to the system remotely form console like we can connect to sparc sc or alom .. (9 Replies)
Discussion started by: fugitive
9 Replies
2. HP-UX
Hi,
Whenever I reboot this server remotely by using the command 'shutdown -r now' or 'reboot'. The server does not return to normal multi-user mode. It boots in single user mode.
To bring back the server, someone is required to connect via console and fire 'init 3'.
Please suggest on what... (1 Reply)
Discussion started by: mystition
1 Replies
3. SCO
Hi,
We are using SCO UNIX 7.1.3 and the server recently started rebooting by itself.
Do anyone know how can i create a dump or crash dump while the server rebooots?
Your quick help on this is really appreciated.
Regards,
Ravikumar R (1 Reply)
Discussion started by: rrb2009
1 Replies
4. Solaris
I need to configure the iLOM for x4600 server. before I can set the IP details and commit, I need to set network state should be enabled. However my firmware is already the latest and I need not upgrade. I am not able to set the /SP/network state to enable. pls assist. i BELIEVE the bug was fixed... (5 Replies)
Discussion started by: incredible
5 Replies
5. AIX
Hello folks,
Could someone tell me why I unable to create pdisks for a RAID Array
# lscfg | grep scsi
+ sisscsia0 U787A.001.DPM0707-P1 PCI-X Dual Channel Ultra320 SCSI Adapter
+ scsi0 U787A.001.DPM0707-P1-T10 PCI-X Dual Channel Ultra320 SCSI Adapter... (12 Replies)
Discussion started by: filosophizer
12 Replies
6. Solaris
Hi ,
Everytime after reboot when user tries to start vnc below error is thrown
$ vncserver :5
Couldn't start Xvnc; trying default font path.
Please set correct fontPath in the vncserver script.
Couldn't start Xvnc process.
_XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies
7. Shell Programming and Scripting
Hi guys
I am troubleshooting a script that informs me when a system has rebooted.
The script is placed in /etc/rc3.d folder under root.
The script is as follows:
. /opt/scripts/function.sh
PATH=/usr/bin
EMAIL_ADD=<email address> ... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies
8. Hardware
Booting and checking BIOS there is no option to enable-disable hyperthreading.
I have 8 Dual-Core AMD Opteron(tm) Processor 8220 and I see 16 cores.
Enable hyperthreading I should have 32 cores.
I have red hat 5.4 installed.
Anyone know how can enable hypethreading ? I have last BIOS/Firmware... (2 Replies)
Discussion started by: laxtnog
2 Replies
9. IP Networking
I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool.
Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies
10. Linux
Respected Members,
We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other... (0 Replies)
Discussion started by: Mudit Bansal
0 Replies
LEARN ABOUT SUSE
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)