All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Tom Gundersen <teg@jklm.no>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Simplifying kernel configuration for distro issues
Date: Sun, 22 Jul 2012 21:10:29 +0100	[thread overview]
Message-ID: <500C5E35.8090202@dgreaves.com> (raw)
In-Reply-To: <CAG-2HqVOJ=+YxaVOy2NSXt76zW8edJ0uP7NcObHhESwSwFHcqw@mail.gmail.com>

On 18/07/12 10:55, Tom Gundersen wrote:
> Linus,
> 
>> The point I'm slowly getting to is that I would actually love to have
>> *distro* Kconfig-files, where the distribution would be able to say
>> "These are the minimums I *require* to work". So we'd have a "Distro"
>> submenu, where you could pick the distro(s) you use, and then pick
>> which release, and we'd have something like
> 
> As someone working on one of the smaller distributions (Arch), I think
> it would be even better if rather than having "distro" entries, we'd
> have "application" entries. I.e., entries for applications that have
> specific kernel requirements/suggestions (udev, systemd, upstart,
> bootchart, pulseaudio, networkmanager, etc). If applications have soft
> requirements, they could have sub-entries explaining the benefit of
> enabling each.

Also coming from a 'very small distro' position; I had this problem a few months
ago... my solution was this:

https://github.com/lbt/mer-kernel-check/blob/master/mer_verify_kernel_config#L127

So I'd appreciate something very much along the lines of what various low-level
services need and why since that way we can share work between distros and
package maintainers and offer this kind of ability to our users too.

David

-- 
"Don't worry, you'll be fine; I saw it work in a cartoon once..."

  reply	other threads:[~2012-07-22 20:29 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  9:55 [RFC] Simplifying kernel configuration for distro issues Tom Gundersen
2012-07-22 20:10 ` David Greaves [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-13 20:37 Linus Torvalds
2012-07-13 20:54 ` Myklebust, Trond
2012-07-13 21:02 ` Dave Jones
2012-07-13 21:17   ` Linus Torvalds
2012-07-13 22:26     ` Josh Boyer
2012-07-19 15:26     ` Steven Rostedt
2012-07-19 15:43       ` Linus Torvalds
2012-07-19 16:12         ` Steven Rostedt
2012-07-19 15:45       ` Josh Boyer
2012-07-19 16:08         ` Steven Rostedt
2012-07-19 17:19           ` Josh Boyer
2012-07-19 17:30             ` Alan Cox
2012-07-19 17:38               ` Josh Boyer
2012-07-19 21:13               ` Ben Hutchings
2012-07-20  2:44                 ` david
2012-07-19 17:33             ` Steven Rostedt
2012-07-19 17:41               ` Alan Cox
2012-07-19 17:56               ` Josh Boyer
2012-07-19 18:13                 ` Steven Rostedt
2012-07-19 18:36                   ` Josh Boyer
2012-07-19 21:04                     ` david
2012-07-19 22:35                       ` Josh Boyer
2012-07-19 22:49                         ` Steven Rostedt
2012-07-21 20:47                 ` valdis.kletnieks
2012-07-19 18:20             ` Paul Bolle
2012-07-19 18:22               ` Josh Boyer
2012-07-19 18:49                 ` Geert Uytterhoeven
2012-07-19 18:55                   ` Paul Bolle
2012-07-19 21:30                 ` Geert Uytterhoeven
2012-07-13 21:29   ` Geert Uytterhoeven
2012-07-13 21:50   ` Paul Bolle
2012-07-13 21:55     ` Dave Jones
2012-07-13 22:11       ` Tony Luck
2012-07-13 22:20       ` Paul Bolle
2012-07-13 23:07       ` Frank Rowand
2012-07-13 21:06 ` Khalid Aziz
2012-07-13 21:17 ` Casey Schaufler
2012-07-13 21:20   ` Linus Torvalds
2012-07-13 22:13     ` david
2012-07-13 21:59 ` Hans de Bruin
2012-07-13 22:33 ` Jesper Juhl
2012-07-13 22:46   ` david
2012-07-14  9:44   ` Olivier Galibert
2012-07-14  4:18 ` Ben Hutchings
2012-07-14 12:35   ` Josh Boyer
2012-07-19  1:48 ` Steven Yong
2012-07-20  9:47 ` Jiri Kosina
2012-07-20 10:26   ` Sam Ravnborg

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=500C5E35.8090202@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teg@jklm.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.