08-19-2008
the card is configured with the rsc-admin tool. if it is installed you should find it at /usr/platform/sun4u/... (don't know the whole path...).
if it is not installed, download the tool at the sun website. it's free to downlod...
https://cds.sun.com/is-bin/INTERSHOP...-F@CDS-CDS_SMI
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What command do I use to determine how many/what kind/how big the hard drives on a box are? (2 Replies)
Discussion started by: abolshoun
2 Replies
2. Solaris
I wana know my box hardware specification ( Like RAM , processor speed .... Etc ) and used version of Solaris i mean (SPARC, 32-bit) or (x86, 32-bit) or(SPARC, 64-bit) or what ??
very Urgent please (5 Replies)
Discussion started by: KSA
5 Replies
3. Solaris
Hi,
anybody know how to check the system specification for the unix by using the command like the memory size, cpu's speed and etc.
Thanks. (3 Replies)
Discussion started by: efang
3 Replies
4. Solaris
I setup RSC on a 280R using the network connection. Unfortunately, I am unable to telnet to this card and I was wondering if there was a way to test the link from the rsc card. Here is my rsc configuration:
machine1:/tmp/rsc# /usr/platform/SUNW,Sun-Fire-280R/rsc/rscadm show
page_enabled="false"... (0 Replies)
Discussion started by: dangral
0 Replies
5. Shell Programming and Scripting
Hello Friends,
I want to use range in for loop. For that i used (..) operator but it is not working.
Ex:
for i in 1..24
do
echo $i
done
Instead of printing 1 to 24 nos, it gives o/p as: 1..24
Please help me
Thanks in advance. (2 Replies)
Discussion started by: Niyati
2 Replies
6. UNIX Desktop Questions & Answers
Does Red Hat Fedora support Nvidia card 8800GTX and 260 card?
Does any Linux OS support Nvidia card? (1 Reply)
Discussion started by: sito
1 Replies
7. Solaris
Hi all,
Can anyone help me to get the server specifications like the following?
eg.
SUN Fire XXX
X UltraSPARC X MHZ
X MB Memory
X GB od hard disk
X On board PCI IO card
X PCI HNI card
Thanks. (4 Replies)
Discussion started by: beginningDBA
4 Replies
8. Solaris
All,
I have a unique situation concerning RSC cards and would like to see if anyone has a solution. Here is the situation:
We are migrating older versions of Solaris using ufsdump images to like older hardware. We basically installed a temporary Solaris O/S then copied the dumps over and... (5 Replies)
Discussion started by: sljack
5 Replies
9. AIX
I am planning to implement sudo for users.
Under , it looks I have to put the users who need to have sudo access:
What are the recommended for users? I don't think I need to give the ALL privilege (i.e ) to AIX users.
I'd like to know the commonly used privilege specification for sudo... (9 Replies)
Discussion started by: Daniel Gate
9 Replies
10. Shell Programming and Scripting
Hi I am working on a program that reads a file with multiple columns and was curious how to specify the columns to be manipulated in the command line.
For example the file may look something like:
Column1 Column2 Column3 Column4 Column5 Column6
AC 82542 3525 ... (1 Reply)
Discussion started by: drossy
1 Replies
LEARN ABOUT FREEBSD
device
DEVICE(9) BSD Kernel Developer's Manual DEVICE(9)
NAME
device -- an abstract representation of a device
SYNOPSIS
typedef struct device *device_t;
DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into,
disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during
autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and
other devices will be added as children of their relevant bus.
The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have
children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and
device_delete_child(9)).
A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a
devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see
device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe-
cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)).
Devices can be in one of several states:
DS_NOTPRESENT the device has not been probed for existence or the probe failed
DS_ALIVE the device probe succeeded but not yet attached
DS_ATTACHED the device has been successfully attached
DS_BUSY the device is currently open
The current state of the device can be determined by calling device_get_state(9).
SEE ALSO
devclass(9), driver(9)
AUTHORS
This manual page was written by Doug Rabson.
BSD
June 16, 1998 BSD