True, but from what I could tell, his sysprog was looking for something containing the ipltext which "had to be in the right place." Looking at boot.map or the parmfile copy wasn't going to tell him much of anything.
Mark Post -----Original Message----- From: Patterson, Ross [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 11:19 AM To: [EMAIL PROTECTED] Subject: Re: Attempting first IPL after initial SuSE install Post, Mark K <[EMAIL PROTECTED]> writes: > The silo command does not create a file, it just writes some > information > (including the "ipl text" found in ipleckd.boot out to the > appropriate part > of the DASD unit. Actually, silo writes one or two files. It creates a file called "boot.map" in the current directory (hence the advice to "cd /boot; silo ..."), and may also create a copy of the parm file if the "readonly" option is specified in /etc/silo.conf. Ross Patterson Computer Associates
