SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Reading security guides I've noticed that many fellow slacker's indicate that they use logwatch to view their log's so I figured that I'd give it a go.
I've read that I should use the most current as their were some security 'issues' on older versions.
If there is a simpler application or better please advise.
I'd like to install this but it has a *.sh script to install; as do many other app's; like vmware for example. How do you guys track what installer's like this "blow out" all over your system. I've been reading 'man checkinstall' for the /extra/checkinstall that Mr. Pat V gives, and it appears that it's only for programs that you run make && make install for. Is there anything like the old installwatch that apparently is built into checkinstall and can't be run separately to monitor these common *.sh and perl (vmware for examlple) installer's?
I went' over to installwatch's homepage and they have a download links, but I keep getting file not found on server error's.
The readme describes how to install logwatch by hand. I suppose you could either write a slackbuild script for future versions .. or copy everything to a seperate directoro (say /tmp/logwatch) so the whole structure is under that directory
/tmp/logwatch/etc/*
/tmp/logwatch/usr/*
and then set the permissions right, cd into /tmp/logwatch andd run makepkg on it
that's a good idea, I'll give that shot and make an install directory and a slack-desc fiile too.
But as a side note, is there an appliction for programs that us .sh or perl installer's...let's take vmware for example. You have to run a perl script to install it, and it put's a lot of stuff all over the place.
They have an 'uninstaller' but I've noticed that some stuff does not necessarily get removed. Is there an application that can monitor these days?
Might not be what you're looking for, but what I usually do is modify the script (or preferably use a built in option) to install to a specific root directory, then build the specified root directory into a slack-package with pkgtools (my prefered method of package management). I never install anything to my computer without making it into a .tgz first.
regards,
...drkstr
**edit**
I just realized my reply was pretty much the same thing as Black Panthers. Sorry Fogie, probably not to much help to you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.