Originally posted by: Spyro
Originally posted by: BingBongWongFooey
Originally posted by: Spyro
Originally posted by: BingBongWongFooey
Originally posted by: SnapIT
With SLackware you are locked into a specific configurations.
Care to explain that statement?
It takes forever to change things around, since you not only need to compile them yourself, but you need to work out any kinks between different software and libraries.
YARILD (Yet Another Reason I Like Debian)
However there are countless other solutions to the problem.![]()
Could you give me one, so that I can stop disliking slackware. I still remember rpm hell with mandrake before the days of apt-rpm. The solutions that I usually took for that are as follows, listed in order of least to most used.
Solution 1: Very potent medicines
Solution 2: A hand-crafted white flag
Solution 3: Apply head to wall, repeating as necessary up to 7 times (for good luck)
Solution 4: Throw things..... throw them everywhere....... large, mettalic things.......
Solution 5: Eat soap... Preferably lever 2000
Solution 6: Give up, go play a game of Freeciv. Come back later and approach the problem with a clear mind
Solution 7: Begin viciously attacking the computer with a rubber mallet
Slackware is a *nix freak distro, no doubt about that, you can, if you want to use the included packaging tools, which incluces RPM and pkgtool (for .tgz) (this is for slack 9) or you can compile it yourself, which is what any self respecting *nix freak would do anyways (and you could probably get debian tools to work on slack too if you really wanted to)...
What is nice about Slack is that you get what ask for, nothing more and nothing less, it's precise and installs just what you want it to install, the downside is that you have to know the dependencies yourself (just RTFM)...
You need your sweet gui and package system? bah...
BingBong... i'm just about ready to install NetBSD... i'll rip on the install proggy tomorrow...
