9/25/2023 0 Comments Kali linux nethunter wont update![]() ![]() until some new monkey-patch is added that has to be undone, like making a standard read-write system folder read-only.The highlights for Kali’s 2022.3’s the release: Suddenly everything just works, the first time. In my own Ubuntu install, I have been having better luck writing packages that first remove and clean up all changes made by WSL's invasive init system, then re-applying them through the standard interfaces. So arbitrarily assuming and writing to them would at best not work, and in worse cases possibly do damage. That approach would also allow non-FHS distributions (like NixOS) to more easily integrate, since the folders and mount points WSL2 is using may not exist. These could properly configure the distributions, instead of applying arbitrary non-standard monkey-patches. If we had services and extension points, we could create normal system packages for each distribution. Instead, would it not be better for WSL2 to provide documented interfaces, services, and/or drivers? Similar to guest tools and packages like are provided for other virualizers? It is after all a set of extensions and wrapper tools for Hyper-V. The same as they would have to if the system remounts, overwrites, or deletes the folder or socket. The work around will likely cause more issues and workarounds, not less! Anyone trying to integrate the system will most likely have to trip over this issue, spend time diagnosing it, then spending time fixing it. If it is also being done in the hopes it also allows easier installation of arbitrary third party distributions, I would argue that installing an untested and possibly incompatible distribution IS an advanced activity. While I agree there is no 100% perfect solution, I argue that breaking the standards to work around a current compatibility issue is even less ideal. These issues appear to have been fixed in the preview version of Ubuntu for WSL, so the changes aren't required for version 22.10 and after. This appears to have been done to work around a current compatibility issue with a specific set of release versions of of Ubuntu for WSL. ![]() X11-unix folder work, WSL is breaking compatibility with just about everything. It's hard to use any kind of system file protection or validation with WSL2, when at any time a patch could be released where WSL will monkey-patch the guest system in arbitrary and non-standard ways! Since WSL2 can, to a degree, control the host system, isn't that creating a large surface area for security problems?īy changing how standard system extension points like the. It would be easier to use the built-in extension points instead of monkey-patching system files and configuration! Plus it would be more secure. So, is WSL an environment or a distribution? Isn't this problem caused by the hybrid approach? The systemd units are breaking it, because WSL is overwriting system files and settings in a more malware-like way. This directory is mounted read-only by default to prevent systemd-units (like gdm for instance) from deleting the 'X0' socket, which would break wslg. Unfortunately with this kind of issue it's pretty much impossible to have a 100% perfect solution. Would you please re-open it for discussion and evaluation? ![]() This issue seems to effect a number of users and not be resolved. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |