Thanks one and all who offered suggestions on the .PRM file. It is working now. I am now having problems getting connected to an FTP site. I tried ftp.redhat.com and yes I realize this is an exercise in futility. I did attempt this at off hours, very late night, very early morning but no luck
]
Subject: past the .PRM file, now another issue
Thanks one and all who offered suggestions on the .PRM file. It is working
now.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED
I don't know what was wrong, but I used Brock Organ's format/suggestion
and it worked the first time I tried it.
Below is an example of his .PRM file
.PRM
root=/dev/ram0 ro ip=off ramdisk_size=4 DASD=200-201
HOSTNAME=foobar.life.redhat.com IPADDR=192.168.10.105
NETWORK=192.168.10.0
the .PRM file, now another issue
I don't know what was wrong, but I used Brock Organ's format/suggestion
and it worked the first time I tried it.
Below is an example of his .PRM file
.PRM
root=/dev/ram0 ro ip=off ramdisk_size=4 DASD=200-201
HOSTNAME=foobar.life.redhat.com IPADDR
This works for me on Redhat 7.2 Make sure you have case set to mixed, the
silly thing is case sensitive.
root=/dev/ram0 ro ip=off DASD=200-205
CHANDEV=qeth0,0x3000,0x3001,0x3002
HOST=ldal.xxx.xxx:hsi0:xx.xx.xx.xx
NETWORK=xx.xx.xx.x:xxx.xxx.xxx.x:xx.xx.xx.xxx:xx.xx.xxx.x
DNS=xxx.xxx.xxx.xx
I'm having to reload the starter linux system multiple times and am
getting tired of having to re-enter the various information everytime I
reboot.
I know I can put this information in the .PRM file and infact have, but
other than the root=/dev/ram0 ro ip=off DASD=200-20F
line, I can't get
Ref: Your note of Fri, 5 Mar 2004 07:52:33 -0500
Here is one I have that works. It looks messy, but it is 80 byte records
and since you're only allowed 10 or 11 records, I squish all the
variables together.
ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc IP_HOST=linuxwwvm.pok.ibm.com
Make sure you re-punch these files out to the reader.
Larry
-Original Message-
From: Steve Gentry [mailto:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 07:53 AM
To: [EMAIL PROTECTED]
Subject: the .PRM file
I'm having to reload the starter linux system multiple times and am getting
, Larry
Sent: Friday, March 05, 2004 8:32 AM
To: [EMAIL PROTECTED]
Subject: Re: the .PRM file
Make sure you re-punch these files out to the reader.
Larry
-Original Message-
From: Steve Gentry [mailto:[EMAIL PROTECTED]
Sent: Friday, March 05, 2004 07:53 AM
To: [EMAIL PROTECTED]
Subject
to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject:Re: the .PRM file
Of course, that will work only if he's doing this on z/VM. If it is an
LPAR, then he only gets 1 876-byte record. Also, only Red Hat supports
these additional parameters, SUSE does
punch out.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Steve Gentry
Sent: Friday, March 05, 2004 10:46 AM
To: [EMAIL PROTECTED]
Subject: Re: the .PRM file
This is RedHat and it is in z/VM. I've tried a couple of suggestions and
it still
]
03/05/2004 10:52 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject:Re: the .PRM file
Well, then I guess I need to ask how many files you have in your virtual
reader. If a cp change rdr all keep nohold command got issued, the
starter
: the .PRM file
Mark, the EXEC that I use . .
exec
/* */
'VMFCLEAR'
'cl rdr'
'purge rdr all'
'spool punch * rdr'
'punch kernel img a (noh'
'punch redhat prm a (noh'
'punch initrd img a (noh'
'ch rdr all keep nohold'
'i 00c'
/exec
Post, Mark K [EMAIL PROTECTED]
Sent by: Linux on 390 Port
13 matches
Mail list logo
