SPARC Live CD?

[Tom Buskey]

On 12/21/06, Paul Lussier <p.lussier at comcast.net> wrote:
> Neil Joseph Schelly <neil at jenandneil.com> writes:

> >> > (though not with locate because that's not there).
> >> Locate is too often wrong (i.e. not up-to-date) to be dependable for me.
> >
> > It's not up to date?  It's as up to date as it was when it last ran.
>
> Right, my point exactly!  When was that?  Is it set to run out of cron
> properly?  Is cron running correctly?  Has this system been off for
> some amount of time?  Has it had periods of being up, then down?  Has
> software been installed since the last time locatedb was updated?
> Does locate know about all the paths where something might be
> installed? All these questions are rhetorical.  In a forensics
> situation they're almost all unknown, and therefore make locate
> unreliable.
>
> Most people assume locate just magically "knows" where everything is
> and never consider the possibility it could be wrong.  It is often
> reconfigured.  I manage an environment with 300+ machines and all them
> use a localized locatedb.conf file which actually prunes certain
> directory structures from being included.  And many of things which
> are pruned do in fact contain stuff someone might expect locate to
> know about.  Locate is nothing more than an cron-automated find.
>
> Not to mention that on many systems the locatedb is intentionally
> turned off because it gets in the way of other things when it's
> running.
>

Solaris doesn't have locate :-)  Not even Solaris 10.