Date: Sat, 26 Sep 2020 11:58:30 -0700 From: Benjamin Kaduk <bjkfbsd@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: "Rodney W. Grimes" <rgrimes@freebsd.org>, Ian Lepore <ian@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r365643 - head/bin/cp Message-ID: <CAJ5_RoC-0dBDBz62oBz_O0VFyv2kVdvFwxoObfZy3BLvR%2BAdkg@mail.gmail.com> In-Reply-To: <CANCZdfpDx8jWT7Lo8HXkomDZWB3F3KAnk4zWzySpSH_-XEF6uw@mail.gmail.com> References: <a1302355a272f5790562551dfe7631c280107b55.camel@freebsd.org> <202009261702.08QH2AQ1055654@gndrsh.dnsmgr.net> <CANCZdfpDx8jWT7Lo8HXkomDZWB3F3KAnk4zWzySpSH_-XEF6uw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 26, 2020 at 11:55 AM Warner Losh <imp@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ5_RoC-0dBDBz62oBz_O0VFyv2kVdvFwxoObfZy3BLvR%2BAdkg>