LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 08-14-2013, 05:25 AM   #1
bartgymnast
Member
 
Registered: Feb 2003
Location: Lelystad, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 272

Rep: Reputation: 93
kernel config options request


I would like to request the following options in the slackware kernel

CONFIG_UEVENT_HELPER_PATH=""
CONFIG_FW_LOADER_USER_HELPER=n (should not be set)
CONFIG_FHANDLE=y
CONFIG_IPV6=y
CONFIG_AUTOFS4_FS=y
CONFIG_SCHEDSTATS=y

Explanation of the 3 top options are below:


CONFIG_UEVENT_HELPER_PATH:
Path to uevent helper program forked by the kernel for every uevent. Before the switch to the netlink-based uevent source, this was used to hook hotplug scripts into kernel device events. It usually pointed to a shell script at /sbin/hotplug. This should not be used today, because usual systems create many events at bootup or device discovery in a very short time frame. One forked process per event can create so many processes that it creates a high system load, or on smaller systems it is known to create out-of-memory situations during bootup.

To disable user space helper program execution at early boot time specify an empty string here. This setting can be altered via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper later at runtime.

CONFIG_FW_LOADER_USER_HELPER:
On recent systems, if the kernel configures
CONFIG_FW_LOADER_USER_HELPER=y and a firmware is not found by the kernel, the kernel will issue a request which is ignored by userspace and will block in that for 60 seconds.

Udev is no longer in the game of firmware loading, not even as a fallback, it will just completely ignore all kernel firmware class events.

The source code in udev to handle firmware requests is disabled by default, currently still kept around for old kernels without the in-kernel firmware loader, but it will be deleted in the near future.

* slackware ships udev with the following configure options: --with-firmware-path=/lib/firmware/updates:/lib/firmware
this makes the above options in kernel useless


CONFIG_FHANDLE:
If you say Y here, a user level program will be able to map file names to handle and then later use the handle for different file system operations. This is useful in implementing userspace file servers, which now track files using handles instead of names. The handle would remain the same even if file names get renamed. Enables open_by_handle_at(2) and name_to_handle_at(2) syscalls.
 
Old 08-14-2013, 09:46 PM   #2
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,833
Blog Entries: 15

Rep: Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187Reputation: 1187
Didn't we ditch hotplug for udev to handle things like Firmware handling and such?
 
Old 08-15-2013, 04:35 AM   #3
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
Poor Pat. No sooner does 3.10.6 hit current than Greg releases 3.10.7! Still, it gives him the opportunity to look at the above I suppose.


Is anything making use of the new fhandle features yet? Slackware doesn't even include the man pages for those syscalls.

I'm not sure I agree with you on including ipv6 (which I don't use) and autofs4 (which I do use). IMO they're still not commonly used and better as modules. And schedstats isn't that a debug option in the kernel hacking section?

Last edited by GazL; 08-15-2013 at 05:08 AM.
 
Old 08-15-2013, 04:57 AM   #4
gmgf
Member
 
Registered: Jun 2012
Location: France
Distribution: Slackware Zenwalk
Posts: 166

Rep: Reputation: Disabled
kernel-3.10.6 have serious bug on usb2 sd device, don't mount and umount this device correctly here, reboot crash when a sd device is connected

i have compiled a kernel-3.10.7, and it work correctly
 
Old 08-15-2013, 05:28 AM   #5
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 876

Rep: Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826
Quote:
Originally Posted by GazL View Post
Poor Pat. No sooner does 3.10.6 hit current than Greg releases 3.10.7! Still, it gives him the opportunity to look at the above I suppose.
The first three changes are in the 3.10.6 kernels that are up now.

Quote:
Is anything making use of the new fhandle features yet? Slackware doesn't even include the man pages for those syscalls.
I'll give you one guess what is using them.

Quote:
I'm not sure I agree with you on including ipv6 (which I don't use) and autofs4 (which I do use). IMO they're still not commonly used and better as modules. And schedstats isn't that a debug option in the kernel hacking section?
I agree with this assessment.
 
4 members found this post helpful.
Old 08-15-2013, 05:33 AM   #6
Darth Vader
Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 659

Rep: Reputation: 138Reputation: 138
Also I strongly suggest:

Code:
CONFIG_DRM_LOAD_EDID_FIRMWARE=y
This feature is provided as a workaround for broken monitor hardware, and give the possibility to EDID data to be loaded from the /lib/firmware directory or one of the provided built-in data sets.

In other words, it offer an simple workaround for the well known "my KMS wants only 1024x768".

And no, the xorg.conf workaround is not a better solution, because, there we can use it as kernel parameter, and give possibility to activate this feature at will. Also, in this way, you fix also the kms console resolution. Personally, I have an (mini-)computer which have configured five monitors in this way.

Later...
I just discovered that the latest kernel update, at 3.10.6, ship that option activated. Thanks, P.V.!

Last edited by Darth Vader; 08-15-2013 at 08:52 AM.
 
1 members found this post helpful.
Old 08-15-2013, 06:20 AM   #7
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024
Quote:
Originally Posted by volkerdi View Post
I'll give you one guess what is using them.
That which must not be named?
 
3 members found this post helpful.
Old 08-15-2013, 06:45 PM   #8
astrogeek
Senior Member
 
Registered: Oct 2008
Distribution: Slackware [64]X{.0|.1|.2|-current} ::X>=12<=14, FreeBSD_10{.0|.1}
Posts: 2,165

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Quote:
Originally Posted by GazL View Post
Poor Pat. No sooner does 3.10.6 hit current than Greg releases 3.10.7! Still, it gives him the opportunity to look at the above I suppose.
But Pat rises to the challenge...

Code:
Thu Aug 15 21:23:13 UTC 2013
a/bash-4.2.045-i486-1.txz:  Upgraded.
a/kernel-generic-3.10.7-i486-1.txz:  Upgraded.
a/kernel-generic-smp-3.10.7_smp-i686-1.txz:  Upgraded.
a/kernel-huge-3.10.7-i486-1.txz:  Upgraded.
a/kernel-huge-smp-3.10.7_smp-i686-1.txz:  Upgraded.
a/kernel-modules-3.10.7-i486-1.txz:  Upgraded.
a/kernel-modules-smp-3.10.7_smp-i686-1.txz:  Upgraded.
d/kernel-headers-3.10.7_smp-x86-1.txz:  Upgraded.
k/kernel-source-3.10.7_smp-noarch-1.txz:  Upgraded.
extra/bash-completion/bash-completion-2.1-noarch-1.txz:  Upgraded.
extra/linux-3.10.7-nosmp-sdk/*:  Upgraded.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.
 
Old 08-19-2013, 02:17 AM   #9
jon lee
Member
 
Registered: Jul 2013
Posts: 81

Rep: Reputation: Disabled
Quote:
Originally Posted by GazL View Post
That which must not be named?
I'm guessing kio_nfs.so -ltirpc?
http://nfsv4.bullopensource.org/doc/tirpc_rpcbind.php
 
  


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] Kernel 3.9.7 config request torimus Slackware 4 07-20-2013 07:07 AM
essential kernel config-options rasidrasid Linux - Software 2 07-07-2012 03:45 PM
Options Missing in Kernel config sushemsu Linux - Kernel 2 06-13-2010 10:04 PM
Kernel config options elmu Linux - General 2 11-02-2005 12:15 PM
kernel config options for soundblaster acidjuice Slackware 6 02-24-2005 04:57 PM


All times are GMT -5. The time now is 01:35 AM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration