• 0 Posts
  • 81 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • For a reliable and useful remote control solution, you’re looking for an IPKVM with ATX power control. To setup the power control, you effectively set up a parallel circuit where your power switch connects to the motherboard, letting the KVM effectively press the power button ‘normally’. As a bonus, you can connect to the video and data of the KVM for even more remote control options, like be able to troubleshoot boot issues or load a virtual CD/DVD to upgrade the OS.

    For tinkerers, I recommend the PiKVM, either DIY or Preassembled. It’s important to know that a RaspberryPi is energy efficient compared to an x86. This guy crunched the numbers

    If you’re looking for a product instead of a project, I’d recommend JetKVM.






  • I appreciate that arch’s package manager is a bit of a monster - but that’s also what made it the prefect choice for me.

    In the immediate aftermath of the release of the Steam Deck, there was many hot weeks where arch’s ability to turn on a dime was exactly the tool needed to run all the new things valve released (fast development to deploy is aur’s specialty). This advantage was destined to not last more than 6 months, as that’s the release cycle for other distros.

    Nothing prevents ya from using Arch to install Flatpack, tho. It’s also really well documented at https://wiki.archlinux.org/title/Flatpak 😅






  • In FOSS world, this is only as true for the subset of developers (including both programmers and designers) that are contributing code as their job duties. Additionally that effect is only prominent in projects that are dominated by one organization. Both those things do happen, but there’s also numerous exceptions, too.

    Some developers are paid to write unrelated proprietary code and the developer also contributes to open source on their free time. Some projects have so many corporate contributors that none of them can single-handedly direct the development.





  • TeddE@lemmy.worldtoLinux@lemmy.mlAntiviruses?
    link
    fedilink
    arrow-up
    2
    ·
    2 months ago

    Hard disagree - the point is a decade ago there wasn’t enough Linux market share for bad actors to target Linux. Proton is a compatibility layer, which while technically being a sandbox, it isn’t designed around security the way a browser sandbox is. It would not be hard for a virus embedded in a made-for-windows program to identify that it’s actually a proton sandbox, then deploy a Linux-specific payload (assuming the malware designer gave it some forethought for that situation). Heck - there’s plenty of viruses that do their work in scripting languages that don’t care what OS you’re running on.