On Fri, Jul 13, 2018 at 04:48:32PM +0700, Robert Elz wrote: > Date: Fri, 13 Jul 2018 09:38:02 +0000 > From: m...@netbsd.org > Message-ID: <20180713093802.ga20...@homeworld.netbsd.org> > > | ack. we should probably leave the build broken, anyone who tries out the > | resulting netbsd might have to spend some time figuring out how to boot > | without /sbin/init (it's boot -a and then pick /rescue/init). > > You may have seen from my more recent message to current-users > that I encountered that problem.... > > However I assumed that if init was going to core dump, most likely > so would everything else, and init was just the one that hit the problem > first. Are you saying that is wrong, and it is only init that is broken? > > I cannot test at the minute, I generally do "update" builds, so I have > started a "destroy and restart" build instead - so my test filesystem is > empty right now. > > Once that finishes (more hours than it should take, as I don't use -j > as I don't really want to swamp the build system, which has other real > work to do, with my playing around...) I will test again. > > If no other fix (or likely fix) has appeared in the meantime, I will see if > I can work out how to cleanly revert joerg's changes (locally here) and > see if that helps.
No, everything dumps core. Fortunately I updated with a terminal open running as root, so I could PATH=/rescue ftp base.tgz, tar.
