I have installed Blulefin on two Framework laptops at this point. I fully understand why Bluefin´s approach with an immutable Linunx system is so important. I really really dig it. However, there are two issues, which I have already posted about on this forum that are holding me back from making Bluefin my permanent new home.
Things that needs to have access to kernel are just not possible on Bluefin. Or at least I have not yet found a way to accomplish this. This leads me to ask about how this issue was thought about when putting Bluefin together?
Virtualization requires this as well as a host of other pieces of software. Are these things just not intended to have working on Bluefin, and that is just the cost of business for this immutability?
This is not a whine or anything likek that. I just want to be clear of this question before I continue down a rabbit hole that is going to dead end.
I really appreciate ALL of the work that has gone into Bluefin!
As to your question, I’m trying to do the things I am asking about here:
Despite my best efforts with using distrobox, etc. I just cannot get vmnet and vmon installed for Workstation. I can’t get Crossover to fully work either. I was able to get Resilio Sync working through a Fedora distrobox though.
Oh, not sure on the vmware kernel modules, I think we’d have to build those? This is probably something that’s out of scope for us though. No clue on crossover.
This is quite understandable given the Fedora Atomic (Silverblue) context
One other way would be to make a custom image based on Bluefin,
But at this point, if you’re comfortable with NixOS, I guess NixOS is better fit for that
Yes, TBO its getting very close to switching back to nixos again as Im finding bluefin feeling very much like M$ meaning feeling extremely restrictive and painful to tweak
Both bluefin-dx and aurora-dx have full libvirt support, the OPs original question was about vmware’s kernel modules, which we don’t support in Bluefin.
As far as I understand you can install VMware workstation in one of 3 ways. You can still use overlays like in silver blue with rpm-ostree, so if it can be installed as an rpm package you can do that and it’ll juslow your updates a bit because it needs to be relayered with every update. Or if it’s something like a shell script as I seem to recall, or installer, you could install it in a container image you build as a pipeline fork of bluefin and essentially build your own os image. Maybe you could also install in distrobox.
None of this is documented of course except how to build your own os with a bluefin. But you may have better luck googling “ +vmware +silverblue “