From: Douglas Gilbert <dougg@torque.net>
To: linux-scsi@vger.kernel.org
Subject: sg3_utils-1.07 released
Date: Thu, 08 Jul 2004 10:12:23 -0400 [thread overview]
Message-ID: <40ED5647.7060707@torque.net> (raw)
Tarball and rpms can be found on http://www.torque.net/sg .
Summary of sg3_utils, sg_utils and other packages are on
this page: http://www.torque.net/sg/u_index.html
A release announcement will be sent to freshmeat.net
shortly.
Changelog for sg3_utils-1.07 [20040708]
- sginfo: clean up inquiry vendor,product,revision strings
- '-Fhead': sort defect list by head
Tom Steudten <steudten at mx dot ch>
- rework sg_err for better command name coverage: service actions,
variable length and peripheral device type
- update asc,ascq codes to SPC-3 revision 19
- move scsi_devfs_scan to archive directory
- add sg_opcodes utility to list supported operation codes
- add sg_persist utility to support persistent reservations
- add '-i' option to sg_inq to decode device identification VPD
page (0x83)
- sg_inq tries an ATA IDENTITY if SCSI INQUIRY fails
- sg_dd, sgm_dd and sgp_dd calculate block device sizes (if count
not given)
- drop SG_GET_VERSION_NUM ioctl guard in most utilities
Doug Gilbert
reply other threads:[~2004-07-08 14:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40ED5647.7060707@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox