LinuxQuestions.org
Visit Jeremy's Blog.
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 04-12-2013, 09:18 PM   #16
mlslk31
Member
 
Registered: Mar 2013
Location: Florida, USA
Distribution: Slackware, FreeBSD
Posts: 109

Rep: Reputation: 30

Do what you need to do to compete, Pat! Here's my opinion on it...

1) Good decision! Besides, it's easy to install a later kernel on Slackware. I'm stuck on 3.8 now, will probably be forced to 3.9 by the EOL tag, and hoping that the "follow the money" angle will kick in to "encourage" sane release management.

2) OK decision. I disagree on the kernel bugs part because I haven't hit a new one yet that I wouldn't have hit with 4.7.2. However, in my lame attempts to program in C, it seems like the new GCC libbacktrace feature needs more work, seeming to point to parts of a bad function that lead me away from the answer, not to it. The Clang Error Caret ^ it is not...but those GCC guys are pretty smart...they'll catch up...

Maybe a timetable for GCC 4.8.1/2/3 versus the timetable for Slackware 14.1/15 would be helpful.

3) My need for a newer X is driven solely by the work of Chris Wilson and the Intel Open Source Technology Center. Otherwise, I don't need a new xorg-server. The first really good editions (for me) of xf86-video-intel were tested against 1.13, so that's OK. No earlier, though.

This year of trying to follow the latest changes--pretending like it was 1999 and a two-week old kernel and six-month-old GCC wasn't new enough to compile the latest KDE--that has taken a slight toll on my sanity as a sysadmin. If you take your foot off the gas a little bit, I'll be the first to understand.
 
Old 04-12-2013, 09:24 PM   #17
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 7,739

Rep: Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460Reputation: 1460
I'm just going to agree with Erik_FL. He put into words what I was thinking.
 
Old 04-12-2013, 09:49 PM   #18
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,236

Rep: Reputation: 176Reputation: 176
Quote:
Originally Posted by GazL View Post
For me, the 1.14.0 XServer, 3.8 kernel and nvidia 310.44 blob have been working together better than they have in a good while. Do what you feel you have to, but I'll be keeping a copy of the current versions for my own use as I'm loath to go back when it's all working this well...
+1
Currently everything is working better with the "current" -current than it has in quite a while.
 
3 members found this post helpful.
Old 04-12-2013, 09:54 PM   #19
AceofSpades19
Senior Member
 
Registered: Feb 2007
Location: Chilliwack,BC.Canada
Distribution: Slackware64 -current
Posts: 2,079

Rep: Reputation: 57
I found that everything works much better in kernel 3.8 than any previous release so I would be very disappointed if Pat decided to move down to 3.4.
 
1 members found this post helpful.
Old 04-12-2013, 10:29 PM   #20
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 14.1
Posts: 1,141

Rep: Reputation: 55
I am okay with moving to 3.4 provided we have a config for 3.8 and/or 3.9. I must add I haven't seen any issues with 3.8 though.

For gcc, I am no programmer but I am running -current right now and compiled quite a bit of SBo packages and I don't see any issues. I don't see why we should move back to 4.7.x.

No opinion on the Xorg-server.

Thanks,
 
Old 04-12-2013, 10:47 PM   #21
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 728

Rep: Reputation: 168Reputation: 168
My x86_64 Slackware 14.0 system was freezing on my Ivy Bridge laptop with kernel 3.2.29 so I upgraded it to 3.8.4 and the freezing went away. So as long as Ivy Bridge graphics are working on a 3.4 kernel, then I'm okay with going back to that. As for the other bits, I say whatever Pat decides is fine with me. Stability over bleeding edge any day.
 
Old 04-12-2013, 11:31 PM   #22
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,170

Rep: Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534Reputation: 534
Quote:
Originally Posted by chess View Post
My x86_64 Slackware 14.0 system was freezing on my Ivy Bridge laptop with kernel 3.2.29 so I upgraded it to 3.8.4 and the freezing went away. So as long as Ivy Bridge graphics are working on a 3.4 kernel, then I'm okay with going back to that. As for the other bits, I say whatever Pat decides is fine with me. Stability over bleeding edge any day.
Well-said. As long as my Acer netbook successfully down-grades to 3.4 I am fine with the move. Slackware = stability.
 
Old 04-12-2013, 11:34 PM   #23
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
1) I've asked Greg about what will be the next LTS kernel when 3.8 came out, because I was interested in the user namespaces additions (BTW, things still has to go in with 3.10.x), and he told me that he's already got a lot of work maintaining two stable branches (3.0.x and 3.4.x) so unless someone else step in (like Ben has done for 3.2.x) for what he knew at the time there was no plan for another LTS kernel yet;

2) I was starting to like the 4.8.0 errors spam , but I also read about Stuart's problems in the arm changelog, so I suppose consistence comes first;

3) 1.14.0 is still giving me some problems with nx and virt-manager with qemu hosts using spice, two things that I use a lot: I was planning to try x2go and I'm using a workaround for the spice thingie (spicec works), but I suppose upstream still needs some time to fix this.

So, no prob at all for the downgrades here, but as GazL said, should be nice to have the stuff in testing/ to keep playing with them (besides the problems above, the rest here seems to work pretty fine)

Last edited by ponce; 04-12-2013 at 11:44 PM.
 
Old 04-12-2013, 11:37 PM   #24
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,438

Rep: Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850Reputation: 850
I share the experience reported by GazL and cwizardone.
On:
1) A stable release can remain on a server setup for a long time (heck, my server at work is still running 13.37), so it makes sense to have a LTS kernel as the base for a stable release. The option for a later kernel to support recent release hardware is highly desirable.
2) No informed opinion. My only comment is that a trusted compiler is preferred.
3) Upgrades of third party software packages may expect the new ABI.
 
1 members found this post helpful.
Old 04-13-2013, 01:48 AM   #25
kooru
Senior Member
 
Registered: Sep 2012
Location: Italy
Distribution: Slackware, NetBSD
Posts: 1,315
Blog Entries: 5

Rep: Reputation: 260Reputation: 260Reputation: 260
Quote:
Originally Posted by frankbell View Post
I'm just going to agree with Erik_FL. He put into words what I was thinking.
I agree with him too.
 
Old 04-13-2013, 02:29 AM   #26
solarfields
Member
 
Registered: Feb 2006
Location: Outer Shpongolia
Distribution: Slackware
Posts: 471

Rep: Reputation: 120Reputation: 120
Quote:
My x86_64 Slackware 14.0 system was freezing on my Ivy Bridge laptop with kernel 3.2.29 so I upgraded it to 3.8.4 and the freezing went away. So as long as Ivy Bridge graphics are working on a 3.4 kernel, then I'm okay with going back to that. As for the other bits, I say whatever Pat decides is fine with me. Stability over bleeding edge any day.
This! I have a ThinkPad S430 and experienced a lot of freezing with the 3.2.29 kernel. I later upgraded to kernel 3.7.7 and it has been working really well so far. Even if I need to upgrade the kernel again with the next release it is not such a big deal.

Actually, disabling compositing almost fixed the problem in KDE (almost), but it was absolutely horrible in XFCE. I really don't know why...

Last edited by solarfields; 04-13-2013 at 02:31 AM.
 
Old 04-13-2013, 05:17 AM   #27
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 479

Rep: Reputation: Disabled
I'm running three (two laptops and a desktop) machines on -current with no problems I'd rather not go back. If that is what happens, then so be it. I'll survive. Since it was mentioned (post 15), I would definitely not want to backtrack on KDE. Version 4.10.2 is working just fine on all three of my machines.
 
Old 04-13-2013, 05:32 AM   #28
cynwulf
Senior Member
 
Registered: Apr 2005
Distribution: OpenBSD, FreeBSD
Posts: 1,299

Rep: Reputation: Disabled
I don't see any issues - if someone needs a newer kernel than 3.4 they can build one.
 
Old 04-13-2013, 05:45 AM   #29
tuxbg
Member
 
Registered: Sep 2012
Location: Bulgaria,Varna
Distribution: Slackware64
Posts: 249

Rep: Reputation: Disabled
I really like -current.Don't have any problems compiling kernel or any other package.My system feel more responsive under -current.
 
1 members found this post helpful.
Old 04-13-2013, 07:23 AM   #30
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 345

Rep: Reputation: 56
Hiya. Generally my observation is that -current works well with the machines I administer, which is not to say that they wouldn't with an older set of releases. Another general statement is that I do not necessarily see the correlation between "old" and "stable", and those who think there is are welcome to use Debian stable. It is, however, true that the existing experience with older releases makes it easier to choose the "highlights" if there are any.

Detailed response:

(1) I don't care about the shipped kernel as I always compile my own. I usually run pretty recent kernels, with improved cpu and i/o schedulers patched in.

Having said that I don't care, I don't want kernel headers that are too old.

(2) I'm undecided on GCC. Does 4.8.0 produce better code? If not, I see no reason for not going back.

(3) Particularly the intel drivers (from i915 kernel driver to xf86 modules and mesa) are a moving target that are continually fixed, even for older chipsets. The quarterly recommendation by intel usually contains the latest releases. Before I kicked out intel graphics on my main workstation I event went to the crazyness of building new xorg version just to get a grip on the rare crashes that always came at the wrong time. In closing I would advise to go with the latest releases for the graphics subsystem.
 
1 members found this post helpful.
  


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
modversions.h and my sanity! stcinifeic Mandriva 1 05-28-2004 05:12 PM
samba sanity skywaterhulk Linux - Software 0 04-22-2004 08:13 PM
Question of sanity ch4s3r Linux - Newbie 3 02-29-2004 07:22 PM
I guess a simple backtracking problem spank Programming 15 08-27-2003 11:21 AM
in the name of a musicians sanity! leprechaun Linux - Newbie 3 02-17-2002 01:34 PM


All times are GMT -5. The time now is 03:45 AM.

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