Sponsored Content
Operating Systems Solaris Solaris 8 booting from wrong device Post 302206963 by taran on Thursday 19th of June 2008 12:28:24 AM
Old 06-19-2008
y can not boot from cdrom and then edit the vfstab?

if y then boot from cdrom , save the data and reinstall solaris.
 

4 More Discussions You Might Find Interesting

1. Solaris

What's wrong with my system? Solaris not booting.

Booting the 32-bit OS ... SunOS Release 5.7 Version Generic_106541-31 Copyright (c) 1983-2002, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: wz-ultra1 metainit: wz-ultra1: there are no existing databases The system is coming up. Please wait. checking ufs... (2 Replies)
Discussion started by: CollenM
2 Replies

2. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

3. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

4. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
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
All times are GMT -4. The time now is 12:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy