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
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.
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
-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
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
[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,
-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
[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
-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
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
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
-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
-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
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
... 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
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
-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
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
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
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
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
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
-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
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
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:
-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
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
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
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 ***
-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
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
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)
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
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
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
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
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
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
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
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
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
41 matches
Mail list logo
