>>> On 4/30/2009 at 2:20 AM, Tobias Doerkes <[email protected]> wrote: > Hi list, > > in the past we placed our installation sources for linux installations on a > linux server. from now on we want to provide them via z/OS services.
Why in the world would you want to do that? (System Programmer Standard Response # 1). There have been one (maybe two) people that have done this in the past. They did get it to work, but I seem to recall they had, umm, issues. Try checking the mailing list archives. If you've already got Linux running on your mainframe, why not use that as your installation source? It would be a lot easier than what you're trying to do. > So we > took an z/OS FTP space and copied the unloaded iso images into z/OS. It seems > that the SLES11 installation image uses relative path information. This is That's been true ever since SLES10 GA. > not the best way, because when logging into z/OS FTP, we are in z/OS > Filesystem. I don't understand what you mean by that. Do you mean the "normal" dataset lists, and not the USS HFS? > So my question: Is there a way to tell the sles11 installation image to use > absolute path information for install parameter in PARMFILE? No. I suspect there is a way to tell MVS to start out in the HFS, though. It's been a while since I worked with it though, so I'm not sure. > A possible alternative could be to provide sources via http, but we prefer > ftp. My preference is the exact opposite, mainly because most HTTP servers give you better logging than FTP servers when you're trying to debug installation/network problems. As I said, it's been quite a while since I worked with the FTP server from MVS, so that may not be an issue for you. Mark Post ---------------------------------------------------------------------- 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
