Re: Putty security
Apart from a classic linux desktop with openssh, there is no better alternative than putty :) As an argument towards putty: - security fixes will be delivered JIT - broad user base Am 06.03.2013 21:29, schrieb Melancon, Ruddy: I have a security officer that has raised the issue regarding free [Putty] software. Has anyone encounterd security issues with Putty beyond the Release 0.60? I am looking for documented problems. I am also interested in what I could use as a fee based product to replace Putty. Ruddy Melancon zVM and Linux Support -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- Zentrum für Informationsverarbeitung und Informationstechnik (ZIVIT) - Betriebliches Architekturmanagement - Dienstsitz Bonn, An der Küppe 2, 53225 Bonn Telefon: +49-228/99-680-5199, Mobil: +49-172/2042527 Internet: http://www.zivit.de -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ 0xDD66C4B1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: SLES11SP2 Installation Problem
On Wed, Mar 06, 2013 at 03:11:39PM -0500, Michael MacIsaac wrote: mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso Is that an NFS mount? I'm not sure it's reading from /etc/exports and utilizing the NFS server daemon. Try this: # mount localhost:/dev/sr0 /tmp/iso That doesn't make sense. Loop-mount that ISO on the server and export the result. You cannot loop-mount block devices over NFS. Kind regards Philipp Kern -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ signature.asc Description: Digital signature
Re: SLES11SP2 Installation Problem
You cannot loop-mount block devices over NFS. So perhaps therein lies the problem. Perhaps the device has to first be converted into a .iso file? There's an example with dd in section 4.3.1 of the latest Virtualization Cookbook: http://www.vm.ibm.com/devpages/mikemac/CKB-VM62.PDF Mike MacIsaac mikemac at-sign us.ibm.com -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Mauro Souza A good way to know is running a showmount -e on the laptop. If it returns the contents of your /etc/exports, we have to think about what else could possibly be wrong. If don't, look on dmesg or /var/log/messages to see any informative error messages. [root@localhost ~]# showmount -e Export list for localhost.localdomain: /tmp/iso * [root@localhost ~]# cat /etc/exports /tmp/iso *(ro,no_root_squash) [root@localhost ~]# Then: [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. According to my notes, except for trying 'localhost:' in the mount command, this is the exact procedure we used to install RHEL about three weeks ago. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Just for grins, after you do the mount, run 'exportfs -a' to force the exports list to be updated. [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
[root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# Just for clarity, this part is on he laptop, yes? So the localhost: implies that the laptop is mounting *from* NFS (ie: client). It's not. It wants the CD. The vers=3 also implies NFS (client). Then you get mount.nfs: access denied, so yeah, the laptop things it is importing an NFS filesystem. It's not. If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. Perfect. So do that. NOTE: You may also need an 'exportfs -a' after mounting the CD. Your laptop, being the NFS server, needs to serve out the contents of the CD, not the empty directory over which it got mounted. VERY LIKELY, there was an exportfs operation before you mounted the CD, so your NFS server code still sees that empty directory. NOW ... to the installation end. You should be able to (from a shell) ... mkdir /tmp/testit mount thelaptop:/tmp/iso /tmp/testit What happens from that? -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of David Boyes Just for grins, after you do the mount, run 'exportfs -a' to force the exports list to be updated. [root@localhost ~]# exportfs -a exportfs: /tmp/iso requires fsid= for NFS export [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# Perhaps the access denied message (below) has something to do with this? [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
[root@localhost ~]# exportfs -a exportfs: /tmp/iso requires fsid= for NFS export [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# Perhaps the access denied message (below) has something to do with this? It does indeed, but it's not the problem you're looking for. First step is to get the CD/DVD mounted on the right mountpoint on the NFS server (that's a physical device mount on the machine in question, so the localhost: syntax isn't usable -- you're not using the network for this step, it's a local device on a local mountpoint). Once the DVD is mounted, then you tell the NFS server to reparse /etc/exports using 'exportfs -a'. It doesn't automatically do this if something changes (in order to make NFS server configuration processing atomic; you might want to make a bunch of changes and then commit the export after you're all done messing around), and most NFS servers won't export an empty mountpoint, even if it is configured in /etc/exports) Is there any reason why you're not putting all the mount options in /etc/exports (that's what's in the parens)? You *will* forget one, and be very confused why it doesn't work -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth [root@localhost ~]# systemctl start nfs.service [root@localhost ~]# mkdir /tmp/iso [root@localhost ~]# mount -o ro,vers=3,nolock localhost:/dev/sr0 /tmp/iso mount.nfs: access denied by server while mounting localhost:/dev/sr0 [root@localhost ~]# Just for clarity, this part is on he laptop, yes? Yes. So the localhost: implies that the laptop is mounting *from* NFS (ie: client). It's not. It wants the CD. The vers=3 also implies NFS (client). Then you get mount.nfs: access denied, so yeah, the laptop things it is importing an NFS filesystem. It's not. If I omit 'localhost:' from the mount command, the mount works; in that no hate mail is returned and I can then cd to /tmp/iso and ls the contents of the DVD. But then the SLES install program running on z/VM can't find the repository. Perfect. So do that. Done. NOTE: You may also need an 'exportfs -a' after mounting the CD. Done. Your laptop, being the NFS server, needs to serve out the contents of the CD, not the empty directory over which it got mounted. VERY LIKELY, there was an exportfs operation before you mounted the CD, so your NFS server code still sees that empty directory. NOW ... to the installation end. You should be able to (from a shell) ... mkdir /tmp/testit mount thelaptop:/tmp/iso /tmp/testit What happens from that? [root@localhost ~]# mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso [root@localhost ~]# exportfs -a [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# mkdir /tmp/testit [root@localhost ~]# mount localhost:/tmp/iso /tmp/testit wait about two minutes ^C [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Try the -v flag on your mount. Perhaps verbose will give a clue of why it is hanging. The information contained in this e-mail message is intended only for the personal and confidential use of the designated recipient(s) named above. This message may be an attorney-client or work product communication which is privileged and confidential. It may also contain protected health information that is protected by federal law. If you have received this communication in error, please notify us immediately by telephone and destroy (shred) the original message and all attachments. Any review, dissemination, distribution or copying of this message by any person other than the intended recipient(s) or their authorized agents is strictly prohibited. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... [root@localhost ~]# mount -o ro,vers=3,nolock /dev/sr0 /tmp/iso [root@localhost ~]# exportfs -a [root@localhost ~]# cat /etc/exports /tmp/iso*(ro,no_root_squash) [root@localhost ~]# mkdir /tmp/testit [root@localhost ~]# mount localhost:/tmp/iso /tmp/testit wait about two minutes ^C [root@localhost ~]# Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Veencamp, Jonathon D. Try the -v flag on your mount. Perhaps verbose will give a clue of why it is hanging. [root@localhost ~]# mount -v localhost:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:26:19 2013 mount.nfs: trying text-based options 'vers=4,addr=127.0.0.1,clientaddr=127.0.0.1' three minutes after timeout expired ^C [root@localhost ~]# -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. -jc- -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Replying to myself -Original Message- -Original Message- From: Linux on 390 Port On Behalf Of Rick Troth Looks like part of the problem is that both ends call themselves localhost. DO NOT use localhost for the NFS mount (unless you really want to NFS mount something served back to the same box, clearly not this case). ... Maybe try mounting by IP address. mount 192.168.55.44:/tmp/iso /tmp/testit ... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. Here's what I get on the SLES install program on z/VM: / # mount 10.250.24.67:/tmp/iso /tmp/testit / # ls -l /tmp/testit drwxr-xr-x2 00 40 Mar 7 16:45 . drwxrwxrwt3 00 60 Mar 7 16:45 .. / # ls -l 10.250.24.67:/tmp/iso 10.250.24.67:/tmp/iso: No such file or directory / # -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
... replacing 192.168.55.44 with the address of the laptop. [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# I often get timeout (or never-completing mount) when some magical part of the RPC suite hasn't been started. The server will need at least 'rpc.mountd'. I think the client will need 'rpc.statd'. (I confess to not retaining these details.) Both are likely to need 'rpcbind'. In case you're assuming I have two machines, I have only the one Linux laptop, on which I've tried all suggestions so far. Yes, I was assuming that. Sorry to have missed that part. NFS mounting this content back on the laptop (from which it is served out) DOES answer the question if the NFS server software is working. Otherwise, it's not all that useful. Should I be trying these mount commands from another machine, e.g. the SLES install program on z/VM? I could also use one of the RHEL identities on z/VM. Yes. As I recall, you're using this media hosted on the laptop to effect an install hosted on VM. So you'll eventually want an NFS client mount on the SLES installation target end. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
Hang in there, John. This will eventually work. Here's what I get on the SLES install program on z/VM: / # mount 10.250.24.67:/tmp/iso /tmp/testit / # ls -l /tmp/testit drwxr-xr-x2 00 40 Mar 7 16:45 . drwxrwxrwt3 00 60 Mar 7 16:45 .. The mount command on the SLES inst side appears to succeed. That's a good sign. But the content of that directory is still empty. Not so good. Did you do the 'exportfs' on the laptop after mounting the CD there? / # ls -l 10.250.24.67:/tmp/iso 10.250.24.67:/tmp/iso: No such file or directory / # The 10.250.24.67:/tmp/iso syntax is only useful as the object of an NFS (client) mount. 'ls' doesn't know what to do with it, so treats it like a local file which turns out to not exist. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: Suspicious URL:Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth [ snip ] I often get timeout (or never-completing mount) when some magical part of the RPC suite hasn't been started. The server will need at least 'rpc.mountd'. I think the client will need 'rpc.statd'. (I confess to not retaining these details.) Both are likely to need 'rpcbind'. The systemctl command shows that rpcbind.service is running, but the others are not. It also shows nfs-mountd.service as failed (did not notice that before). There does not appear to be an rpc.mountd or rpc.statd in Fedora 18. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
SLES10 SP4 to SLES11 SP2 upgrade issue
We made it to SLES11 and at point of patching Have hit an issue in that script uses YaST2 Perhaps an export DISPLAY issue Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Anyone else hit this issue going to SLES11? Ann Sm This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
No, but I used VNC instead. Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Smith, Ann (CTO Service Delivery) Sent: Thursday, March 07, 2013 10:54 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] SLES10 SP4 to SLES11 SP2 upgrade issue We made it to SLES11 and at point of patching Have hit an issue in that script uses YaST2 Perhaps an export DISPLAY issue Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Anyone else hit this issue going to SLES11? Ann Sm This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
On 3/7/2013 at 11:42 AM, Chase, John jch...@ussco.com wrote: [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# OK, this clearly indicates that your NFS server isn't working right. So rather than try to figure out why, lets come at this from a different angle. Do the various firewalls between your mainframe and your laptop allow FTP, HTTP, or even SMB traffic to flow. If so, use one of those. HTTP is the easiest to diagnose problems with, followed by FTP, SMB and NFS. The other option would be to download and install the SUSE Linux Starter System, and replace the contents of the installation directory with what's on your SLES11 SP2 DVD. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
On Thu, Mar 7, 2013 at 2:40 PM, Mark Post mp...@suse.com wrote: On 3/7/2013 at 11:42 AM, Chase, John jch...@ussco.com wrote: [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# OK, this clearly indicates that your NFS server isn't working right. So rather than try to figure out why, lets come at this from a different angle. Do the various firewalls between your mainframe and your laptop allow FTP, HTTP, or even SMB traffic to flow. If so, use one of those. HTTP is the easiest to diagnose problems with, followed by FTP, SMB and NFS. The other option would be to download and install the SUSE Linux Starter System, and replace the contents of the installation directory with what's on your SLES11 SP2 DVD. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ Hello! Mark is right of course, but a completely crazy thought occurred to me earlier. About your laptop, did you have a chance to configure both a unique user name, and a machine name? That might be confusing the NFS process. If all else, would it be possible to use that starter system to create an image that could be used as a mount point to create those images that our correspondent could use to create others? Including the one that's concerning this discussion. - Gregg C Levine gregg.drw...@gmail.com This signature fought the Time Wars, time and again. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Mark Post On 3/7/2013 at 11:42 AM, Chase, John jch...@ussco.com wrote: [root@localhost ~]# mount -v 10.250.24.67:/tmp/iso /tmp/testit mount.nfs: timeout set for Thu Mar 7 10:34:01 2013 mount.nfs: trying text-based options 'vers=4,addr=10.250.24.67,clientaddr=10.250.24.67' ... ^C [root@localhost ~]# OK, this clearly indicates that your NFS server isn't working right. Here's another new wrinkle: Previously, from the SLES install system on z/VM it appeared that the mount command worked. I just tried it again with the -v flag, and got this: /tmp/testit # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: invalid number of arguments But man mount (on Fedora, anyway) indicates only two arguments are needed: filesystem id and mount point. What's different about SLES? -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
Here's another new wrinkle: Previously, from the SLES install system on z/VM it appeared that the mount command worked. I just tried it again with the -v flag, and got this: /tmp/testit # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: invalid number of arguments Command looks good. On both SLES and OpenSUSE, I get (roughly) ... # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Thu Mar 7 12:19:36 2013 mount.nfs: text-based options: 'addr=10.250.24.67' ... HOWEVER, I recommend not being in the directory where you're about to mount something. (Various possibilities w/r/t what would happen, more than you probably want to know.) -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
myhostname is a vmware session running Windows XP Only have PuTTY for access No longer allowed to use Hummingbird Exceed Xwindows -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 2:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Rick Troth Here's another new wrinkle: Previously, from the SLES install system on z/VM it appeared that the mount command worked. I just tried it again with the -v flag, and got this: /tmp/testit # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: invalid number of arguments Command looks good. On both SLES and OpenSUSE, I get (roughly) ... # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Thu Mar 7 12:19:36 2013 mount.nfs: text-based options: 'addr=10.250.24.67' ... HOWEVER, I recommend not being in the directory where you're about to mount something. (Various possibilities w/r/t what would happen, more than you probably want to know.) OK, changed back to root directory; same result. No clue what a valid number of arguments might be. -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
I seem to recall another option is to use the DVD drive on your Hardware Management Console. And with SLES at least, I also think we could use FTP as an installation source. It might be quicker for you to get that going than to continue to bang your head on NFS. But it's been a few years, so I could be mixed up. The information contained in this e-mail message is intended only for the personal and confidential use of the designated recipient(s) named above. This message may be an attorney-client or work product communication which is privileged and confidential. It may also contain protected health information that is protected by federal law. If you have received this communication in error, please notify us immediately by telephone and destroy (shred) the original message and all attachments. Any review, dissemination, distribution or copying of this message by any person other than the intended recipient(s) or their authorized agents is strictly prohibited. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
myhostname is a vmware session running Windows XP Sounds good. Should be fine. Only have PuTTY for access PuTTY can do the X tunneling. (X tunneling is a special case of tunneling via SSH, supported by most SSH clients, including PuTTY.) No longer allowed to use Hummingbird Exceed Xwindows There are others. XMing is my current favorite (and it's no charge). Another good one (also free) is Cygwin/X. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
Providing more detail Upgrade to sles11 works and reboot of server- but maintenance not done Get message: *** sshd has been started *** You can login now and proceed with the installation Run the command '/usr/lib/YaST2/startup/YaST2.ssh' When enter the command get *** Starting YaST2 *** Terminate called after throwing an instance of 'YUIException' what(): Can't open display YaST got signal 6 at YCP file Wizard.ycp:36 /usr/lib/YaST2/startup/YaST2.call: line 511: 10647 Aborted FBITERM y2base $Y2_MODULE_NAME $Y2_MODE_FLAGS $Y2_MODULE_ARGS ARGS Continue with booting ... You can login with the (new) root password or the Newly created user account in a few seconds ... (/root) Ready(0)# -Original Message- From: Smith, Ann (CTO Service Delivery) Sent: Thursday, March 07, 2013 3:27 PM To: 'Linux on 390 Port' Subject: RE: SLES10 SP4 to SLES11 SP2 upgrade issue myhostname is a vmware session running Windows XP Only have PuTTY for access No longer allowed to use Hummingbird Exceed Xwindows -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 2:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
-Original Message- From: Linux on 390 Port On Behalf Of Veencamp, Jonathon D. I seem to recall another option is to use the DVD drive on your Hardware Management Console. Not a viable option: Our machine room is remote, and we haven't set up a local HMC yet. And with SLES at least, I also think we could use FTP as an installation source. It might be quicker for you to get that going than to continue to bang your head on NFS. Might be worth a try. But I'm a stubborn old pheart and don't like giving in to a dumb machine, even though there aren't any more hard spots on the wall. :-) Time to hit the road for the day, and give the wall time to recover some hardness. :-) -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
Taking a step back ... I've been thinking just about trying to get X working (since YaST2 will need that). There are other ways to get the maint finished. Marcy mentioned VNC. Do you know if a VNC server was started on the upgraded system? If so, then it might be wwwaaayyy easier just to use that (than to get X talking). In the VNC case, X is totally local (to the upgraded system). Your X DISPLAY variable would be set to :0 or to localhost:0. You would then use a VNC client/viewer. Are you familiar with this? On Thu, Mar 7, 2013 at 4:09 PM, Smith, Ann (CTO Service Delivery) ann.sm...@thehartford.com wrote: Providing more detail Upgrade to sles11 works and reboot of server- but maintenance not done Get message: *** sshd has been started *** You can login now and proceed with the installation Run the command '/usr/lib/YaST2/startup/YaST2.ssh' When enter the command get *** Starting YaST2 *** Terminate called after throwing an instance of 'YUIException' what(): Can't open display YaST got signal 6 at YCP file Wizard.ycp:36 /usr/lib/YaST2/startup/YaST2.call: line 511: 10647 Aborted FBITERM y2base $Y2_MODULE_NAME $Y2_MODE_FLAGS $Y2_MODULE_ARGS ARGS Continue with booting ... You can login with the (new) root password or the Newly created user account in a few seconds ... (/root) Ready(0)# -Original Message- From: Smith, Ann (CTO Service Delivery) Sent: Thursday, March 07, 2013 3:27 PM To: 'Linux on 390 Port' Subject: RE: SLES10 SP4 to SLES11 SP2 upgrade issue myhostname is a vmware session running Windows XP Only have PuTTY for access No longer allowed to use Hummingbird Exceed Xwindows -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 2:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
I did have trouble with ssh -X Tried ssh -X myhostname and my IP address (/root) Ready(0)# ssh -X myhostname ssh: Could not resolve hostname myhostname: Name or service not known (/root) Ready(255)# ssh -X xxx.xxx.xxx.xxx ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused (/root) Ready(255)# I am not familiar with vnc but having no luck with what we are trying now:) Is there a SLES11 upgrade doc with vnc method? Annie -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 4:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Taking a step back ... I've been thinking just about trying to get X working (since YaST2 will need that). There are other ways to get the maint finished. Marcy mentioned VNC. Do you know if a VNC server was started on the upgraded system? If so, then it might be wwwaaayyy easier just to use that (than to get X talking). In the VNC case, X is totally local (to the upgraded system). Your X DISPLAY variable would be set to :0 or to localhost:0. You would then use a VNC client/viewer. Are you familiar with this? On Thu, Mar 7, 2013 at 4:09 PM, Smith, Ann (CTO Service Delivery) ann.sm...@thehartford.com wrote: Providing more detail Upgrade to sles11 works and reboot of server- but maintenance not done Get message: *** sshd has been started *** You can login now and proceed with the installation Run the command '/usr/lib/YaST2/startup/YaST2.ssh' When enter the command get *** Starting YaST2 *** Terminate called after throwing an instance of 'YUIException' what(): Can't open display YaST got signal 6 at YCP file Wizard.ycp:36 /usr/lib/YaST2/startup/YaST2.call: line 511: 10647 Aborted FBITERM y2base $Y2_MODULE_NAME $Y2_MODE_FLAGS $Y2_MODULE_ARGS ARGS Continue with booting ... You can login with the (new) root password or the Newly created user account in a few seconds ... (/root) Ready(0)# -Original Message- From: Smith, Ann (CTO Service Delivery) Sent: Thursday, March 07, 2013 3:27 PM To: 'Linux on 390 Port' Subject: RE: SLES10 SP4 to SLES11 SP2 upgrade issue myhostname is a vmware session running Windows XP Only have PuTTY for access No longer allowed to use Hummingbird Exceed Xwindows -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 2:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
I'm curious, why do you NEED X to do maint? I do all our manual maintenance in Yast2 via Putty. There are a few things you can't do in non-graphical (like mark a patch taboo), but otherwise it's almost all there. Also, You really might want to try VNC. If you don't have a vnc client, or know how to get started, just start vnc1 and vnchttpd1 services in xinetd and point your browser at http://hostname:5801 and you have a graphical desktop. You can get at Xinetd config via putty yast2 xinetd. The information contained in this e-mail message is intended only for the personal and confidential use of the designated recipient(s) named above. This message may be an attorney-client or work product communication which is privileged and confidential. It may also contain protected health information that is protected by federal law. If you have received this communication in error, please notify us immediately by telephone and destroy (shred) the original message and all attachments. Any review, dissemination, distribution or copying of this message by any person other than the intended recipient(s) or their authorized agents is strictly prohibited. Thank you. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
On 3/7/2013 at 03:14 PM, Chase, John jch...@ussco.com wrote: /tmp/testit # mount -v 10.250.24.67:/tmp/iso /tmp/testit mount: invalid number of arguments But man mount (on Fedora, anyway) indicates only two arguments are needed: filesystem id and mount point. What's different about SLES? It's not SLES, per se, it's the installation system. To keep that small, dumber versions of some commands are used that don't accept all the options the installed versions do. On Inte/AMD systems, a package called busybox is frequently used for the same purpose. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
On 3/7/2013 at 03:14 PM, Chase, John jch...@ussco.com wrote: Here's another new wrinkle: Previously, from the SLES install system on z/VM it appeared that the mount command worked. It didn't actually work, it just didn't complain. Remember that commands in the installation system are supposed to be called by YaST. The YaST developers are familiar with the limitations of these commands, and put other checks in to see if they work. Such as whether certain files are found after the mount command is executed. You really need to fix the NFS server on your laptop or try a different network protocol. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
On 3/7/2013 at 04:29 PM, Veencamp, Jonathon D. jdveenc...@fedins.com wrote: I'm curious, why do you NEED X to do maint? I do all our manual maintenance in Yast2 via Putty. There are a few things you can't do in non-graphical (like mark a patch taboo), but otherwise it's almost all there. As you yourself noted, it's not necessary. But, some people like the GUI versus the ncurses interface. Since my network connections to our mainframe are transatlantic, I prefer ncurses, simply because trying to use X (or even VNC at times) is excruciating. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
In this case the upgrade process script is calling YaST2 Perhaps because we chose the ssh method rather than vnc in original parm file I have used YaST2 for a few years and do like it It was nice and easy for doing hipersockets though yast maybe is as well vnc method may have required installing a product in my vmware Open source not allowed and only certain approved products allowed PuTTY is allowed so opted to try ssh method (silly us) Don't know why the install process is invoking YaST2 rather than yast Annie Smith -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post Sent: Thursday, March 07, 2013 5:52 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue On 3/7/2013 at 04:29 PM, Veencamp, Jonathon D. jdveenc...@fedins.com wrote: I'm curious, why do you NEED X to do maint? I do all our manual maintenance in Yast2 via Putty. There are a few things you can't do in non-graphical (like mark a patch taboo), but otherwise it's almost all there. As you yourself noted, it's not necessary. But, some people like the GUI versus the ncurses interface. Since my network connections to our mainframe are transatlantic, I prefer ncurses, simply because trying to use X (or even VNC at times) is excruciating. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
On 3/7/2013 at 06:03 PM, Smith, Ann (CTO Service Delivery) ann.sm...@thehartford.com wrote: In this case the upgrade process script is calling YaST2 /sbin/yast is simply a symbolic link to /sbin/yast2. /sbin/yast2 is a bash script that tries to figure out whether to run in ncurses mode or GUI mode depending on a number of things it checks on the installed system. Perhaps because we chose the ssh method rather than vnc in original parm file That is exactly what I do all the time, so that's not your problem. -snip- vnc method may have required installing a product in my vmware If your firewalls allow access to port 5801, you can use any Java-enabled web browser for the VNC install. (Not that having a Java-enabled browser is a very good idea these days, but that's a different topic.) -snip- PuTTY is allowed so opted to try ssh method (silly us) Not at all. As I said, that's what I do most of the time. It does work, we just have to figure out why not for you. Don't know why the install process is invoking YaST2 rather than yast That is the question. If you look at /usr/lib/YaST2/startup/YaST2.ssh, it's just a shell script that checks a few things, and then makes this call: /usr/lib/YaST2/startup/YaST2.call installation continue That is also a shell script, which means that you can invoke it directly (without going through the YaST2.ssh script) this way: sh -x /usr/lib/YaST2/startup/YaST2.call installation continue Do that and send me the output off-list. I'll see if I can figure out what's going on in your case. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES11SP2 Installation Problem
I did my first zlinux install using FTP from a filezIlla server running on my laptop. It was a fast connection on same LAN. -Original Message- From: Linux on 390 Port On Behalf Of Veencamp, Jonathon D. I seem to recall another option is to use the DVD drive on your Hardware Management Console. Not a viable option: Our machine room is remote, and we haven't set up a local HMC yet. And with SLES at least, I also think we could use FTP as an installation source. It might be quicker for you to get that going than to continue to bang your head on NFS. Might be worth a try. But I'm a stubborn old pheart and don't like giving in to a dumb machine, even though there aren't any more hard spots on the wall. :-) Time to hit the road for the day, and give the wall time to recover some hardness. :-) -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- -- Bruce -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
Okay, I just have to add my 2 cents. :-) Doesn't seem like you can use X there, so don't try to force it. We just upgraded ~230 servers without using X or VNC. We used the good old ncurses interface. I have to admit that these upgrades were completely automated and the script accessed the upgrading guest via ssh from another zLinux guest. However, if you're up for trying it... Make sure X11 forwarding is disabled in your ssh client. After connecting to the target guest, make sure the DISPLAY variable is NOT set: unset DISPLAY Then try the /usr/lib/YaST2/startup/YaST2.ssh command. Not saying this will work for you, but if you have the time, patience, and you don't mind the ncurses interface... Leland On Thu, Mar 7, 2013 at 3:09 PM, Smith, Ann (CTO Service Delivery) ann.sm...@thehartford.com wrote: Providing more detail Upgrade to sles11 works and reboot of server- but maintenance not done Get message: *** sshd has been started *** You can login now and proceed with the installation Run the command '/usr/lib/YaST2/startup/YaST2.ssh' When enter the command get *** Starting YaST2 *** Terminate called after throwing an instance of 'YUIException' what(): Can't open display YaST got signal 6 at YCP file Wizard.ycp:36 /usr/lib/YaST2/startup/YaST2.call: line 511: 10647 Aborted FBITERM y2base $Y2_MODULE_NAME $Y2_MODE_FLAGS $Y2_MODULE_ARGS ARGS Continue with booting ... You can login with the (new) root password or the Newly created user account in a few seconds ... (/root) Ready(0)# -Original Message- From: Smith, Ann (CTO Service Delivery) Sent: Thursday, March 07, 2013 3:27 PM To: 'Linux on 390 Port' Subject: RE: SLES10 SP4 to SLES11 SP2 upgrade issue myhostname is a vmware session running Windows XP Only have PuTTY for access No longer allowed to use Hummingbird Exceed Xwindows -Original Message- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Rick Troth Sent: Thursday, March 07, 2013 2:57 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 SP4 to SLES11 SP2 upgrade issue Lots of tips/tricks here. If you already know, please excuse me. Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Be sure that myhostname is running an X server. (Is it your PC? Do you have one of the X server programs for Windows? Or maybe it's running Linux?) Also be sure that X traffic is not blocked. BETTER ... use X via SSH tunnel. From a system with working X windows, run a command like ... ssh -X yourSLES11system ... and then 'xterm' from there (to confirm it works). If you follow the usual rules about not signing on as root, you may have additional tricks to pull. We'll cross that bridge once you have X display working. -- -- R; -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: SLES10 SP4 to SLES11 SP2 upgrade issue
Make sue you started an X server on you PC and make sure X11forwarding is enabled prior to logging in. On Mar 7, 2013 12:54 PM, Smith, Ann (CTO Service Delivery) ann.sm...@thehartford.com wrote: We made it to SLES11 and at point of patching Have hit an issue in that script uses YaST2 Perhaps an export DISPLAY issue Tried issuing 'export DISPLAY=myhostname:0.0' and 'echo $DISPLAY' to see it took But when I issue YaST2 get the message below: Cannot open display Anyone else hit this issue going to SLES11? Ann Sm This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
