mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom-hi6Y0CQ0nG0@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dracut: automatically add "unix" kernel module
Date: Fri, 12 Aug 2011 09:58:35 +0200	[thread overview]
Message-ID: <2596808.kGfioqbkmA@ernie> (raw)
In-Reply-To: <4E44C1B0.7050605-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

Hello!

Please CC me, since I am not on the list.

Am Freitag, 12. August 2011, 06:41:56 schrieb WANG Cong:
> On Fri, 12 Aug 2011 08:01:20 +0200, Harald Hoyer wrote:
> > On 12.08.2011 01:01, Dennis Schridde wrote:
> >> Dracut currently does not seem to automatically include the "unix"
> >> kernel module in the initramfs, which causes udev to be unable to start
> >> ("address family not supported by protocol").
> >
> > Just add a file /etc/modprobe.d/myaliases.conf to your system,
> > containing: alias net-pf-1 unix
> 
> The kernel already does the same thing:
> 
> MODULE_ALIAS_NETPROTO(PF_UNIX);
> 
> don't know why udev can't load it automatically...

The problem is that dracut does not automatically include the "unix" module in 
the initramfs it generates. If I include the module manually (via 
"add_drivers" in dracut.conf) it will be successfully loaded.

Does the kernel use a different aliases table than dracut?

Kind regards,
Dennis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2011-08-12  7:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 23:01 dracut: automatically add "unix" kernel module Dennis Schridde
2011-08-12  6:01 ` Harald Hoyer
2011-08-12  6:41   ` WANG Cong
2011-08-12  6:47     ` Harald Hoyer
     [not found]   ` <4E44C1B0.7050605-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-12  7:58     ` Dennis Schridde [this message]
2011-08-12  8:09       ` Harald Hoyer
2011-08-15  6:21         ` WANG Cong

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=2596808.kGfioqbkmA@ernie \
    --to=devurandom-hi6y0cq0ng0@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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