[SOLVED] what is specific about Slackware Linux what makes it different?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
He sent them on to Patrick. Jeremy's blog will probably announce when the podcast is finished. There should also be an announcement on the front page of LinuxQuestions.org as well.
The questions have been submitted to Patrick. Once I have the answers, they will be posted to the Interviews forum (and I'll update this thread with a link).
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Posts: 1,444
Rep:
Hi nooralain.
If you are looking on installing SlackWare because you want to learn and undestand linux then you are doing the right thing.
As mentioned above SlackWare put the user in control by allowing you to manage the installation. So it doesnt give you settings by default assuming that is what the user wants. Also the majority of software in SlackWare is installed from source by compailing it. By doing that the software get the proper settings base on your hardware, resulting in a more stable installation.
SlackWare is a Community Supported Distribution, so it doesnt have a big company behind its releases, like Canonical, Novell, or Red Hat.
Over all SlackWare is best for people who want to learn Linux and want to develop good system admin habits and also good for people who already know what they are doing.
Slackware does not do "branding." For example, the KDE you get from Slackware is the KDE from KDE, and so on.
I find the BSD style structure of the init scripts in /etc to be much easier to understand and work with than other methods, such as systemd or SystemV.
Slackware does not hold your hand. It expects you to think.
I wonder why nobody has mentioned it: Slackware is the only distro out there (well, maybe except LFS) that has a package management system without dependency resolution.
What you meant by that ???i dont understand exactly i guess that it can install packages and not automatically install the dependencies .............
Thats a bad point if its does not configure them auto
coz its like doing more work..??
i wanned good points so that i can install slackware
What you meant by that ???i dont understand exactly i guess that it can install packages and not automatically install the dependencies .............
Thats a bad point if its does not configure them auto
coz its like doing more work..??
i wanned good points so that i can install slackware
Don't let that put you off. Slackware is one of the best distros out there and many people will agree or argue 'not one of, but the best'. Slackware's package management doesn't solve dependencies and lacks automation. It's more comparable to dpkg or rpm than apt or yum. Don't let this put you off though, because working this way has it's benefits too. You have more control over your system working like this, and something that is often forgotten is that not all dependencies are actually needed by an application, but may be in fact there for a certain functionality, and you may not have a need for foo functionality.
for example, sometimes i like to use gnome2/mate desktop environment, but i hate nautilus, i prefer to use xfdesktop and Dolphin to replace it, but nautilus is a dependency of gnome-session. Try removing nautilus without the rest of gnome2/mate and it can be pretty hard, especially in a Debian based distro.
Another reason it's not so bad; You may have compiled a package from source and the package manager is not aware of it, well if you are running a package manager that check dependencies it won't cooperate with your compiled package very well. Or maybe you want to install a package that depends on a lower version of a library, than you have installed, and a simple symlink of the library would work nicely; that way you don't have to downgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.