It stretches the player models out and makes them easier to hit I guess? Seems pretty stupid, but people do it.
It stretches the player models out and makes them easier to hit I guess? Seems pretty stupid, but people do it.
Self-hosting is just a generalized term for running your own stacks instead of just using the standard corpo stuff. It’s not a regimen or lifestyle or anything like that. Don’t worry about the terminology.
If it fails it’s healthcheck, then it reports unhealthy. Check and see what it’s healthcheck is configure to be.
It’s not that there’s anything inherently wrong with this, but it’s not the most in line with your goals. If you’re worried about data loss, you could have made a volume that spans both drives like RAID1/Z1, or you could have setup some clever data spanning with BTRFS or likewise. Then you’d be killing two birds with one stone for the Timeshift portion.
If you want safe backups, you need a separate backup drive at a bare minimum.
Doesn’t look like anything integrates with it yet except for something called Mastopod.
Well Nix and other immutable distros are about versioning with binary compatible layers that will be repeatable. Directory structure is already baked-in, so that’s sort of my point.
This project, from the docs at least, seemed like a week intentioned thing that has been handled and passed over in a different way.
Not to offend, but the entire premise of this distro is about directory names, which seems a bit…dated. What are the other selling points?
Not this much. Try disabling desktop effects and see if anything improves: https://userbase.kde.org/Desktop_Effects_Performance
Well my first guess is that your GPU is engaged by every single process you seem to have running. Any idea why?
If you have a second clean drive to work with, you can clone it there and just change your boot target in your BIOS. This is the simplest way.
If you’re simply concerned about config incompatibilities and finding what will break (not hardware), you could clone down to a VM image and boot that then run the upgrade, and boot it again.
If you’re concerned about hardware issues, you could clone down to a liveUSB compatible image (skipping heavy media files) and boot that from an external device and see how it runs.
It’s a bit of an early release to test with your daily driver, so it’s going to be a nightmare. Just a heads up.
What’s the output of nvidia-smi
?
Does it happen with all games or GL engagement, or just the heavier ones?
What’s your memory util?
Does your machine use swap when gaming?
Are you overclocking your memory or CPU freq?
April Fool’s sure is super lame this year.
Okay, so I just found a simple post with steps, so this is the basic setup.
Then you just find an RDP client on Windows that you like, move it to the monitor you want it on, and run it in fullscreen mode. Then you have a full desktop view on one of your monitors that is your remote Gnome desktop.
Which desktop environment are you using?
Right. From what I’m reading, those tools were simply VNC clients, so whichever method you choose above should work to serve the session, and you just need to match the protocol for your windows client. Tons of great RDP clients out there for the windows side.
You’re not giving specifics, but both KDE and Gnome have their own RDP solutions built-in.
If using another DE, just check for solutions as there are many generic ones. I’d generally be looking for RDP solutions over CNC because of Wayland compatibility.aybe NoMachine is interesting to you.
If you want to forward just single windows, look into XWayland and SSH forwarding X apps.
If you’re strictly speaking about console access, then SSH.
That’s not the issue, it’s the changing kernel extensions and passthrough methods of hardware. Causes hiccups from time to time.
You’ll definitely be struggling with that GPU, so maybe that’s a no-go.
Don’t mix your public and private DNS records. Use your public records for public things, and a local DNS forwarder for your local network.
A records only reference IPs and not ports.
SRV can be used to specify where to find ports, but the client needs to support those lookups to properly use it. You can use a reverse proxy or HTTP redirects to point things to different ports.