Date: Sat, 16 Sep 2000 23:56:23 -0700 From: "Crist J . Clark" <cjclark@reflexnet.net> To: Kris Kennaway <kris@FreeBSD.org> Cc: cjclark@alum.mit.edu, "Jason C. Wells" <jcwells@nwlink.com>, freebsd-chat@FreeBSD.org Subject: Re: Tripwire vs. Mtree Message-ID: <20000916235623.Z69158@149.211.6.64.reflexcom.com> In-Reply-To: <Pine.BSF.4.21.0009162119250.4662-100000@freefall.freebsd.org>; from kris@FreeBSD.org on Sat, Sep 16, 2000 at 09:21:32PM -0700 References: <20000915161430.A97377@149.211.6.64.reflexcom.com> <Pine.BSF.4.21.0009162119250.4662-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 16, 2000 at 09:21:32PM -0700, Kris Kennaway wrote: > On Fri, 15 Sep 2000, Crist J . Clark wrote: [snip] > > But to be honest, I never realized mtree was as powerful as it is. The > > fact that the file specification info is quite human readable would > > make doing detailed modifications easy, and that can be awkward in the > > tripwire configuration file. However, scripting to build the basis of > > a specification file for mtree that will not be extremely labor > > intensive to tweek is a non-trivial job. > > mtree can scan an existing filesystem to generate the specification file - > see the -c option. Right, but the problem is that you want different specifications for different trees. You still need some sort of script to run mtree for each tree with the proper keywords. Actually, if someone were to undertake this, it might actually be interesting if the script could read a Tripwire configuration file and make the specification from that. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000916235623.Z69158>