brian@natinst.com (Brian H. Powell) (05/07/89)
I had a bad weekend. If you want the details, I'd be happy to send you a story about it. Among other things, I was trying to clone our boot disk (xd0) onto xd1. After I set things up (ran installboot, etc.), I halted. In the monitor, I set up the eeprom to boot off of xd(0,1,0). Fine. I booted, and it got vmunix off of xd1, as expected. But it suddenly decided to use the root and swap off of xd0: Apr 29 11:00:03 natinst vmunix: root on xd0a fstype 4.2 Apr 29 11:00:03 natinst vmunix: swap on xd0b fstype spec size 20803K Apr 29 11:00:03 natinst vmunix: dump on xd0b fstype spec I looked through the documentation, but couldn't find anything that explained what I was doing wrong. (Sun doesn't describe how to make an alternate boot disk very well.) I tried the monitor command "b -a", and pointed it to xd1 for root and swap, and that worked fine. Unfortunately, that information didn't stick, so the next boot used xd0 for root and swap. I eventually resorted to changing the drive id of xd1 to 0, and xd0 to 1. I reset things to boot off of xd(0,0,0), and it worked fine. What have I done wrong? Brian H. Powell National Instruments Corp. brian@natinst.com 12109 Technology Blvd. uunet!cs.utexas.edu!natinst!brian Austin, Texas 78727-6204 AppleLink:NATINST (512) 250-9119