Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Jun 2021 17:13:45 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>
Cc:        "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org>
Subject:   Re: Files in /etc containing empty VCSId header
Message-ID:  <ac82878fbd635cbdf19707e7daabe15cf753ea0f.camel@freebsd.org>
In-Reply-To: <202106082211.158MBrbe010419@gndrsh.dnsmgr.net>
References:  <202106082211.158MBrbe010419@gndrsh.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote:
> > On Tue, 8 Jun 2021 09:41:34 +0000
> > Mark Linimon <linimon@lonesome.com> wrote:
> > 
> > > 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.  
> 
> There is a command for that which does or use to do a pretty
> decent job of it called whereis(1).
> 

revolution > whereis ntp.conf
ntp.conf:
revolution > whereis netif
netif:
revolution > whereis services
services:

So how does that help me locate the origin of these files in the source
tree?

-- Ian

> > > 
> > > 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 ...)
> > > 
> > 
> > I use locate for this kind of search, e.g.
> > 
> > locate netoptions
> > /etc/rc.d/netoptions
> > /usr/src/libexec/rc/rc.d/netoptions
> > 
> > -- 
> > Gary Jennejohn
> > 
> > 
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ac82878fbd635cbdf19707e7daabe15cf753ea0f.camel>