From: devzero@web.de
To: 7eggert@gmx.de, David Miller <davem@davemloft.net>
Cc: bunk@kernel.org, jengelh@computergmbh.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in
Date: Mon, 31 Dec 2007 14:23:01 +0100 [thread overview]
Message-ID: <78342039@web.de> (raw)
when i had that module modular and added to the initrd, udev didn`t work, though.
same error message:
udevd[1226]: init_udev_socket: error getting socket: Address family not supported by protocol
not sure if i did a mistake here....
anyway, this message is not obvious to the end user.
i like the kernel being modular, but i also like it if things "just work" - and with "allmodconfig", modular UNIX domain sockets seem to create hassle.
(see http://forums.gentoo.org/viewtopic-t-476363-highlight-.html or http://forums.gentoo.org/viewtopic-t-463793-highlight-.html )
so, if this patch is being rejected, maybe it would be useful if udev would give a proper hint, if it`s missing this kernel feature.
btw, udev documentation telling this:
- The kernel must have sysfs, unix domain sockets and networking enabled.
(unix domain sockets (CONFIG_UNIX) as a loadable kernel module may work,
but it is completely silly - don't complain if anything goes wrong.)
furthermore, if this needs to be modular, then i`d please have tcp/ip networking modular, too. :)
regards
roland
ps:
not being a skilled programmer, so this is mostly an admins/users perspective.
>
> From: Bodo Eggert <7eggert@gmx.de>
> Date: Mon, 31 Dec 2007 13:09:43 +0100 (CET)
>
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and fails to run if UNIX=m.
> >
> > Signed-Off-By: Bodo Eggert <7eggert@gmx.de>
>
> People who use udev can make sure they have it built into their kernel
> if they have such a dependency.
>
> Not everyone uses udev, and therefore needs AF_UNIX non-modular.
>
> I keep seeing this crap patch get submitted and I'm going to keep
> dropping it because it's bogus.
>
> It seems to stem from some filesystem interface or whatever that the
> VFS folks don't want to export or one they want to now stop exporting.
>
> But that is a really cruddy reason to want to force AF_UNIX to not
> be allowed to be modular, and the udev thing just makes it more of a
> joke rather than a good technical reason.
>
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
WARNING: multiple messages have this Message-ID (diff)
From: devzero@web.de
To: 7eggert@gmx.de, David Miller <davem@davemloft.net>
Cc: bunk@kernel.org, jengelh@computergmbh.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in
Date: Mon, 31 Dec 2007 14:23:01 +0100 [thread overview]
Message-ID: <78342039@web.de> (raw)
when i had that module modular and added to the initrd, udev didn`t work, though.
same error message:
udevd[1226]: init_udev_socket: error getting socket: Address family not supported by protocol
not sure if i did a mistake here....
anyway, this message is not obvious to the end user.
i like the kernel being modular, but i also like it if things "just work" - and with "allmodconfig", modular UNIX domain sockets seem to create hassle.
(see http://forums.gentoo.org/viewtopic-t-476363-highlight-.html or http://forums.gentoo.org/viewtopic-t-463793-highlight-.html )
so, if this patch is being rejected, maybe it would be useful if udev would give a proper hint, if it`s missing this kernel feature.
btw, udev documentation telling this:
- The kernel must have sysfs, unix domain sockets and networking enabled.
(unix domain sockets (CONFIG_UNIX) as a loadable kernel module may work,
but it is completely silly - don't complain if anything goes wrong.)
furthermore, if this needs to be modular, then i`d please have tcp/ip networking modular, too. :)
regards
roland
ps:
not being a skilled programmer, so this is mostly an admins/users perspective.
>
> From: Bodo Eggert <7eggert@gmx.de>
> Date: Mon, 31 Dec 2007 13:09:43 +0100 (CET)
>
> > As suggested by Adrian Bunk, UNIX domain sockets should always be built in
> > on normal systems. This is especially true since udev needs these sockets
> > and fails to run if UNIX=m.
> >
> > Signed-Off-By: Bodo Eggert <7eggert@gmx.de>
>
> People who use udev can make sure they have it built into their kernel
> if they have such a dependency.
>
> Not everyone uses udev, and therefore needs AF_UNIX non-modular.
>
> I keep seeing this crap patch get submitted and I'm going to keep
> dropping it because it's bogus.
>
> It seems to stem from some filesystem interface or whatever that the
> VFS folks don't want to export or one they want to now stop exporting.
>
> But that is a really cruddy reason to want to force AF_UNIX to not
> be allowed to be modular, and the udev thing just makes it more of a
> joke rather than a good technical reason.
>
_______________________________________________________________________
Jetzt neu! Schützen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2007-12-31 13:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 13:23 devzero [this message]
2007-12-31 13:23 ` [PATCH] Force UNIX domain sockets to be built in devzero
-- strict thread matches above, loose matches on Subject: below --
2007-12-31 12:09 Bodo Eggert
2007-12-31 12:20 ` David Miller
2007-12-31 14:03 ` Bodo Eggert
2007-12-31 19:38 ` Al Viro
2008-01-01 3:45 ` Bodo Eggert
2008-01-01 3:48 ` David Miller
2008-01-01 4:48 ` Bodo Eggert
2008-01-01 5:01 ` Theodore Tso
2008-01-02 10:25 ` Herbert Xu
2008-01-02 12:26 ` Bodo Eggert
2007-12-31 12:24 ` Adrian Bunk
2007-12-31 13:26 ` Bodo Eggert
2007-12-31 14:42 ` Adrian Bunk
2007-12-31 15:19 ` Bodo Eggert
2007-12-31 15:34 ` Jan Engelhardt
2007-12-31 17:43 ` Patrick Mau
2007-12-31 22:20 ` Jan Engelhardt
2007-12-31 17:51 ` Adrian Bunk
2007-12-31 18:05 ` Adrian Bunk
2007-12-31 15:55 ` Torsten Kaiser
2007-12-31 15:59 ` Michael Buesch
2007-12-31 16:01 ` Alan Cox
2007-12-31 16:17 ` Torsten Kaiser
2007-12-31 16:38 ` Alan Cox
2007-12-31 17:18 ` Michael Buesch
2007-12-31 18:37 ` Torsten Kaiser
2007-12-31 19:05 ` Michael Buesch
2007-12-31 16:11 ` Torsten Kaiser
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=78342039@web.de \
--to=devzero@web.de \
--cc=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.