Date: Tue, 8 Jun 2021 09:41:34 +0000 From: Mark Linimon <linimon@lonesome.com> To: Ian Lepore <ian@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, John Baldwin <jhb@freebsd.org>, Michael Gmelin <freebsd@grem.de>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: Files in /etc containing empty VCSId header Message-ID: <20210608094133.GA25151@lonesome.com> In-Reply-To: <2a280bc83d9a6289b3443329eb15bb0cb6c75063.camel@freebsd.org> References: <20210520183705.3673dfb2@bsd64.grem.de> <2bd37d63-1806-b621-a32b-954c912bd16b@FreeBSD.org> <CANCZdfo59R2Gd%2B-KB1=WvPY-RxR4h4U9ikAECHOnCddqh3VVRw@mail.gmail.com> <2a280bc83d9a6289b3443329eb15bb0cb6c75063.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote: > Sometimes it's a real interesting exercise to figure out where a > file on your runtime system comes from in the source world. A tangential problem I trip over is "what is on this SD card?" It generally takes me 5-10 minutes to remember: strings /<mount>/boot/kernel/kernel | tail AFIAK it's the only way to be sure; nothing in /<mount>/* seems to have that data. (Yes, in theory they all live in their own little box each of which is labeled but things happen ...) mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210608094133.GA25151>