I don't have the roborio available, so no pictures. I did grab some logfiles, however. If you ssh into the roborio, check out /var/log/messages. You'll find messages like this:
Code:
Jan 25 16:55:38 roboRIO-1418 nimDNSResponder: Local Hostname roboRIO-1418.local already in use; will try roboRIO-1479.local instead
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Received from 10.14.18.20:5353 20 20.18.14.10.in-addr.arpa. PTR roboRIO-1418.local.
Jan 25 16:55:40 roboRIO-1418 nimDNSResponder: mDNSCoreReceiveResponse: Unexpected conflict discarding 20 20.18.14.10.in-addr.arpa. PTR roboRIO-1479.local.
Looking at the log closer, you'll see messages from avahi-daemon and nimdnsresponder, which have the same purpose. However, if you look at my other post, some further investigation today has shown that if I disable one or the other, then I end up with different effects. Apparently the driver station requires the avahi-daemon, but my OSX machines cannot resolve the hostname when it's enabled.
You can also use "ps -Af" to see avahi-daemon and nimdnsresponder both running.
You might check to see if you have iTunes/bonjour installed, as they provide a similar mDns service, and it might have the same problems that we have on OSX.
You can find rc.d symlinks to activate the services in /etc/rc5.d/...avahi-daemon and /etc/rc5.d/...nimdnsresponder