Mark,
I can mount either one, using a command like this:
mount -o nolock -o vers=3 ipaddress:/install/penguin/SLES/sles12sp2/dvd1 /nfs
The contents of the dvd1 folder:
LXTS12T2:/nfs # ls -l
total 25952
-r--r--r-- 1 root root 5486315 Jun 13 18:50 ARCHIVES.gz
-r--r--r-- 1 root root 1484 J
That's all dependent on the server and software you use for FTP ... it
you keep FTP confined to a users /home directory - that's what you get..
it may be set up differently depending on what flavor of ftp and how it's
configured. ( and what security is in place).
Scott Rohling
On Thu, Jul 20, 2
On 07/19/2017 06:06 PM, Julie Phinney wrote:
One person said they created a symbolic link to the mounted .iso in the ftp
user's home directory.
I was able to get this to work.
I could not get SLES12SP2 to FTP install unless the .iso was mounted on a
mount point in the FTP user's home directo
>>> On 7/20/2017 at 02:19 PM, Julie Phinney wrote:
> Thanks Mauro, Mark, Alan and everyone..
>
> Mark,
> My parm file has these lines:
> Install=nfs://ipaddress/install/penguin/SLES/sles12sp2/dvd1
> UseSSH=1 SSHPassword=12345678 upgrade=1 nfsopts=tcp,vers=3,nolock
And what are the contents of /
Thanks Mauro, Mark, Alan and everyone..
Mark,
My parm file has these lines:
Install=nfs://ipaddress/install/penguin/SLES/sles12sp2/dvd1
UseSSH=1 SSHPassword=12345678 upgrade=1 nfsopts=tcp,vers=3,nolock
The /etc/exports on the nfs server has this line:
/install/penguin -vers=3,sec=sys:none,rw
And
>>> On 7/19/2017 at 06:06 PM, Julie Phinney wrote:
> Back in April you all talked about a problem someone had installing SLES12
> sp2, zvm 6.4, using FTP.
> Several people recommended burning the iso to dvd and installing from that.
> One person said they created a symbolic link to the mounted
>>> On 7/20/2017 at 10:15 AM, Mauro Souza wrote:
> SLES11 worked fine with FTP, if I am not mistaken. SLES12 don't.
That's just not true. I mostly use FTP in my testing, and it worked just fine
for me, every time. You have to make sure you understand how the FTP server is
set up, and whether
Yes Alan, I know and agree, and I already got scolded by Mark the last time
I said so.
But I don't think most of us work on an environment where "let's try again,
file a bug report, send the logs, and install AFTER the fix is available"
is something possible. Or let's just reinstall a dummy machin
On Thursday, 07/20/2017 at 02:16 GMT, Mauro Souza
wrote:
> SLES11 worked fine with FTP, if I am not mistaken. SLES12 don't.
>
> We gave up on FTP and used HTTP on the repositories. FTP implementation
on
> yast is buggy right now, and it's way faster to just enter the directory
> and run "python
SLES11 worked fine with FTP, if I am not mistaken. SLES12 don't.
We gave up on FTP and used HTTP on the repositories. FTP implementation on
yast is buggy right now, and it's way faster to just enter the directory
and run "python -m SimpleHTTPServer" than to fill a bug request, send lots
of logs, r
10 matches
Mail list logo