To review, I used WS_FPT to FTP the 3 files initrd, vmrdr.ikr, and parmfile from the URL Mark Post recommended. Then FTP'd those same three to VM, with SITE specification of FIX 80, in Binary, except for the Parm file for which I used ASCII. Editted the PARM file to include iplparm=30s and disk=200-202, the three disks initialized in CMS for Linux use, making certain the file remained in lower case. The three minidisks are defined to DIRECT as follows:
MDISK 0200 3390 0117 0200 LINUX1 MR ALL MDISK 0201 3390 0000 1999 LINUX2 MR ALL MDISK 0202 3390 0000 1998 LINUX3 MR ALL And defined in the Device Map as 3390, 2000 cyl each. Copy/renamed the three files to the Linux 191 minidisk. Ran lin REXX, documented yesterday, to load to VM reader, then IPL from reader. Anyone see anything I've done incorrectly or left out? Thanks again to all for your help. -----Original Message----- From: Alan Altmark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 8:29 AM To: [EMAIL PROTECTED] Subject: Re: Subject: Kernel panic: VFS: Unable to mount root fs on 01: 00 On Wednesday, 04/24/2002 at 07:24 ZE2, Rob van der Heij <[EMAIL PROTECTED]> wrote: > [snip] > Make sure to ftp in binary by hand and not let Netscape do > it for you. We've found that depending on the configuration > of your PC the browse can negotiate with the web server to > corrupt your file while downloading ;-) We have found that web browsers often request ASCII transmission of everything by default, on the erroneous assumption that it means the same thing as binary (Everything In The Universe uses the same encoding as Windows, right?). That means that LF gets translated to CRLF, messing up any offsets into the binary image. And, of course, the LF wasn't *really* an LF, it was compiled/compressed code or data! Alan Altmark Sr. Software Engineer IBM z/VM Development
