On 2016/05/02 09:34, Martin Natano wrote: > Diff below simplifies the device open path and removes an explanation > about bpf device nodes from the manpage.
There's a problem with this. If someone is doing an "untar sets" upgrade (which is not _supported_ but is pretty much necessary in some situations) and relies on dhclient for network to get back in to the system, they lose. Since they won't have a new MAKEDEV at the right time, I think our options are either "change dhclient back to using /dev/bpf0" or "tell them to run mknod manually before updating". (The other programs are affected too of course, but those are less likely to lock people out of remote systems so they should be able to fix them more easily).
