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.
Slackware-current (that you shouldn't run, as that's for experienced Slackware users).
I didn't know that. I just assumed we all ran 64bit multi-lib current.( Seriously, I tell people to upgrade to current all the time to fix oddball problems associated with libs or new software releases).
Historically, I've run into a couple of issues but I just chalked that up to the Slackware Motto,
'If it you don't have to tinker with it, you aint tryin'.
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Main aim of Slackware-current is helping iron out future stable Slackware. It is unlikely that newcomers can actually help (though that probably happens sometimes). In any case it is not intended to be used in production.
There is little benefit to run Slackware-current over Slackware stable, but some specific cases, like new drivers or software versions that fit a specific system configuration. But even then, the new drivers or software versions can often be backported to -stable, just rebuilding the involved package or kernel (module).
However seldom, -current can be unstable at times. A Slackware newcomer will probably have more difficulties to solve such a problem.
FYI I'm running Slackware 14.0 at the moment and am perfectly happy with it. I occasionally run more recent versions, but only for testing or to provide stuff for these versions.
Main aim of Slackware-current is helping iron out future stable Slackware.
I'm working a lot in my free time with libvirt and qemu-kvm, I know they aren't in current but based on where I pulled them down from, I'd imagine they are on the table for future releases. On the whole they work extremely well on current, though I haven't started benchmarking the guest OSs' yet, I want to make sure I've fully explored the options for configuration and image creation before I worry about stability and bloat. I'm trying to keep copious notes as I work with them, for my own purposes originally but if they could be helpful, what should I do, just post them somewhere and leave a link here?
Thanks, the LQ blog is where I was thinking of posting them anyway, but I appreciate any direction I can get.
I don't think they'd be suitable for Slackware Documentation, not, at least until somebody else tries to repeat the steps and has the same outcome. Just the same, I'd like to contribute to the Distro in any way I can so any suggestions you think would be useful, I appreciate the time you invest in conveying them to me.
Creating a thread... I tried that once but the result wasn't what I'd hoped for. When I'm done with this side project, I'll try it again.