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.
The real problem is that "/etc/termcap" sorely needs an update.
This is what annoys me, having two separate databases for the same info, with one (/etc/termcap) always getting out-of-sync. Then the programs that use termcap have strange behavior because of those differences.
Let me quote what Andries Brouwer wrote on 2002-10-12
Quote:
The file /etc/termcap defines the escape sequences used by many programs addressing the console (or any other terminal). See termcap(5). A more modern version is found in /usr/lib/terminfo.
twelve years later, terminfo stays "more modern" but termcap is still alive
Last edited by Didier Spaier; 01-04-2015 at 06:05 PM.
Reason: date corrected
Any other packages left that need to be checked, or have we fairly much covered everything?
If so, or when we can say enough is enough, the fate of certain packages needs to be addressed, namely those that are forked packages like procps-ng versus procps for example, which has not been actively developed for some time. Should the newer editions of such packages be considered for /testing possibly?
I have been listing everything than could (not necessary should) be upgraded in slackware-current, with when possible the homepage of the source package, for those interested in tracking.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.