LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-24-2013, 04:46 PM   #1
mlpa
Member
 
Registered: May 2008
Location: Aveiro
Distribution: Slackware
Posts: 503

Rep: Reputation: 38
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.
 
Old 03-24-2013, 05:26 PM   #2
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,242

Rep: Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573Reputation: 573
Agreed! Slackware-current is looking very good indeed!
I am thinking that Slackware 14.1 will be another amazing release.
 
Old 03-24-2013, 10:48 PM   #3
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 8,099

Rep: Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536Reputation: 1536
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?
 
Old 03-25-2013, 12:31 AM   #4
JWJones
Member
 
Registered: Jun 2009
Location: Cascadia
Distribution: Slackware, LinuxBBQ, OpenBSD, Mac OSX
Posts: 723

Rep: Reputation: 187Reputation: 187
Quote:
Originally Posted by mlpa View Post
I am expecting a impressive Slackware.
Is there anything else?
 
Old 03-25-2013, 02:05 AM   #5
comet.berkeley
Member
 
Registered: Dec 2009
Location: California
Distribution: Slackware current
Posts: 152

Rep: Reputation: Disabled
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?
 
Old 03-25-2013, 02:30 AM   #6
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Quote:
Originally Posted by comet.berkeley View Post
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?
Since there are not any updates to the kernel once a slackware version is marked stable, is having an EOL kernel an issue?
 
1 members found this post helpful.
Old 03-25-2013, 03:46 AM   #7
comet.berkeley
Member
 
Registered: Dec 2009
Location: California
Distribution: Slackware current
Posts: 152

Rep: Reputation: Disabled
Quote:
Originally Posted by D1ver View Post
Since there are not any updates to the kernel once a slackware version is marked stable, is having an EOL kernel an issue?
I think it is a question of "how stable is it?" to be on an EOL kernel.

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.

Last edited by comet.berkeley; 03-25-2013 at 03:50 AM. Reason: spelling
 
Old 03-25-2013, 04:37 AM   #8
kooru
Senior Member
 
Registered: Sep 2012
Location: Italy
Distribution: Slackware, NetBSD
Posts: 1,342
Blog Entries: 5

Rep: Reputation: 266Reputation: 266Reputation: 266
Quote:
Originally Posted by mlpa View Post
MySQL was removed and substituted with MariaDB.
Yeaaaahhhhhh
 
Old 03-25-2013, 04:51 AM   #9
D1ver
Member
 
Registered: Jan 2010
Distribution: Slackware 13.37
Posts: 527
Blog Entries: 3

Rep: Reputation: 126Reputation: 126
Quote:
Originally Posted by comet.berkeley View Post
I think it is a question of "how stable is it?" to be on an EOL kernel.

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.
Fair enough Usually Pat's pretty good about providing different .configs for kernel branches, for example there's a 3.5 and 3.6 .config in /testing and a 3.7 in -current. I do understand what you are saying though, I'd prefer to see a LTS kernel used for the next stable.

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!
 
1 members found this post helpful.
Old 03-25-2013, 03:10 PM   #10
comet.berkeley
Member
 
Registered: Dec 2009
Location: California
Distribution: Slackware current
Posts: 152

Rep: Reputation: Disabled
Quote:
Originally Posted by comet.berkeley View Post
...
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...
Quote:
Originally Posted by D1ver View Post
...
I tried to jump from 3.2.29 to 3.2.40 and experienced a couple of hard system lockups this week...
LOL. It seems there is no one "best" version of the 3.2 kernel.

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.
 
Old 03-25-2013, 03:40 PM   #11
GazL
Senior Member
 
Registered: May 2008
Posts: 3,480

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
Quote:
Originally Posted by comet.berkeley View Post
I hope that 3.9 becomes the next Long Term Stable (LTS) branch.
Unlikely, 3.4 isn't even a year old yet. If I had to guess I'd probably say 3.10 or 3.11.
 
Old 03-25-2013, 04:56 PM   #12
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,356

Rep: Reputation: 184Reputation: 184
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.
 
Old 03-25-2013, 09:55 PM   #13
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,385
Blog Entries: 3

Rep: Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479
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/;README.TXT;
Quote:
Untar Linus' source in /usr/src. Make all files owned by root:root with reasonable perms. Install a suitable .config, or use make menuconfig, etc. An example would be to use one of the config files here:
# cat config-generic-3.7.10 > /usr/src/linux-3.7.10/.config

Then run the build programs:
make oldconfig
make bzImage
make clean
make prepare
rm .version

That's it! You now have a clean Slackware-configured Linux source tree. The kernel in Slackware supports SMP. With as common as multicore CPUs and SMP boards have become, this seemed like the obvious choice. The kernels are probably better for single CPU machines, too, if they will run them. At this point if you are running huge.s or generic.s, you should have no problems building kernel modules. Have fun! :-) Pat
No problems to date while running '3.7.10'.

Last edited by onebuck; 03-26-2013 at 08:53 AM. Reason: typo
 
Old 03-26-2013, 06:08 AM   #14
GazL
Senior Member
 
Registered: May 2008
Posts: 3,480

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
Quote:
Originally Posted by onebuck View Post
Hi,

I think PV has already stated the '3.7.1' will eventually be the kernel of choice.
I think you meant 3.7.10 not .1, but what he actually said was:
Quote:
Here we go with some more updates... a few notes on them are in order.
For this kernel update I decided to go with 3.7.10. Yeah, the 3.7 series
is EOL, but I've heard about some broken drivers in 3.8.x that make me
hesitate to push forward. Another option might be to move to 3.4.x, which
is working on my machine finally (a clocksource bug was crashing it with
earlier versions).
"For this kernel update". It doesn't necessarily mean he intends to ship with it when the time comes. Maybe the issues in 3.8 that he's trying to avoid will have been resolved by upstream before current hits RC1.
 
Old 03-26-2013, 08:30 AM   #15
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 489

Rep: Reputation: Disabled
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..
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] setup fails on most current Slackware-current March 26, 2012 AlleyTrotter Slackware 15 04-09-2012 07:05 AM
[SOLVED] Script to build always a current ISO image of Slackware (slackware-current) robertjinx Slackware 2 12-09-2010 03:00 AM
Slackware64 -current vs Slackware -current or Slackware onebuck Slackware 16 06-23-2009 02:19 PM
slackware current question on the current kernels davimint Slackware 3 06-03-2007 08:39 AM
DISCUSSION: Upgrade to Slackware -current without a -current CD truthfatal LinuxAnswers Discussion 0 09-19-2006 02:42 PM


All times are GMT -5. The time now is 04:17 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration