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.
Originally posted by geeman2.0 I'm confident that there are enough dedicated slackers out there to pick up the slack, so to speak, if Pat retires. Even if there isn't an official release there will be a fork.
There's no way the linux community would let the greatest distribution ever die out
While I agree, I do wonder if it could ever be as good as it is now, under the control of one or more 'fans' that take over when he retires. IMHO, it's primarily his iron will that keeps Slack from becoming bloatware.
As soon as you get ahold of 11.0, you'll be wondering where 11.1, or 12.0 is. If you're really into the Slackware thing, you would already be using packages out of /current, and that negates version numbers altogether.
<maruko> apt-get is a program. right? i cant see it on my system. im using slackware
<OldMonk> maruko: then you're beyond anyone's help.
* OldMonk shakes his head sadly.
* synapsis laughs.
<OldMonk> maruko: don't say sorry -- use a Real Distribution.
<OldMonk> well, i use debian, but i hear there are a couple of thers too.
<Steakk> man, i am friggen tired as hell
<OldMonk> others even
<maruko> what's wrong with slackware?
<OldMonk> maruko: no package management, dependent on one person who's about to die, no security updates, should i go on?
<Steakk> OM: It sucks.
* OldMonk needs to get out of delhi.
<OldMonk> Steakk: that she do
<maruko> poor pat
<viking667> it's a lot harder to ensure programs fit together...
<viking667> does he STILL have that medical problem?
<OldMonk> viking667: yeah, he's going to die.
<OldMonk> of course, we're ALL going to die, but that's not the point
My worry is that if official development of Slackware stops for whatever reason, it won't be replaced by a single community driven effort but by a whole bunch of splinter groups, each of which will claim that it is the One True Slack. Another holy war which nobody will win.
Oh, and discussing when someone is going to die? Classy. Very Classy. </sarcasm>
To me, it feels like Slackware is already dying. The decision to get rid of Gnome seems like a bad one. As slow as Debian is, it has a viable 2.6 kernel option not to mention you'll have a hard time finding a program that's NOT available. I've been living off of Slackware for the past year, but I'm tired of fighting with it to get basics working. KDE, as far as I can tell, is crippled without Gnome. I've finally given up on KDE and am now switching over to Sarge with Gnome. I'm a Gnome newby, but everything is working and my nVidia driver actually installed properly without me having to make concessions in the boot loader. The sound works, the scroll on the mouse works, everything works and I don't have to re-administer my cdrom every time I want to use it.
The real reason why I'm switching? I can actually record from the sound card 'line in'. You see, I'm looking to convert church tapes and other important things to mp3 to conserve space and to back up important audio. What good is a stable distro if it doesn't help you back up what I need backed up.
Slackware has served me well. It was a great learning experience, but now it's time to actually get something done. It did play DVD's really well.
Distribution: Slackware, Slackwarearm, Salix and Porteus
I find a couple of your comments rather curious.
What's wrong with the 2.6 kernels in ../current/extras? I have never had any problems with them except for compiling in some extra modules for dvb cards that weren't even in the kernel source from kernel.org yet.
How could taking out Gnome cripple KDE? I haven't installed Gnome since installing slack-10.0 and I have never had a problem with KDE. The odd gnome/gtk'ish package I compile and install or download from linuxpackages always seems to work anyway even though I'm using a KDE desktop.
I've never had to put anything in lilo.conf in order to run a nvidia card either. Can't say anything about what you want to do with sound but I seem to be able to do that with streamed music and digital tv.
Maybe your hardware's different than mine.
I suppose its just serendipidy that I've hobble together several boxes here with mostly salvage cards and and drives on top of anyold gigabyte mobo with processor that's cheap
and slackware always seems to work time after time. Just work.
Any slack release is just a stable snapshot at that moment in time usually within 4 weeks my systems are evolving into something higher, sometimes with current sometimes without. It's just a solid base that you can leave alone or expand/change to suit your needs.
Nothing wrong with debian though. Just seems that for me I decided about 2 1/2 years ago that distro hoping didn't give me anything more than sticking with just one and sorting out what my problems were. It just turned out the ride stopped at slackware. I'm kind of grateful for that.
Last edited by justwantin; 07-13-2005 at 05:45 AM.
You are correct, we have different hardware. Any time I wanted to do something with Slackware, I would drive my wife and myself crazy. One of the most important things to me is getting the nvidia driver working. I didn't have to add anything to my lilo. I had to remove some things. I had to use standard text (say goodbye to the penguin) or TTY1 would be a garbled and unreadable mess. That would be when I finally find the exact one that would actually compile for me. I sure am tired of clicking 'yes' for compile anyways even though I have the RivaTNT module as part of my kernel.
Don't get me wrong, I still have my 10.1 install and still love to use it once in a while. I love how the rc files are set up and how they seem to be well documented. I know Slackware a lot better than I know Debian at this point. I did get digikam working in Slackware and haven't gotten a camera program working in Debian yet. I'm having the same permission problem on my large FAT partition in both. I need to learn more about mounting drives. What good is a media drive that you need to be root to access.
My Slackware install never worked right with the 2.6 kernel in testing. You have to remember to use all the other programs in testing that have been compiled with it, but there doesn't seem to be a complete set. It's not as stable as just using the standard 2.4.29 on my machine anyway. I do have an oddball machine and it has been suggested to me that I need more cooling. I tried LFS and my compiles started going bad. I think my hardware may have some issues.
Perhaps there's something about Linux not being fully prepared for Rambus on a PIII with differing values in each of the two slots. I have a 1 Gig processor with an adapter in a slot 1.
I'm just saying that Slackware is the most temperamental distro in my machine so far and Debian just works. I am running with my Slackware settings in most programs. If I was more versed in using groups, I would probably had fewer problems in Slackware. I've been using Linux for about 2 years, but I'm still a relative on some things.
Wow you must have some pretty weird hardware. The 2.6 kernel in slack isn't going to be any different then a 2.6 kernel in debian. maybe a few different options but its pretty much the same. Also the apps don't have anything to do with the kernel. They aren't compiled against it. I'm not sure what you mean about this. I've been using a 2.6 kernel with slackware for a long time without much problems. 2.6.11 sure was a lemon though. Hardly slackware's fault. I just kept using 2.6.10 which ran like a champ. Until I bought my WD SATA HDD last week I didn't even want to upgrade from 2.6.10. As for the nvidia driver that is very strange. As for no vesafb at startup It's something you see for 20-30 seconds and either have KDM or GDM or XDM load up or just login and startx on your way.
But hey, whatever works for you is fine. If slackware isn't for then its your choice. Who cares what distro people use anyways. It's whatever you're more comfortable with is all.