Subject: Re: -current kernel hangs/init busy loops
To: None <firstname.lastname@example.org>
From: Scott Ellis <email@example.com>
Date: 02/16/1997 15:26:09
In "Re: -current kernel hangs/init busy loops", Bill Studenmund
> On Sun, 16 Feb 1997, Scott Ellis wrote:
> > When booting with GENERIC, init runs, and then it loops on
> > 'init got Signal 10'. L1-A into the kernel ddb, and do a 'ps', shows that
> > only init, swapper, and pagedaemon are running.
> I saw a similar problem on my SE/30 when I updated to 1.2. I had booted
> single user and then installed all the tar files. When I rebooted, I got
> the "signal 10" messages. I then rebooted single user and did an fsck. One
> file was sick, and when I fixed it, all was well. IIRC, the sick file was
> init, which probably stemmed from the fact it was in use while I was
> installing. When it got unlinked, it stayed around (as it was open). Since
> there was no way to unmount the root fs with init closed, there was a
> problem. :-)
> I think the moreal of the story is to move init to something else and
> install the new init, rather than installing via a tar x... --unlink.
I did this (mv init init.bak && mv init.new init). Also, the new init and
the old kernel works fine, so I think that's not the problem.
I can't even boot into single user mode with the new kernel...I get
the same behaviour. ;-/ Good idea though.
// Scott Ellis // firstname.lastname@example.org // email@example.com //
// WARNING: This signature warps time and space in its vicinity //