Weekly Edition
Return to the Distributions page
| |||||||||||||
Slackware 14 released
The Slackware 14
release is available. "We are sure you'll enjoy the many
improvements. We've done our best to bring the latest technology to
Slackware while still maintaining the stability and security that you have
come to expect. Slackware is well known for its simplicity and the fact
that we try to bring software to you in the condition that the authors
intended."
Update: Slackware ARM 14.0 is also available. (Log in to post comments)
Slackware 14 released Posted Sep 30, 2012 0:06 UTC (Sun) by hadrons123 (guest, #72126) [Link]
I wonder who is still using slackware?
I am not sure what "latest" according to slackware dictionary mean either.
What a shocker Posted Sep 30, 2012 0:11 UTC (Sun) by allesfresser (subscriber, #216) [Link]
I saw there was one comment on this article, and I knew it had to be some joker casting aspersions. If you had actually looked before tossing your meme-bomb, you would see that Slackware is just as up to date (if not more so) than other contemporary distributions, and has an active user community.
What a shocker Posted Oct 1, 2012 11:38 UTC (Mon) by miguelzinho (subscriber, #40535) [Link]
Could you point me to Slackware's mailing lists and bug tracker, so I can help the project?
http://slackware.com Posted Oct 1, 2012 13:03 UTC (Mon) by rvfh (subscriber, #31018) [Link]
Mailing list: http://slackware.com/lists/
Bug tracker: no idea, but you can ask the mailing list ;-)
http://slackware.com Posted Oct 1, 2012 13:42 UTC (Mon) by miguelzinho (subscriber, #40535) [Link]
I mean a mailing list where I can discuss with other people. The page you refered me to only contains slackware-announce and slackware-security, read-only lists.
http://slackware.com Posted Oct 1, 2012 13:55 UTC (Mon) by troy.unrau (guest, #73654) [Link]
There's no real mailing list. However, LQ handles most slackware discussion. Pat is active there and fixes a lot of bugs that people bring up in the threads.
Don't be such a PUTZBUNTU Posted Sep 30, 2012 1:08 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
I keep Kubuntu on the Desktop and Slackware on the laptop.
Ubuntu gives me access to a whole lot of software for whatever I need. I use use it for video editing and bit torrent.
For me, Slackware is all business. I use it for WORK, mostly writing and editing text and graphics. Somehow, the uncluttered, straightforward architecture seems to lend itself to getting things done. I feel that I'm a lot more productive with Slackware. For someone else, it may be different.
But it's specialized, and limited. You're just being ignorant when you imply the packages aren't current, but you don't get the easy automatic access to software choices you'll get with a Debian or buntu based distro, but it's a great no-nonsense tool for basic work.
It's also fun to tinker with Slackware. It's been the basis of some of the most interesting and original second-generation distros, beginning with Slax and Porteus, through Vector Linux and zenwalk. I was actually able to release my own homemade live cd based on Slax 6.1.2. I've been maintaining and refining it since 2010.
http://www.kiaragnulinux.blogspot.com
Slackware 14 released Posted Sep 30, 2012 2:30 UTC (Sun) by hadrons123 (guest, #72126) [Link]
Sorry for the above comment.certainly not the correct statement. Saturday night effect. I apologize.
Slackware 14 released Posted Sep 30, 2012 4:36 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
I'll take it as good natured ribbing.
Slackware 14 released Posted Sep 30, 2012 0:33 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
I've been trying the release candidates. The xfce 4.10 is sweet, but I couldn't install KDE3 from binaries that were released for Slackware 13.0. KDE4 is not terrible, but I just can't let go. I suppose I'll have to try a compile, but for now I'll be sticking with Slackware 13.37
Slackware 14 released Posted Sep 30, 2012 6:31 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]
Of course you cannot install KDE 3 binaries which were made for 13.0! I remember someone on IRC trying to do that one year ago. It didn't work back then and it won't work now either.
As a general rule:
NEVER MIX BINARIES FROM DIFFERENT VERSIONS (OF SLACKWARE).
Slackware 14 released Posted Sep 30, 2012 16:09 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
Well, it works great with 13.37
Slackware 14 released Posted Sep 30, 2012 19:12 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]
You've been very lucky.
Slackware 14 released Posted Sep 30, 2012 16:42 UTC (Sun) by burdi01 (guest, #65371) [Link]
"NEVER MIX BINARIES FROM DIFFERENT VERSIONS (OF SLACKWARE)". *Most* of the time this rule of thumb is simply not true. You may have to carry forward some libraries, but that is all there is to it.
Actually the last KDE 3 (3.5.10) was for 12.2, and I have been carrying forward that version for quite some time. I think that missing hal will be the stumbling block for running that version for 14.0.
At the moment I run Trinity 3.5.13 on Current (which at the moment is identical to 14.0). There are some glitches, but nothing fatal.
Slackware 14 released Posted Sep 30, 2012 18:25 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
>>Actually the last KDE 3 (3.5.10) was for 12.2,
Well, no, there's this:
http://ftp.gwdg.de/pub/linux/slackware/unsupported/kde-3....
Thanks for the tip.
Slackware 14 released Posted Sep 30, 2012 18:45 UTC (Sun) by blackbelt_jones (guest, #62623) [Link]
I had some problems last time I tried Trinity.
(sigh) Hello, XFCE.
Slackware 14 released Posted Sep 30, 2012 19:17 UTC (Sun) by Camarade_Tux (guest, #51944) [Link]
Differences of semantics. :-)
What we usually say is: do not mix. Of course, stuff like xlander hasn't been recompiled recently and yet it works well. But for packages that have changed, don't attempt to take one from version X of the distribution and use it on version Y. Don't attempt to do backports.
Slackware 14 released Posted Sep 30, 2012 15:39 UTC (Sun) by geofft (subscriber, #59789) [Link]
That's true of all distros, right? Isn't that just how we decided dynamic linking on Linux is going to work?
Slackware 14 released Posted Oct 1, 2012 14:15 UTC (Mon) by vonbrand (subscriber, #4458) [Link] No. One of the (many) benefits of dynamic linking is that you can change the library (as long as the ABI remains) under the executables. Thus, a change to fix, e.g. a security problem, doesn't require rebuilding the world. If the library developer is careful, this can work for a surprisingly long range. And you can (via library versions) have several ABIs supported at the same time.
Slackware 14 released Posted Oct 1, 2012 19:24 UTC (Mon) by zlynx (subscriber, #2285) [Link]
Unfortunately the Linux community is lucky if the developer even notes an ABI change in the change log, let alone bumps the .so version or maintain versioned symbols. (Although as someone who maintains a proprietary C++ library for Linux, I understand what a pain versioned symbols are for anything but C.)
Of course if the developer does bump the .so version, good luck getting any bug fixes back-ported into the last version.
Slackware 14 released Posted Oct 4, 2012 0:26 UTC (Thu) by nix (subscriber, #2304) [Link]
For ABI additions, you're pretty much right (which means you can run older binaries on newer systems, but not generally vice versa). However, for ABI changes and deletions, soname compatibility is maintained pretty well for the vast majority of packages, and it is universally considered a bug if it is accidentally broken. Recently, even some of the odious old standbys like OpenSSL have come into the light. (Berkeley DB remains a frequent-breakage annoyance, but even it bumps its soname when appropriate. And often when not appropriate.)
Slackware 14 released Posted Sep 30, 2012 15:39 UTC (Sun) by juliank (subscriber, #45896) [Link]
As the last time, congratulations from my side. I consider Slackware to be a close relative of our Swirl's highness, and wish it all the best.
Slackware 14 released Posted Oct 1, 2012 16:35 UTC (Mon) by ovitters (subscriber, #27950) [Link] and the fact that we try to bring software to you in the condition that the authors intended.Does this mean bringing software via tarballs or something else?
Slackware 14 released Posted Oct 1, 2012 16:37 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]
It generally means no distribution specific patches.
Slackware 14 released Posted Oct 1, 2012 17:14 UTC (Mon) by dark (subscriber, #8483) [Link] Ah so it doesn't mean "untested" :)
Slackware 14 released Posted Oct 1, 2012 17:19 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]
no, it doesn't mean untested.
It also doesn't mean _no_ distro patches, but they try really hard to avoid them.
One of the biggest things that it means is that the package gets installed where the developer configured it to be installed. You won't ever see a discussion about merging /bin and /usr/bin on slackware, for the simple fact that slackware doesn't overrride the decision from the upstream package as to where it wants to be installed.
Slackware 14 released Posted Oct 2, 2012 20:02 UTC (Tue) by mgedmin (subscriber, #34497) [Link]
Don't packages usually install into /usr/local, when you do ./configure && make && sudo make install? I haven't used Slackware since 1998, but IIRC it kept most stuff in /usr/bin, not /usr/local/bin.
Slackware 14 released Posted Oct 2, 2012 20:50 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
picking compile time options is not patching the software.
some software compiles into local, some doesn't. It varies from package to package.
Slackware 14 released Posted Oct 7, 2012 19:40 UTC (Sun) by bersl2 (subscriber, #34928) [Link]
I actually don't recall any official Slackware packages installing into /usr/local for quite some time (aaa_base notwithstanding). In fact, most patches applied in the official SlackBuilds seems to be related to install paths of various sorts sometimes not being configurable except by changing a file.
raspberry pi support Posted Oct 2, 2012 20:53 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
As of 14.0, raspberry pi is one of the options.
http://www.daves-collective.co.uk/raspi/installing.shtml
I'm a little fuzzy on what is 'official' vs what is 'community' supported here. It looks like the pi install bootstrap is 'community', but the packages are 'official'
raspberry pi support Posted Oct 3, 2012 18:10 UTC (Wed) by mozes (subscriber, #53630) [Link]
Thanks for pointing that out. You've got the picture right.
I've just added the distinctions to http://www.armedslack.org/supportedplatforms/
That should clear it up I hope.
|
|||||||||||||