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.
Hey guys, I'm sure you have heard this question a lot, but I'm thinking about jumping into Slackware and trying to get my feet wet with this distro. I'm coming from a Redhat/Fedora environment... I feel I am very proficient with CLI and compiling and configuring packages. I's there anything else I should be aware of when jumping into this distro? Your thoughts and opinions would appreciated.
Thx
Click here to see the post LQ members have rated as the most helpful post in this thread.
Sounds like you're more than skilled enough to appreciate Slackware with that background. You should have no problem.
1) Don't ignore all the readme's in the top directory of the install CD.
2) At your first opportunity switch to a generic kernel + initrd as described in /boot/README.initrd
3) Take advantage of slackbuilds.org and learn to write your own early on.
4) Once you go Slack, you don't go back
big thing about Slackware is it is a full CLI and GUI Distro. Word of advice if you want to compile something 9 out of 10 some one has already built build scripts for you. slackbuilds.org or the SBOPKG browser builder. that is used with slackbuilds.
Every programe ran on Slackware is built from source with Slackware scripts. this really helps keep them programs packages in line with pkgtool.
Have fun.
the most easy way to install Slackware is the DVD, but the fastest way is to download the packages with wget
Code:
mkdir slackware64
cd slackware64
for i in a ap d e f k kde l n t tcl x xap y; do mkdir $i; cd $i; wget ftp://pathtoslackwaremirror/slackware64-13.1/slackware64/$i/*; cd ..; done
and then you may either create a minimal install-CD without packages (read here: ftp://ftp.gwdg.de/pub/linux/slackwar...nux/README.TXT) or download the USB-bootimage ftp://ftp.gwdg.de/pub/linux/slackwar...xe-installers/ which is even more convenient. The installer will give you the option to install the packages from a "premounted partition". So you create the slackware64 directory on a partition which you don't format while the installation. That's how I install Slackware.
all the startup scripts are in /etc/rc.d and the standard is to have each script completely functional on its own.
services are controlled with "/etc/rc.d/rc.<service> start|stop|restart" aside from those that are controlled by the rc.inetd.
If you want a default slackware program to start when the system does, 'chmod +x /etc/rc.d/rc.<service>'
Read the /etc/rc.d/rc.mysqld file for how to setup mysql before running it. THERE IS NO DEFAULT SQL DATABASE AND YOU MUST SET UP MYSQL BEFORE USING IT.
Any third party daemon software you want to run will need it's own startup file. Slackbuilds.org will include these for anything located there. You must manually add their execution to /etc/rc.d/rc.local[shutdown] to get them to start when the system is booted.
Slackware Package Management
Slackware is a complete OS. Therefor you do a Full install and the package manager doesn't need to track dependencies. If you modify what packages are installed, you are now the System Admin and have to manage all that your self. Good Luck.
Other than that? It's still Linux and everything should be the same.
Greetz
Here is an install tutorial complete with screenshots so you can install with pre-knowledge and confidence. It was written for v13 but 13.1 is identical. Once in you will never worry ever again that some random upgrade will break your system or removing something you don't want will also remove something you do want. The worst that can happen is an app won't run until you solve the dependency. Plus the vast majority of what you learn about Slackware today will still be useful in 5 years, maybe 10. The nuts and bolts are sacred.
PS I hate initrd and it is not necessary if you make sure to load early essentials at kernel level instead of as modules. Once you get up and running if this interests you, please start a new thread or read all the docs on the DVD regarding Installing and Upgrading.
Thanks guy's for all the advice, I am going to give this a whirl on my laptop this weekend. If everything goes good from there, and have no issues. I'll install on my desktop!
Thanks guy's for all the advice, I am going to give this a whirl on my laptop this weekend. If everything goes good from there, and have no issues. I'll install on my desktop!
Probably the biggest thing to get used to (it was for me) coming over from another distro is Slackware software management. I've got a fairly lengthy tutorial on the subject:
First post from Slackware! lol Managed to get in an setup with no documentation, now its time to figure this out and learn.. Thx guys for all the posts!
In order to have the Slackware-logo in your posts here in LQ, you may open firefox and enter the adress about:config
Rightclicking into the window will give you the option New->String, the string is "general.useragent.vendor" and the value has to be "Slackware"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.