<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - udev 197 network device renaming race condition"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59964#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - udev 197 network device renaming race condition"
href="https://bugs.freedesktop.org/show_bug.cgi?id=59964">bug 59964</a>
from <span class="vcard"><a class="email" href="mailto:shados@shados.net" title="Alexei Robyn <shados@shados.net>"> <span class="fn">Alexei Robyn</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=59964#c2">comment #2</a>)
<span class="quote">> This looks like the same issue:
>
> <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Predictable interface names are inconsistent"
href="show_bug.cgi?id=59610">https://bugs.freedesktop.org/show_bug.cgi?id=59610</a>
>
> if this is also about dhcpcd, then we should close this one as duplicate....</span >
It's not about dhcpcd per se, it's about simple networking unit files (straight
`ip` commands configuring a static address, for instance). Your point about
network configuration tools is true, but you don't always necessarily want to
use them if your network configuration is pretty trivial. For that kind of
situation, it'd be a lot nicer if you could just trigger off of network.target
and not have to worry about writing code to wait on udev's renaming of
boot-time interfaces to finish.
True, this kind of simplistic configuration approach isn't exactly durable, but
it does work well in a lot of situations and is useful during initial setup and
any other circumstance where you might not have access to more flexible tools.
If you haven't read it already, the Arch forums link at the bottom of my report
may help illuminate things.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>