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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You can use rpms for Slackware, if you have rpm installed. But, you would probably have to use .src.rpm for any package you want to compile for Slack, since it isn't a .rpm based distro.
Or, you can use checkinstall. Install a tarball, via checkinstall. and make a slackpack, which will install.
Or, you can use Alien, which will convert among rpm, deb, and slackpacks.
Or, you can forget about the binary packages, and use something like encap or stow to install source packages, in a manner which is easy to delete the package if you find you don't want it, or upgrade the tarball to a newer version (the only utilities I've found to this date that can update a tarball install).
Then there's Sorcery. It's amazing ( I use it in SourceMage). The Sorcery files seem to be fairly easy to write to install and update source packages which are not part of the distro.
I've recently "upgraded" my SuSE installation to use apt-get (via apt4rpm) to update and upgrade SuSE. That's another tool that needs more exposure. My ideal Linux world would have rpm and apt-get working together in one package.
The one and only time I needed to use an RPM in slackware, I did exactly what he described: converted it using rpm2tgz, and then used installpkg to install it.
The only reason I did this is because this software was _only_ made available as a binary RPM, and it was required for a course I was taking. If there is source code available it is ABSOLUTELY advised to use this over converting RPMs.
regarding the comments on SuSE and apt4rpm...i think apt-get is a wonderful system in Debian. However I've found Yast works just fine for the same purposes in SuSE. I see you're running 8.2? Perhaps older versions had worse problems with the "dependency hell" that RPM-based distros are so notorious for. These days in 9.1, 9.2, or 9.3 Yast does a pretty damn good job of resolving deps. And last I checked, apt4rpm is just using the same repositories. Why not use the dependency management system that the distro is designed around? Things like SuSE and Red Hat are messy enough as it is...tossing a 3rd party package manager on top seems bound to just make more mess.
And of course, if you just really enjoy apt-get and its syntax...why not run Debian? It works great there.
i have these arguments with people regarding slapt-get all the time...