>>> On 12/13/2010 at 01:30 AM, Bern VK2KAD <[email protected]> wrote: -snip- > I now want to try installing SLES so I used my RHEL herc.conf and just added > two mod9's at 130 and 131 and ipl'ed the SLES installer.
This isn't off-list, but if no one complains, we can keep it here. > I have an FTP server on another Ubuntu box (192.168.1.201) - it was used for > the RHEL install. > > As LCS isn't supported on SLES I have the following definition for my CTC in > herc. > > # networking, channel-to-channel adapter > 0600 3088 CTCI -n /dev/net/tun -t 1500 10.0.2.13 10.0.2.14 > 0601 3088 CTCI -n /dev/net/tun -t 1500 10.0.2.13 10.0.2.14 I have mine set up so that the two ends are in different subnets: 0500.2 3088 CTCI 192.168.2.1 192.168.1.2 > As I'm using a VirtualBox VM my Ubuntu 'host' has the IP address 10.0.2.15 -snip- > After starting the installer I get confused as to what is what!!! Having a picture of your network is always helpful. > I select FTP as the network protocol, my CTC device as the CTC with > read/write channels as 0.0.0600 and 0.0.0601 respectively. > > I chose "Extended Mode" as per the install guide., said "no" to the DHCP > question and then >>> > > My IP address I chose 10.0.2.13 as per the CTCI definition in the herc.conf > above. > For the PLIP partner I chose 10.0.2.15 (the IP address of my virtual host), OK, that's wrong. You have to specify the IP address that is on the other end of the CTC. According to your hercules.cnf file, that is 10.0.2.14. > same for the name server and for the FTP server I chose 192.168.1.201 which > is the ftp server in the 'other' box. This technique was OK for the RHEL > install using LCS. > > The ftp server doesn't need login so I'm expecting the installer will try > 'anonymous'. - I can get a clean ftp session from the 10.0.2.15 host to > 192.168.1.201 so connectivity looks good. But of course you need connectivity from the SLES instance all the way to the FTP server. You don't have that at this point. > Eventually the installer bails out as it can't find a repo - I'm stuck as to > how to debug this shemozzle. > > Any clues as to how to proceed ??? Typically, I wind up using tcpdump on all the systems involved in setups like this. That way I can tell just where packets are going or not, and whether they're coming back or not. I saw your other note that talked about trying to use the "fake 9336" method that Rick Troth discussed. I saw the same litany of apparent I/O errors you did, but at the end of it all, I was still able to mount the file system and read the DVD contents. You say you didn't know what to specify for the path to the DVD contents, so you chose "/". That's not going to work very well, unless you actually mounted the DVD image there, in which case you'll have hidden the contents of your entire ramdisk. Do a "mkdir /dvdmount" or something like that, mount the DVD there, and specify that to the installer. Mark Post ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
