I have a product that is built using installtool software(using makekit utility). I am able to build the product successfully but while installing the product on a machine i am getting errrors as shown below,
Last edited by DukeNuke2; 08-20-2010 at 12:37 PM..
hello solaris friends,
I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url:
http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png
I'm able to install it all the way through but I get no... (2 Replies)
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (2 Replies)
hi
i have written a program to display files in a directory
but it doesnt compile on the sun/solaris system....
im using gcc(inbuilt compiler)
im generally used to working on a windows environment so maybe im overlookiing something
ive added comments to help readability of the program
i also... (2 Replies)
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Hi to all I have a sun Ultra 10 workstation with the following configuration
SUN ULTRA-10 Workstation
440 Mhz CPU
1024 MB RAM
40 GB HDD Seagate (Connected as Primary master)
FDD
Samsung DVD Writer (connected as Secondary master)
CABINET
SMPS
Sun keyboard and mouse
the command -... (3 Replies)
hi guys,
actually am experiencing an big issue.. while compiling MIBs ''RFC 1213 and Host-Resources-MIB'' on my solaris server version 9 ... i got object errors!! :(. i used a software that can monitor network devices, but unfortunately it can not polled information from my solaris 9 because... (1 Reply)
Hello I am installing Nagios XI on red hat 7 and I am getting this error message
./fullinstall
========================
Nagios XI Full Installer
========================
This script will do a complete install of Nagios XI by executing all necessary
sub-scripts.
IMPORTANT: This script... (0 Replies)
Discussion started by: DOkuwa
0 Replies
LEARN ABOUT LINUX
fiz
FIZ(1) General Commands Manual FIZ(1)NAME
fiz - analyze damaged zoo archive for data recovery
SYNOPSIS
fiz archive[.zoo]
DESCRIPTION
Fiz is used to analyze damaged zoo archives and locate directory entries and file data in them. The current version of fiz is 2.0 and it
is meant to be used in conjunction with zoo version 2.0. Fiz makes no assumptions about archive structure. Instead, it simply searches
the entire subject archive for tag values that mark the locations of directory entries and file data. In a zoo archive, a directory entry
contains information about a stored file such as its name, whether compressed or not, and its timestamp. The file data are the actual data
for the archived file, and may be either the original data, or the result of compressing the file.
For each directory entry found, fiz prints where in the archive it is located, the directory path and filename(s) found in it, whether the
directory entry appears to be corrupted (indicated by [*CRC Error*]), and the value of the pointer to the file data that is found in the
directory entry. For each block of file data found in the archive, fiz prints where in the archive the block begins. In the case of an
undamaged archive, the pointer to file data found in a directory entry will correspond to where fiz actually locates the data. Here is
some sample output from fiz:
****************
2526: DIR [changes] ==> 95
2587: DATA
****************
3909: DIR [copyrite] ==> 1478
3970: DATA
4769: DATA
****************
In such output, DIR indicates where fiz found a directory entry in the archive, and DATA indicates where fiz found file data in the ar-
chive. Filenames located by fiz are enclosed in square brackets, and the notation "==> 95" indicates that the directory entry found by
fiz at position 2526 has a file data pointer to position 95. In actuality, fiz found file data at positions 2587, 3970, and 4769. Since
fiz found only two directory entries, and each directory entry corresponds to one file, one of the file data positions is an artifact.
Once the locations of directory entries and file data are found, the @ modifier to zoo's archive list and extract commands can be used and
the archive contents selectively listed or extracted, skipping the damaged portion. This is further described in the documentation for
zoo(1).
In the above case, commands to try giving to zoo might be x@2526,2587 (extract beginning at position 2526, and get file data from position
2587), x@3090,3970 (extract at 3090, get data from 3970) and x@3909,4769 (extract at 3909, get data from 4769). Once a correctly-matched
directory entry/file data pair is found, zoo will in most cases synchronize with and correctly extract all files subsequently found in the
archive. Trial and error should allow all undamaged files to be extracted. Also note that self-extracting archives created using sez (the
Self-Extracting Zoo utility for MS-DOS), which are normally executed on an MS-DOS system for extraction, can be extracted on non-MSDOS sys-
tems in a similar way.
SEE ALSO zoo(1)BUGS
Random byte patterns can occasionally be incorrectly recognized as tag values. This occurs very rarely, however, and trial and error will
usually permit all undamaged data to be extracted.
DIAGNOSTICS
Fiz always exits with a status code of 0.
FUTURE DIRECTIONS
Automation of data recovery from a damaged archive is potentially achievable. However, since damaged archives occur only rarely, fiz as it
currently stands is unlikely to change much in the near future.
AUTHOR
Rahul Dhesi
Jan 31, 1988 FIZ(1)