SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm writing a new program and would like some help/feedback on ideas for a name.
The program is meant to inspect a package or package-tree and report any 'unusual' conditions. There are several programs which inspect sources which are called 'lint' or some variation thereof. The debian distro includes a tool called 'lintian' which is for inspecting packages -like what I want to do.
My conservative Scottish ancestry suggest a name like: pkg-lint
But, following the idea of 'impurity' suggested by the word 'lint', my more perverse side comes up with ideas that lean toward some variant of these:
fuzz, grit, grime, filth or Dreck (means filth in German)
Or maybe something like: pkg-veto, minority-report
Of course, Slackish sentimentality might suggest something based on:
slag or slime
But, the program is not likely to support only Slackware-style packages, so slack-check, etc., would not be too good.
I'm open to suggestions or thumbs up for your favorite. Or, if one name would definitely make you avoid having the program, what name is that?
It may be worth noting that the program is not intended to do any corrections to packages -just point out anything unusual about the content.
You get extra points if you supply an acronym reverse-engineered from the name, or a name forward-engineered from the acronym.
Credit (or blame) for the name will of course be given, if appropriate and wanted. Have fun!