It would be nice if an installation could use both LOADPARM and PARM. Use LOADPARM to select from previously prepared configurations (PROD, TEST, RESCUE, INIT-1, etc), and use PARM to override individual settings within that configuration.
/Thomas Kern /301-903-2211 > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Richard Troth > Sent: Thursday, July 08, 2004 16:01 > To: [EMAIL PROTECTED] > Subject: PARM and such [was: Linux under VM and Cloning] > > ...snipped... > > We really need proper support for parm handling. > For those who do not know, VM has long time supported a PARM parm > on the IPL command which effects a 64-byte parm string whether booting > from device or from named saved system (NSS). SAN support breaks it. > So when you're booting Linux on z/VM, you can append parameters, > as long as you're on traditional disk or booting from NSS. > ...snipped... > > LOADPARM is another thing, and is seen in the hardware, so you > z/OS folks are more familiar with that one. I don't like LOADPARM. > At only 8 bytes, it doesn't foster entry of arbitrary boot parm text. > The above examples do not fit into LOARPARM space. Any alternate > boot parameters must be pre-set and stamped into a collection. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
