Slackware-current is looking good
MySQL was removed and substituted with MariaDB.
Upgraded version of network manager, version 0.9.8 support bridge interfaces. A minor upgrade to xfce. And the addition of elilo. I am expecting a impressive Slackware. I just want to thanks all the Slackware team for their effort. |
Agreed! Slackware-current is looking very good indeed! :)
I am thinking that Slackware 14.1 will be another amazing release. |
I saw the mariadb when I updated one of my Slack boxes today (I'll do the other tomorrow).
Mariadb now has the PV seal of approval. Who could ask for more? |
Quote:
|
I keep wondering what the final kernel version will be.
The latest "longterm" kernels are from the 3.4 series. https://www.kernel.org/ 3.7 is at End of Life (EOL) and 3.8 is destined to end once 3.9 is released. http://www.kroah.com/log/ If Slackware is to be released soon, should it use a longterm 3.4 kernel instead of an EOL 3.7 kernel? |
Quote:
|
Quote:
Frequently a kernel needs to be replaced because of newer hardware compatibility or for security reasons. For example, my current hardware cannot run X using the Slackware 14.0 kernel 3.2.29. So I had to upgrade my kernel to a later one. To keep a "stable" system the logical thing to do is upgrade to the latest 3.2 kernel, which today is 3.2.41 A jump staying on the same 3.2 level is usually fairly easy as the kernel configuration does not change very much at all. If kernel 3.2.29 were EOL then I would be forced to go to 3.4 or higher in order to make the system work. The kernel jump from 3.2 to 3.4 introduces changes to the configuration for which there are no easy answers. Try configuring a 3.4 kernel starting with a config file from kernel 3.2.29. Then use "make oldconfig" and you will see all the questions that need to be answered... So a kernel jump to a new level introduces instability because there are more changes than simply upgrading a kernel on the same level. |
Quote:
|
Quote:
I tried to jump from 3.2.29 to 3.2.40 and experienced a couple of hard system lockups this week, so I'm not sure jumping between LTS releases is completely safe, but it's probably safer than jumping between minor number releases. I'd wager -current will release with the next branch marked LTS, but time will tell! |
Quote:
Quote:
Being able to change kernels easily is one of the reasons I chose Slackware over Debian. I hope that 3.9 becomes the next Long Term Stable (LTS) branch. And I'm running 3.9-rc4 right now with no problems. |
Quote:
|
yeah I'm also running a more current kernel, the 3.8.4 kernel due to heating problems with my amd hd6700m hybrid graphics caused by the 3.7.10 kernel.
|
Member Response
Hi,
I think PV has already stated the '3.7.1' will eventually be the kernel of choice. Just upgraded my Slackware64 14.0 to '3.7.10' to get the Intel Corporation Centrino Wireless-N 1030 working properly after my Laptop motherboard and wireless daughter-board were replaced by Dell. They still need to replace the USB daughter-board that is still erratic. PV provides everything at http://slackware.oregonstate.edu/sla...ent/source/k/; Quote:
Quote:
|
Quote:
Quote:
|
I was a bit worried with this "drop in" MariaDB replacement for MySQL, but all is well. Not one glitch so far with any of my databases. Phew that's a relief.. :)
|
All times are GMT -5. The time now is 05:15 PM. |