Try Pulseway for free and start remotely monitoring and managing your server or PC at https://lmg.gg/Ktd7ZUse code LINUS and get 25% off GlassWire at https:/...
The second episode of LTT’s Linux challenge is out.
The exotic setup of Linux is also often left under the table. Hardly anyone has their PC in a 19" rack in another room.
Aside from the Thunderbolt connection maybe not getting proper driver support (because Intel sucks with open source), I don’t see the problem with this. Linux is very widely used in servers, embedded systems, and digital signage, all of which have more challenging display/input setups than Linus’s setup.
For someone who knows what he does, it’s no problem. But for a beginner?
Server run headless. So no monitor. Embedded systems mostly have their display directly onboard or have none, like the APU/ALIX Boards. And all of them have other usages than gaming.
Well, servers can also have software remote displays, display over ethernet or IPMI, or KVM switched displays. Digital signage may place the display many meters away from the computer in an outdoor electrical box, could well require a mosaic of displays over many ports to make a huge image, and can also be interactive through a large touchscreen or other sensors. Digital signage can sometimes also require pretty substantial graphics processing if the effective resolution is huge or if it’s highly reactive or interactive with many animations. Embedded devices can have irregularly shaped displays, weird interfaces, or again, multiple displays. Linux has excellent solutions for all of them, so I find it hard to believe that a remote PC environment connected through Thunderbolt would challenge it, barring a driver issue (which, again, would be Intel’s fault since Thunderbolt is proprietary to them, not a problem with Linux per se).
Aside from the Thunderbolt connection maybe not getting proper driver support (because Intel sucks with open source), I don’t see the problem with this. Linux is very widely used in servers, embedded systems, and digital signage, all of which have more challenging display/input setups than Linus’s setup.
For someone who knows what he does, it’s no problem. But for a beginner?
Server run headless. So no monitor. Embedded systems mostly have their display directly onboard or have none, like the APU/ALIX Boards. And all of them have other usages than gaming.
Well, servers can also have software remote displays, display over ethernet or IPMI, or KVM switched displays. Digital signage may place the display many meters away from the computer in an outdoor electrical box, could well require a mosaic of displays over many ports to make a huge image, and can also be interactive through a large touchscreen or other sensors. Digital signage can sometimes also require pretty substantial graphics processing if the effective resolution is huge or if it’s highly reactive or interactive with many animations. Embedded devices can have irregularly shaped displays, weird interfaces, or again, multiple displays. Linux has excellent solutions for all of them, so I find it hard to believe that a remote PC environment connected through Thunderbolt would challenge it, barring a driver issue (which, again, would be Intel’s fault since Thunderbolt is proprietary to them, not a problem with Linux per se).