← Back to context

Comment by mtlmtlmtlmtl

12 hours ago

Why? Nothing wrong with running your network interface in a VM. There are reasons for doing so even if drivers aren't an issue. Qubes OS does this, for instance, for security reasons.

5 comments

mtlmtlmtlmtl

Reply
wolvoleo  12 hours ago

Windows also does. Almost everything is a VM in windows these days.

It's just how things work these days. If you'd say "I run my VPN client in a docker container" it would raise a lot less eyebrows. Yet it's not very different, really.

Though conceptually I'd frown at having to run Linux. I'd prefer upgrading the hardware to a supported chip.

  • PunchyHamster  7 hours ago

    Windows isn't running entire fucking separate kernel to run wifi driver, the fuck you're talking about

    • evanjrowley  6 hours ago

      Definitely not independent kernels but my guess is he's referring to Virtualization-Based Security (VBS) - it gets turned on by default if your Win10/11 system has virtualization enabled.

        One such example security solution is memory integrity, which protects and hardens Windows by running kernel mode code integrity within the isolated virtual environment of VBS. Kernel mode code integrity is the Windows process that checks all kernel mode drivers and binaries before they're started, and prevents unsigned or untrusted drivers or system files from being loaded into system memory.

      I suppose this applies to Wi-Fi drivers?

      Link: https://learn.microsoft.com/en-us/windows-hardware/design/de...

NooneAtAll3  9 hours ago

no matter how it's implemented, it must not be a user-requiring (or even user-facing) task

  • mtlmtlmtlmtl  4 hours ago

    Why not? FreeBSD has never been intended as a batteries included, everything "just works" out of the box OS. It's meant to have a bare minimum install and let the user choose how things are set up. You can disagree with that philosophy, but that's not an indictment of FreeBSD. Just go use something that aligns better with your preferences.