Don't get me wrong but Slackware is kinda "bloated"
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.
I don t think so myself. I learned so much from just installing in on so many different ocasions. I m also planning to get back to my old slackware on my farely low end MSI Wind U90X netbook sometime this week. I also plan to make a seedbox and help the community with the ISO seeding of both -current and -stable images.
So yeah, welcome back into my life Slackware, i missed you so much <3 "bloated" as you are !:d
I don't think Slackware is bloated, but there are some packages I'm curious about. Why are they included and does anybody even use them?
virtuoso-ose
raptor
rasqal
redland
obex*
does anyone actually use any of these, and if so, what for? I've asked for Postgresql before, which I'd be willing to bet is much more popular than virtuoso, but we have virtuoso and not PG. Or am I wrong about its popularity?
Don't get me wrong, I understand Slackware needs to have a range of packages for different users. That's cool, and I don't care that virtuoso and the others are included, nor that I turn around and always uninstall them.
What I'm wondering is why they got included. What is popularity? Just a whim? $$$? If I can understand that, maybe I can get Postgresql included. See?
I don't think Slackware is bloated, but there are some packages I'm curious about. Why are they included and does anybody even use them?
virtuoso-ose
raptor
rasqal
redland
obex*
does anyone actually use any of these, and if so, what for? I've asked for Postgresql before, which I'd be willing to bet is much more popular than virtuoso, but we have virtuoso and not PG. Or am I wrong about its popularity?
-Andy
Except obex* all others + soprano strigi akonadi phonon* libbluedevil qimageblitz are used ONLY by KDE. So the right question is why this stuff is not moved from /l to /kde.
And also why can't we have for example /l-gui with all the gtk-1,2,3 + atk + pango + cayro + qt + pygtk + pyqt stuff. And may be /l-av for the audio/video libraries. And may be /x-scim for those who need it and maybe /x-drivers for all the xf86-input-* and xf86-video-* packages and /n-bluetooth for bluez* and obex* and /n-wifi for all the wifi stuff and /n-wifi-firmware for the firmware stuff and /ap-database for mariadb and postgresql (it's a shame to not have it).
And /ap-workbone for our special quest
Slackware as a whole is not bloated. You don't even get libreoffice by default. But may be after some 20 years the tree needs several new branches.
hahaha nice! love it! Where did you get the sticker?
They can be found at the Slackware Store. I can vouch that the sticker looks great on a tower too. Certainly an upgrade of the Corsair plate that came with my case.
I'm just going to go out on a limb and say that I'd be okay with Slackware dropping PCMCIA support.
in other words, "I don't use it, why ship it?"
Prediction: the support for PCMCIA will be removed from Slackware 100.
Workaround: chmod -x /etc/rc.d/rc.pcmcia
Local fix: remove the package pcmciautils, remove the support for pcmcia in the kernel you use (and modules), remove the script /bin/pcmcia in the installer as well as all you'll find running at the root of the initrd "find -iname "*pcmcia*", remove all pcmcia stuff from usb.ids and pci.ids. I certainly forgot a lot of necessary cleaning, sorry about that
I'm just going to go out on a limb and say that I'd be okay with Slackware dropping PCMCIA support.
I have quite a few machines that depend on PCMCIA for network or wireless, and a few odd other things.
Admittedly, most of those will not likely be reinstalled with a newer Slackware, but it could happen - and I am certainly glad it wasn't dropped from earlier versions!
PCMCIA support is tiny (AFAICT) and the drivers are all modules, so why pick on PCMCIA?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.