On Mon, 07 Apr 2014 12:38:15 -0400 (EDT), Brian Potkin wrote:
...
8. Observed there was a file, tmp-rules--70-persistent-net.rules, in
/run/udev. It had entries for the machine's two interfaces.
Yes, it seems that the temporary file is being created. It just isn't
being copied to the
Hi,
Am 08.04.2014 11:59, schrieb Stephen Powell:
On Mon, 07 Apr 2014 12:38:15 -0400 (EDT), Brian Potkin wrote:
...
8. Observed there was a file, tmp-rules--70-persistent-net.rules, in
/run/udev. It had entries for the machine's two interfaces.
Yes, it seems that the temporary file is
Am 08.04.2014 12:36, schrieb Michael Biebl:
# copy the rules generated before / was mounted read-write
for file in /dev/.udev/tmp-rules--* /run/udev/tmp-rules--*; do
dest=${file##*tmp-rules--}
[ $dest = '*' ] continue
cat $file /etc/udev/rules.d/$dest
rm -f $file
done
I'll
On Tue, 08 Apr 2014 06:36:37 -0400 (EDT), Michael Biebl wrote:
Ubuntu has named the upstart job /etc/init/udev-finish.
Debian has a file called /etc/init/udev-finish.conf, and I
tried changing the similar logic there to reference directory
/run/udev instead of /dev/.udev, but it didn't seem to
Am 08.04.2014 12:58, schrieb Stephen Powell:
On Tue, 08 Apr 2014 06:36:37 -0400 (EDT), Michael Biebl wrote:
Ubuntu has named the upstart job /etc/init/udev-finish.
Debian has a file called /etc/init/udev-finish.conf, and I
tried changing the similar logic there to reference directory
On Tue, 08 Apr 2014 07:13:42 -0400 (EDT), Michael Biebl wrote:
Stephen Powell wrote:
Debian has a file called /etc/init/udev-finish.conf, and I
tried changing the similar logic there to reference directory
/run/udev instead of /dev/.udev, but it didn't seem to have
any effect. Adding the
On Sat 05 Apr 2014 at 19:29:51 -0400, Stephen Powell wrote:
In the past, the init scripts contained a work-around for this problem
by re-directing output to a temporary file. Originally, this file was
called /dev/.udev/tmp-rules--70-persistent-net.rules. In later releases,
the name of the
On Mon 07 Apr 2014 at 09:54:37 +0100, Brian Potkin wrote:
A way to fix this bug would be to implement Predictable Network
Interface Names. The case is well made at at
And then you remember having read
https://lists.debian.org/debian-devel/2013/09/msg00180.html
and
On Sat 05 Apr 2014 at 19:29:51 -0400, Stephen Powell wrote:
Thanks for your research, Brian. None of the above surprises me, based
It's about all I can do because my understanding of how udev works is
sparse. Continuing:
8. Observed there was a file, tmp-rules--70-persistent-net.rules, in
On Fri 04 Apr 2014 at 06:28:48 +0200, Michael Biebl wrote:
On 4. April 2014 05:43:10 MESZ, Stephen Powell zlinux...@wowway.com wrote:
You may ship it, but it doesn't actually work. It may be useful during
installation, but if you erase the file after installation, it does not
get
On Sat, 05 Apr 2014 10:16:10 -0400 (EDT), Brian Potkin wrote:
The following was done on an install from d-i's Jessie Alpha 1 release.
Only the base system was installed, so no DE.
1. Observed that 70-persistent-net.rules was created by 'Detect network
hardware' and was present on first
On 04/03/2014 11:28 PM, Michael Biebl wrote:
On 4. April 2014 05:43:10 MESZ, Stephen Powell zlinux...@wowway.com wrote:
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this doesn't tell the whole story. While it is true, that
upstream has deliberately removed that
Am 04.04.2014 14:57, schrieb Dale Schroeder:
On 04/03/2014 11:28 PM, Michael Biebl wrote:
On 4. April 2014 05:43:10 MESZ, Stephen Powell zlinux...@wowway.com
wrote:
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this doesn't tell the whole story. While it is true,
On 04/04/2014 8:17 AM, Michael Biebl wrote:
Am 04.04.2014 14:57, schrieb Dale Schroeder:
On 04/03/2014 11:28 PM, Michael Biebl wrote:
On 4. April 2014 05:43:10 MESZ, Stephen Powell zlinux...@wowway.com
wrote:
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this
On Fri, 04 Apr 2014 07:57:42 -0500, Dale Schroeder wrote:
...
Also referencing one of Stephen's comments:
If you only have one network interface of a given type, you
probably don't need this file. After all, if your machine only
has one ethernet interface, it's a pretty safe bet that it
On Thu, 03 Apr 2014 08:17:46 -0500, Dale Schroeder wrote:
It looks like that discussion is almost 3 years old.
Debian is just now switching to systemd. udev was a separate
package in wheezy. Under jessie it is part of systemd.
And the systemd version of udev has made some changes.
Do you
Am 04.04.2014 03:12, schrieb Stephen Powell:
In short, this bug is not a bug. It is an intentional design change
made by upstream. 70-persistent-net.rules is not going to be created
or maintained automatically anymore. But it is still honored during
boot, if it is present; and you can
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this doesn't tell the whole story. While it is true, that
upstream has deliberately removed that feature (for the reasons you
mentioned, renaming network interfaces within the same namespace is
racy), in the Debian udev
On 4. April 2014 05:43:10 MESZ, Stephen Powell zlinux...@wowway.com wrote:
On Thu, 03 Apr 2014 22:14:28 -0400 (EDT), Michael Biebl wrote:
Actually, this doesn't tell the whole story. While it is true, that
upstream has deliberately removed that feature (for the reasons you
mentioned,
19 matches
Mail list logo
