Stuart Henderson <[email protected]> writes: > 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.
Indeed. > 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" I support this option. Making things easier for updates matters more to me than saving a byte in a file name. >From a general point of view, I'd be fine if we used only /dev/bpf0 everywhere. No extra /dev/ entry, no compat/upgrade question, no difference between base and ports. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
