-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
On 3/8/2013 at 05:12 PM, Chase, John jch...@ussco.com wrote:
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
-snip-
I would use this in my parmfile:
On 3/8/2013 at 05:12 PM, Chase, John jch...@ussco.com wrote:
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
-snip-
I would use this in my parmfile:
install=ftp://ip.address.of.server/pub/
Or, if you haven't exploded the contents of the .iso file:
-Original Message-
From: Linux on 390 Port On Behalf Of Bruce Furber
I did my first zlinux install using FTP from a filezIlla server running on my
laptop. It was a fast
connection on same LAN.
OK, as of this morning I'm throwing in the towel on trying to install via
nfs. There's
Hi, John.
You will need to change the Install= parameter to specify a FTP URL
instead of an nfs URL.
The format of an ftp: url is:
ftp://user:password@host:port/path
I think that is self-explanatory, but the full details can be found here:
http://www.cs.tut.fi/~jkorpela/ftpurl.html
Good
On 3/8/2013 at 10:46 AM, Chase, John jch...@ussco.com wrote:
Here's the current specification for the Install= parm in the PARM-S11 file
on z/VM:
Install=nfs://10.250.24.67/var/nfs/sles/iso/SLES-11-SP2-DVD-s390x-GM-DVD1.is
o
To try via ftp, what do I need to change besides the obvious
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
[ snip ]
The only other things you need to worry about are:
1. Whether you're going to be using anonymous FTP, or have to provide a
userid and password 2. The
directory the FTP daemon puts you when you connect.
On 3/8/2013 at 12:13 PM, Chase, John jch...@ussco.com wrote:
Well, here we go again. After getting to the Could not find ... message, I
opened a shell session on the SLES installation program:
7
/ # ftp 10.250.24.67
bash: ftp: command not found
/ #
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
On 3/8/2013 at 12:13 PM, Chase, John jch...@ussco.com wrote:
Well, here we go again. After getting to the Could not find ...
message, I opened a shell session on the SLES installation program:
7
/ # ftp
On 3/8/2013 at 03:26 PM, Chase, John jch...@ussco.com wrote:
Thanks. Using vsftpd but still need to do some configuration work on it.
Looks like user 'anonymous' is chroot-jailed somewhere. Its working
directory at login shows as /; an ls -l command shows only a directory
named pub.
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
On 3/8/2013 at 03:26 PM, Chase, John jch...@ussco.com wrote:
Thanks. Using vsftpd but still need to do some configuration work on it.
Looks like user 'anonymous' is chroot-jailed somewhere. Its working
On 3/8/2013 at 04:32 PM, Chase, John jch...@ussco.com wrote:
Found it to be /var/ftp. Copied the SLES11SP2 .iso file to /var/ftp/pub,
verified that it's reachable via anonymous ftp from a Windows box, then tried
almost every permutation of the install path according to the format
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
On 3/8/2013 at 04:32 PM, Chase, John jch...@ussco.com wrote:
Found it to be /var/ftp. Copied the SLES11SP2 .iso file to
/var/ftp/pub, verified that it's reachable via anonymous ftp from a
Windows box, then tried
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
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
-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
-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
-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
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
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
Hi, All,
Trying to install SLES 11 SP 2 on z/VM 6.2, using a laptop running Fedora 18 as
the NFS, and loading from a real DVD (not an iso image file). Unfortunately,
we get only to this point:
*** Could not find the SUSE Linux Enterprise Server 11 Repository.
Activating manual setup program.
On 3/6/2013 at 01:39 PM, Chase, John jch...@ussco.com wrote:
Hi, All,
Trying to install SLES 11 SP 2 on z/VM 6.2, using a laptop running Fedora 18
as the NFS, and loading from a real DVD (not an iso image file).
Unfortunately, we get only to this point:
*** Could not find the SUSE
JC,
using a laptop running Fedora 18 as the NFS, and loading from a real
DVD (not an iso image file).
Were you able to mount the NFS export locally (on the Fedora box) using
localhost?
And if so, were you able to 'cd' into that directory, then 'cd suse' and
see the RPMs?
Mike MacIsaac mikemac
-Original Message-
From: Linux on 390 Port On Behalf Of Michael MacIsaac
JC,
using a laptop running Fedora 18 as the NFS, and loading from a real
DVD (not an iso image file).
Were you able to mount the NFS export locally (on the Fedora box) using
localhost?
Yes: mount -o
JC,
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
Mike MacIsaac mikemac at-sign us.ibm.com
-Original Message-
From: Linux on 390 Port On Behalf Of Mark Post
On 3/6/2013 at 01:39 PM, Chase, John wrote:
Hi, All,
Trying to install SLES 11 SP 2 on z/VM 6.2, using a laptop running
Fedora 18 as the NFS, and loading from a real DVD (not an iso image file).
On 3/6/2013 at 03:16 PM, Chase, John jch...@ussco.com wrote:
I configured the SLES install url as nfs://10.250.24.63/tmp/iso (that's
where the DVD is mounted). Should that have been specified as
nfs://10.250.24.63/tmp/iso/suse ?
No, you had it right the first time. You want the directory
On 3/6/2013 at 03:47 PM, Chase, John jch...@ussco.com wrote:
-Original Message-
From: Linux on 390 Port On Behalf Of Michael MacIsaac
JC,
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
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.
Mauro
http://mauro.limeiratem.com - registered
47 matches
Mail list logo
