Just passin’ through
it’s not a setup issue, it’s a hard limit of xorg. maybe having two xservers may help, but then you wouldn’t be able to move windows between them. the way multiple monitors are done using x is that they’re treated as one continuous screen, but that means it can get a bit wacky because they’re not the same.
Multimonitor is just a better experience on Wayland. For instance, you can have different refresh rates for your monitors and the way it’s handled isn’t janky and hacky.
The only things id be concerned about is that multi monitor will work better under Wayland but nvidia may not. Nvidia and wayland is getting better while multimonitor on X isn’t, but I don’t know exactly how things are rn enough to say
resolved sucks imo. i usually disable it and manually set the resolv.conf, or use something else. it has no way to force it to check name servers in a specific order and it has a memory so it’ll use the same name server for multiple checks even if it’s not the right name server. if these things were configurable, I’d agree that it’s good. but they’re not and it makes it very difficult to use in a lot situations.
i think I’ll give that a shot
did you pass through the disks or straight on zfs?
one of us one of us one of us
I really really like Fedora Server, but any RHEL derivative is my go to for servers. I use Rocky Linux when I need something closer to RHEL, and Fedora server for pretty much everything else. I highly recommend Cockpit as well (main reason I like Fedora server) as it has allowed me to so easily manage all of my servers from a single point.
here we go again
i am a fag and idc if im a beta
nixos looks fun but doesn’t really seem like the thing for me, at least jot yet anyways. im not totally into the whole atomic desktop thing atp so no thank you
oh believe me i am
this is the way
on my main system i have arch with a partitioning scheme that has worked well for me because i took time to research and identify what i needed from it. i even got full disk encryption working after the fact!
on fedora i click automatic partitioning, wipe the drives i want, and don’t do more than that because the partitioning screen feels extremely confusing.
This package is not the fault of the Arch team. However they did push a legitimately broken update that required some people to manually reinstall core components of their system to make it functional again. They sre not responsible for my issues but they did actually fuck up recently.
It was my weekly update, ngl I’m not entirely sure all of which packages broke. That one’s on me
It was a way to learn how to actually use SE Linux and its different components. I still have more that I wanna do with it, but it’s one of those projects that’s been on the back burner for a while
This specific version of the package isn’t the issue, it’s that main repo packages are built on the updated version and this hasn’t been updated yet. I’m unsure of the process that is used to choose and apply the patches for this project, and I’m unsure if the current version in the repos actually has the work done on it for this specific package.
I attempted to do so, but the package applies some patches to the source code and it’s version dependent. I don’t have the experience with this specific project to easily fix it, and I suspect by the time I figure it out the update will have already been pushed.
I prefer Fedora Server. It comes with a lot of nice integrations into more enterprise/centralized Linux administration and management tools. A lot of these are FOSS so if you like infrastructure, this is a really good way to take an easy step up.
Thanks for the insight. It’s something I’ll definitely consider
I’ve spoken with a colleague who’s more experienced with physical networking (my work is mostly cloud based) and it seems the issue is that i have a dumb switch in-between my server and my managed router/switch so nothing is crossing VLANs properly. We figured this out because I did a packet capture on my network and did two DNS queries, one from my machine on my VPN network to the DNS server and one from the docker container to the DNS server. Both sent the same query except my machine got a response and the container did not. I am a bit skeptical that it’s purely a VLAN issue, but this DNS server hasn’t had any other issues with other subnets that aren’t dealing with VLANs so when you’ve eliminated the impossible all that remains is the improbable.