Dos2Unix; Rhba-2009:0276: Bug Fix Update; Dump; Rhba-2009:0425: Bug Fix Update - Red Hat ENTERPRISE LINUX 5.4 - TECHNICAL NOTES Manual

Chapter 1. Package Updates

1.41. dos2unix

1.41.1. RHBA-2009:0276: bug fix update

Note
This update has already been released (prior to the GA of this release) as FASTRACK
RHBA-2009:0276
errata
Updated dos2unix packages that resolve two bugs are now available.
The dos2unix utility converts DOS or MAC format text files to UNIX format.
This updated package provides fixes for the following bugs:
• dos2unix did not allow for instances where a user specified the -c option without a conversion mode
name following it. An input in this format would therefore result in a segmentation fault. Dos2unix
now exits safely with a message to the user that option -c requires an argument.
• when dos2unix created a new file as the output of its conversion (when run with the -n option), the
new file would always have its permission mode set as 600, regardless of the permission mode
of the original file. Dos2unix now sets the permission mode for the new file to be the same as the
mode of the old file, filtered through the user's umask.
Users of dos2unix should upgrade to this updated package, which resolves these issues.

1.42. dump

1.42.1. RHBA-2009:0425: bug fix update

Note
This update has already been released (prior to the GA of this release) as FASTRACK
RHBA-2009:0425
errata
Updated dump packages that resolve several issues are now available.
The dump package contains both dump and restore commands. The dump command examines files
in a file system, determines which ones need to be backed up, and copies those files to a specified
disk, tape, or other storage medium. The restore command performs the inverse function of dump; it
can restore a full backup of a file system. Subsequent incremental backups can then be layered on top
of the full backup. Single files and directory subtrees may also be restored from full or partial backups.
These updated dump packages provide fixes for the following bugs:
• when running the dump command without specifying a dump level, then neither did dump's output
indicate the dump level, as in the following example output:
46
251
252