Sepherosa Ziehau wrote:
On 1/9/07, Matthew Dillon <[EMAIL PROTECTED]> wrote:---- Virtual Kernel In Search of Network Interface!Would someone like to write a pseudo network driver for the virtualkernel this week, for the release? Sephe maybe? It has to be someonefamiliar with NETIF due to our release deadline. The /usr/src/sys/dev/virtual/net directory is empty and waiting!./kernel.debug -I /dev/tap0 -r /opt/vkernel/rootimg.01 -m 128m # ifconfig vke0 vke0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.4.6 netmask 0xffffff00 broadcast 192.168.4.255 inet6 fe80::2257:ff:fe00:0%vke0 prefixlen 64 scopeid 0x1 ether 20:57:00:00:00:00 :DD http://leaf.dragonflybsd.org/~sephe/vke.diff Hope ppl can improve it, when I wake up tomorrow.
Hmm, might I propose a uniform naming scheme for drivers which are meant for the vkernel?
Matt named the disk device 'vd'. Following this scheme, the ethernet driver could be named 've'. What do people think about this?
I actually don't mind if it's 'vk' or 'v' as a prefix, so vkd for the disk driver and vke for the network driver would be fine with me as well. It's just that I'd like to write a vdevice(4) manpage (or something like that) which discusses all drivers for vkernel, and I thought it could be nice to point out that all those drivers follow some uniform naming scheme.
Now would be a good time to agree on one. Regards, Sascha -- http://yoyodyne.ath.cx
