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.
onebuck, I've been thinking about using Slackware more ... I've tried it before, but didn't stick with it for very long ... what do you think is better about Slackware than other distributions?
Because Slackware acts like a real operating system should act. For me it is that simple. The first time I installed Slackware I was too stupid to realize that it is "as user friendly as a coiled rattlesnake" ... from the Vector Linux website. I just read and followed the instructions. Got used to using the command line and editing config files with a text editor. Would never attempt to run Linux without MC the Midnight Commander. Now I'm running 12.2 and one thing I really like is that it recognizes Atheros based wireless cards automagically without having to install alien packages. I use Alien Bob's makeinitrd shell script and Slackupdate shell script from Darklinux.
Slack does everything I need it to do. Looking forward to version 13.0 soon.
We have the best forum around. Generally the information available to you is possibly a
simple search >>> LQ Search <<<
So if you don't find your answer with a search of the knowledge source(s) here on LQ then post the query. Please be sure to include all information possible i.e.; System Info, distro, kernel, error messages, log messages and even your personal observations.
You need to remember the helpers here are not sitting behind you. Jeremy had us all send back the cracked crystal balls. The balls were giving us smoky looks or views that would not allow us to look clearly over your shoulder.
> Thu Aug 6 00:48:30 CDT 2009
Hi folks! We're going to call this set of updates RC2. There are still
README files to be handled (that's the nature of documentation, I guess), as
well as some other things remaining on the TODO list, but X seems pretty
stable now, and it seems like a release soon would be in order so that we
can march right back into development territory with -current again soon. :-)
Enjoy, and let us know about any problems you run into!
'mirror-slackware-current.sh' is still the best way to get your '-current' ISO. Be sure to check your md5sum for the burnt ISO image since the download md5sum is already done for you.
Some confusion about Slackware 13.0 release from a lot of users that are not aware of what really is going on;
Originally Posted by Alien Bob
There won't be an official statement about switching to x86_64 because that switch is not being made. If you had followed Slackware's progress over the past months, you would have seen that there are now two supported architectures for Slackware that are jointly developed and maintained - one for 32bit and one for 64bit architecture.
You get to choose what to install. The 32bit Slackware will not be dropped.
Well the dust is settling and the new release of SlackwareŽ 13.0 x86_32/x86_64 seems to be getting smoother for all.
One problem that a lot of new users have is partly due too the creation of an account for a new user in that they fail to include user(s) in proper groups;
users floppy audio video cdrom plugdev power netdev <<<< suggested groups
When adding a new user you can get the suggested groups by pressing the up-arrow at the prompt after 'users' group prompt at the additional groups prompt;
Or press the UP arrow to add/select/edit additional groups
:users floppy audio video cdrom plugdev power netdev <<< up-arrow response, you can move across line to modify
I've also noticed a lot of the new users fail to revert their '/etc/rc.d/rc.inet1.conf' and '/etc/wpa_supplicant.conf' files to the original state when they attempt to use 'wicd'. It should also be noted that 'wicd' KDE tool is very clumsy and not a reliable means too initially setup your access. I suggest that users should rely on the 'wicd-curses' to setup initially from a console. Sure a little more work but reliable.
Another potential error is that a lot of people fail to verify their copies of the ISO along with the media for the burnt image. Then claim to have errors at the fault of SlackwareŽ. Guys the computer does as it's instructed to perform. If it's garbage in then garbage out. Test the ISO and Burnt Image to insure a valid copy. Don't A$$ume (A$$ u and me)! Don't just rely on the burner application to verify as these too can provide a potential problem.
Whenever posting to the forum please provide enough detail as to your problem along with supporting information to aid everyone in hopefully getting things resolved for you. A lot of our responses to new forum members is requesting information such as to the Distro/version, kernel used, hardware specification(s) along with any error or messages you may have received with your attempt.
Some helpers do request information that may seem critical, if so just xxx out anything that may seem a security risk. Keys are not necessary as long as they are valid for you. The response to a request like 'ifconfig -a' instead of just 'ifconfig' may seem redundant but it's not. The '-a' option shows you all devices that are recognized;
excerpt 'man ifconfig';
-a display all interfaces which are currently available, even if
Meaning your device is there but not available when shown with 'ifconfig' alone. 'man' those commands!
PV and team have provided a lot of valuable information that everyone should read in the form of text files on the media;
Be sure to use the LQ search function as a lot of the problems most new users experience have solutions. The queries you get from your search may aid you in solving your problem. If not then the same results may aid you in defining a new thread/post.
Happily Slacking along instead of distro hopping! ...
A heads up for 'SlackwareŽ 13.0 x86_64' users that multilib;
Originally Posted by Alien Bob
Did you by any chance install the 32bit multilib packages that I created, and then ran the slackpkg command after that?
There is a bug in my multilib setup (which I am fixing right now) so that if you run slackpkg after installing my set of multilib packages and then tell slackpkg to install the *.new files that it finds, you will end up with empty /etc/rc.d/rc.hald , /etc/rc.d/rc.messagebus and /etc/rc.d/rc.mysqld scripts.
The result of not starting hal and dbus when the computer boots will perhaps not be immediately obvious, but if you start X, you will have no mouse and no keyboard.
The fix is to reinstall the hal, dbus and mysqld packages: