This would, in fact, rock.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects. 

These improvements will be incorporated into a future major release of Red Hat
Enterprise Linux. Red Hat does not currently plan to provide a resolution for
this in a Red Hat Enterprise Linux update for currently deployed systems.

Err... RHEL4 is still in Full Support [1] mode, so I'd suspect this falls into
the "available and qualified errata" catagory (and Fedora Core has proven that..).  

While probably not the primary objective of an Update Release, I think this is
super-useful and supports the Full Support model.  The fact of the matter is
that the default terminal for the default desktop environment is darn close to
unusable, which is probably not great for a Linux product (enterprise or otherwise).

I could open a bunch of bugs if you'd like, but it seems silly as this FE would
addess them all:
- Doesn't work with screen
- Mysterious resizes when term window is > 80x24
- Random crashes
- Poor encoding support
- Slow
- High memory usage per tab, makes more than 5 tabs is painful on a 1GB P4
system (while in RHEL3 with dzt, I typically ran about 20 tabs and performance
was more than acceptable).

(FWIW, uga.edu has an academic site license, which means we don't have the
ability to open up Support incidents on these sorts of things, else I would have
already.)

I humbly ask that you reconsider.

Thanks,

-n

1 - http://www.redhat.com/security/updates/errata/

Hi,

I am adding this to the proposed list for potential inclusion into a future RHEL
4 update.  Once on the proposed list it will be evaluated against other
candidates for update and weighed against Quality Engineering resources.

Thanks!  

Rebasing definitely solve a ton of bugs, but it definitely introduce new ones too...

PM NAK based on the risk assessment.

Product Management has reviewed and declined this request.  You may appeal this
decision by reopening this request.