From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [HEADS UP] udev-181
Date: Mon, 19 Mar 2012 11:15:11 -0700 [thread overview]
Message-ID: <CAK2H+ec_28cOamGYWMc3n_ci1V+DTCLq=JnkTVGFYkfTuVT5yQ@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiBCKWd-0B3AoLHaL9v5qfdJAccNnnz4HJLHEHTOqrWtBg@mail.gmail.com>
On Mon, Mar 19, 2012 at 8:15 AM, Michael Mol <mikemol@gmail.com> wrote:
<SNIP>
>
> Is there an ENOTICE warning in the ebuild to hit people over the head
> with these?
>
> Also, how trivial would it be to have the ebuild check the running
> kernel config (if available under /proc or wherever) for the necessary
> config options?
Concerning the kernel config stuff file an enhancement request. Dracut
checks for the same variable. They should be able to just copy it from
there.
- Mark
next prev parent reply other threads:[~2012-03-19 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 14:56 [gentoo-user] [HEADS UP] udev-181 walt
2012-03-19 15:15 ` Michael Mol
2012-03-19 15:55 ` [gentoo-user] " walt
2012-03-19 18:15 ` Mark Knecht [this message]
2012-03-19 17:54 ` [gentoo-user] " jason
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='CAK2H+ec_28cOamGYWMc3n_ci1V+DTCLq=JnkTVGFYkfTuVT5yQ@mail.gmail.com' \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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