We had a TCPIP performance issue when we upgraded from
OS/390 2.7 to 2.10. The conclusion of that the problem is attached
below (from an IBM ETR record).
This could be another lead to follow
... from looking at the trace and the dump, we see that
Optimal max segment size is 65,495 bytes,
I've successfully selected the vnc installation method and have loaded
the first bits using SMB from my PC's CD drive. The DASD have
been formatted and partitioned and I then get to the YaST2 Installation
Settings screen. But under the section 'Software' it gives the error: 'Not
enough disk space
Thanks to Alan Fargusson, Vic Cross, Taraka Srinivas Kumar.
Here I come in the morning and I have something
to clutch to :-)
I've selected SMB as the installation source.
Likely something is wrong with this although
I did not notice any error messages from the boot/
configuration setup via HMC.
Found the following error mesages in/var/log/linuxrc.log:
smbmount //10.192.99.66/CM227W38/EDRIVE /var/adm/mount -o
ro,ip=10.192.99.66,username=root,guest 2
SMB connection failed
INFO: Debug class all level = 1 (pid 227 from pid 227)
227: session request to 10.192.99.66 failed (Called name not
Thanks Srinivas and Allan:
http://portal.suse.com/sdb/en/2003/05/jreuter_sles8_yast_missing.html
This helped me to understand where I went astray.
I defined a user and pswd on the SMB host, re-run
/inst_source script and now the YaST works.
Thanks again
... Janek
I booted the first time SLES-8 in an lpar from CD1.
I can sign on as root via telnet ssh, however
I do not seem to be able to run YaST.
When I enter 'yast' command I'm getting:
-bash: yast: command not found
I've looked in the various install system directories
but it is not obvious where the
