cannot open /etc/path_to_inst file Post: 48391

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file activity (open/closed) file descriptor info using KORN shell scripting

I am trying to find a way to check the current status of a file. Such as some cron job processes are dependent on the completion of others. if a file is currently being accessed / modified or simply open state I will wait until it is done being processed before attempting the next process on that...

2. Filesystems, Disks and Memory

/etc/path_to_inst

Hello Friends I was using V490 server with StoreEdge 3500 on Solaris 5.8 platform. It got crashed when the optical link between 3500 and V490 got failed. After a long effort it is now getting messege like below, Rebooting with command: boot Boot device:...

3. UNIX for Dummies Questions & Answers

path_to_inst output for usb storage device

Hello, I have a sun blade 100 with solaris 10 and am perplexed by the instances of devices that I see when I attach a usb flash stick to one of the ports in the back of the chassis. Here is what I see for USB storage in /etc/path_to_inst: "/pci@1f,0/usb@c,3/storage@3" 0 "scsa2usb"...

4. Solaris

path_to_inst file question

When path_to_inst file get created? Can we manually edit it? Thanks

5. Programming

libRmath.so: cannot open shared object file: No such file or directory

% locate Rmath /m/backup/backup/lib/R/include/Rmath.h /usr/lib/R/include/Rmath.h % gcc -g -o stand stand.c -I/usr/lib/R/include/ -lRmath -lm % ./stand ./stand: error while loading shared libraries: libRmath.so: cannot open shared object file: No such file or directory What's the trouble...

6. Programming

Some how the open(file,flag, acc) returns 0 and write to the screen, instead of the file ???

I am out of idea what to do to resolve the problem! I need to use the open(file, for.., access) function to write a file. Never have the situation like that: it is return 0 - zero. As a result all write(..) going to the screen! What the problem it could be? I do not even know...

7. Red Hat

cannot set user id: Resource temporarily unavailable (not open file/open process related)

First post, sorry to be a bother but this one has been dogging me. I have a process user (java application server) that trips a resource limit every couple weeks and need help finding what limit we're hitting. First, this is what's running: This is the error when jobs are run or the...

8. Solaris

Before I delete any file in Unix, How can I check no open file handle is pointing to that file?

I know how to check if any file has a unix process using a file by looking at 'lsof <fullpath/filename>' command. I think using lsof is very expensive. Also to make it accurate we need to inlcude fullpath of the file. Is there another command that can tell if a file has a truely active...

9. Shell Programming and Scripting

Newbie.. Find if a file exists and open, if not create the desired file..

Hey all, I'm brand new to script writing, I'm wanting to make a script that will ask for a file and then retrieve that file if it exists, and if it doesn't exist, create the file with the desired name, and I'm completely stuck.. so far.. #! bin/bash echo "Enter desired file" read "$file" if ...

10. Solaris

Incorrect fabric WWN and path_to_inst Solaris 9

Hi, Over a period of time we gradually migrated all LUN's from our HP EVA array over to our EMC array. From the server it would appear some files require a tidy up and was wondering what the impact it would have if changes were to be made to the fabric_WWN_map and path_to_inst files and if...

LEARN ABOUT BSD

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)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file activity (open/closed) file descriptor info using KORN shell scripting

Discussion started by: Gary Dunn

2. Filesystems, Disks and Memory

/etc/path_to_inst

Discussion started by: ailnilanjan

3. UNIX for Dummies Questions & Answers

path_to_inst output for usb storage device

Discussion started by: montana77

4. Solaris

path_to_inst file question

Discussion started by: mokkan