I symlink the AppImage. It’s still a manual process in that you have to recreate the symlink but feels like less of a hassle than updating the desktop file.
In my experience, if you need to do Linux kind of things on a Windows computer, it’s far less glitchy, buggy and laden with weird caveats and edge cases than the alternatives (like Cygwin and Git Bash).
To be fair, I’ve never used it. But I’ve been the guy people come to when shit doesn’t work. Switching from Cygwin or Git Bash to WSL frequently fixes issues.
It’s fine if all you need/want is a Linuxy shell to work with, but if you actually want a proper Linux computer, with a DE that doesn’t suck, mapable keyboard shortcuts, no spyware, working workspaces, tools that do what you want rather than what Microsoft wants for you, etc., you’re going to be miserable.
Looks like it’s using a video mode the monitor doesn’t support, you’ll need to set the refresh rate as well as the resolution to ones that are supported. Likely candidates are 800x600@75hz or 1024x768@60hz, but it really depends on the monitor, check the manual if you can
If it’s a vga monitor you could probably plug it into a modern computer to see the available video modes in the display settings. Then on the old computer just change the video mode with xrandr in your xinit
I did not use virt-manager for a while, but probably it allocates the whole virtual disk by default (i don’t remember for sure). Try to create it manually and ensure that checkbox “allocate the whole volume” is disabled. You can also do this with qemu-img create command (see man qemu-img for options).
BTW it is possible to compress existing qcow2 images. Before that I recommend to run fstrim -a inside the VM. Then shut it down and execute qemu-img convert -cp old_image.qcow2 new_image.qcow2 && mv -f new_image.qcow2 old_image.qcow2.
I am a big fan or repackaging Appimages as Flatpaks, with appstream metadata, sane package management (not the windows way or simply nothing at all), sandboxing and desktop entries.
There’s honestly not a lot of practical uses for it when you have the option of just running a Linux Distro anyway. It’s mostly to keep people who NEED to run Linux for work in Windows as an OS. Otherwise, I’ve found no purpose for it. Neat I guess? Useful, no.
I think qcow2 images are always a fixed size (but I could be wrong on that) however I saw some threads explaining how you could relatively easy modify the size of the qcow2 image :)
I find your mileage is somewhat dependent on the rest of the system config and how you access it. I kinda hate how WSL2 is based on hyper-V because the network stack for that is a pain in my ass, but tools like NMAP just don’t work on WSL1.
I have found that using something like MobaXterm is pretty awesome. The built-in X-Server lets me run a few useful graphical tools within WSL (GIMP, Wireshark, etc) without needing to install their windows counterparts.
Okay, folks. NixOS needs your help. No bull. I’m talking documenters, designers, coders, package maintainers. Why? Because the NixOS community has a lot on it’s plate right now.
Like I can understand why flakes haven’t become standardised, why it’s still marked as unstable, even though it’s pretty much feature complete, and that’s because nix is a complex environment builder and the current contributes are taxed to the max.
But what is nix?
Nix’s job is to create reproducible environments where you can put any library, any service, any application. It does this through compile time flags and modifying ELF headers to isolate applications on a system to their own, exclusive UNIX path. These are linked together as clojures, or a dependency graphs, that can share libraries, applications and services intetchangably with each othet, or use another version or patched version without causing any dependency conflicts.
You can fire up pretty much whatever you want and it will be reproducible elsewhere. It’s like if you took a package manager, build environments, as well as VMs and micro services and make them kiss.
You can spin up a nix environment on any supported system and expect it to run 1:1. This however breeds complexity and there’s a lack of NixOS contributors.
If only you spin up a nix environment on a VM or use it to replace your current build systems (because nix can use several build systems in one single environment), and then contribute back with some changes to nixpkgs, then you are helping to bring about the most powerful deployment tool since kubernetes.
No joke. Check out how you can contribute, because at the end of the day learning nix is gaining a new superpower.
Like the others, I suggest you stick to a distro designed for desktop use (Ubuntu, Fedora etc), you’ll have a much easier time.
If you really want to go with something closer to “scratch made” I’d recommend Arch. Its documentation is killer and you can build a system suited to your requirements.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.