<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 18-02-2015 18:49, Reindl Harald
wrote:<br>
</div>
<blockquote cite="mid:54E4FACC.6090804@thelounge.net" type="cite">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 12px;" lang="x-unicode">that won't change the fact
that if <b class="moz-txt-star"><span class="moz-txt-tag">*</span>anybody<span
class="moz-txt-tag">*</span></b> comes to the idea to take
an interface which <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>is up<span class="moz-txt-tag">*</span></b>
down for rename it should get removed any commit permissions
instantaneously because he don't care about <b
class="moz-txt-star"><span class="moz-txt-tag">*</span>a ton<span
class="moz-txt-tag">*</span></b> of implications depending
on the local environment doing so
<br>
<br>
</div>
</blockquote>
First of all, I'm not a systemd dev. Nor want to be. Secondly, I
believe you didn't really understood my proposition. You are talking
about userspace *after* initramfs and *after* systemd is initialized
and renamed (or not) any interface. Of course systemd should *never*
mess with an interface *after* system initialization. But it can do
anything *right after* the initramfs hand the control to systemd. Of
course except if the interface is up for a nfsroot. In this case the
renaming shouldn't happen. But this is an exception.<br>
<br>
Cheers,<br>
Giancarlo Razzolini<br>
</body>
</html>