Although I think having to fix a borked bootloader is a good bit of experience, it's probably not something you are always going to want to spend time on. I have used boot-repair only once, but it was like magic. Just throwing it out there for your future use and a general recommendation. :)
Only two things. Rust is 12 gigs on disk(which translates into 12 gigs of ram if you use tmpfs) and IDK how much in ram. Chromium is about same. Keep rest of ram for linker.
To be clear Steam will download the Linux build by default on Linux. No user intervention required.
(If you need to for some strange reason you get run the Windows build in Wine via the “Compatibility” menu but that is unlikely to work better than the native build.)
LSPs, linters, AI auto complete, multiple ranked auto complete sources, contextual syntax highlighting abused to feed things like symbol tree views, type analysis, scoped file trees depending on what you’re working on, infinite undo since last commit, and all available in real-time.
I feel like I use up 8GB the moment I type “neovim” on a sufficiently large node project, lol.
Run different virtual machines for different purposes. For example, you can have a VM that does all its networking over a VPN and downloads torrents in the background while you do other things. Or you can run other OSs in VMs.
Also, containerized software is everywhere now and it uses more resources. Extra memory helps.
I asked a similar question and I was lead to this post.
I got side tracked and eventually lost motivation to get it working. I might give it another try in the new year. Hopefully this is what you are looking for. I assume your distribution is using PipeWire, otherwise you may have to look into HRIR for PulseAudio.
The post explains them quite well. HRIR (Head-Related Impulse Response) and SOFA (Spacially Oriented Format for Acoustics) are standards for representing spacial audio (surround sound) in audio files and streams. A convolver is something that performs convolution (a mathematical term for taking one function, applying it to another, and then producing a third function as a result), and a spatializer is more specifically something that, as the name suggests, gives “space” to audio (distorting audio to represent sounds coming from more than simply 2 directions, or again, what you call surround sound). So HRIR Convolver is simply a method to apply the HRIR function to audio to represent it in a way our brain would interpret as 3D audio, and SOFA Spatializer is simply a method to do the same thing, just with the SOFA standard instead of the HRIR standard. Based on the comments of the post, it seems that they recommend you use SOFA.
In either case, Pipewire supports both standards, and it is trivially easy to implement them through filters (as the post covers in depth). You could try both if you want and see which you prefer. If you’re unfamiliar with managing Pipewire and need further resources, the Arch wiki has an entry in great length about it here. I’d recommend reading the comments to that post first if you struggle with anything, such as persistence. Everything you need to set it up should be accessible in that post and its comments.
I’d also like to recommend that you read the post and comments to the post, or simply use a search engine if you come across unfamiliar terms. You can find answers to all the questions you’ve asked through the linked post and a simple search.
I managed to get it working, I just can’t control where the sound actually is coming from. I have to set my default sink to the new surround, so it just picks one random device that’s connected it’d seem. How can I tell it where to play my audio back?
Simple thing, but are you sure you mounted the NFS share as NFSv4? I don’t have access to a machine to check right now, but I think it might default to mounting NFSv3, even if both sides support v4.
<span style="color:#323232;">vineta.h.kfe.pt:/nfs/nas on /nfs/nas type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp6,timeo=600,retrans=2,sec=krb5p,clientaddr=2001:470:7391::ce,local_lock=none,addr=2001:470:7391::c0,_netdev)
</span>
The command prompt to be exact. Which is presumably a version of MS-DOS. Which makes me wonder if you can’t simply boot MS-DOS or FreeDOS — assuming you can find a copy that boots under UEFI. It’s certainly lighter then a whole Windows iso and you can include the firmware with it on a tiny FAT partition.
KDE is the best desktop environment, period. Why not go with a stable OS base but enjoy all the current updates of your desktop, app suite? Introduction: KDE Neon
Know that you’ll probably hate what you try first. Personally I say you shouldn’t use Pop_OS!, but its better than being scared of making a wrong choice. “distrohopping” is a great way to learn.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.