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.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by kcirick
I never understood, or had the need to understand, how the packages were built. I could compile a software from source and install it onto a system, but I never understood how to put it into a package. I would use SlackBuild script, but I'd never written one on my own, and had never fully understand each and every line. Also, because Slackware install is broken into groups, and typically, I install groups at once, I didn't quite understand how each package within the group were linked/useful to others. Again, most people wouldn't care about these things, and that's fine.
Also, a new user wouldn't want to learn the inner working of a new OS right away... one would want to get used to using the system, become comfortable navigating through before attempting to dig deeper. I found that Slackware has a nice path into the system (transparency and again, organization), while system like Ubuntu is like a maze with series of symlinks and useless (!) scripts.
Oh, I agree. My point was more that while LFS can be a good projetct or hobby you're not nececerily going to learn more about GNU+Linux by doing it.
I think Slackware has the balance where compilation of packages and really tweaking you system is possible while shielding one from compiler flags and the like which don't really pertain to how Linux works so much as how it is built.
In other words LFS isn't going to make you more knowledgeable about using Linux than Slackware.
Is it true that Slackware development has "slacked" off a bit? I've heard that it isn't as well maintained as it once was. Is there any truth to that?
I believe that if you jump over to Distrowatch and look at all the "tracked" packages, you'll notice that Slackware-current is the most up-to-date distro right now.
Location: Geneva - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware 14.2 - 32/64bit
Posts: 609
Rep:
Quote:
Originally Posted by Yuhan
Is it true that Slackware development has "slacked" off a bit? I've heard that it isn't as well maintained as it once was. Is there any truth to that?
I'm quite surprised by this question... Didn't you see the freshly active thread Is Slackware still alive ? Moreover with the large amount of answers you had for your original question, you were seriously asking yourself this question ?
Anyway, I hope it's only the fact that you're a newcomer and you might be overloaded with unknown information to process.
Welcome to Slackware, an active distribution with an active community !
Last edited by NoStressHQ; 06-11-2016 at 12:42 AM.
Reason: Fixed my usual clumsy phrasing...
Things get slow because of the fact a system is stable and it can be nice to take a break from development for personal reasons while the que is still active.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Here we go again...sometimes I want to say, yes Slackware is dead nothing to see here, we are all in the grace of Bob now, slacking as we choose...carry on now.
Glad I did not say that outloud.
Lao-tzu said it best: "The highest person upon hearing of the Tao acts on it immediately, the middle person thinks about it from time to time and practices it when he feels like it, the lowest person laughs and ridicules those who follow it." Lao-tzu continued: "If it were not laughed at, then it would not be Tao."
I have faith in our BDFL. Pat has never let us down. Development is ongoing and 14.2 is close.
Uh we've strayed off course a bit here, folks. The original poster asked about the best way to learn about Slackware. Back on topic. Read and understand the ample, available documentation and howtos on the install media and you will prevail.
Slackware!
Lao-tzu said it best: "The highest person upon hearing of the Tao acts on it immediately, the middle person thinks about it from time to time and practices it when he feels like it, the lowest person laughs and ridicules those who follow it." Lao-tzu continued: "If it were not laughed at, then it would not be Tao."
Yes, my initial question was about the best way to learn Slackware and I'm sorry if I deviated from that topic. The helpful points here are all very instructive and some of the links provided are tremendous resources! Do you recommend dvd installation as the easiest way to go initially? It seems most people recommend that.
Location: Geneva - Switzerland ( Bordeaux - France / Montreal - QC - Canada)
Distribution: Slackware 14.2 - 32/64bit
Posts: 609
Rep:
Quote:
Originally Posted by Yuhan
Do you recommend dvd installation as the easiest way to go initially? It seems most people recommend that.
Yes DVD is the easiest, with full install. And if you're scared about partitioning your disks, (or lazy to use the command line for that), you can burn a gparted ISO (from here), to comfortably setup your disks before booting with the Slackware DVD.
Full install is the norm, don't try to cherry pick anything, as even the most seasoned Slackers avoid to do that. Appart from the disk partitioning and the full install tips, everything should be straightforward.
(Have the documentation site accessible somewhere nearby, on another machine/device, it can help for your first steps).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.