m i s c q u e s t i o n s . . .
What are the list of the services used by SVM
Changing IP (IPv4) address in Solaris 10
cange all the standard files ( /etc/hosts, /etc/hostname.<yourinterface>, /etc/resolv.conf, /etc/netmasks, /etc/nodename, /etc/defaultrouter) plus /etc/inet/ipnodes
How to tell what ethernet settings you have?
1. THE NDD WAY: "ndd /dev/hme \?" will give a list of variables, and ndd /dev/hme variable-name will return the value. if link_speed = 1, you are running 100Mb/s, if link_speed=0, you are running 10mb/s. Likewise, link_mode=1 means full duplex, link_mode=0 means half duplex.
2. THE DMESG WAY: dmesg | grep hme will give Human readable output as to link speed and mode.
3. THE SNEAKY WAY: netstat -k hme0
How to tell what version of Sun AnswerBook is runing?
more information: http://www.sun.com/software/ab2
What motherboard revision do I need in order to run 400 MHz CPU's on Sun Ultra 2?
501-3132 rev13 or higher
What are the names of the packages of Sun's Trunking software?
SUNWtrkm Sun Trunking Man Pages (sparc) 1.2.1,REV=5.8.2000.02.11
SUNWtrku Sun Trunking Utility (sparc) 1.2.1,REV=5.8.2000.02.11
HP SureStore DAT - Verifing Installation in UNIX (R)
In this document:
As part of the installation process, you will have installed the appropriate device driver for your UNIX (R) system, and created device files to communicate with the tape drive. This section describes how you can verify that the installation has been performed correctly. In outline, the procedure is as follows:
- Write test data to a tape.
- Read the test data from the tape.
- Compare the data read from the tape with the original data on disk.
Verifying the Installation
- Test the SCSI connection to the tape drive by doing a rewind operation:
- Remove tape cartridge, if there is already one in the drive.
- Insert a tape cartridge.
- Rewind the tape using the command line:
% mt -t <archive name> rewind
- or for SCO UNIX:
% tape -a /dev/rStpX rewind
If you do not see the Tape light flash as the tape rewinds, the hardware installation may be faulty. Check the troubleshooting section for help in identifying the problem.
- Write a sample file to tape, using 'tar':
% cd /
% tar cvf <archive name> <file>
The options to tar have the following meanings:
c Create a new archive on the device. v Operate in verbose mode. f Specify the archive name explicitly.
The arguments follow the cvf options in the command line. Their values depend on the operating system; suggested values are given in System-Specific Arguments below, click here to go to that section now.
The arguments are as follows:
<archive name> The name of the archive to be created.
<file> The name of the file to put into the archive, prefixed with './'.
NOTE: Make sure you prefix the file name with a '.' when you back it up to tape. If you do not, the restore operation in step 2 will overwrite the original copy on disk.
- Read the file back from tape:
% cd /tmp
% tar xvf <archive name>
The 'x' option to tar here means "extract from the archive".
Use the same value for the <archive name> argument as in step 2.
- Compare the original with this retrieved file:
% cmp <original file> /tmp/<retrieved file>
This step compares the retrieved file and the original file byte by byte. If they are the same, there
should be no output, and this verifies that the installation is correct.
The arguments are as follows:
<original file> The name of the original file, prefixed with '/'.
<retrieved file> The name of the file retrieved from the archive.
Suppose you are verifying the installation of an HP DDS-format tape drive on an HP-UX 10.X system. The procedure would be as follows. Click here to see System-Specific Arguments below for the choice of <archive name> and <file> arguments:
- Change directory to root:
% cd /
- Back up /stand/vmunix to tape:
% tar cvf /dev/rmt/0m ./stand/vmunix
Note the prefix of '.' to the filename.
- Change to the temporary directory:
% cd /tmp
- Extract the file from the tape:
% tar xvf /dev/rmt/0m
- Compare the original with the restored version:
% cmp /stand/vmunix /tmp/stand/vmunix
Note that the original filename is not prefixed with '.'.
The following table lists suggested values for the arguments <archive name> and <file> in the verification procedure described above:
System <file> Desc. <archive name> Notes DEC vmunix OSF
/dev/rmt/Ym Y is the instance of the drive. HP-UX 9.x
hp-ux HP-UX kernel /dev/rmtcxxxdIl xxx is the SCSI card.
I is the device number.
l is the density.
(See man 7 mt for further details.)
HP-UX 10.x stand/
HP-UX kernel /dev/rmt/Ym Y is the instance of the drive. IBM AIX unix AIX
/dev/rmt/X.1 X is the device ID reported
back as available when you ran
'smit -C tape'
to create the device files.
/dev/rmt/tpsCdX X is the SCSI ID of the drive.
C is the SCSI card.
Sun Solaris 1
bin/csh C shell /dev/rst0 If you installed with SCSI ID 4. /dev/rst1 If you installed with SCSI ID 5. Sun Solaris 2
bin/csh C shell Determine the archive name as described below*. SCO unix SCO
/dev/rStpY Use the device file created during
the running of 'mkdev tape',where Y is the instance of the tape drive.
*For Sun Solaris 2, determine the archive name by typing:
% ls -l /dev/rmt/*m | grep "st@X"
where X is the SCSI ID.
Identify the line for the tape drive. For example, if the drive was at SCSI ID 2, look for the line containing 'st@2,0'. This might be as follows (but on a single line):
lrwxrwxrwx 1 root root 63 Mar 1 00:00 /dev/rmt/0m ../../devices/sbus@1f,0/espdma@e,8400000/esp@e,8800000/st@2,0:m
Here you could use /dev/rmt/0m (shown in bold above) as the archive name.
Last changes: ,
:P 2002-2005 filibeto.org, site statistics, legal stuff