https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235920
--- Comment #7 from Zhenlei Huang <z...@freebsd.org> --- (In reply to Franco Fichtner from comment #6) > And tun/tap is a little tricky in its own regard here since the device nodes > that > may be required by the service are never being renamed (/dev/tunX etc.). Yes, you are right. For tap(4), even its unit number is freed the original controller device should still exist so that the applications (which have opened the /dev/tap) will not be disturbed. I'm proposing UUID naming to fix that. Please see https://reviews.freebsd.org/D39689 . For the design of tap(4), why not create `/dev/tap/some-uuid-name` and an alias `/dev/tap0 -> /dev/tap/some-uuid-name` ? -- You are receiving this mail because: You are the assignee for the bug.
