On Fri, Sep 24, 2010 at 3:59 PM, <j...@mbstemps.com> wrote: > Bryan, > > Thank you for your interest, the system in question was running RHEL5.5, so > every comment is based on that machine, used as a test bed for rhel6b2. > > Motherboard Asus A8v-vm; Processor -AMD Athlon 64 - Memory 2GB; on board > lan-Realtek; Modem - USR 2976pci fax/modem. > > For me the system is very vanilla and again was running all the functions > before. Just as an interesting side issue, after not getting solutions to > any of the problems I attempted to re-load RHEL5.5 and find that the hard > drives won't re-format so the conversion back doesn't work. And of course > the ext4 file system isn't in rhel5.5. > > I don' t use anything but AMD chips in our servers, only use Intel in > netbooks(not much choice) which run Fedora 11&12 fine. Also the network > setup in FC12 works fine or netbooks and notebooks, doesn't work in
I'm not happy with NetWorkManager and what it does to network setups. I think it's unnecessary bloatware for servers, and of very questionable utility for laptops. > rhel6b2! We have used KDE from before there were Enterprise Linux distros, > when we tried Gnome cut &paste didn't work and I personnaly didn't like the > look(still don't) anyway Kylix and Qt graphic interface seemed to like KDE > better and there have always been more features in KDE that fit our > methods. In RHEL5.x KDE menu operation and VNC make a very impressive and > reliable solution platform for our solution(50+ programs) and I am NOT > changing our solution because Red Hat hasn't seen fit to test or integrate > KDE better. Also it would be nice if Red Hat provided documentation that > ran on KDE as well as Gnome, if they are 'compatible' solutions it should go > straight across? Can't help you there. Maintaining compatibility for two entirely different sets of GUI standards and desktop environments is painful, and I understand their desire to provide primary support for only one. > Again immediate problems -Network, if it doesn't work I can't attach to the > server and do a lot of testing. > > -Modem, if I can't configure dial in remote support, I can't ship a system > that I can't support. Fair enough. Can you install the "HylaFAX" software from Sourceforge? I'd love to see that enter RHEL for modem handling, its "faxaddmodem" script is a superior tool for probing modems, and its "faxgetty" a very good tool for keeping modems configured in working states. > -KDE, if I start a vnc session from KDE I get a 'gnome' based menu to work > with, one of the thrills of 'gnome' is that it seems to be double click Oh, *THAT* is griggered from your $HOME/.vnc/xstartup files, and is following the RHEL standard of using Gnome as your default. It can be edited there, or you can try to track the maze of twisty little config files to set it as a system standard. > driven, KDE allows selecting single or double click, gnome doesn't seem to. > When I accidentially double clicked a program, lo it does seem to work under > rhel6b2! So far that has been the only positive experience I have had with > rhel6b2. also under KDE the system only has a 800x600 screen resolution, on > a flat pannel that is at least 1024x768 capable. I do believe that the > majority of my real world problems are KDE based with rhel6b2, although not > recognizing the network or modem are both show stoppers. Personal opinion, > since gnome is the default environment for Red Hat, Suse, Ubuntu... the fact > that KDE is only a tick behind in popularity shows that KDE is worth the > extra effort to bring up, so is if both were even, the more popular > environment. Is it worth it to the paying customers? While it's conceptually desirable, it takes a lot of engineering time to mix and match components to get both Gnome and KDE to play nicely (as you are noticing). > Anyway, I will step down off my KDE soapbox and thank you for showing > interest in the problems. I, unlike some of the other comments in this > batch am in no hurry for Red Hat to ship RHEL6, to me it isn't ready and I > think there is every reason to be cautious, also if you have read the > pre-realease guide, there are way to many 'TBA' solutions. > > John A. Ward > > > > _______________________________________________ > rhelv6-beta-list mailing list > rhelv6-beta-list@redhat.com > https://www.redhat.com/mailman/listinfo/rhelv6-beta-list > _______________________________________________ rhelv6-beta-list mailing list rhelv6-beta-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv6-beta-list
