Slackware is really Fast, I think I will stick to it
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.
Everything works everywhere once it's configured right.
The only thing different between different distros are package management, default settings, optimizations, included software, and versions. And those things can easily be changed.
Ultimately, you can run apt on slackware, and you can run pkgtools on Ubuntu, and if configured the same, you couldn't tell an Ubuntu machine from a Slackware machine. When configured the way you want it to be that is.
That's what makes distro hopping boring for me. No matter what distro I use, my experience, after maybe only 2 days-1 week configuring, is exactly the same.
Perhaps the best characteristic of this distribution I have heard is this: if you need help with your Linux box, find a Slackware user. A Slackware user is more likely to fix the problem than a user familiar with any other distribution.
That's what makes distro hopping boring for me. No matter what distro I use, my experience, after maybe only 2 days-1 week configuring, is exactly the same.
I always feel exactly the same. I find it pointless and boring to be jumping around between distros just checking which different software/config they have, when you could have the same with the distro you're using after you spend some time configuring it.
The only thing different between different distros are package management, default settings, optimizations, included software, and versions. And those things can easily be changed.
I would also add build options(besides optimization), system of updates(fixes to stable, rolling, binary/source base etc.).
Sure, you can tweak one distro to any other, but it's a question if your investments(time and effort) will pay off when there is a complete solution to your needs already available.
Everything works everywhere once it's configured right.
I totally agree with u on this point. Whenever I install a new distribution, I feel like almost a lost guy in some new city. For example, the location of scripts. I always get confused when I switch among distributions.
In Fedora and Redhat
Code:
/etc/rc.d/init.d/smb start
In Ubuntu and Debian
Code:
/etc/init.d/samba start
And in Slackware
Code:
/etc/rc.d/samba start
But, as u read about it or get some help, you will find the concept is almost same for all of them. And as u get familiar with it, u get confortable with it.
But, till now there's no part of Slackware that I didn't like....GAIM is there, Kdevelop is there, skype works fine. httpd, vsftpd etc etc, all are working fine with no problems. Now, I wish to get this line to be true for me
Quote:
Once you go Slack, you never go back
Last edited by manishsingh4u; 06-21-2006 at 03:57 AM.
That's what makes distro hopping boring for me. No matter what distro I use, my experience, after maybe only 2 days-1 week configuring, is exactly the same.
I think most people distro-hop because they don't know enough to configure their install as much as they would like. So they keep hunting around, hoping that some available distribution either works exactly as they want out of the box or is easy enough to tweak to their personal preferences.
If you're lucky, you find something great and ... live happily ever after, I guess.
If you're like me, you sit down one day and realize that the combined 100+ hours you spent installing and partially configuring 12 versions of 8 distributions were mostly wasted. Picking one version, almost any version, and learning the ropes would have put me way ahead of where I am today.
Manually editing .conf files and running .tgz installs work on any distribution after all. (Just don't use another package manager afterwards.)
Perhaps the best characteristic of this distribution I have heard is this: if you need help with your Linux box, find a Slackware user. A Slackware user is more likely to fix the problem than a user familiar with any other distribution.
That is a VERY true statement. The reason it's true is because of Slackware's lack of "user friendly/idiot-friendly" scripts and interfaces. To use Slackware, you must understand the OS, how it works and how things interact with each other.
I tried Redhat, Debian, Caldera, etc. when I migrated from SunOS/Solaris and didn't like/trust their GUI interfaces. They had way too much overhead for my taste. Slackware on the other hand, was a down and dirty OS (at Slackware 8 and still at 10.2) that once you installed, you had to learn how to control or the beat would eat you alive.
To this day, I still use Slackware exclusively (unless forced by a customer to use something else) for all my commercial projects. I have three different ISP's with Slackware servers running web, mail, user authentication, etc. with very low down time. I've also got a customer using it for high-capacity/traffic SMB/fileserver applications with the 3-Ware 9XXXX PCI-E sata controller who's still kicking himself for ever having bought a Windows 2003 server for his other office.
Yeah, Debian and that ilk are nice for the home user, but real nerds are Slackers.
Now, I am trying to install Mplayer on my Slackware. I have installed the main package and some of it's dependencies which I could find through google. Right now I am getting this error when I try to start it.
Code:
root@Manish:~# mplayer
mplayer: error while loading shared libraries: libmp3lame.so.0: cannot open shared object file: No such file or directory
root@Manish:~#
MPlayer likes to be compiled from the source since it turns on or off functionality based on what it's './configure' finds on your system. You will probably have more success doing it this way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
