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.
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.
Why not follow the recommended procedure? Why not install KDE even if you plan to use Xfce as your WM? What do you hope to gain by a basic install except hard drive space?
I didn't want to install any of it that was all, I'm running twm on an old laptop and it does me just fine that way. Besides, I followed the recommended procedure on the family computer where we all use xfce and we have menus cluttered with kthis and kthat. If I could be bothered I would go in and edit all the desktop files to nodisplay but it would have been a lot easier to just deselect kde* on install which I'm sure a lot of people do.
As I said, I realise that generally support on here assumes a full install and I readily accept that, I'm not asking for help with a system problem, I was just querying something about the functionality of slackpkg really.
There's metadata associated with each slackbuild that has that information in it. It's the package_name.info file, which contains something like (taking 14.1's libvirt SlackBuild as an example):
If you really want that functionality, then you should consider using slapt-get as well as one of the slapt-get repositories where someone's done that analysis for a standard slackware distribution. Like this one (look at the contents of PACKAGES.TXT at the link).
That's a good one too, I could simply download and grep PACKAGES.TXT for whatever I was interested in. Thanks.
I didn't want to install any of it that was all, I'm running twm on an old laptop and it does me just fine that way. Besides, I followed the recommended procedure on the family computer where we all use xfce and we have menus cluttered with kthis and kthat. If I could be bothered I would go in and edit all the desktop files to nodisplay but it would have been a lot easier to just deselect kde* on install which I'm sure a lot of people do.
As I said, I realise that generally support on here assumes a full install and I readily accept that, I'm not asking for help with a system problem, I was just querying something about the functionality of slackpkg really.
Thanks for your considered reply. I'm always interested in how people choose to continue to use old machines effectively. I'm also fond of Xfce but at least half the apps I use in it are "k-something".
For my oldest laptop I'm still using Slackware 12.2 w/ KDE 3.5 but at some point I assume that will become limiting. Hopefully that will coincide with new laptop time
For my oldest laptop I'm still using Slackware 12.2 w/ KDE 3.5 but at some point I assume that will become limiting. Hopefully that will coincide with new laptop time
Depends on how you define limiting. Slackware 12.2 was EOLed on 2013-12-09, so you are already limited to not getting security updates.
Depends on how you define limiting. Slackware 12.2 was EOLed on 2013-12-09, so you are already limited to not getting security updates.
Actually, to be completely honest, with 2 hardware firewalls and iptables on each box plus rkhunter run at routine intervals, I don't worry about security updates much on home boxes. This is an ever-changing landscape so maybe one day I will have to increase my security habits at home.
For now though, the limitations are minimal since internally it does all I need it to do. It just becomes increasingly a standalone box because everything is just faster and more powerful on my main box. Whether intranet or usb device, there is just very little need to connect it to the outside world.
Also as phones become more powerful, laptops for me become less useful. I tend to now choose either phone or desktop. I'm nearly at the point where the only reason I keep it is because it would just hurt to toss out a working machine.... that and the nagging notion that the following week I would need it LOL.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.