03-28-2011
Why was "-ar" added to the boot options? Where you having problems with /etc/path_to_inst?
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
We have a SunFire V880, hooked up with 2 T3 arrays. When ever we issue a reboot command on the system, it hangs at the same place right where it says
syncing file systems done.
To bring it back we shutdown power and it comes clean.
By the way init 6 command works fine.
Has anyone come... (3 Replies)
Discussion started by: smohd
3 Replies
2. Solaris
Hi all,
I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console .
Both the IP adresses of the server and the console are in a private network (address 10.67.xxx).
For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Discussion started by: aribault
2 Replies
3. Solaris
Greetings Forumers!
I tried installing Solaris Cluster 3.3 today. I should say I tried configuring the Cluster today. The software is already installed on two systems. I am trying to configure a shared filesystem between two 6320 Blades. I selected the "Custom" install because the "Typical"... (2 Replies)
Discussion started by: bluescreen
2 Replies
4. Solaris
Solaris 10 (Sun V210) System hangs every couple of months. Have to go into ALOM to reset. I did a consolehistory report and seen this in it.
Failed to exec inetd_start method of instance svc:/network/bootps/udp:default: I/O error
WARNING: /pci@1c,600000/scsi@2 (glm0):
Resetting... (3 Replies)
Discussion started by: Joeentech
3 Replies
5. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
6. Solaris
Power server up runs through diagnostics.
Goes to the boot section and then the bit where the cursor is spinning and thats it. Hangs completely.
Any ideas? (10 Replies)
Discussion started by: psychocandy
10 Replies
7. Solaris
Anyone ever see an issue where ufsdump 'hangs' after the IV Pass?
Normally, it will update with an estimate of how long it will take to complete...and update the info every 20 minutes.
I'm running the following command:
root# ufsdump 0f - /fsmount | ( cd /zfs/newfsmount ) ; ufsrestore rf - )... (2 Replies)
Discussion started by: RTM
2 Replies
8. Solaris
dear members,
i am a newbie to solaris 11.3, and deeply impressed. On my test pc (Lenovo M90), however, using the internet hangs the system from time to time;
initializing the connecting (WLAN) during installation (via the live cd)
took two attempts as well.
Maybe someone has a solution... (7 Replies)
Discussion started by: RichardLichten
7 Replies
LEARN ABOUT DEBIAN
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)