>>> On Sat, Feb 16, 2008 at 5:02 PM, in message <[EMAIL PROTECTED]>, Dennis Foreman <[EMAIL PROTECTED]> wrote: -snip- > I have no clue as to what that all means, except that the build is bad, > which is really sad for what should be a cookbook process. (I think that the > ref to 0150 is my Linux boot drive).
It should be relatively cookbook, I agree. If the tools you're using aren't getting the desired results, I tend to go back to basics and do things manually. Since you seem to have your own webserver, try this: 1. Re-IPL into CMS 2. Spool your console to yourself (#cp sp cons * start) 3. Re-IPL your Linux system 4. When you encounter your error, close the console spool (#cp sp cons close stop) 5. Re-IPL into CMS 6. RECEIVE your console log to disk, and FTP that to your web server 7. IPL back into your Linux system using whatever you've been doing to re-try things, and FTP the suspect initrd to your web server 8. Tell the list where those two things are so we can look at them. It's really much easier to offer constructive suggestions when we have more of the whole picture to look at. I think this will give us a good start at it. Mark Post ---------------------------------------------------------------------- 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
