I finally got my drives back from year end processing and now it is back to work.
Using Suse 8, I created a FTP server, created a LVM with 3 3390-3 drives and uploaded the 6 SLES9 CDs. The LVM is mounted as /data. I used the mksles9root perl script to create the file structure. It created the sles9root and it looks like it is complete. I created a user called suse9, which has a home directory of /data. I proceed with the installation of Suse 9, and it loads the ram disk. I use ssh to continue the installation. I bring up putty and logon to the Suse 9 machine. Go into yast, select english, activate the drives, format the drives, new installation, and then we get the: Software: Cannot read package data from installation media. Media error? * ERROR: No proposal Now, I'm beginning to believe that it is either the userid I'm using to connect to the FTP server, or the basic file structure. The userid "suse9", is just a regular userid. It's home directory is /data. (/data/sles9root is the directory of the installation files) When I FTP from Windows using that userid, I am dropped into the /data directory and I can do the CD to change to sles9root and all other subdirectories, so it seems that the permissions are right. However, during the installation, where all the documentation says I can just enter "sles9root", if I enter just that, the installation FTP comes back with cannot find directory message (it is looking for /sles9root). 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? So, I'm obviously beating my head against yast and what it is looking for. 1. Is there any special authorization needed for the userid on the FTP server, (like root priviledges?). 2. Is there a certain home directory needed for this userid? 3. Can a "mount --bind /data/sles9root sles9root" be done without any problems or do I have to have sufficient filespace on the root volume for all the installation data? Where before, I thought I was having problems with the installation process, now I think it is something more basic, like setup. Tom Duerbusch THD Consulting ---------------------------------------------------------------------- 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
