

After reviewing your post again, I don’t recommend the cart I go on about below. Anything heavy and stable enough to support multiple monitors, is not going to be easy to wheel out of the way. And any wall, ceiling, or pole mounted monitor arms will be massive and expensive. Anything with wheels all around is going to be less stable than fat man on a tiny skateboard. Any little imbalance will send the whole thing to the ground. I’d probably just use a few of those portable (and lightweight) extra laptop screens.
I made a rolling server cart out of an IKEA BEKVÄM. The shelves were spaced just enough to fit my printer on one shelf, the UPS and network gear on another, and the server (in an htpc style case) on top. It’s heavy, with the heaviest part (the UPS) taking the bottom shelf. True, it only has 2 wheels, but it’s built like a tank and rolls around easy enough without feeling like it’s going to fall apart. The cart spends most of its time tucked in a corner, but the wheels make it easier to pull out to work on the various things connected to it. A monitor currently only sits on top, but given the weight of the UPS on the bottom shelf, I would not be afraid to mount some simple monitor arms that don’t extend too much.
Side note: Trackball mice work a lot better where mouse pads fear to tread like couches, laps, chairs, even standing. I use a mouse all day for CAD work so these things have made it worth the adjustment from standard mouse: it being in the same place on my desk every time, being able to relax my arm and shoulder while moving the mouse across 3 monitors, and being able to use my laptop in the field from the seat of a vehicle. I have a Logitech Ergo with Bluetooth and a dongle (several actually), one at each desk or couch and one in my work bag.






Ever really destroyed your server because the it needed were available? I have. It was so much worse than a boot process that froze.
If Systemd was pausing due to a network share being down, it’s only because I (or you) told it to do exactly that. There are lots of good reasons to delay the boot process until all drives the system expects to be there are actually there or the network is up. Cleaning up the mess that happens when the system does not check these kinds of things at boot is so much worse. It’s never really some nebulous thing. Like it or not, intentional or not, the machine is doing exactly what you asked it to do and a delayed boot or a boot halted until you can solve the real problem is almost always better (or at least safer) than the alternatives. I’ve experienced all the things you’ve mentioned, dealt with each of those issues, and it was so much more of a hassle to diagnose before Systemd.