Well, great progress. Via NFS, I loaded the RAM drive for the installation and loaded the contents of CD1. However, I couldn't do anything with CD2.
I got the message to load CD 2 On the Linux laptop, I "umount" the device. Put the next CD in and "mount" the device. Responded to the CD switch message.
I got "something not found" (I forget if it initially said "directory not found" or "file not found"). I clicked on "details" and the path was "/media/cdrecorder/" I'ved tried adding on "suse" subdirectory as well as "s390" subdirectory. Couldn't get past this point.
I burned another CD2 (which is CD1 of Suse with the first CD being CD1 SLES) and got the same thing.
So, what is the trick?
BTW, as a side note, my consoles are via Dialup. Ever try using ssh over dialup? Half hour for a full screen update. I went to a Windows PC and dialed in and used tightvnc. What a difference! When I'm at the office, you don't really see much a difference in local performance. But dial up shows a lot of things.
Tom Duerbusch THD Consulting (will never use yast over ssh over dialup again, if it is within my power not too)
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Tom Duerbusch Sent: Thursday, December 23, 2004 11:03 PM To: [email protected] Subject: Linux install via NFS
Slowly I'm moving to the modern world, that is one without Windows.
Historically, I've installed Suse (7.3 and 8.0) using SMB from Windows/2000. That still works. But there seems to be a problem with the current Suse 9.0. I've opened a support issue, but it seems to be paced at one email exchange a day. Kind of slow process.
So, it is time to use a different install process. Like NFS.
Initially, I was trying to setup an install where I used the CD drive on my Suse 9.0 laptop as the installation source. When I was at work, and on the local network, the installation would accept the node (PC) as the source, but I couldn't figure out what "directory" it was looking for.
On the laptop, the CD drive is /media/cdrecorder and I think the install directory on the CD is /suse/s390. But the install process kept saying that it didn't have permissions. I had read and write specified for the CD for all three types of users (I believe that is called 666...right?)
But now, I'm working from home over the holidays. I have a static IP address that I can ping to from the mainframe.
I seem to have the PC setup as a valid NFS server. I have a desktop (Suse 8.0) that can mount the share on the laptop without any problem (but all from within my firewall).
So I tried, from a Suse 8.0 image that I have running under VM to get my NFS share. I couldn't. I can ping, but couldn't get the share (no permissions). I disabled everything on my firewall (a 2Wire firewall) and get the same problem.
Friday, I'll try to install vial NFS, but I expect the same problem. (I punch the install files to the rdr and the files currently exist up in CMS.)
I think everything should be straight forward, but since I'm facing the holidays and some of the knowledge base may not be online, I thought I better check to see if there are any "tricks" that are not intuitive to me at this point.
Merry Christmas (or comparable greeting for your belief) Tom Duerbusch
---------------------------------------------------------------------- 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
