Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/7] systemd: don't recommend IPv6 kernel module
Date: Wed, 27 Feb 2013 17:07:31 +0100	[thread overview]
Message-ID: <1361981251.1809.12.camel@rrMBP> (raw)
In-Reply-To: <CAJTo0Lav+DWFa_XRCJKmZ6=GhTq4gn7Zge2bCAy8_FKviPajjQ@mail.gmail.com>

On Wed, 2013-02-27 at 14:53 +0000, Burton, Ross wrote:
> On 27 February 2013 14:40, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > On Wed, 2013-02-27 at 14:17 +0000, Ross Burton wrote:
> >> systemd doesn't need ipv6 support directly, so don't pull it.
> >
> > It will trigger an error on startup, which seems to scare most of my
> > users :(
> 
> Well that's silly of systemd isn't it.  Just noticed it didn't cause a
> problem here because the BSP I'm testing on appears to put ipv6 into
> the kernel
> 
> Can you point to where the log is coming from - silencing that warning
> seems like a sensible thing to do, as no ipv6 is a legitimate choice
> (albeit rapidly not a sane choice...)

src/core/kmod-setup.c:

static const KModule kmod_table[] = {
        { "autofs4",  "/sys/class/misc/autofs",    NULL } ,
        { "ipv6",     "/sys/module/ipv6",          NULL },
        { "unix",     "/proc/net/unix",            NULL } ,
};

[..]

                err = kmod_module_probe_insert_module(mod,
KMOD_PROBE_APPLY_BLACKLIST, NULL, NULL, NULL, NULL);
                if (err == 0)
                        log_info("Inserted module '%s'",
kmod_module_get_name(mod));
                else if (err == KMOD_PROBE_APPLY_BLACKLIST)
                        log_info("Module '%s' is blacklisted",
kmod_module_get_name(mod));
                else
                        log_error("Failed to insert module '%s'",
kmod_module_get_name(mod));

And looking at the other code you'll need to load ipv6 before starting
the sockets otherwise socket activation over ipv6 won't work.

regards,

Koen




  reply	other threads:[~2013-02-27 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 14:17 [PATCH 0/7] systemd tweaks Ross Burton
2013-02-27 14:17 ` [PATCH 1/7] systemd: systemd uses libkmod instead of modprobe, remove dependencies Ross Burton
2013-02-27 14:17 ` [PATCH 2/7] systemd: don't recommend IPv6 kernel module Ross Burton
2013-02-27 14:40   ` Koen Kooi
2013-02-27 14:53     ` Burton, Ross
2013-02-27 16:07       ` Koen Kooi [this message]
2013-02-27 14:17 ` [PATCH 3/7] systemd: make gcrypt support (for signing the journal) optional Ross Burton
2013-02-27 14:17 ` [PATCH 4/7] systemd: remove unused cached configure variables Ross Burton
2013-02-27 14:17 ` [PATCH 5/7] systemd: make xz support (compressed journal) optional Ross Burton
2013-02-27 14:41   ` Koen Kooi
2013-02-27 14:58     ` Burton, Ross
2013-02-27 14:17 ` [PATCH 6/7] systemd: remove --with-distro option, it's not used Ross Burton
2013-02-27 14:17 ` [PATCH 7/7] systemd: set the location of the kill binary Ross Burton
2013-02-27 17:26   ` Otavio Salvador

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=1361981251.1809.12.camel@rrMBP \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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