Y u no Mamaleek

  • 69 Posts
  • 857 Comments
Joined 2 months ago
cake
Cake day: November 3rd, 2025

help-circle









  • Afaik original WSL suffered from the fact that filesystem syscalls went through Windows’ APIs, which allow user-level third-party programs to plug in at many points — like path resolution, block access, etc. Which also involves switching the context between the kernel and userspace a bunch of times. File access patterns in Linux apps worked poorly with this. Plus Linux apps expect the filesystem to cache metadata, which Windows doesn’t seem to do.

    Much of this is mitigated when file access on the Windows side is done by chucking blocks into and out of a virtual disk, and when a kernel with the whole caching thing is introduced.

    I’m guessing such mismatch problems would crop up in other places too.


  • Funny thing: judging by the styling, that text might be from the documentation for Ansible, the declarative configuration manager. Well, you can’t run Ansible itself in Windows, you need a *nix vm, even if WSL — though you can control Windows machines via Ansible. Afaik the same is true for the popular alternatives Salt, Puppet and Chef.

    (Though I couldn’t find the screenshotted page.)






  • [object Object]@lemmy.worldtoMicroblog Memes@lemmy.worldThe audacity
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    7 hours ago

    Programmatically-inclined people can also likely do that with the Automate or Tasker apps, since presumably Buzzkill does its thing via the same APIs. As a bonus, the apps can do many other things.

    (I recommend Automate: Tasker looks more compact at first glance, but its idioms are quite wacky, whereas Automate is pretty much regular programming, just visually organized. Plus, Automate doesn’t require buying more apps for more functionality, and doesn’t have advertising code in it. However, Automate can’t do custom dialogs and onscreen buttons, so in practice I occasionally use Tasker too.)