novice26

[Log in to get rid of this advertisement]

i would like to try slackware after reading all the of greatness everyone says but still very new to linux. i'm switching over from suse 9.2 and going to install slackware 10.1 and im curious doing the installation and after when installation additional programs if slackware informs you if you have all the needed software to install? when when uninstallation is tells you this software is needed for this program or something like that?

thanks!

linmith

Slackware doesn't have an RPM-like system as SuSE does, but I haven't found this to be a problem. It just means that you have to read the dependencies of new programs and make sure you have them by hand. There are also programs like slackpkg and Swaret that will check that sort of thing for you.

I hope this helps, and sorry if I misunderstood your question.

davatar

Slackware's means of installation is straight-forward and basic. There are slackware packages (.tgz) that can be added/removed via the "pkgtool" at the console, or the seperate installpkg, removepkg, upgradepkg, etc. also at the console. (View their man pages.)

Most of these slackware-ready packages have install scripts which are executed at installation to take care of whatever is necessary. Otherwise, your only means of installation is compiling the source code for the program, but that's not so hard. Just be sure to read the README or INSTALL, or whatever documentation comes with the program source code.

Don't feel intimidated, I was at first but I've grown attached to Slackware in these last couple months. I've tried Suse 9.2 and Fedora Core 3 but found them to be too frustrating, and in some ways too controlling. (like Winblowz.) I didn't like the Yast configuration for Suse because it didn't like it when I tried to change things manually.

I've heard the phrase, "Once you go Slack, you don't go back" and I'm beginning to think it's true, even if you're a total linux newbie and crazy enough to try the so-called "difficult" distro, like me. (If by difficult they mean you have to perhaps read more howto's, and become familiar with configuration files, then yes it's "difficult." But I far prefer it, because I know exactly what's going on in my system. Well, ok not exactly yet because I don't know a whole heaping lot about how it all works, but I atleast know to some degree what's going on.)

~Davatar

Tuttle

amen.

novice26

regarding checking by hand is there a way that to check what programs are installed then?

thanks for your replies

keefaz

That depends on the install method. If install come from a slackware package,
you just cd /var/log/packages, then ls and cat the files in this directory

Other than that for a compiled and installed from source program, it is up to you to
know what program you installed. There is a program named ' checkinstall ' that
build slackware package for you though.

gbonvehi

novice26, you can do as keefaz suggested or use pkgtool (as root) and select the View option.

cathectic

No, the Slackware system is that you install it, and then figure out the dependencies yourself, since you know best. Alternatively, you may frequently roll your own packages instead.

When you remove a package, it checks against the contents of other packages that it is not removing a file that is also in another package. If that is the case, it will not delete that particular file (but it will remove the rest of the package).

bobinglis

I have Slackware 10.0 installed after using Mandrake 10.0 and 10.1, I´ve also tried SUSE and some other flavours of linux distroś. I now have 2 40gig discs setup as Production and test. I reccomend this for anyone who has important info on their system.
I am x sys prog so command lines don´t phase me, I find Slackware not so difficult as some make out. Loading new software for newbies is no problem if you use KDE, I have found Kpackage an excellent tool, just don´t tick the dependencies box. Read the install guides and do a search in Kpackage for the laid down reqs.
I have a WinXP laptop connected and sharing the network connection through a Zoom ADSL router. Only the windows network setup is a pain if anything happens to btreak the connection u have restart the network connection in WinXP.
I use shorewall as firewall, that takes a while to learn but once u have setup its ok.
If u want a reliable system I´d reccomend linux to anybody with some experience of computer setups.
I am now trying to find a solution for sharing my scanner with the XP m/c.
I have just purchased a Cannon N670U and it worked out of the box with linux and slack. Brilliant. A great way to spend rainy days as a pensioner.