SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I am not posting my thread regarding to slackware problem but I need some little guidence about it. So going to back about my start in linux. I was using Linux since last 9 years and my start was Red Hat Linux 9 (for learning purpose) at that time.It was quite interesting to learn it. Soon I switch to Fedora and start learning it,then CentOS was my last choice in which I configure different types of servers.
I appreciate linuxquestions.org that it is a forum where from very begineer to experts write their comments/answers regarding to the problem.Couple of days ago I download Debian 6 and try to use it.I face problems a bit bcz I was too much familier with rpm style distro.
Learning Debian was a new task. I though about slackware why not I try it. Believe me I found it too much interesting and really it is good saying that I"f you lean slackware u will learn Linux." The thing which was calling in my mind was it is a community base distro like Debian or like a company base like Fedora which is powered by Red Hat?
2- The second point is there is no Samba,Squid,Openldap configuration files by default if i install every thing so how can I configure these things.Does slackware ware have its own repository where where we just update a package and it automatically install all dependencies ? like for example we do in fedora
#yum samba* update
in Slackware how can I do work for desktop point of view and Server side as well ?
First I would like to point out that Samba is included with default Slackware install. It is under n packages (networking related stuff). So only thing is to configure samba. Here is the detailed walkthrough how to configure Samba in Slackware
Dependency resolution is something that is intentionally left out in Slackware. It gives you immense freedom to do anything. Great freedom however requires great responsibility so it is your task to maintain your system. If you break it, you must fix it. Once configured properly however. Slackware requires almost no maintenance and just keeps running forever.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Slackware works with package management tools; e.g., installpkg, upgradepkg, removepkg. "Packages" are, for all practical purposes, the output of configure-make-make install created in a special way so that one of the mentioned tools can deal with installing, upgrading or removing packaged software.
There is a utility, src2pkg (see http://distro.ibiblio.org/amigolinux/download/src2pkg/) you can use to create a Slackware package from source -- in fact, once you have installed src2pkg, there is an example for creating a Slackware package from Squid source. The example will be found in /usr/doc/src2pkg-2.7/examples/squid.
The most useful place to find what are called SlackBuilds (files that are used to actually make Slackware packages from source code) is http://slackbuilds.org/; there is a search box and, if you enter the name of a package, you'll be presented with a link to the files you need plus a link to the source code. As it happens, squid is one of the SlackBuilds available at SlackBuilds.org.
Doe a little reading about how to use both src2pkg and SlackBuilds.org and you'll have an easy time of installing additional software as time goes on.
slackbuilds.org and the tool that goes with it, sbopkg, are my slack-fu. I use that most of the time, or just build from source. Or sometimes look on slackbuilds.org for the dependencies and build them all from source. I'm more of a hack than a guru, so I don't do that to edit the flags, it just seems to be more stable. But to be honest slackware built with packages seems to me more stable than most other distros. The one program I ALWAYS compile is wine.
I does not know from where I may start slackware. Suppose I want to install squid in my slackware I shall download the gz kind of fine.Extract it, then
# make install
In fedora,Centos I do like it but in slackware ....Well can u give me any link or tutorial from where I get help about the installation process in slackware ?
That works. IMHO the best way to do it. Read the README first because its not always exactly the same process.