Long time Debian user considering switching to Slackware
 

I have been using Debian for 10 years now and am considering switching to Slackware. I do have a few questions that I am hoping can be answered before I backup my hard drive and wipe it in favor of Slackware. I have read the slackbook, installed Slackware as a virtual machine, familiarized myself with Slackware's slackpkg and other package management tools, and I have been using the VM for a few days now. The VM is running Slackware 14.1 and I am enjoying it thoroughly.

I have not tried to replicate the same environment within the Slackware VM that I have on the Debian host. With that said I am a Ruby programmer and avid gamer. Replicating my current Debian installation would take up too much time, so I am here with some questions.

How up to date are the packages in slackware64-current?

I saw that multilib is possible, but how time consuming is it to set up a 64 bit system to include 32 bit libraries in Slackware? I hope to install wine.

Will Slackware include a newer version of Ruby than 1.9.3? So far it looks like I will have to install ruby 2.2 from source.

Thanks for any input, it is much appreciated.

Yeah, no worries when going from Debian to Slackware. :) -current packages are somewhat mixed in up-to-date-ness, but you can follow the ChangeLog.txt.

If you're programming Ruby, I recommend using rbenv or similar tools.

to see how current are the usual packages in current
http://distrowatch.com/table.php?distribution=slackware

multilib is not that time consuming when you get used to it
lazy case you can just rsync Alien Bobs repository (or some mirror, idk) and mass install/upgrade it
more info on http://alien.slackbook.org/dokuwiki/...kware:multilib
although for wine you don't need them all (X things, glibc, png, the usual)
note that glibc from stock will conflict with glibc from multilib (same for gcc)

edit: the slackpkg+ way lems pointed out is less time consuming

Welcome and happy Slacking.

There is no general answer. For a specific package, Ctrl+F the ChangeLog or check the tree.

But Slackware-current is just a preview of the next stable release, not intended to be used in production, see Get acquainted with Slackware.

I don't use multilib but AFAIK that's not time consuming considering your knowledge, see Adding Multilib Capability to Slackware on x86_64 Architecture.

It will, but nobody but Patrick J. Volkerding knows when. In any case, you can always make yourself an upgraded Slackware package. That's not difficult and way better than just compiling from source to keep your system clean, see the link above "Get acquainted...".

Current isn't bleeding edge, but it is somewhat stable.

Multilib... Only use multilib if absolutely needed, otherwise just use a Pure64 setup.

Ruby-2.x will come when Patrick feels it has matured enough. There might be a Slackbuild for it though if you absolutely need it.

Just a small note to link to a post by phenixia2003 regarding setting up multilib:
http://www.linuxquestions.org/questi...9/#post5066064

With a package manager such as slackpkg+, it only takes two to three commands.

I use my own package manager, and it goes something like this:
See the link for instructions using slackpkg+.

Although someone will surely issue a counter since this is a matter of choice. if you are really an AVID gamer I recommend installing 32 bit unles you have more than 16GB ram. PAE handles up to 16GB effortlessly in all but a few instances and Wine is just easier if it is all 32 bit at least for now. This is in no way meant to denigrate multilib which is a real proper job. It's more Wine's fault but it does exist to some extent. There are only a few apps so far that really post a substantial gain in 64 bit so it really doesn't amount to having to accept some huge loss just to make Wine easier.

Incidentally the same guy that wrote multilibs also wrote this excellent How To Build a Custom Kernel at Custom Kernels with an edge and it even includes realtime and low-latency settings. A custom kernel like this is literally up to 10 times faster than any Windows kernel can be and 5-7 times faster than stock Linux kernels with the exception of a few distros who offer low-latency kernels usually for some Studio variation of their main offering such as would be used in a DAW or for video recording.editing. The most important part of this is that it directly affects mouse and keyboard response speed and trust me, this you can FEEL!

there is a trend lately of releasing only 64bit versions of games
although not many support linux (star citizen will be the first linux native game requiring 64bit, that i know of)

Welcome to Slackware. I've been Slacking since 04 and love it. I've also used Debian on and off since 4.0. I am sure you will enjoy the simplicity, durability, and security of Slackware. :)

I've been Slack-curious for a while now and have dual-booted with Sid. With your familiarity with Debian you will find Slackware takes longer to install everything but things like multilib are just a few commands. As long as you're willing to use the command line and spend some time installing I'd say "go for it".

I'm running Slackware64 14.1 stable with multilib and Wine. Solitaire and Space Cadet run nicely. ;)

But seriously, there are different ways to setup multilib. Simplest method is to install slackpkg+, configure Eric Hameleers' multilib repository, define precedence over the main repo (you might have to RTFM a little bit for that), and then it's a handful of commands to install everything.

I've been a long-time Debian user too. You'll probably like Slackware.

Cheers,

Niki

Long time Debian user considering switching to Slackware
 

I was sold a few replies ago and I am currently installing Slackware64 14.1 on my laptop.

Years ago I tried Slackware when I was still very new to Linux and was stolen away by the Ubuntu fad and then moved to Debian seeking more control over what packages were installed on my system.

I am very impressed with Slackware and will likely remain a Slackware user for years to come. I like the simplicity of the installer and package management. I am also impressed by how helpful and friendly the Slackware community is.

Thanks all.

I've used Debian and Slackware for years. For the past year or two (until a month ago) the wife's PC was on Debian and I was on Slackware 14.1.
I find the Slackware packages (even 14.1 'regular'... I'm not on -current) are more up to date than Debian, although I haven't tried Jessie yet.

I also found that it was far easier to build a newer Slackware package using a .slackbuild file from SBo, or script from the source DVD + latest source tgz. I have built some updated deb's, but to me it was far easier in Slackware to build and also maintain.

Debian and Slackware are my two favorite distros, though I'm not running a Debian box at the moment. Both of them value stability over bleeding edge.

The release kernel in Slackware --Current is v. 3.18.11. In contrast, the one on my Mint 17 box (on which I do update the kernel as kernel updates come out) is 3.13.0-52. Slackware --Current just updated Firefox to v. 38 as did Mint just a few days ago.

In terms of the currency of package versions, for all practical purposes (as my father used to say), I don't think you will find much difference between the two. Neither try to be bleeding edge and both value stability and functionality over newness for the sake of newness.

Here is a pretty easy way of maintaining multilib without needing to install any new packaging tools.