Is slackware really all that difficult to install?
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.
I remember the first time I installed Slack and expected it to be hell. I was genuinely surprized at how easy it actually was. In fact, I remember thinking, 'so what's all the fuss about?'. Just take your time and read the prompts, Slack will take care of the rest. If you have problems, this is a great forum with very knowledgeable people.
Just curious, why are you switching from J.A.M.D ?
Goby - lsmod results in command not found. so dunno what to do.
freychef - switching from jamd under duress. my webcam software doesn't play nice with it anymore and it's one of the things I need to be able to work.
and about the router......i really don't think i need one, whether or not its inexpensive. i have one computer and enough cable trails/modem wires everywhere. unless it's dire to have a router for one lousy (and trust me lousy fits) computer I don't see the need in it.
Generally Slackware is very easy to be installed. To maintain Slackware and install non-prepackaged software is another story. Though many sources compile without any problems, once you have dependency problem you're f*cked. That's why I love Slackware
I guess you've already got your answers but I'd say that Core was the hardest install I ever did, though it didn't have to be - I just made some mistakes along the way that made it a real pain, like wiping out my kernel configuration 9/10 the way through the process. Second hardest was Debian - and it's worse than Core in that it *seems* like it has nice helpful menus and crap but then they take you off into some horrible parallel dimension and torture you for eons. The easiest is stuff like Mandrake - zip, bang. Slackware is actually just as easy though - contrary to what you heard prior to this thread, it's a very logical menuing system. The only part that freaks people out is being dumped to a command line and being handed 'fdisk' and told 'go to it!'. But that's really no big deal.
As far as configuring, most everything should mostly work but there are some things that may not and almost everything requires some kind of tweak. But that's the learning experience.
As far as keeping up with packages, the package tools for *.tgz are easy. 'installpkg foo.tgz'. Bang. And I prefer compiling, myself. Slackware makes that fairly easy. Certain apps want all kinds of weird libraries that you have to track down but most sensible apps with sensible demands just compile right away. And 'checkinstall' turns them into Slackware packages just like that. People criticize Slack for it's package management - I dont see why. Want to see what you've got? Look in /var/log/packages. Want to get rid of something? 'removepkg'. Want to add something? 'installpkg' or 'checkinstall'. Have a depndency issue with some weird app? Pay attention to the error messages and a quick google usually fixes it. And a lot of people love swaret, so there's that. I just check the website for any critical updates.
So Slackware is more work and less handholding than some but it's a perfect medium between a DIY and an Everything Done for You Whether You Like It or Not. But then I have a distorted view maybe - for all I know, Slack can be as automatic as RH, Mandrake, or Suse if you rely on KDE or Gnome for everything (especially dropline gnome, which basically rewrites half your system and turns your Slackware box into a dropline gnome box). I do all system-stuff with a text editor or CLI tools, in console or in fluxbox, so my idea of Slack may be more Spartan than it actually is.
Another curiosity question - if you were forced to jump from JAMD (which you seemed to enjoy) what made Slackware the next option?
digiot: I remeber the first time I installed Debian.... I was used to the "slack way of installing" and felt like I was falling in a installation nightmare... I took more than 6 installs to get my system running as I wanted.. I couldn't understand that dselect stuff... my problems were over when a friend of mine explained me the "apt-get/apt-cache philosophy" since I learnt that I feel very comfortable to do just basic system install (kernel, aaa_base, a little more needed and that's it) and install debian from the scratch with my beloved apt-get.... but I need to say something.... apt-get is a nightmare for some users like myself.... it's just such a temptation to type apt-get distupgrade every 5 minutes! you start to want updates everytime even if you don't need them... that's another nightmare
When I first started playing with Linux in December of 2001, I was always told that Slackware was the beast of all distros. I am glad I didn't listen to those who told me Slackware was a no-newbie zone. I have been happy with Slackware ever since I found it. The only other distro I use is for testing purposes only.
Another curiosity question - if you were forced to jump from JAMD (which you seemed to enjoy) what made Slackware the next option? [/B]
Well it's my second option actually.....but everyone I know seems to regard it in high esteem so I've been wanting to check it out, but don't want to nuke my system.
Originally posted by Trinity22 Goby - lsmod results in command not found. so dunno what to do.
hi Trinity, you will get that if you do not type the command as root..
su <return>
put in your root password
get the '#' command prompt
try lsmod again
post the output and me or somebody can probably tell you what your NIC is using.
Originally posted by digiot
The only part that freaks people out is being dumped to a command line and being handed 'fdisk' and told 'go to it!'. But that's really no big deal.
I can understand that, although I haven't found fdisk quite hard to use ...
Originally posted by GOBY hi Trinity, you will get that if you do not type the command as root..
su <return>
put in your root password
get the '#' command prompt
try lsmod again
post the output and me or somebody can probably tell you what your NIC is using.
I did it proper.........
Quote:
[trinity@44ba0c212 trinity]$ su
Password:
[root@44ba0c212 trinity]# lsmod
bash: lsmod: command not found
[root@44ba0c212 trinity]#
Originally posted by wuck I can understand that, although I haven't found fdisk quite hard to use ...
I prefer not to take the risk...
Tried fdisk once or twice, did what I need but cfdisk is indeed easier
Don't fix what ain't broken, don't take the risk if you can avoid it unless it worths the effort
(don't get me wrong... I don't use slack and have plans on LFS and FreeBSD for nothing!)
Originally posted by GOBY ahh it's the tulip driver.
Anyone have a tulip-driven NIC automagically setup in a Slackware install? I think that is the reassurance Trinity seeks
Thanks -X- I had no clue why Trinity's lsmod wasn't working.. oh, the MINUS sign, yees..
I did. My card is an old Netgear, and Slack automatically found it & loaded tulip for me. I entered my IP settings (private IP, not DHCP) and I was off and running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.