03-26-2010
No sorry for the confusion. I am logged in to the OBP to run the upgrade just by running boot cdrom from the ok> prompt.
6 More Discussions You Might Find Interesting
1. AIX
Hello,
We are using AIX 5.2 ML 7.
One of the process in its log file said the following and stopped running.
Caught signal=5, exiting.
What would cause the signal 5 to be generated on an AIX box.
Please advise.
Thx
Jerardfjay (2 Replies)
Discussion started by: jerardfjay
2 Replies
2. Solaris
Rebuilding a server (T2000) from a flash archive I created on another server. Using a Solaris 10/08 DVD to boot from the was going to point it tot he flash archive and pull it over NFS. I've done this many times with success until now.
It initially boots off the DVD, you input the... (5 Replies)
Discussion started by: Probos
5 Replies
3. Solaris
Hello all,
I have a problem when installing Solaris 10 on Enterprise 450.
I booted from dvd, then the installation was started. The error appeared after determining the installation method, F2-Standard, F?-Flash......
The error was Exiting signal 6.
Please, need help. Thank you (4 Replies)
Discussion started by: Hardono
4 Replies
4. Solaris
I get an error after the initializing screen. I am using a DVD/ROM to boot up the installation on a Dell Inspiron 1520. Segmentation fault - core dumped. I have tried to restart multiple times. Please help (1 Reply)
Discussion started by: Jimasaurus
1 Replies
5. Solaris
I created a new Virtual machine and was trying to install Solaris but keep getting this error.:confused:
EXITING (caught signal 11)
Type "install-solaris to restart"
Can't find anything on Google.
This is the iso image I am using "sol-10-u11-ga-x86-dvd"
Followed all the instructions on... (5 Replies)
Discussion started by: newborndba
5 Replies
6. Shell Programming and Scripting
Is it possible to continue after signal is caught and control goes to function specified in the trap statement? (3 Replies)
Discussion started by: Soham
3 Replies
LEARN ABOUT FREEBSD
devfs.conf
DEVFS.CONF(5) BSD File Formats Manual DEVFS.CONF(5)
NAME
devfs.conf -- boot-time devfs configuration information
DESCRIPTION
The devfs.conf file provides an easy way to set ownership and permissions, or create links for devices available at boot.
It does not work for devices plugged in and out after the system is up and running, e.g. USB devices. See devfs.rules(5) for setting owner-
ship and permissions for all device nodes, and devd.conf(5) for actions to be taken when devices are attached or detached.
Lines starting with a hash sign ('#') and empty lines are ignored. The lines that specify devfs.conf rules consist of three parameters sepa-
rated by whitespace:
action The action to take for the device. The action names are only significant to the first unique character.
devname
The name of the device created by devfs(5).
arg The argument of the action.
The actions currently supported are:
link This action creates a symbolic link named arg that points to devname, the name of the device created by devfs(5).
own This action changes the ownership of devname. The arg parameter must be in the form of an owner:group pair, in the same format used
by chown(8).
perm This action changes the permissions of devname. The arg parameter must be a mode as explained in chmod(1).
FILES
/etc/devfs.conf
/usr/share/examples/etc/devfs.conf
EXAMPLES
To create a /dev/cdrom link that points to the first SCSI(4) CD-ROM, the following may be added to devfs.conf:
link cd0 cdrom
Similarly, to link /dev/cdrom to the first ATAPI CD-ROM device, the following action may be used:
link acd0 cdrom
To set the owner of a device, the own action may be specified:
own cd0 root:cdrom
To set the permissions of a device, a perm action should be used:
perm cd0 0660
SEE ALSO
chmod(1), devd.conf(5), devfs(5), devfs.rules(5), chown(8)
AUTHORS
This manual page was written by Roland Smith <rsmith@xs4all.nl>.
BSD
May 17, 2005 BSD