Date: Fri, 5 Jul 2002 19:51:32 -0600 (CST) From: Ryan Thompson <ryan@sasknow.com> To: Lee <lee@unassemble.co.uk> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: File System Monitoring Message-ID: <20020705194252.D44558-100000@ren.sasknow.com> In-Reply-To: <003701c22476$4bb529e0$6400a8c0@Administrator>
next in thread | previous in thread | raw e-mail | index | archive | help
Lee wrote to freebsd-questions@FreeBSD.ORG: > Sorry I should have been more clear. > > Although maybe this defeats the point in using FreeBSD I am not > using the Ports collection unless absolutley necessary. Mostly I am > installing from source. OK. You should know that the ports are much nicer than installing from source... But since you are a self-proclaimed newbie, I will guess that you're installing from source to learn about the make process, which is a good exercise. You can use the same advice that another poster gave you; use script(1) as described before you run the "make install" following the source build. In most cases, FreeBSD ports are little more than automated fetch/build of the source. > To put this into perspective, something I am currently doing is > testing out various mail servers. > > At the moment I am trying out Postfix, but in the future I will > probably try qmail, exim and even sendmail for a little nostalga (or > a headache trying to figure out how the full-formed config files > work). > The thing is all these programs put files everywhere. Want I want > to be able to do is install the program, try it out for a bit and > then remove it so I can try something else. If you just want to experiment with a whole bunch of programs, I *will* highly recommend the ports. If you don't like it, you can just pkg_delete it by name, and it will go through the port's pkg-plist and clean up everything but the configuration files (which you may have modified) for you. > Cheers > > Lee > > ----- Original Message ----- > From: "Danny Pansters" <danny@ricin.com> > To: "Lee" <lee@unassemble.co.uk> > Sent: Friday, July 05, 2002 9:50 PM > Subject: Re: File System Monitoring > > > On Friday 05 July 2002 21:39, Lee wrote: > > Because I use my FreeBSD 4.6 machine purely for learning rather product > use > > I am installing a lot of different programs to try them out. What I am > > looking for is a program that I can run after each program is installed to > > see a the most simple level what files have been added, but I would also > > prefer to be able to see what files have been modified. > > > > I believe this can be done using a combination of find & diff, but does > > anyone know of any good programs that provide more advanced options or > > simply provide better results. > > Find can be used for many things including what you want; diff is used to > show > differences between file.old and file.new. > > But if you're building/installing from ports or if you are installing from > binary packages but also have the ports tree installed, then you can simply > look at /usr/ports/*/your_port/pkg_plist which lists exactly which files go > where. > > HTH, > > -- > DaN > > Want music? http://www.mp3.com/stations/ricin_radio > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -- Ryan Thompson <ryan@sasknow.com> SaskNow Technologies - http://www.sasknow.com 901 1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020705194252.D44558-100000>