Single file version available here.
Last updated on 2008-06-28.
To discuss, comment here.
| Prev | ||
| Home |
I've been going to Slackware -current at the main site to download the most recent packages of my favorite programs (ktorrent, firefox, thunderbird, etc). I thought this was its purpose actually, to provide the latest packages that were compiled specifically for Slackware. But after perusing the forums a bit I'm starting to get the impression that this is not recommended.
I've not been downloading system files (cups, etc.) just the most recent versions of the software I use. Is there any problem with this?
You are definitely not supposed to run curent packages with the stable release as versions of core components differ. Unpredictable things can happen if you do.
If you plan to stay with 12.0 I would reinstall those packages from 12.0 to be safe.
Current is the development tree and not the same as the stable version, See CURRENT.WARNING in the current directory for more information.
If you want to find any updated packages for Slack 12.0, all you need to do is look in any Slackware mirror. Under the 'slackware-12.0/patches/packages' directory are the latest official packages (product updates, patches, security updates, etc.) that are available for Slack 12.0.
documented on: 04-25-08, regis_n_bits
> I'm currently using the latest generic kernel and kernel module packages out > of Slackware -current (2.6.24.5). The stock kernel (2.6.21.5) does not > support my acpi properly and I haven't yet the time to compile my own. I > made an initrd to load it properly and everything is running fine.
As long as you don't need to compile any modules that are external to the kernel (for example, madwifi, nvidia or ati proprietary drivers, etcetera), then that should be fine. There's a chance that udev wouldn't behave properly with the newer kernel, but that's not very likely in this case, and since it's working fine for you, even less likely
documented on: 04-28-08, rworkman, Robby Workman