- I'd be fine with any. Trying Fedora, or maybe Debian. But I'd rather set up networking at the qemu level so the vm only has access to what I want it to.
- I don't know how it would work, but I can create a new device id and make a new wireguard conf file. I don't know why this wouldn't work with any other conf/interface on my host.
- I want this to be physical router agnostic, as the host is a laptop. Only the vpn and host should be exposed to the VM.
For the tablet? I'm considering a Surface keyboard or cheaper alternative, but I would usually be using it for handwritten notes and other tasks for which I would not use the keyboard. It would really be most useful during initial setup. I would still need to easily open it when the keyboard is removed.
Yup. I checked their webpage. Might help battery but I'll try vanilla first. Unfortunately, no dice with the secondary display thing. With RDP, the hardware cursor won't send, and I can find a way to use RDP over type c cable.
Flare isn't feature complete but you can run it in the background for all notifications.
I'd imagine the drm would ruin that plan. No HD streaming.
I think a server is for streaming the audio to different devices. They don't want to stream from phone to the player (or the other way around). They just want to be able to browse library and control playback from their phone.
Looks nice, I'll check it out if I have to use Mac OS again.
I much prefer Windows to MacOS. The fact it is missing decent tiling is a nonstarter. It's too inflexible for my workflow.
And sure, Windows can be maddeningly inconsistent, but what really destroys the experience is the constant ensh*ttification. I know a lot of people here hate everything about Windows, but for me, it only sucks because Microsoft designs it to suck.
Not only are there ads and (some) first party lockin, I cannot trust they will continue offering updates, paywall feaures, restrict more functionality, or insert stuff like AI to mess up my workflow.
I used to think reliability was just about stability and bugginess, but now I think it is about trust as well.
I'm glad you do. I want to start contributing and donating too. But I do think the definition of freeloader is a bit adjusted for FOSS software.
I get your point, but this definition applies to all users of FOSS software who do not actively contribute to its development. Purpose is a consideration here; I am freeloading if I use netflix's service through loopholes or piracy when it is intended for paid customers, but am I freeloading if I, a non developer and a student not in a position to donate, use libreoffice? By this definition, I clearly am a freeloader. But it is clearly intended for use by the general public.
For RHEL, there is more ambiguity, because although they sell it at cost, it is still based in an open source ecosystem. I understand how using rhel binaries without becoming a paying customer could be seen as freeloading, but the crucial difference is the intent of an open ecosystem and standard. RHEL establishes itself as a standard, and that means it's work will be used, not just contributed to. By closing it off, they are cutting off that standard.
Compare this to standards like USB or audio codecs. A powerful company or consortium may create an open standard and use it in their paid offerings, but others using it aren't freeloaders, even if they compete with said offerings. They're intended (or expected) users.
Sorry if I'm not making much sense. I'm only commenting because I find this interesting, not angry keyboard warring.
So basically all those who used CentOS and did not contribute anything even though CentOS cried for contributions for years until Red Hat eventually bought them? (=Most notably Oracle.)
Not contributing is not necessarily freeloaders. Users have no obligation. That's the point of open source. Only building off of open code and the closing yours off is freeloading.
Oracle and others used the source code and publish their distro's source. Oracle not contributing is jerky, sure, but for them to be freeloaders they would have to use enterprise linux as a basis for a pay walled proprietary or restricted source OS. Correct me if I'm wrong, but their business model is using Oracle Linux in their cloud offerings.
Red Hat is still the biggest FOSS contributor. (I use openSUSE and SteamOS, btw, so I'm not even a RH product user.)
Hell, I use Fedora, so anything I contribute to is upstream of RHEL. I'm not saying RH socks. There are a lot of great people they employ and their business has been a huge positive for FOSS. But those (great) achievements were and are premised on community collaboration, and it's more than fair to raise a stink about it.
It's really not a loophole.
You're right about GPL. I have nothing against paid software. I was more describing the broader enterprise linux ecosystem. That is to say, RHEL's success is based on making it an open standard. The greater community can contribute either directly to the upstream or to the application ecosystem, with the understanding their work is applicable to the FOSS community. Closing the downstream is a loophole out of this system where they get to profit. It's a bait and switch.
Simply reusing Red Hat's source RPMs isn't an open ecosystem. All the EL downstreams finally collaborating is.
"Ecosystem" wasn't referring to the existence of clone distros but the development and adoption of enterprise linux they enable(d). The ecosystem is not only those directly contributing to enterprise linux but the developers targeting enterprise linux and the (IT/CS) user base familiarizing itself with enterprise linux. The market for a RHEL clone is not the market for RHEL enterprise solutions. As I said above, free availability of clones gets people into the ecosystem, and on the corporate end, as long as RH's offerings aren't enshittified, Red Hat converts these people into customers. It should be a win-win, but short-term profit maximization will hurt its trust and future growth.
Was looking for this comment. Donate your plasma to KDE!