From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: udev_141 vs. udev_network_queue.sh
Date: Thu, 15 Mar 2012 14:32:50 +0100 [thread overview]
Message-ID: <4F61EF82.6060609@dresearch-fe.de> (raw)
In-Reply-To: <CAAwVp3u7i6ptQ=dvCV_RGwctHqDWKLXXPXKjGwZJ_okhDx8gwg@mail.gmail.com>
On 13.03.2012 16:06, Mario Schuknecht wrote:
> The udev script /etc/udev/scripts/network.sh writes all not configured
> interfaces into the file /dev/udev_network_queue
> root@3065-4-00001:~# cat /dev/udev_network_queue
> eth0
> lo
> ra0
> But no script or program check this file.
> I googled udev_network_queue and found an old bitbake recipe
> http://svn.nslu2-linux.org/svnroot/slugos/releases/slugos-3.10-beta/openembedded/packages/udev/udev_084.bb
> that
> installs udev_network_queue.sh.
> That script checks this files and starts the interfaces.
>
> Why is this file not installed any longer? Is there any other way or
> concept to handle this situation?
It seems that the installation of this script was lost in between udev_084 and udev_089. The latter was introduced by Philipp Zabel (commit 83e3ce3dbc5f49a7c8ee4b535ed14d8938c252aa).
Can someone remember if this script wasn't installed any longer by intention or by mistake?
Should it be installed in later udev versions again?
Regards,
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2012-03-15 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 15:06 udev_141 vs. udev_network_queue.sh Mario Schuknecht
2012-03-15 13:32 ` Steffen Sledz [this message]
2012-03-19 8:56 ` Philipp Zabel
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=4F61EF82.6060609@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.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.