2006-03-28 s390-tools 1.5.3 ("April 2004" and "October 2005") (superseded)

If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

Category: operating system. Contains the source tree of a set of user space utilities that should to be used together with the Linux on zSeries kernel and device drivers.

s390-tools-1.5.3.tar.gz / MD5 recommended (superseded) (2006-03-28)

These s390-tools-1.5.3 replace s390-tools-1.5.1 (Note that we are skipping the 1.5.2 version).

Added new tool:

This package contains the following bug fixes:

Description:
chccwdev: Various problems with chccwdev.
Symptom:
  1. The first devno that does not exist in a range will cause an error.
  2. Using more than two generic attributes causes the command to hang.
  3. Use of a devno with more than 4 digits was not detected as error.
  4. Upper-case character in devnos were not accepted.
Problem:
Solution:
Problem-ID:
22070
Description:
chccwdev: Generic attributes are only set on first device of a range.
Symptom:
When using generic attributes with more than one device, only the first device will be set correctly.
Problem:
The attribute values are deleted to handle pre- and post-online attributes but not restored for the next device.
Solution:
Remember the values of the generic attributes and restore them before working on the next device.
Problem-ID:
22498
Description:
chccwdev: Can not set generic attributes with chccwdev.
Symptom:
The chccwdev command does not support other attributes than online.
Problem:
Generic attribute support was not available.
Solution:
Added support.
Problem-ID:
21498
Description:
dasdview: Validate characteristics and confdata before printing.
Symptom:
Device characteristics and configuration data are always reported by dasdview, even if they are undefined.
Problem:
The constant size of the buffer is used for checking valid data amount.
Solution:
Use 'characteristics_size' and 'confdata_size' to check amount of data to be reported.
Problem-ID:
22533
Description:
lsdasd: lsdasd shows internal errors to user.
Symptom:
When the blockdev command issues error messages they will go to the screen.
Problem:
stderr is not suppressed for the blockdev call.
Solution:
Re-direct stderr to /dev/null.
Problem-ID:
22501
Description:
lsdasd: Shows incorrect information.
Symptom:
lsdasd shows some devices as not-formatted with invalid major and minor numbers.
Problem:
Latest changes to the sysfs layout broke the internal query.
Solution:
Change query to work with all sysfs versions.
Problem-ID:
20903
Description:
lsdasd, lstape, lscss, chccwdev: Sysfs mountpoint hardcoded to /sys for various tools.
Symptom:
The tools lsdasd, lstape, lscss and chccwdev may fail if sysfs is not mounted to /sys.
Problem:
The path to sysfs was hardcoded.
Solution:
Dynamically check where sysfs is mounted.
Problem-ID:
21499
Description:
lszfcp: directory of block device not printed.
Symptom:
"lszfcp -D -V" does not show the directory of the block device.
Problem:
Symbolic link from scsi device to its block device was renamed with kernel version 2.6.16.
Solution:
Adapt lszfcp to work with old and new symlink names for the link from a scsi_device to its block device.
Problem-ID:
-
Description:
osasnmpd: Improve handling of interface changes.
Symptom:
OSA-interfaces not shown when added while osasnmpd is running.
Problem:
netsnmp updates its "number of interfaces" counter within 60 seconds after a change in the number of networking interfaces. But osasnmpd tries to update its interfaces immediately after adding or removing a qeth-interface. That means snmpd and osasnmpd are no longer in sync regarding the number of interfaces.
Solution:
Schedule a second invocation of update_mib_info() 70 seconds after the first invocation.
Problem-ID:
15130
Description:
scsi_logging_level: scsi_logging_level -v does not work.
Symptom:
scsi_logging_level -v does not show version of s390-tools.
Problem:
Placeholder for s390-tools version was not replaced during installation.
Solution:
Adapt Makefile to replace the placeholder with s390-tools version.
Problem-ID:
22613
Description:
tunedasd: Misleading tunedasd message after profile reset.
Symptom:
Message 'Profiling seems to be inactive' when profile info is read directly after profile-reset.
Problem:
The IOCTL BIODASDPRRD had no return code for 'profiling is inactive' and therefore tunedasd wrote this message for request-counter = 0.
But this is also true for active profiling when read prior to first request processing.
Solution:
Introduced return-code EIO for inactive profiling and check against EIO.
Problem-ID:
20026
Description:
vmconvert: Compile error in dump.h.
Symptom:
Compile of vmconvert with a new gcc fails with messages error: extra qualification 'ProgressBar::' on member 'initProgress'.
Problem:
In the definition of class ProgressBar the method initProgress is explicitly qualified as 'ProgressBar::initProgress'.
Looks like older gcc versions tolerate this, but newer versions do not. The file compiled with 'gcc (GCC) 4.0.3 20051013 (prerelease)' but failed with 'gcc (GCC) 4.1.0 20051205 (pre-release)'.
Solution:
Remove extra qualification from class definition.
Problem-ID:
20666
Description:
vmcp: Re-arrange error messages and return codes to cover all possible cases with useful information.
Symptom:
Some error cases missed detailed information.
Problem:
Misleading error messages.
Solution:
Re-arrange the error codes and messages, other cleanups.
Problem-ID:
19648
Description:
zfcpdump: SCSI dump does not work if too many I/O devices are attached to the system.
Symptom:
System seems to hang after the two MLO-Machine-Loader messages. No zfcpdump message at all and the CPU is looping.
Problem:
zfcp dump runs out of memory in case there are too many I/O devices present, because all of them will be probed and memory will be allocated.
zfcpdump is restricted to 32MB memory.
Solution:
Probe only the IPL device and nothing else.
Problem-ID:
22563
Description:
zfcpdump: Make zfcpdump kernel compile with gcc 4.1.
Symptom:
Compile error in uaccess.h __get_user().
Problem:
Imperfect definition of __get_user() according to gcc 4.1.
Solution:
Change __get_user() primitive.
Problem-ID:
22564
Description:
zipl: Missing check for overlapping boot components.
Symptom:
Booting a system initialized by zipl may fail without warning in case kernel image gets too large.
Problem:
In the standard configuration, large kernel images (> 8MB) may overlap the initial ramdisk component during IPL. zipl does not check for this type of mis-configuration.
Solution:
Add a check to zipl that aborts with an error message when it identifies overlapping components.
Problem-ID:
-
Description:
zipl: zipl fails when /tmp is mounted with option 'nodev'.
Symptom:
When trying to run zipl on a system which has /tmp mounted with option 'nodev', it will fail with the non-descriptive error message 'Permission denied'.
Problem:
zipl tries to create temporary device nodes in /tmp which may be configured not to allow device nodes. In addition the fallback logic implemented in zipl that should try different paths for temporary device nodes if one path fails does not cover this error case.
Solution:
Try to create temporary device nodes in /dev first. Also fix fallback logic to cover 'nodev'-mounted file systems.
Problem-ID:
-

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.