Alright, we just reproduced this problem in house (one of the devs). However, I'm still not sure whats causing it, but I do have a workaround that should prevent this from happening again.
Everyone if you can go to a shell (option 8, and issue): chmod a-w /boot/loader.rc chflags schg /boot/loader.rc If the file gets trashed again then we have some type of MAJOR kernel issue going on. Scott On 9/16/05, Scott Ullrich <[EMAIL PROTECTED]> wrote: > Sorry, I meant 0.79. There was a race condition on shutdown that we > corrected. > > Scott > > On 9/16/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > At 04:24 PM 9/16/2005, you wrote: > > >Scott, > > > > > >My system was installed from scratch as 0.79.4 or 0.80. I don't remember > > >the > > >exact release but I installed it from CD by the very end of August. Than I > > >upgraded to 0.82.4 and finally to 0.84. This is the 0.84 upgrade that broke > > >my boot up. The .70< estimate doesn't seem to fit my case... > > > > I had a similar occurence. I think it might have been a 0.79. I did > > a fresh install from 0.82 I think and it never came back. > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
