after much trial and error I got the SLES9 install to work from a zvm linux ftp server. My ../installroot directory resembles your /data/sles9root. The directory with the install material in my case is /home/usrdk01/installroot. I authorized with chmod all files in installroot and its subdirectories to a user of student. When the rdr IPL linux starter system asked me for the media directory for the ftp I specify: ../../home/usrdk01/installroot ( dot dot slash dot dot slash home slash usrdk01 slash installroot ) I entered student for the ftp user, and the password for student. All went swimmingly after that. Also got NFS install to work by specifying in /etc/exports: /home/usrdk01/installroot * (ro,sync) Hope this helps David
________________________________ From: Linux on 390 Port on behalf of Tom Duerbusch Sent: Thu 3/10/2005 12:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES9 Install problems again linux15:~ # ls -l /data/sles9root total 1 drwxr-xr-x 5 root root 224 Mar 9 14:41 . drwxr-xr-x 12 suse9 users 1376 Mar 9 17:16 .. lrwxrwxrwx 1 root root 14 Mar 9 14:41 boot -> sles9/CD1/boot lrwxrwxrwx 1 root root 17 Mar 9 14:41 content -> sles9/CD1/content lrwxrwxrwx 1 root root 21 Mar 9 14:41 control.xml -> sles9/CD1/control.xml drwxr-xr-x 7 root root 168 Mar 9 13:39 core9 lrwxrwxrwx 1 root root 17 Mar 9 14:41 media.1 -> sles9/CD1/media.1 drwxr-xr-x 3 root root 72 Mar 9 13:39 sles9 drwxr-xr-x 2 root root 104 Mar 9 14:41 yast linux15:~ # Well, I'm using an FTP server because I needed to create an FTP server for other uses. This setup gave me a test bed prior to producing a production one. Perhaps, later next week, if this isn't fixed, I will try an NFS server. But, so far, using a Linux/390 ftp server gave me the same results as using Samba on my Win/2000 box, except for the much greater performance the Linux/390 side has due to not having to go out on the wire. Tom Duerbusch THD Consulting Michael MacIsaac wrote: > Tom, > > >>If I enter in /data/sles9root, then I can load the ram disk. >>But I wonder if yast can handle the /data/sles9root or if >>it is also looking for /sles9root? > > > The SuSE "Architecture Specific Information" manual says: > > "INST_IP_DIR=/s390 Enter a directory on the installation server, which > holds the installation data of the SUSE LINUX Enterprise Server CDs." > > To me that implies a fully qualified directory should work, and in fact > this is how you get the RAMdisk loaded. > > On the FTP server, what is the output of "ls -l /data/sles9root"? > > A workaround is to use NFS rather than FTP, but if you want to get to the > bottom of *this* problem I understand. > > "Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
