[SOLVED] Kernel config

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
caliban
White ninja
White ninja
Posts: 9
Joined: 26 Jan 2011, 22:46
Location: USA

[SOLVED] Kernel config

Post#1 by caliban » 22 Feb 2011, 00:38

Can someone point me to the kernel .config file used in 1.0 Alpha ? Or even better can I suggest that it be enabled in the kernel itself (CONFIG_IKCONFIG_PROC). This came about while I was trying to determine if the kernel supported Multi LUN devices (CONFIG_SCSI_MULTI_LUN).

Supplying a .config or being able to pull the config from /proc/config.gz, would help other individuals and myself make those few kernel tweaks we need.
Last edited by caliban on 22 Feb 2011, 13:17, edited 1 time in total.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4546
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Kernel config

Post#2 by fanthom » 22 Feb 2011, 09:03

@caliban
config is built as "M" so you need to load it first:

modprobe configs && zcat /proc/config.gz > porteus.config

please add [SOLVED]
Please add [Solved] to your thread title if the solution was found.

caliban
White ninja
White ninja
Posts: 9
Joined: 26 Jan 2011, 22:46
Location: USA

Re: Kernel config

Post#3 by caliban » 22 Feb 2011, 13:17

You learn something new everyday. It never occurred to me to modprobe configs. I usually just use it for hardware drivers and never really considered it for anything else. For the record, CONFIG_SCSI_MULTI_LUN is Y (enabled).

Thanks and will mark it [SOLVED]

User avatar
fanthom
Site Admin
Site Admin
Posts: 4546
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: [SOLVED] Kernel config

Post#4 by fanthom » 23 Feb 2011, 08:25

"It never occurred to me to modprobe configs."
vmlinuz (kernel) needs to be unpacked to the memory at each boot. bigger vmlinuz size = longer boot time. kernel config is rarely needed for the user (if at all), that's why i have decided to compile it as a module (M).
Please add [Solved] to your thread title if the solution was found.

Post Reply