11-29-2007
thy this command
Quote:
Originally Posted by
biker007fr
Hi,
try using the command uname -a to list information
I'm writing a script to display a lot of information which describe a server (OS distrib, release, Hardware platform, CPU, HD, S/N...).
For Linux side it is ok as you have almost all the information in /proc/cpuinfo, /proc/meminfo... and you can use dmidecode but for HP-UX I didn't find such files and command.
Could you please help me?
Best regards
biker007fr
[QUOTE=biker007fr;302147978]Hi,
try using the command uname -a to list information
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm just getting started with unix and would like to know 1) how to tell how big the harddrive is 2) how to tell if there are multiple harddrive installed on the machine 3) a relitavely easy way to tell what programs are installed on the machine.
I'm using Sun OS 5.6
Thanks (3 Replies)
Discussion started by: ViperD
3 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I am new to Unix and am working on AIX ( rs6000 ). I am looking for the system info of the unix box like
1. Number of CPUs
2. CPU speed
3. RAM size
Your help is much appreciated
Thanks
rao. (6 Replies)
Discussion started by: rao
6 Replies
3. HP-UX
How do I get the system information on a HP UNIX server. details like CPU speed, number of processors etc. (4 Replies)
Discussion started by: Olamide
4 Replies
4. Shell Programming and Scripting
hi
I am new to this forum. hope to get help from u all.
how can i write these by using shell programming?
1. The name of the machine and the date/time at which the report was produced.
2. Licensing information such as the operating system revision level and license restrictions in terms of... (1 Reply)
Discussion started by: nokia1100
1 Replies
5. Shell Programming and Scripting
Hey,
I am after the commands to get the following information for my Unix system:
default visual editor (i dont even know where to start with this one)
default window manager (this one either, no idea)
total quota (just the size, none of the other data. I've narrowed it down to quota -sv)... (1 Reply)
Discussion started by: bonjour
1 Replies
6. AIX
Hi,
How to get the AIX system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
... (4 Replies)
Discussion started by: forumguest
4 Replies
7. Infrastructure Monitoring
Hi,
How to get the Linux system hardware and software basic information using terminal command ?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
OS Build Type:... (6 Replies)
Discussion started by: forumguest
6 Replies
8. Solaris
Hi,
How to get the Solaris system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
... (15 Replies)
Discussion started by: forumguest
15 Replies
9. BSD
Hi,
How to get the FreeBsd system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS... (2 Replies)
Discussion started by: forumguest
2 Replies
10. AIX
Hi all,
I have googled around quite a bit and tried many different commands to get system information about my AIX 5.3 box but none of the commands I've used have given me quite what I'm looking for. I am interested in finding out the model of the motherboard, and amount of available RAM, the... (2 Replies)
Discussion started by: ThePistonDoctor
2 Replies
badsect(8) System Manager's Manual badsect(8)
NAME
badsect - Creates files to contain bad sectors
SYNOPSIS
/usr/sbin/badsect bbdir sector...
DESCRIPTION
The badsect command makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which
provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is preferable to use that
method to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
file systems or in swap areas.
On some disks, adding a sector that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be used to good
effect.
Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory. Make a direc-
tory BAD there. Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers
must be relative to the beginning of the file system, as reported in console error messages.) Change back to the root directory, unmount
the file system, and run fsck(8) on the file system. The bad sectors should show up in two files or in the bad sector files and the free
list. Have fsck remove files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files. This operation will
leave the bad sectors in only the BAD files.
The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block
address is the block containing bad sector and whose name is the bad sector number. When fsck discovers the file, it will ask "HOLD BAD
BLOCK?" An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.
RESTRICTIONS
If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks in the
bad sector files cover all the sectors in a file system fragment.
ERRORS
The badsect command refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued
if the block is already in use.
SEE ALSO
Commands: fsck(8)
badsect(8)