On 02/03/2012 08:46 AM, Konstantin Olchanski wrote:
>> On Thu, Feb 2, 2012 at 5:19 PM, Yasha Karant<[log in to unmask]>  wrote:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=636628
>>>
>
> That bug report is no good as it is filed against Fedora. If you want to see
> the same bug fixed in RHEL/SL, you better file a bug against RHEL (with reference
> to the fedora bug). In the RHEL world, no bug report - no problem - no fix.
>
> P.S. And that's my personal experience. system-config-date has been busted
> since SL6.0. Original bug was reported in Fedora, *fixed* in Fedora for years,
> then shows up again in RHEL6. So I file a bug against RHEL6.0. First it is
> downgraded to low priority, (RHEL6.1 is out), then it is bumped into high
> priority (RHEL6.2 is about to go out), now the fix is scheduled for RHEL6.3.
> If you think it is too cumbersone and too difficult and too slow, please
> go ahead and roll out your own YaLinux or whatever.
>
> P.P.S. The quoted bug report includes a workaround for the problem (RTFBR!),
> so I vote to delete this whole email thread out of existance - problem is known,
> is reported through proper channels and there is a workaround. There is nothing
> to discuss other than whining about bugs not being fixed quickly enough or
> diverge into unrelated topics such as bios and grub password protections.
>

I vote to keep the thread.  Your statement that the bug report is only 
in Fedora and that no one else has experienced this issue with EL 6 is 
not correct, and I quote from a previous post I made to this thread:

From:
https://bugzilla.redhat.com/show_bug.cgi?id=636628

Geeky 2011-06-04 09:02:40 EDT

Also present in RHEL6.1 ! paid, licensed, commercial support

End quote.  If necessary, to satisfy the poster, I suppose that the 
report can also be filed against RHEL 6.1, although I personally do not 
have such RH "paid, licensed, commercial support".  (Is that needed for 
posting against a licensed-for-fee binary product?)


Thus, the entire set of TUV compliant distributions probably have this 
"feature", including RHEL 6.1 and SL 6.1

In private communication off list, it has been pointed out to me that:

I suspect the big difference is the use of upstart in 6.x where just
plain old init was used before. Upstart may either be just using mode 
that are there or setting some different one than before.

End quote.

The mode to which the correspondent refers are TTY control and 
interpretation modes (bits) set in the software, and possibly not even 
reflected into the hardware via the driver.

Yasha Karant