On Sat, Sep 26, 2020 at 11:55 AM Warner Losh <i...@bsdimp.com> wrote:
> And there's the rub: how did this file come to exist? I'm certain it isn't > booting or shutting down the system based on when devfs is mounted (before > init) and unmounted (it's not done by the shutdown scripts). Now, it's > always possible there's a hole in my understanding of the sequence of > events. But given the examination of code, it's crazy to think this could > be created by anything but some weird bug. That's why a step-by-step from > scratch guide is needed. Im happy to look into it, but I need a bit more to > go on. > > I don't think it's terribly complicated; either set up a multi-boot system or pull the physical drive with / from one machine, and mount it while booted into a different environment. Then, chroot into it and do ... just about anything. If you didn't mount devfs before chrooting, then you get a file /dev/null (and some really confused errors from, e.g., buildworld!). -Ben _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
