The  Linux sg3_utils package

  1. The  Linux sg3_utils package
    1. Introduction
    2. Contents of sg3_utils
    3. Exit status
    4. Changing mode page settings
    5. Examples
    6. Notes
    7. Download

Introduction

The sg3_utils package contains utilities that send SCSI commands to devices. As well as devices on transports traditionally associated with SCSI (e.g. Fibre Channel (FCP), Serial Attached SCSI (SAS) and the SCSI Parallel Interface(SPI)) many other devices use SCSI command sets. ATAPI cd/dvd drives and SATA disks that connect via a translation layer or a bridge device are examples of devices that use SCSI command sets.

SCSI command sets are divided into a common set and several device class specific sets. The common set of commands is referred to as the SCSI Primary Commands (SPC) with SPC-3 being the most recent standard. The mandatory SCSI INQUIRY command is defined in SPC-3. The SCSI Block Commands (SBC) cover direct access devices such as disks. The MultiMedia Commands (MMC) cover CD and DVD drives and the media within them. SCSI command sets and transport definitions can be found at the www.t10.org site with this page giving a good diagrammatic overview: www.t10.org/scsi-3.htm .

The sg3_utils package targets the linux kernel 2.4 and 2.6 series and is still being enhanced. An earlier package called sg_utils targeted the linux kernel 2.2 series with some support for the 2.0 series. See an earlier version of this web page for further information about sg_utils.  This document describes version 1.23 of sg3_utils .  A subset of these utilities have been ported to the FreeBSD, Tru64 and the Windows operating systems.

In the linux kernel 2.4 series most of these utilities must be used with a SCSI generic (sg) driver device name (e.g. /dev/sg0). In the lk 2.6 series almost all of these utilities can be used with the primary device names as well (e.g. /dev/sda, /dev/scd0, /dev/st0 and /dev/hdd (if it is an ATAPI device)). The SCSI generic (sg) interface still represents a cleaner interface than the primary device names since the drivers behind primary device names have their own policies, may interfere with error processing and, in some cases, run their own state machines.

A list of SCSI and storage utility programs that was at the bottom of this page has been moved to the tools page.

Contents of sg3_utils

This package contains over 30 utilities, their "man" pages, build files and general documentation (e.g. several README files). The utilities have a command line interface which in general has this form:

UTILITY_NAME [OPTIONS] DEVICE

No more than one DEVICE name can be given (and in a few cases, no DEVICE name is required). Here is a listing in alphabetical order of the utilities in the sg3_utils package:

Table 1 Utilities in sg3_utils
Utility
Main SCSI commands
directory
CLI
Ported
Notes
hxascdmp
-
utils
adhoc
fb
converts stdin (assumed binary) to ASCII hex and ASCII, sending its output to stdout (like the Unix od command)
rescan-scsi-bus.sh
-
archive
adhoc

copy of Kurt Garloff's useful script
scsi_inquiry
INQUIRY
examples
adhoc

uses deprecated SCSI_IOCTL_SEND_COMMAND ioctl
sdparm
MODE SENSE/SELECT, INQUIRY
-->
getopt
fb,t64,w
was in sg3_utils for a short time; now in own package, see sdparm . sdparm manipulates mode pages, reads VPD pages and sends simple commands.
sg_chk_asc
-
utils
getopt
fb
check asc/ascq codes from www.t10.org page against sg3_utils table
sginfo
MODE SENSE/SELECT, READ DEFECT

adhoc

symbolic decoding (optional changing) of mode pages. Can also output (disk) defect lists. In lk 2.4 can be given primary device nodes (e.g. /dev/sda) as well as sg device nodes. Port of older scsiinfo utility.
sgm_dd
READ, WRITE

dd

sg_dd variant that uses memory mapped IO (only on linux sg devices)
sgp_dd
READ, WRITE

dd

sg_dd variant that uses POSIX threads
sg_dd
READ, WRITE

dd

Unix dd command variant, uses SG_IO ioctl to send SCSI commands to copy data. See the sg_dd page.
sg_emc_trespass
MODE SELECT

adhoc

utility specialized for EMC Clariion series
sg_format
FORMAT

getopt
fb,t64,w
format or resize a SCSI disk
sg_get_config
GET CONFIGURATION

getopt
fb,t64,w fetch features and profiles of a cd/dvd drive and/or its current media
sg_ident
REPORT/SET IDENTIFYING INFORMATION

getopt
fb,t64,w default is to report (fetch) the device identifier. With the '--set' option a new identifier is sent to the device.
sg_inq
INQUIRY

getopt+
fb,t64,w fetch standard response, VPD pages or version descriptors. Also can perform IDENTIFY (PACKET) DEVICE ATA command. VPD page decoding also performed by sg_vpd and sdparm.
sg_logs
LOG SENSE

getopt+
fb,t64,w fetch log sense pages, decode standard and some vendor pages
sg_luns
REPORT LUNS

getopt
fb,t64,w fetch luns reported by a device (lun 0 or "well known lu")
sg_map
INQUIRY

adhoc

shows mapping between sg devices and primary device node (if any). In lk 2.6 see lsscsi .
sg_map26


getopt

maps between single linux sg device and primary device node (and vice versa). Also does mapping in to, and out of, sysfs. For the linux 2.6 series.
sg_modes
MODE SENSE

getopt+
fb,t64,w fetch mode pages (mainly in hex)
sg_opcodes
REPORT SUPPORTED OPERATION CODES

getopt+
fb,t64,w
fetch supported SCSI commands or supported task management functions
sg_persist
PERSISTENT RESERVE IN/OUT

getopt
fb,t64,w control persistent reservations and report reservation status
sg_prevent
PREVENT ALLOW MEDIUM REMOVAL

getopt
fb,t64,w control media removal, mainly for those SCSI devices which have removable media (e.g. CD/DVD and tape drives)
sg_rbuf
READ BUFFER

getopt+

read from SCSI device cache. Typically for testing the SCSI transport (for throughput or errors)
sg_rdac
MODE SENSE/SELECT

adhoc
fb,t64,w display or modify RDAC redundant controller mode page
sg_read
READ

dd

read continually from same offset. Syntax similar to sg_dd (without write side). Can test SCSI device cache and transport performance.
sg_readcap
READ CAPACITY

getopt+
fb,t64,w fetch the number of blocks and the individual block size for disks and CD/DVD media
sg_read_buffer
READ BUFFER

getopt
fb,t64,w
read descriptors or data
sg_read_long
READ LONG

getopt
fb,t64,w read data from given lba which includes the block and ECC data.
sg_reassign
REASSIGN BLOCKS

getopt
fb,t64,w reassign a lba from one sector on a disk (typically damaged) to a new (spare) sector. User data copied if it is recoverable.
sg_requests
REQUEST SENSE

getopt
fb,t64,w fetch sense data from the given device. Modern uses include getting a progress indication (e.g. during a format) or finding the power condition state.
sg_reset
-

adhoc

Issue a driver, (SCSI) bus or device (target or lun?) reset.
sg_rmsn
READ MEDIA SERIAL NUMBER

getopt
fb,t64,w Relatively new command added to SPC-3. Format of response is vendor specific so this utility outputs it in hex (default) or binary.
sg_rtpg
REPORT TARGET PORT GROUPS

getopt
fb,t64,w Specialized for multi-ported SCSI devices where one port (or a group of them) is preferred for IO over another (or others).
sg_sat_identify
ATA PASS-THROUGH
getopt
fb,t64,w
Sends IDENTIFY DEVICE or IDENTIFY PACKET DEVICE ATA commands via the SAT ATA PASS-THROUGH (16 or 12) SCSI command.
sg__sat_identify
ATA PASS-THROUGH
examples
adhoc

Simpler version of sg_sat_identify that uses the linux SG_IO ioctl directly. See also sg_sat_chk_power, sg_sat_set_features and sg_sat_smart_rd_data in the examples subdirectory.
sg_scan
[INQUIRY]

adhoc
[win:
getopt]
w
maps each sg device name to the corresponding numeric <host, channel, target, lun> tuple. In lk 2.6 series the "lsscsi -g" command is similar. In Windows shows one device per line, with the device's various names and INQUIRY response string on that line.
sg_senddiag
SEND DIAGNOSTIC

getopt+
fb,t64,w Issues either a default self test or a short/extended foreground/background self test. With no arguments it uses RECEIVE DIAGNOSTIC RESULTS to list all supported diagnostic pages.
sg_ses
SEND/RECEIVE DIAGNOSTIC

getopt
fb,t64,w Fetches status diagnostic pages from, and sends some control pages to, a SCSI Enclosure Services (SES) device.
sg_simple1,2,3,4,5
INQUIRY, TEST UNIT READY
examples
adhoc

Simple code examples of using the scsi generic (sg) driver interface
sg_simple16
READ
examples
adhoc

Simple code example of sending a 16 byte cdb SCSI READ command
sg_start
START STOP UNIT

getopt+
fb,t64,w Controls the power condition state of a SCSI device. Primary use is to spin up and down SCSI disks. Can also load and eject removable media.
sg_sync
SYNCHRONIZE CACHE

getopt
fb,t64,w Causes disk caches to be flushed to media
sg_test_rwbuf
READ/WRITE BUFFER

getopt

Random pattern written to SCSI device buffer then read back and checked. Used in testing for data corruption.
sg_turs
TEST UNIT READY

getopt+
fb,t64,w Issue one or more Test Unit Ready commands. Can be used to time SCSI command overhead.
sg_verify VERIFY
getopt
fb,t64,w reads indicated blocks on a SCSI disks, stops on the first error found. Does not yield any data. Useful for media scans.
sg_vpd
INQUIRY

getopt
fb,t64,w
Decodes standard and some vendor Vital Product Data (VPD) pages.
sg_write_buffer
WRITE BUFFER

getopt
fb,t64,w
write data; can be used to download firmware
sg_write_long
WRITE LONG

getopt
fb,t64,w writes to a lba, data which includes the block and ECC data. Suitable data typically fetched by prior sg_read_long utility.
sg_wr_mode
MODE SELECT

getopt
fb,t64,w writes mode pages supplied in ASCII hex (e.g. from "sg_modes -r") to the  SCSI device. See sdparm for another method of setting mode page parameters.

More SCSI commands may be issued than shown in the Main SCSI commands column. For example many utilities issue a SCSI INQUIRY command to find out the peripheral device type of the given device. Some SCSI commands listed above are only relevant to a specific device type (e.g. FORMAT UNIT) and should not be sent to a device belonging to other peripheral device types (and in some cases these utilities will block inappropriate attempts). See the COVERAGE file in the main directory of the tarball for a more exhaustive list of SCSI (and ATA) commands issued by the sg3_utils utilities.

If the directory column is empty in the above table then that utility is in the main directory and more documentation can be found in its "man" page. Some utilities in the subdirectories have "man" pages.

The CLI column indicates what kind of command line interface the utility has. Recent utilities have a cli based on the getopt_long() function which offers both long option names (e.g. "--verbose") and a short form (e.g. '-v'), both forms can take an argument. Experience has led to consistent use of various options such as "--help", "--verbose" and "--version" across these utilities. Utilities with this type of cli are marked with "getopt". The original utilities had an "ad hoc" type cli that unfortunately lacked consistency and had a mix of long and short forms (with the long form sometime prefixed with "-" and on other occasions with "--". Utilities with this type of cli are marked with "adhoc". There is also a group of utilities that are related to the Unix dd command and share its quirky cli. Finally a group of well used utilities with ad hoc command line interfaces had a getop_long() based interface added in sg3_utils version 1.23 . These utilities include sg_inq, sg_logs and sg_modes. The default cli for this group is "getopt" but by using "--old" or "-O" as the first option the older ad hoc options can be used. This group will default to the older ad hoc interface if the environment variable SG3_UTILS_OLD_OPTS is defined. Utilities with this type of cli are marked with "getopt+".

If the Ported column is empty then the utility is only found in Linux. Support for other ports is indicated by "fb" for FreeBSD, "t64" for Tru64 (OSF) and "w" for Windows. See the README.freebsd, README.tru64 and README.win32 files for more information.

This paragraph contains Linux specific information. All utilities that issue SCSI commands and that appear in the main directory of table 1, with the exception of sgp_dd, issue SG_IO ioctls. The sgp_dd utility issues SCSI commands using the sg driver's asynchronous ( write()/read() ) interface to device nodes that have the sg driver's major device number (i.e. "char" major 21). This means that all utilities in the main directory are "safe" with any given device node. If the device node does not support the SG_IO ioctl then that is reported and the utility exits. [In version 1.14 sgm_dd also use the sg driver's asynchronous ( write()/read() ) interface but that has been changed to the SG_IO ioctl in version 1.15 since the asynchronous action is not needed. sgm_dd will only use mmapped IO on sg device nodes.]

Irrespective of the device node used to access a device, care should be taken not to interfere with a device while it is "active". For example invoking a "sg_format -F" utility on a disk with mounted file systems on it is obviously going to cause damage.

Exit status

Each process containing one of sg3_utils' command line utilities completes with an exit status of 0 when successful. Prior to version 1.21 all errors yielded an exit status of 1. Having finer grain error reporting via the exit status from relatively low level sg3_utils utilities allows higher level scripts and other program wrappers to do more useful error processing.

From version 1.22 the exit status value is one of:
Many of the above exit statuses will be repeatable so executing the utility again with one or more '-v' options may yield more information. Unit attentions (exit status 6) are only reported once per condition. Notice that some of the lower exit status values correspond to the SCSI sense key values. Some examples of bash scripts that use these exit values see the scripts subdirectory.

Changing mode page settings

SCSI devices store settings (metadata) that could possibly be changed by the user (called the "application client" in SCSI jargon) in mode pages. It is a common requirement to find mode page settings and in some cases change them. An example is the Writeback Cache Enable (WCE) bit in the Caching mode page of SCSI disks. Usually the manufacturer's default setting for WCE is set (on) however in some RAID configurations it may be cleared (off).

Generic command line tools to change mode page settings tend to be difficult to use (which in some small part is due to the SCSI rules for manipulating mode pages). Here is a list of some linux utilities for changing mode pages followed by some notes:
The author's recommendation is to use sdparm unless the features of another utility better suit your needs.

Examples

The fundamental SCSI command whose support is mandatory for all SCSI devices is INQUIRY. All devices should respond to a "standard" (i.e. when no Vital Product Pages are requested) INQUIRY.

$ sg_inq /dev/sda
standard INQUIRY:
  PQual=0  Device_type=0  RMB=0  version=0x03  [SPC]
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=1  Resp_data_format=2
  SCCS=0  ACC=0  TGPS=0  3PC=0  Protect=0
  BQue=0  EncServ=0  MultiP=0  MChngr=0  [ACKREQQ=0]  Addr16=1
  [RelAdr=0]  WBus16=1  Sync=1  Linked=1  [TranDis=1]  CmdQue=1
  Clocking=0x3  QAS=0  IUS=0
    length=144 (0x90)   Peripheral device type: disk
 Vendor identification: SEAGATE
 Product identification: ST318451LW
 Product revision level: 0003
 Unit serial number: xxxxxxxxx

Some SCSI devices have version descriptor information showing which standards (and drafts) they support:

$ sg_inq -d /dev/sdb
standard INQUIRY:
  PQual=0  Device_type=0  RMB=0  version=0x03  [SPC]
  [AERC=0]  [TrmTsk=0]  NormACA=0  HiSUP=0  Resp_data_format=2
  SCCS=0  ACC=0  TGPS=0  3PC=0  Protect=0
  BQue=0  EncServ=0  MultiP=0  MChngr=0  [ACKREQQ=0]  Addr16=1
  [RelAdr=0]  WBus16=1  Sync=1  Linked=1  [TranDis=1]  CmdQue=1
  Clocking=0x0  QAS=0  IUS=0
    length=96 (0x60)   Peripheral device type: disk
 Vendor identification: FUJITSU
 Product identification: MAM3184MP
 Product revision level: 0106
 Unit serial number: xxxxxxxxx

  Version descriptors:
    SAM-2 (no version claimed)
    SPI-3 T10/1302-D revision 10
    SPC ANSI X3.301:1997
    SBC T10/0996-D revision 08c

Many modern SCSI devices also support "Vital Product Data" (VPD) pages. Here is a request to list available VPD pages:

$ sg_inq -e /dev/sg1
VPD INQUIRY, page code=0x00:
   [PQual=0  Peripheral device type: disk]
   Supported VPD pages:
     0x0        Supported VPD pages
     0x80       Unit serial number
     0x83       Device identification

For displaying VPD pages, sg_vpd (or sdparm) may be a better choice than sg_inq as sg_vpd has a simpler, less cluttered command line interface and additional support for vendor specific VPD pages.

# sg_vpd /dev/sdh
Supported VPD pages VPD page:
  Supported VPD pages [sv]
  Unit serial number [sn]
  Implemented operating definition (obs) [iod]
  Device identification [di]

The following displays a subset of the device identification VPD page, namely the designators for the target port:

# sg_vpd --page=di_port /dev/sdh
Device Identification VPD page:
  Target port:
    desig_type: NAA,  code_set: Binary
     transport: Serial Attached SCSI (SAS)
      0x5000c500005208ee
    desig_type: Relative target port,  code_set: Binary
     transport: Serial Attached SCSI (SAS)
      Relative target port: 0x2

The sg_scan and sg_map utilities show the relationships between linux sg devices and their <bus, channel, target, lun> tuples and their primary device node names:

Example: given these 3 SCSI devices:
$ cat /proc/scsi/scsi
Attached devices:
Host: scsi1 Channel: 00 Id: 00 Lun: 00
  Vendor: SEAGATE  Model: ST318451LW       Rev: 0003
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi2 Channel: 00 Id: 04 Lun: 00
  Vendor: PIONEER  Model: DVD-ROM DVD-303  Rev: 1.10
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 06 Lun: 00
  Vendor: YAMAHA   Model: CRW4416S         Rev: 1.0g
  Type:   CD-ROM                           ANSI SCSI revision: 02

then the output from sg_scan is:
$ sg_scan
/dev/sg0: scsi1 channel=0 id=0 lun=0  type=0
/dev/sg1: scsi2 channel=0 id=4 lun=0  type=5

/dev/sg2: scsi2 channel=0 id=6 lun=0  type=5

INQUIRY data can be added to that output with the '-i' option. The sg_map utility shows the mapping between scsi generic (sg) devices and the corresponding primary device node. For some peripheral device types, SCSI enclosures for example, there is no mapping and the enclosure device must be accessed via a sg device node.

$ sg_map
/dev/sg0  /dev/sda
/dev/sg1  /dev/scd0
/dev/sg2  /dev/scd1

In the lk 2.6 series of kernels sg_scan and sg_map are less important as most utilities in the sg3_utils package can be issued directly against the primary device node (e.g. /dev/sda).  However the sg driver is still needed to "talk" to devices such as enclosures which have no specialized driver in linux.

The Windows port has its own sg_scan utility which attempts to place all the device names for one device on a line. Here is an example:
$ sg_scan
SCSI0:0,0,0       C:    PD0      IC25N040ATCS05-0        CS4O  *
SCSI1:0,0,0       D:    CDROM0   HITACHI DVD-ROM GD-S200 0034
SCSI2:0,0,0       I: +  PD5      QUANTUM LPS525S         3110
SCSI2:0,6,0             TAPE0    SONY    SDT-7000        0192
                  E:             Generic USB SD Reader   1.00  pdt=0
                        PD1      Generic USB SD Reader   1.00

The first half of each line contains the various device names for a device. The second half are INQUIRY reponse strings. So device names like "PD1" (or the longer "physicalDrive1" form), "D:" and "TAPE0" can be used in the Windows port.

Notes

Starting with sg3_utils-1.09 a library called libsgutils is built in some environments and is required by most utilities. The library is made up of three source files: sg_lib.c, sg_cmds_basic.c and sg_cmds_extra.c; and their associated header files . The sg_lib.c file contains tables of SCSI command names, sense key and additional sense code strings and various related helper functions. The sg_cmds_basic.c file contains low level wrapper functions for commonly used SCSI commands. The sg_cmds_extra.c file contains low level wrapper functions for less commonly used SCSI commands. The library can be built both as a shared object and a static library. The binary rpm package only contains the shared library while the sg3_utils-devel rpm package contains the static library, sg_lib.h, sg_cmds.h, sg_cmds_basic.h, sg_cmds_extra.h and some header files associated with the generic SCSI pass through interface. If users do not want libraries (shared or static) then they can refer to the "no_lib" subdirectory in the tarball which contains "no_lib" versions of the Makefile and the rpm "spec" file.

In Linux many of the utilities in the sg3_utils package ultimately use the SG_IO ioctl (rather than the older write()/read() interface) in the sg driver. In the lk 2.6  series the SG_IO ioctl (or at least a stripped down version of it) has been implemented in the block subsystem (see sg_io.html for more information). This means that commands which previously only worked on sg device names will now work on block device names as well (e.g. "sg_inq /dev/sda"). To use this facility safely version sg3_utils-1.02 or later should be used. Note that SCSI tape devices (both st and osst device drivers) are char devices and support the SG_IO ioctl from lk 2.6.6 onwards.

See the notes about header file problems in the README file inside each package.

Download

Several recent versions of the sg3_utils package are listed below. The tarballs contain README, CHANGELOG, INSTALL files and man pages as well as source and build files. The build files include Makefiles for various architectures, a linux rpm "spec" file and a debian directory for building "deb" packages.  Here is the most recently released sg3_utils CHANGELOG .

Table 2. sg3_utils tarballs and packages
sg3_utils version
release date
  tarballs 
rpm source rpms **
i386 rpm binaries **
   debian packages
1.20
20060418
sg3_utils-1.20.tgz sg3_utils-1.20-1.src.rpm sg3_utils-1.20-1.i386.rpm
libsgutils-1_0-1.20-1.i386.rpm
sg3-utils_1.20-0.1_i386.deb
libsgutils1-0_1.20-0.1_i386.deb
1.21
20060706
sg3_utils-1.21.tgz sg3_utils-1.21-1.src.rpm sg3_utils-1.21-1.i386.rpm
libsgutils-1_0-1.21-1.i386.rpm
sg3-utils_1.21-0.1_i386.deb
libsgutils1-0_1.21-0.1_i386.deb
1.22
20061016
sg3_utils-1.22.tgz
sg3_utils-1.22-1.src.rpm sg3_utils-1.22-1.i386.rpm
libsgutils-1_0-1.22-1.i386.rpm
sg3-utils_1.22-0.1_i386.deb
libsgutils1-0_1.22-0.1_i386.deb
1.23
20070127
sg3_utils-1.23.tgz sg3_utils-1.23-1.src.rpm sg3_utils-1.23-1.i386.rpm
sg3_utils-libs-1.23-1.i386.rpm
sg3-utils_1.23-0.1_i386.deb
libsgutils1-0_1.23-0.1_i386.deb

This sg3_utils_exe.zip file is a zip archive of the most recent version Windows executables made in a MinGW environment. This sg3_utils_man_html.tgz file is a tarball of man pages converted to html by man2html.

Version 1.14 of sg3_utils introduced a shared object (library) called libsgutils. When binary packages are built then libsgutils is in its own package (and there is another "libsgutils*-devel" package which contains C header files and a static libsgutils.o library). The sg3_utils binaries for version 1.14 to 1.23 normally require the libsgutils library but can be built without it. In the future other utilities such as sdparm may also depend on the libsgutils package.

** Some browsers (e.g. firefox) may interpret a file with an extension of "rpm" as an audio file. In which case press the right button over the link and select "Save link as ..." to download the file.

Below is the most recent version of the sg_utils package which targets the linux kernel 2.2 series with some support for the lk 2.0 series. No further work is being done on this package.
Table 3.  sg_utils tarballs and packages
sg_utils
version
  tarballs 
rpm source rpms **
i386 rpm binaries **
1.02 sg_utils-1.02.tgz sg_utils-1.02-1.src.rpm sg_utils-1.02-1.i386.rpm

There is no './configure' logic in sg3_utils so the correct Makefile must be chosen taking into account the operating system and several other attributes.

Table 4.  Building from a source tarball
OS
build to use shared library
build without library
build static executables
Notes
Linux
make
./make_no_lib.sh
./make_no_lib_static.sh
rpm spec file and debian subdirectory included
FreeBSD
make -f Makefile.freebsd
./make_no_lib_freebsd.sh
 
 
Tru64 (OSF1)
make -f Makefile.osf1
./make_no_lib_osf1.sh
 
 
Windows

make -f Makefile.win32
 
Windows NT and later supported (uses SPT interface). Builds in a cygwin environment and requires cygwin1.dll to run.
Windows

make -f Makefile.mingw

Builds in a MinGW/MSYS environment and requires no third party dll


Both sg3_utils and the older sg_utils packages can be found on http://freshmeat.net . Most of the above invocations can take the name of a specific utility (e.g. "make sg_inq") to build only that utility. There are also "install", "uninstall" and "clean" targets in most Makefiles.

Return to main page.

Last updated: 31st January 2007