[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#783995: marked as done ([feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels)

Your message dated Sat, 02 May 2015 13:24:19 +0100
with message-id <1430569459.4113.32.camel@decadent.org.uk>
and subject line Re: Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
has caused the Debian Bug report #783995,
regarding [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
783995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783995
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 3.16.7-ckt7-1

Hi,

It would help me very much, if Debian kernel provided a quick ability
to see it's own configuration in /proc/config.gz.

Reason:
in some cases viewing current kernel configuration via "#
/boot/config-$(uname -r)" is not available; For example when working
with Debian-installer (booting from DVD), or working inside an OpenVZ
(or LXC) container.

For those reasons I ask you to enable "/proc/config.gz" in all
supported Debian kernels (Debian 6, 7 and 8), if possible.

As far as I'm aware it's stable feature, and there is no downside from
enabling it.

+General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz

Original article:
http://superuser.com/questions/287371/obtain-kernel-config-from-currently-running-linux-system

Thanks in advance,
--
-Alexey Eromenko "Technologov", 01.May.2015.

--- End Message ---
--- Begin Message --- 
On Sat, 2015-05-02 at 02:19 +0300, Alexey Eromenko wrote:
> >Why would it be good for this to be exposed inside a container?
> 
> So that applications know, if they can use advanced features such as
> AppArmor or not.

Applications MUST NEVER parse the kernel config; it is not part of the
stable userland ABI.

> And to give more complete environment for the admins.

The host's kernel config doesn't tell you what features are available in
the container.

> Plus, to debug problems inside debian-installer. (it
> lacks /boot/config), like bug # 783982, where normal Debian 8 kernel
> supports floppy /dev/fd0, but d-I kernel doesn't. 

No, the kernel config is the same, but not all modules are included.

> Why it can't be changed in stable releases?  I mean if the change is
> small and beneficial, why not ? (Assuming it doesn't require major
> kernel source code changes, but only kernel config)

Because that's what stable means.  We fix bugs and add hardware support,
we don't add features like this.

We've now established that this won't solve the problems you thought it
could, so closing.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: