Everything looks easy in the magazines ;-) Coming from a mainframe background, Linux can be difficult. The installation instructions are not as good as z/VM or other mainframe OSes. You really have to have some kind of a Linux, PC or mainframe, around to help stage the install, since Windows is so incompatible in assorted areas.
Pick a distribution, start your install, document what you have done, and post your questions here when you hit a problem. Remember, the more info you can give us on the problem, and what you have done, the easier it is to get help. The one advantage that the original Marist version had, was that it did not require an existing Linux to get started with. The later versions kind of need one to stage the install files, but they give you SO MUCH more. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Harting, David Sent: April 27, 2006 11:19 To: LINUX-390@VM.MARIST.EDU Subject: Re: Install question Thank you for your advice. I will try to install CentOS This is the second time. I have tried to install LINUX in a VM guest. First, I tried Debian. Second, I tried Marist. This proof of concept is talking me a long time! A new release of Z/OS or Z/VM might be easier. All I want to do is get LINUX up and running and let some people see what we can do with it. It looks easy to do in the IBM magazines. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, April 27, 2006 10:57 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Install question > I am installing Marist/LINUX on an IBM Z800 in a Z/VM guest. Bluntly, give up on the Marist distribution and start with something more modern that supports guest LANs. The Marist code is *ancient* and lacks a number of important things to make it usable for anything. You'll spend more time chasing those problems than learning anything about Linux. If you need a totally free distribution to play with, check into CentOS or Debian. Both are considerably more up to date, and much more representative of the current state of the art. Returning to your question: > I am able to ping from the tcpmaint ID to the LINUX but it seems I can not > do this from outside of the mainframe. The problem is not in your setup, but in the network outside your setup. You need to have your networking people insert a static route into the network infrastructure that tells the rest of the world that your Linux guest is reachable via the VM TCPIP stack, or configure MPROUTE on VM and have the networking guys accept routing updates from it. They're more likely to do the static route approach. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 <FONT SIZE=1 FACE="ARIAL">^^^^^^^^^^^^^ This email may contain confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, please contact the sender and delete all copies. Any review or distribution by others is strictly prohibited. Personal emails are restricted by policy of the State Employees' Credit Union (SECU). Therefore SECU specifically disclaims any responsibility or liability for any personal information or opinions of the author expressed in this email. </FONT> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
