Whoa. That would be a project indeed. I'm imagining an analogy where I am the owner of a cinemaplex, and I want to make sure everybody leaves the theaters between movies. So I rig up a system to detect the movement of electrical energy through human tissue, pipe that through an algorithm that separates large-muscle movement from "noise," cross-reference against skeletal frame sizes and gait distances, and viola! Now I can tell how many people entered the theater and how many left.
Or I could go into the theater and look, but where would be the fun in that? > -----Original Message----- > From: Sam Phillips [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 16, 2003 2:53 PM > To: [EMAIL PROTECTED] > Subject: Re: [RLUG] Best Way to Detect All Changes After Software > Install or Removal? > > > > On Wed, Jul 16, 2003, at 13:40 PDT, "Robinson, Eric R." wrote: > > I thought of tripwire, but I was hoping for a solution that > I didn't have to > > install, configure, and test on every new machine I come > across where I > > might want to do this. The idea is to have an easy way to answer the > > question, "What did this new rpm, or other kind software > installation, > > actually do to my system?" > > Hmm. I can't think of anything off of the top of my head that does > that, but here is something that you could do. Run what ever > application under strace and then go back through the > voluminous output > of that and look for open and write calls. There would be false > positives, but a trained eye should be able to weed those out. A > wrapper application like strace would be interesting to write. Useful > too. > > -- > Sam Phillips <[EMAIL PROTECTED]> http://www.dasbistro.com Reno Nevada _______________________________________________ RLUG mailing list [EMAIL PROTECTED] http://www.rlug.org/mailman/listinfo/rlug _______________________________________________ RLUG mailing list [EMAIL PROTECTED] http://www.rlug.org/mailman/listinfo/rlug
