Mostly asking out of curiosity, how up to date do you all keep your slackware installs - do you make sure you have the latest and greatest version of everything? update things whenever pat and crew get around to it? update occasionally to fix problems/bugs, or just make it work and leave it alone?

Personally I keep some things as up to date as I can (browsers, mail clients) and otherwise just keep track of security notices and update when I encounter a bug/problem or when there is a security issue that was fixed.

At the moment I'm running four 13.37 stations and one slackware-current box. I keep all of the units up to date with the latest patches/updates.

It truly depends on what I would like it to be. If it's something I use daily, then yes I keep it up to date. If it's a Slackbuilds item and the current Slackbuild isn't up, I go and get the source file myself, edit the .SlackBuild file and ignore sbopkg's information about "updating to the newest" or I just install from source and ignore the .SlackBuild change entirely.

Sometimes (if it bothers me) I'll send an e-mail to the maintainer and tell them the source is out of date since many of them have to work in real life. In addition to that many of them are maintaining more than just one slackbuild.

Other than that, I'm currently using Slackware-current on this machine (my laptop) but Slackware 13.37 on my desktop and run slackpkg update about...once a week I'd say.

I run slackpkg update daily to see if new stuff has arrived. If not. I close up the console. If so, I download and install the new stuff.

And if software hasn't been updated but I can get it working outside the normal releases for current. I make my own package and install it.

I keep everything I can up to date with Slackpkg, I also check for updates in sbopkg occasionally. I check once in a very great while for updates for the few packages I don't get through Slackpkg or Slackbuilds.

When I have spare time, I pull up the changelog and see if I want to update at that time or wait until another day.

I don't. I had Slackware 10 for the longest time and finally moved to 11. After that I was not able to find peace with Slackware and just kept distro hopping. Finally when 13.37 came out, I found peace. I am using it as a home Server. It is my DNS, NTP, HTTP and Samba file server. I also have a couple of Virtual Machines running on it, as well. I am at peace with 13.37. Short of anything (else) major, I doubt I will do anything further with 13.37.

My last major incident resulted in a processor failure. I replaced everything expect the hard disk. When I was done installing everything the only hiccup I had was drive mapping (still need to fix that issue) and I had to reorder my network cards. Took some google'ing to fix that one.

-JJ

When I was learning Slack, I stayed on current. Once I got to where I was comfortable, I just nixed that. I just want stable, and the least amount of headaches. Ran Version 9.1 for a very long time. Now my desktop and notebook are both 13.0. I keep up with all the patches Pat puts out, and just compile anything xtra I need. I don't plan on upgrading to a new version until 13 loses its support, or I have to upgrade machines again. Works, secure, don't fix what's not broken.

I installed from slackware-current and have the RSS feed for -current in my reader. Drinking coffee reading the day's news also lets me know if there are an updates.

http://slackbuilds.org/mirror/rss/slackware-current.rss
http://slackbuilds.org/mirror/rss/sl...64-current.rss

I have also installed from 1337 DVD and then upgraded with all the -current packages to bring me in line with -current (not recommended as a network install of -current was much easier).

I also monitor 1337 and 64-1337.

http://slackbuilds.org/mirror/rss/slackware-13.37.rss
http://slackbuilds.org/mirror/rss/slackware64-13.37.rss

I run Slackware 13.37 and install any official updates that Pat and slackbuilds maintainers grace us with.

Apart from that I regularly update the development version of i3wm.

I run -current on all my boxes and a laptop and keep everything updated and right on the bloody edge.
Been a long time since the last -current update so I imagine the next one will be interesting.

I have run -current 64 since it came out on my main desktop. I check the change logs every couple days but I don't update till usually a week after changes have been pushed. By then someone smarter than I on these forums has figured out what breaks or the broken package has been fixed.

Any other software I use I try to update as often as I have time. I suffer from "Tech Boredom" a lot so I tend to do 10 things at once so its updated quite often lol. Not to mention the many VM's of everything under the sun I play with.

I handle my tech boredom by keeping a fedora partition around to play with, that way I can leave my slackware installs to be stable and reliable, the way I like and often need them.

The more often I use it the more up-to-date I keep it, unless there's a reason not to ... like stability. Examples of things I keep very up-to-date i.e. I maintain and update myself: FF, libreoffice, ffmpeg and mplayer (not all the time).

I update slackware packages, and only rarely uninstall one and install it myself and maintain it myself, only if there are problems with the one that comes with slackware.

I like my slackware tried, tested and stable, so I only upgrade when there is a major stable release: I went from 10.1 to 12.0 to 12.2 to 13.0 to 13.1 to 13.37. I've never tried slackpkg, so I probably suffer more than necessary, because I only do clean installs. I have /home and /var on their own partitions, and I don't mess with them during upgrades so my users' home folders are untouched, and folders with data like /var/www and /var/lib/mysql stay intact. I also back up my /etc folder. Then I reformat my root partition and install slackware cleanly, as if it were being installed for first time, usually a full install, unless a server, in which case I only install minimum packages needed to do its job. I also download the slackbuild scripts and source code for third party packages not included with slackware, and I build and install those for the new version. For tools that I use the most, like clisp, sbcl, mysql, apache, etc, I grab the latest source code, if newer than code provided at slackbuilds.org, accordingly adjust the slackbuild script for the new version, and then execute slackbuild script and install resulting package as normal.. it takes most of a day, but the result feels stable