public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_* used by user-space to figure out whether a feature is on/off
Date: Mon, 15 Jul 2013 17:57:57 -0700	[thread overview]
Message-ID: <1373936277.31535.6.camel@warfang> (raw)
In-Reply-To: <CA+55aFzAg-yU4sX2F8NA0+RZT0v_T3vKc_JrPpX9rXE8-Ofd1A@mail.gmail.com>

On Mon, 2013-07-15 at 17:53 -0700, Linus Torvalds wrote:
> On Mon, Jul 15, 2013 at 5:46 PM, Raymond Jennings <shentino@gmail.com> wrote:
> >
> > I'd like to point out that Google Chrome also makes use of CONFIG_ tests
> > to detect support for namespaces and pid containers and stuff.
> 
> Hmm. It must work fine despite that. Because I run self-compiled
> kernels and there are no config files to be found by user apps.
> Neither in /proc nor in /boot. And I'm using chrome to write this.
> 
>               Linus

It could be the quirks of my package manager though.

I run Gentoo, so it's entirely possible that the ebuild is doing all the
bitching, but chrome itself just fails gracefully and falls back to not
using those features if it can't find them.

I imagine though that the same stuff applying to applications in general
should also apply to installers.

Anyway I just wanted to highlight that it's not just the xen stuff
that's peeking at kernel config.


      reply	other threads:[~2013-07-16  0:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:40 CONFIG_* used by user-space to figure out whether a feature is on/off Konrad Rzeszutek Wilk
2013-07-15 17:02 ` Greg KH
2013-07-15 17:24   ` Konrad Rzeszutek Wilk
2013-07-15 17:46     ` Linus Torvalds
2013-07-15 18:02       ` Konrad Rzeszutek Wilk
2013-07-15 18:25         ` Paul Bolle
2013-07-15 19:03           ` Konrad Rzeszutek Wilk
2013-07-15 19:13             ` Paul Bolle
2013-07-15 17:17 ` Linus Torvalds
2013-07-16  0:46   ` Raymond Jennings
2013-07-16  0:53     ` Linus Torvalds
2013-07-16  0:57       ` Raymond Jennings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1373936277.31535.6.camel@warfang \
    --to=shentino@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox