Hi Alan
Originally, I downloaded the iso images to Win/2000 and burnt the CDs. The CDs all have, what looks like, a normal directory structure.
This was the same process that I used for Suse 7 and Suse 8 installs.
And it still works with Suse 8 installs as I did a fresh install to create my Linux ftp server.
But with Suse 9, I basically get hung up with "media error" when it is trying to create the proposal.
So now, 2 plus months later, I redownloaded the iso images from Novell (well, the new and old images are the same size), and then uploaded them (using Windows client ftp to vsftpd on Suse 8).
I then tried using a mount with loop to mount the iso images. Same problem with "media error".
So I then used the mkinstroot perl script from Mark to create the directory structure, etc. So, at this point, Windows only touched the iso images and wouldn't have a chance to mess up with different naming conventions. But...same problem.
All the documentation states that the process is:
. Select 3 Install from ftp . Enter ip address . Enter directory
The documentation says that I should only have to enter "suse9root".
But when I enter that, plus the userid and password for ftp, it says that it couldn't find the directory and I go back to being able to select 3 Install from ftp.
When I put in the fully qualified name "/data/suse9root", that process works. But it does make me wonder if yast wanted a relative directory entry (suse9root) and can't handle a full directory structure (/data/suse9root).
I then tried the mount --bind to make /data/suse9root look like /suse9root. Same problem.
So currently, I'm fully Linux now. Except for the iso images being downloaded to Win/2000 and then uploaded to Suse 8, it is a MS free zone.
Mark Pace suggested that the setup for vsftpd needed chroot_local_user=YES. This makes sense to me in that I think the problem is some sort of setup problem outside of the installation.
Well, I'm the type that will keep pounding my head into the wall, occassionally I stop for a few days or weeks, but then I get back to it. I have a tendency not to quit until it works.
But in the process, I usually learn a lot.
Tom Duerbusch THD Consulting
Alan Altmark wrote:
On Thursday, 03/10/2005 at 11:15 CST, Tom Duerbusch <[EMAIL PROTECTED]> wrote:
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, when you originally transferred the files from the CD, what platform was the CD loaded on? The Windows CD device driver does not support the Rock Ridge extensions like Linux does. So, a CD created by a Linux machine often has extra data (e.g. file links) stored on the CD that Windows won't find.
This is why it is always recommended to read a Linux CD using a Linux system. When the Linux FTP server reads the CD, it will find the full directory and file contents and will serve them up. Using that technique you can transfer them to any other platform to be served up later.
I would be surprised if NFS will work when FTP does not.
Alan Altmark z/VM Development IBM Endicott
---------------------------------------------------------------------- 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
