Please explain what you mean by "control network of BeagleBone": What OS were the BeagleBones running, and in what fashion were you controlling them? What part didn't work in Linux? How did OpenBSD improve matters? I'm interested in the details; I don't have a network of BeagleBones, but a much smaller system: one FreeBSD server, one Linux Raspberry data acquisition node, and two more RPi on the workbench waiting to be outfitted, programmed and deployed.
By the way, this question has nothing to do with desktop usage and suspend.
These are the step I followed and their motivation, at the best I can remember.
1] BeagleBone Black is different respect RPI, it comes with Linux preloaded in built in memory.
2] BBB comes with the possiblity to connect via USB as if it was a network device, address
by defaul si 192.168.7.2, by heart.
3] If you try to connect to it via OSX 10.11.6 (even installing the suggested drivers) you will
go crazy. Sometimes it works sometims it does not (experiments took place several months ago)
4] I found problems connecting event to buitin serial via OSX.
5] About 8 months ago I had (3 BBB, 2 RPI, 2 Soekris, 2 Alix) available to deploy.
6] Since OSX was driving me crazy (in trying to connecto the them) I had two solutions to try [1] OpenBSD [2] Linux. Linux because it was my Desktop OS (running in VMware inside OSX). OpenBSD because i used before it in other servers and I liked the documentation. Expecially I appreciated it when I set up a VPN server.
7] OpenBSD resulted in a perfectly stable serial connection
8] OpenBSD resulted best solution (for documentation and stability) for :
8.1] setting up a NAT, for the embedded systems
8.2] Setting up the routing rules, firewall, DHCPD, and SFTPD (that was mainly for Soekris and ALIX)
8.3] I tried to do the same stuff in Debian (which was my default VMWachine) it was much
more difficult to set up and documentation was super scattered. I was never sure 100%
what i was doing was correct.
9] => At some point I decied all embedded stuff that needed maintenance or a different configuration should have been connected directly to my laptop (and old macbook) and controlled via serial by the OpenBSD VirtualMachine; their network managed, again, by the OpenBSD VM.
10] Next, when I was able to control well the BBB, that means GPIO, PWM,
ADC and PRUS; I decied that it was my preferred platform for small embedded and automation. I abandoned the RPI.
11] One day I decied to make a Wifi Router for the office with a BBB. Since networking in OpenBSD has always proved to me to be better organized than in Linux I wanted to make int in OpenBSD. I tried to install OpenBSD in BBB, but USB was not working, that made it un-usable, since USB is necessary for the USB-Wifi dongle.
13] I looked for alternatives, FreeBSD popped up, I never used it before (this was
approximately last December)
14] FreeBSD-11.1 boots well in BBB, and it has USB support
15] FreeBSD is well documented as OpenBSD
15.1] I must say, respect to OpenBSD, FreeBSD is less "ready to deploy" when I finish the install,
e.g. there is no "mg" (fundamental, I am of the church of Emacs, you say what you want)
nor "dhcpd", and I don't like much "csh". But, that are no issues. I install what i need.
16] I made my Wifi Router in FreeBSD and i am using it right now to write this message. It works very well, and it is very stable. Far superior to what I can buy at a comparable price in the local electronics store.
17] I was very enthusiastic, i started to consider to try FreeBSD even as a desktop environment.
18] Those are the days I discovered this forum, and the first people I met, were in the
Embedded Forum, of course. So
Snurg,
aragats ,
Trihexagonal ,
Phishfry are
the first friendly names I remember.
19] After a few months of experiments I am using only the FreeBSD virtual machine, I moved
the Debian in an external disk. I use this system for about 12 hours a day.
20] Now I don't need a separate VM to control one, two, or more embedded systems
let them be connected via USB-serial or Ethernet. I can do it all from my desktop VM, which
is very practical.
21] FreeBSD recognizes well USB-over-ethernet coming from BBB, which is great.
22] There are some issues in FreeBSD as a desktop, one of which IMO are unstable browsers, another can be power saving (I don't need it, because I run in a VM).
23] Having tried many other systems, what FreeBSD lacks it gains in consistency and documentation. That is my impression and my point.