<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - please introduce more special targets for facilities like entropy, or netfilter rules" href="https://bugs.freedesktop.org/show_bug.cgi?id=80169#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - please introduce more special targets for facilities like entropy, or netfilter rules" href="https://bugs.freedesktop.org/show_bug.cgi?id=80169">bug 80169</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>Well, we will not lose ourselves in trying to come up with way too generic hook points. We can certainly add some, but you have to make very good, very specific requests for them. And I am pretty sure I have no interest in adding more hook points for the networking mess, this is already too complex: <a href="http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/">http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/</a> We really have to strike the balance here between being generic and being to complex. And complexity starts already with dumping too many unused and weakly defined unit names on them. We shouldn't add all kinds of targets people *might* use one day. Also, it's not sufficient if only very specific setups need it, with systemd upstream we want to cover the general purpose cases. Anyway, to keep this short: please make very specific, concise requests about additional targets and we will consider them.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>