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.
Eric, my thanks for the update. I feel that having a standardised way of handling bridging in Slackware will be a big bonus.
I have already studied your guides on QEMU and VDE which allowed me to get a virtual machine running on my little intranet at work. I also wish to say thankyou on behalf of my colleagues! It has been a boon for productivity.
BTW, Anyone else notice Pat's use of "slackware-next" in the comments for the kernel package? Far more descriptive name than "slackware-current" which has always seemed a bit of a misnomer. I like it.
I saw that and wasn't sure how to interpret it. Does he mean slackware-current will be called "slackware-next" after 14 is released? Was he just using it a placeholder for "Slackware 14" (i.e. the next release number)? Or did he mean slackware-current after 14 is released, not to be confused with -current prior to 14's release?
I took it to just be a placeholder to mean "Slackware 14": "Systems older than that can still be upgraded to -current (or the next release of Slackware) and will work fine using megaraid.ko . . ."
Perhaps you're right, though at this stage he knows he's going to number it 14
Bumped slackware-version to 14.0.
... so why use a placeholder at all.
Changing the name would require coordination with the mirrors and tools though so I wouldn't assume he's planning to change it unless he says so explicitly. It just struck me that slackware-next was a better name than slackware-current considering its role.
Speaking of networking: any chance of a bump for NetworkManager to 0.9.4 in -current? I've been using it with the associated bits and pieces (nm-applet, VPN plugins) for a few months on 13.37 and it works fine. It'd be great to see it in 14.
Maybe he wrote the note for kernel-huge before updating aaa_base and writing the note for it, then didn't go back and just say "Slackware 14" in the kernel-huge note. Either way, it's still a bit of a cryptic reference. I also considered the mirror problem of changing the name of current to "next". Probably unlikely due to tradition and inertia.
Most of the packages have been updated, but not everything. While the base of 14.0 has been set, the real true remaining updates have yet to be made yet, such as the new version of XFce, the newest kernel, and various other library packages to name a few.
You can tell the next release is near, but it's not here yet. Plenty of work left to be done, so until then, keep your eye's pealed on the Slackware.com webpage and the Changelog.