That is what I thought at the time. But I want to say that SLES8 without service packs, perhaps had a "installation problem"? Anytime I didn't prefix the directory:
3 FTP 192.168.193.120 s390/sles8root suse9/install 3 SSH it still showed up on the FTP Server log file as /s390/sles8root. I queried LINUX-390 and the suggestion came back about "chroot". I changed it, it worked, I never looked back. But in the back of my mind, I do thing SP2 (I a skipped SP1) had some sort of change that made this work properly. If that is the case, then your installation may change when: 1. You get a new Windows box. 2. Your Linux server is at a new Version. 3. You apply a SP to your Linux server. 4. What version of Linux you are trying to install. 5. What SP may be applied to your Linux that you are trying to install. There are just too many options and variables for a new zLinux user to have to deal with (that is unless they are really an old Linux user from another platform). The zLinux venders (Suse/Novell, Red Hat, etc), should: 1. Have a zLinux image that can easily be installed from their website. 2. Have a zLinux image available in 3390-3 disk image. 3. Have a zLinux image available in 3390-3 disk image with a functional FTP server running with the installation images and SPs on there ready to go. I've gone thru a lot of pain and suffering just trying to get an image installed. Looking back, it is almost always due to the installation "server" software that just didn't cut it. When Windows Shares worked with SLES7 and not SLES8, on Win/98, I thought it was my problem. Then I thought it was bad .iso images. Then I thought it was a network problem (either the network was bogged down, it I was loosing packets). Then I thought it was Suse's problem. Then I switched to FTP on Win/2000 and everything worked. So it was my problem. 4-6 weeks lost (while doing other things of course). Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 5/16/2006 12:23 PM >>> "chroot_local_user=yes" made things work most likely because you were specifying the FTP server directory as /whatever, rather than a path _relative_ to your home directory, e.g., ../../path/to/install/media/ Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Tuesday, May 16, 2006 1:03 PM To: [email protected] Subject: Re: FTP server I had the same kind of error. Of the many things I tried, the following seemed to "cause things to work". On your FTP server machine (assumming zLinux): Yast Network Services Network Services (inetd) Enable FTP (vsftpd) Service is active Accept Finish Quit Joe /etc/vsftpd.conf Uncomment: Local_enable = yes Write_enable = yes Chroot_local_user=yes Save I seem to recall that the "chroot_local_user=yes" was the part that did the trick. Without it, I couldn't change to the proper directory. BTW, I also had things setup with mksles9root. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 5/15/2006 6:23 PM >>> Bates, Bob wrote: > Hello all, > I am trying to set up an FTP server, SLES9 64-bit, to do the rest of my installs from. The server is running, I have file systems with s390 and s390x code, but when I attempt to do an install, it can't read the software package list, media error? > > I figure I have something setup wrong. I haven't been able to locate a document that describes how the filesystem should be set up. Can somebody give me the name of the document? link? > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
