Using these parameters:ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc
TERM=dumb""
Hostname= Gateway=yy.yy.199.1
HostIP=yy.yy.199.21 Nameserver=none
InstNetDev=osa Netmask=255.255.255.0 Broadcast=yy.yy.199.255
OsaInterface=qdio OsaMedium=eth Layer2=0
ReadChannel=0.0.a100 WriteChannel=0.0
They have changed the format of the install paramters.
Use
Install=ftp://username:passw...@ipaddress/root
On Mon, Apr 13, 2009 at 11:20 AM, Craig Collins wrote:
> Using these parameters:ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc
> TERM=dumb""
> Hostname= Gateway=yy.yy.199.1
> Ho
>>> On 4/13/2009 at 11:20 AM, Craig Collins wrote:
-snip-
> When I look at the directory yy.yy.199.4/../../nfs/sles11/DVD1 I do find a
> file named content but not a directory, which it appears the install is
> searching for. Has anyone run across this or do you have any suggestions?
What are y
>>> On 4/13/2009 at 11:30 AM, Mark Pace wrote:
> They have changed the format of the install paramters.
I don't believe so.
> Use
> Install=ftp://username:passw...@ipaddress/root
That format, or the individual specification of userid and password (for
non-anonymous access) has worked for me.
Actually, specifying the userid & password as part of the ftp specification
got us past that problem. We're using the base ftp service that comes with
redhat 5 that we also used to serve up sles10 without specifying the userid
and password on the ftp parm itself. So it appears to be reacting
diff
Looks like your ftp server is complaining about relative path... instead of
using ../../nfs/sles11/DVD1, try using absolute path (e.g
/somewhere/nfs/sles11/DVD1). From another box, try wget
ftp://ip/somewhere/nfs/sles11/DVD1/content to see if the file is
acessible...
Mauro
http://mauro.limeiratem
It didn't work for me. I found the new format in SUSE Linux Enterprise
Server: Deployment Guide
On Mon, Apr 13, 2009 at 12:29 PM, Mark Post wrote:
> >>> On 4/13/2009 at 11:30 AM, Mark Pace wrote:
> > They have changed the format of the install paramters.
>
> I don't believe so.
>
> > Use
> >
We downloaded the media again and re-deployed it on the ftp server, but we
still received the media failure error. Any ideas?
On Mon, Apr 13, 2009 at 12:09 PM, Craig Collins wrote:
> Actually, specifying the userid & password as part of the ftp specification
> got us past that problem. We're u
>>> On 4/13/2009 at 3:08 PM, Craig Collins wrote:
> We downloaded the media again and re-deployed it on the ftp server, but we
> still received the media failure error. Any ideas?
Here's a cool trick I learned during my testing of SLES11...
Specify both UseVNC _and_ UseSSH (with passwords for
gards,
Dick Waite
Mobile: +49 171 8393 769
--
Sent using BlackBerry
- Original Message -
From: Linux on 390 Port
To: linux-390@vm.marist.edu
Sent: Mon Apr 13 21:53:12 2009
Subject: Re: SLES 11 Install Issue
>>> On 4/13/2009 at 3:08 PM, Craig Collins
Mark, thanks for the tip about having both SSH and VNC available. I pulled
the following from the end of the y2log. We've also opened an issue with
Novell.
2009-04-14 08:14:12 <1> ZVMTST21(2784) [YCP] PackageCallbacks.ycp:1930
Downloading ftp://s...@xx.xx.199.4/../../nfs/sles11/DVD1/media.1/medi
>>> On 4/14/2009 at 8:27 AM, Craig Collins wrote:
> Mark, thanks for the tip about having both SSH and VNC available. I pulled
> the following from the end of the y2log. We've also opened an issue with
> Novell.
That looks like a problem on the FTP server side. Can you try HTTP instead and
12 matches
Mail list logo
