LinuxQuestions.org
Help answer threads with 0 replies.
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 01-27-2017, 05:32 AM   #46
kjhambrick
Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 778

Rep: Reputation: 273Reputation: 273Reputation: 273

Thanks GazL

Yes, after noting that /lib/modules/$(uname -r)/source and /lib/modules/$(uname -r)/build are symlinks to /usr/src/$(uname -r)/

I was wondering the same thing: i.e. whether I could reinstall VMWare and maybe somehow override /usr/include/linux/ with /usr/src/$(uname -r)/include/ ...

However, that's for another day

-- kjh
 
1 members found this post helpful.
Old 01-28-2017, 04:52 PM   #47
slalik
Member
 
Registered: Nov 2014
Location: Moscow, Russia
Distribution: Slackware
Posts: 95

Rep: Reputation: 44
55020, thanks a lot for config-4.9!

Since you provide kernel-headers-4.9, I'd like to ask: does it mean that you suggest to install it?

I know the standard view that
Quote:
As long as you do not upgrade your glibc package, you should not upgrade or remove the kernel-headers package.
(see, e.g., http://docs.slackware.com/howtos:sla...eaders_package)

On the other hand:
Quote:
Originally Posted by volkerdi View Post
As far as I know, I've never encountered any issues with upgrading the kernel headers without recompiling glibc. I'd be interested to hear if anyone ever has, and under what circumstances.
 
1 members found this post helpful.
Old 01-29-2017, 01:16 AM   #48
MikelN
LQ Newbie
 
Registered: Jan 2017
Posts: 10

Rep: Reputation: Disabled
There's also the option to create a .config based on your system. When you make -localmodconfig the running modules on your system are used as basis for the config. This way you get a streamlined kernel with only support for hardware you have. Before you do this you must make sure you've connected everything you'll need (like USB sticks/external drives with filesystems you use, your webcam, everything you use needs to be there or it won't be included. You even need a DVD/CD in your drive or it won't work.). This greatly reduces the compile time. Since you leave out everything you don't need.

Last edited by MikelN; 01-29-2017 at 01:22 AM.
 
3 members found this post helpful.
Old 01-29-2017, 06:19 PM   #49
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,322
Blog Entries: 1

Original Poster
Rep: Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749
Mainline kernel 4.10-rc6 has been released for testing,
https://www.kernel.org/

It is the biggest release candidate of the 4.10 series to date.
http://news.softpedia.com/news/linus...r-512353.shtml

Last edited by cwizardone; 01-29-2017 at 06:22 PM.
 
1 members found this post helpful.
Old 02-01-2017, 07:41 AM   #50
GazL
Senior Member
 
Registered: May 2008
Posts: 4,232
Blog Entries: 6

Rep: Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669
v4.9.7 and v4.4.46 are out.
 
5 members found this post helpful.
Old 02-01-2017, 11:38 AM   #51
kjhambrick
Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 778

Rep: Reputation: 273Reputation: 273Reputation: 273
Thanks GazL.

4.4.46 includes another CVE fix.

-- kjh

Code:
commit 63db7c91a3c0ebe0e291feea53e4c63391db9465
Author: Kees Cook <keescook@chromium.org>
Date:   Tue Jan 24 15:18:24 2017 -0800

    fbdev: color map copying bounds checking
    
    commit 2dc705a9930b4806250fbf5a76e55266e59389f2 upstream.
    
    Copying color maps to userspace doesn't check the value of to->start,
    which will cause kernel heap buffer OOB read due to signedness wraps.
    
    CVE-2016-8405
    
    Link: http://lkml.kernel.org/r/20170105224249.GA50925@beast
    Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
    Signed-off-by: Kees Cook <keescook@chromium.org>
    Reported-by: Peter Pi (@heisecode) of Trend Micro
    Cc: Min Chong <mchong@google.com>
    Cc: Dan Carpenter <dan.carpenter@oracle.com>
    Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
    Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 
1 members found this post helpful.
Old 02-02-2017, 11:36 AM   #52
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 WMaker/XFCE
Posts: 256

Rep: Reputation: 63
4.9.5 with LiveSlack 1.1.5 being used since 1/25/2017 without problems. Installed all pkgs including the headers and have not had any problems slackbuilding other packages. Don't know if that helps answer the question about installing the headers, but just a status report of using all dave's packages.

Last edited by bamunds; 02-02-2017 at 11:38 AM.
 
1 members found this post helpful.
Old 02-04-2017, 05:57 AM   #53
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 365

Rep: Reputation: 150Reputation: 150
Kernels 4.4.47 and 4.9.8

https://cdn.kernel.org/pub/linux/ker...angeLog-4.4.47
https://cdn.kernel.org/pub/linux/ker...hangeLog-4.9.8
 
3 members found this post helpful.
Old 02-04-2017, 06:34 AM   #54
GazL
Senior Member
 
Registered: May 2008
Posts: 4,232
Blog Entries: 6

Rep: Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669Reputation: 1669
Wow, that was quick. I didn't even notice those go through 'review'. Thanks for the heads-up.
 
1 members found this post helpful.
Old 02-05-2017, 07:13 PM   #55
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,322
Blog Entries: 1

Original Poster
Rep: Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749
Kernel 4.10-rc7, is available for testing.

https://www.kernel.org/

Last edited by cwizardone; 02-05-2017 at 07:15 PM.
 
Old 02-05-2017, 11:18 PM   #56
ttk
Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware
Posts: 469
Blog Entries: 17

Rep: Reputation: 471Reputation: 471Reputation: 471Reputation: 471Reputation: 471
Quote:
Originally Posted by bassmadrigal View Post
(Pat highly suggests running generic kernels over huge and only provides huge as a starting point.)
This intrigues me, because I've been using only the huge kernel with Slackware since 1996. It's worked okay so far, but am I incurring a risk? What is the reasoning for preferring generic?
 
Old 02-06-2017, 05:14 AM   #57
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,322
Blog Entries: 1

Original Poster
Rep: Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749
With older hardware the generic kernel, along with the initrd, provides, IMHO, a noticeable performance improvement. With more "modern," as in faster, processors you may not even notice the difference between running the huge kernel vs. the generic.

Last edited by cwizardone; 02-06-2017 at 05:18 AM.
 
1 members found this post helpful.
Old 02-06-2017, 06:37 AM   #58
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,582

Rep: Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729Reputation: 1729
Quote:
Originally Posted by ttk View Post
This intrigues me, because I've been using only the huge kernel with Slackware since 1996. It's worked okay so far, but am I incurring a risk? What is the reasoning for preferring generic?
I'm not positive why he recommends that, but I imagine it is similar to what cwizardone mentioned... mainly a slight savings in resources/boot time.

But, Pat's official words can be found in the CHANGES_AND_HINTS.TXT file on your favorite mirror. He requests people to not report bugs unless they can reproduce it on a generic kernel.

Code:
Use one of the provided generic kernels for daily use.  Do not report
  bugs until/unless you have reproduced them using one of the stock 
  generic kernels.  You will need to create an initrd in order to boot
  the generic kernels - see /boot/README.initrd for instructions.
  The huge kernels are primarily intended as "installer" and "emergency" 
  kernels in case you forget to make an initrd.  For most systems, you 
  should use the generic SMP kernel if it will run, even if your system is 
  not SMP-capable.  Some newer hardware needs the local APIC enabled in the 
  SMP kernel, and theoretically there should not be a performance penalty 
  with using the SMP-capable kernel on a uniprocessor machine, as the SMP 
  kernel tests for this and makes necessary adjustments.  Furthermore, the 
  kernel sources shipped with Slackware are configured for SMP usage, so you 
  won't have to modify those to build external modules (such as NVidia or 
  ATI proprietary drivers) if you use the SMP kernel.
 
2 members found this post helpful.
Old 02-06-2017, 07:09 AM   #59
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2 on Lenovo Thinkpad W520
Posts: 7,158

Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
Quote:
Originally Posted by ttk View Post
This intrigues me, because I've been using only the huge kernel with Slackware since 1996. It's worked okay so far, but am I incurring a risk? What is the reasoning for preferring generic?
Quote:
Originally Posted by bassmadrigal View Post
But, Pat's official words can be found in the CHANGES_AND_HINTS.TXT file on your favorite mirror. He requests people to not report bugs unless they can reproduce it on a generic kernel.

Code:
Use one of the provided generic kernels for daily use.  Do not report
  bugs until/unless you have reproduced them using one of the stock 
  generic kernels.<snip>
I think that you are both right.

There is generally no issue running a huge kernel. In some cases though this can cause an issue. This could be the case if two kernel drivers claim the same device (this device being selected because it matches a glob that would be e.g. found in the output of "modinfo <module>|grep ^alias:" in case of a module) and the driver that takes over the device is not the "good" one.

If you use a generic kernel you can blacklist one of the drivers and see what happens. That is not possible if the drivers are built in, making difficult to analyze and solve the problem in that case.

So my understanding is : in most cases running a huge kernel is fine, but use a generic kernel if need be. "If need be" includes but is not limited to issues that could be linked to conflicting or "not the good one" kernel drivers, and configurations that need an initrd, like including encrypted partitions.

Last edited by Didier Spaier; 02-06-2017 at 02:03 PM. Reason: s/handover/takes over/ Why may we not write in French #~@!???
 
3 members found this post helpful.
Old 02-07-2017, 10:55 AM   #60
fsauer
Member
 
Registered: Jul 2012
Posts: 72

Rep: Reputation: Disabled
huge vs. generic

I did some testing here. For me, the huge kernel boots about 3 to 4 seconds (not significantly) faster than the generic kernel. Considering that, I decided not to get into the hassle of initrd construction after kernel upgrades

(>5 year old desktop, intel core 5, nvidia, off the shelf sata drive, slackware current)

Obviously, this is only a tiny test...

Have a nice day

Franz
 
2 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
Linux.conf.au: Latest Linux kernel release due early March DragonSlayer48DX Linux - News 0 01-18-2010 10:43 PM
No video on latest kernel release Tralce Linux - Kernel 3 11-30-2006 07:48 AM
What is the latest Redhat release TILEMANN Linux - Software 5 11-20-2006 10:48 PM
LXer: News: OpenVZ To Release Support, Patches for Latest Kernel LXer Syndicated Linux News 0 11-01-2006 10:54 PM
latest debian release? doralsoral Linux - Software 5 12-25-2004 12:40 PM


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

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration