If I remember the debates from earlier in the year, if both 3215 and 3270 console support is defined then 3215 should be the default. Whether that is how it is implemented in the code, I don't know. If it is not, and 3270 console is the default when both are present, then the installation process should show how to specify a 3215 console. Support for both should be generated into the kernels, or the customer should have a choice of various kernels to pick from to match their needs. They should not have to re-gen the kernel just to get the right type of console. If you have to pick one or the other (and you really should not), then go with the 3215. There's going to be a lot more Linux/390 running under VM than otherwise.
Mark Post -----Original Message----- From: Hervey Allen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:56 PM To: [EMAIL PROTECTED] Subject: Re: Turbo 2.4.5 Beta and the Console is nolonger 3215 Chris - The only thing I could think of is that having 3270 support might help when using something like the 3270 support module UTS Global offer (see their HOWTO at ftp://ftp.utsglobal.com/pub/tub3270/oldstuff/HOWTO). I'm walking over to engineering right now to see what we'll do with our 2.4 beta (and upcoming GA's) in terms of switching back to 3215 support. Does anyone else on the list have comments about this? Thanks, - Hervey Allen TurboLinux Sales Engineer [EMAIL PROTECTED] T 650-228-5142 >Date: Tue, 18 Dec 2001 22:33:55 -0500 >From: Christopher Lowry <[EMAIL PROTECTED]> >Subject: Re: Turbo 2.4.5 Beta and the Console is nolonger 3215 > >Mark > >Thanks for the help. I had to remove the 3270 support and add the 3215 >support. The 2.4.5 kernel is working with the 3215 console. >After a review of the 3270 documentation and doing some testing, I could >see not see any advantage to the 3270. Is there a 3270 style edit program >(like VM XEdit) that works with this driver ? >Chris
