Bug 709483 - More TN fixes
Summary: More TN fixes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Technical_Notes
Version: 6.1
Hardware: noarch
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 19:37 UTC by Chris Pepper
Modified: 2011-07-28 18:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-28 18:08:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Chris Pepper 2011-05-31 19:37:55 UTC
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/bash.html
only relevant messages are now presented to user. (BZ#664468)
only relevant messages are now presented to users. (BZ#664468)
only relevant messages are now presented to the user. (BZ#664468)


http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/bind.html
The rndc.key is used by rndc utility
The rndc.key is used by rndc the utility

Users requiring the rndc utility should generate key themselves,
Users requiring the rndc utility should generate a key themselves,
Users requiring the rndc utility should generate the key themselves,

Consequently, "named" could not be stopped using the "/etc/init.d/named stop".
Consequently, "named" could not be stopped using "/etc/init.d/named stop".
Consequently, "named" could not be stopped using the "/etc/init.d/named stop" command.

named writes error message to the system log 
named writes an error message to the system log 

when bind-sdb package was installed.
when the bind-sdb package was installed.


when resolv.conf contained "search" keyword with no arguments host/nslookup/dig utilities failed to parse it correctly.
when resolv.conf contained the "search" keyword with no arguments, host/nslookup/dig utilities failed to parse it correctly.

The the dnssec-keygen 
The dnssec-keygen 

and allows to start named 
and allows starting named 

with this update, size, MD5 and the modification time of /etc/sysconfig/named configuration file is no longer checked
with this update: size, MD5 and the modification time of the /etc/sysconfig/named configuration file are no longer checked


http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/binutils.html
Missing bullets & punctuation:
fix strip to keep the address of an empty section consistent with its offset in the object (BZ#614443) if one of the input files is of a non-ELF format the linker may crash (BZ#680143) fix occasional crash in linker (BZ#697703)

Again:
add support for the large code model on PowerPC (BZ#663587) add support for ELF core dump notes sections for extra s390 registers (BZ#633448) add support for the new instructions in the System z196 processor (BZ#631540) add support for ELF objects with more then 65535 program headers (BZ#578661)


http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Technical_Notes/cifs-utils.html
This was due to the --legacy-uid command line option for cifs.upcall not properly implementing.
This was due to the --legacy-uid command line option for cifs.upcall not being properly implemented.
Or not properly implementing *what*??

This patch ensures that it properly implements,
Incorrect usage of 'implements'.

This is unclear. Do you mean to say the mount is retried with a different (theoretically equivalent) value for one or more of those options? What if all 3 are used -- does it convert one or all? Does it retry with different combinations?
>mount.cifs did not handle numeric uid=, gid=, or cuid= options correctly, and would often return an error when they were specified. With this patch, a check is run to see if any error occurred by setting errno to 0 before the conversion. If one did then it will attempt to treat the value as a name, allowing them to be correctly handled. (BZ#696951)

Comment 2 Martin Prpič 2011-07-28 18:08:17 UTC
All of the issues from comment #0 have been fixed.

Thank you for reporting this issue,
Martin


Note You need to log in before you can comment on or make changes to this bug.