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.

one of us one of us one of us

holy shit is that what that is??? it’s fucking awful i thought that video playback was somehow really intensive on my phone is fucky weird ways that were random and annoying.

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 wonder if you can do a waterfall init where you can have an entry point that defines what services to run next. then you services can continue to pass on the next to run, or if it encounters one with a service that isn’t running, it looks at what services that one requires and traverses up to start the root unstarted service. Easy way to define dependencies without much hassle. The former case handles system services, the latter handles application services.

I haven’t personally done it, but I believe so based on my friend’s experience. I’d read the arch wiki, they surely have a guide on it for EFI.

It’s a lot easier because you don’t have to play around with EFI stuff at all. Windows gets its drive and it’s EFI partition, Linux gets its own pair. Et voila, much less crossover and issues.

Having to occasionally go back to OpenRC or Upstart systems is jarring. Systemd just does so much and does it so much better. Poettering seems like a bit of a chode but he genuinely made an incredible project. I also think that when people say systemd isn’t Unix-like, they forget that systemd isn’t monolithic and it’s possible to use some components of it but not others. The core is all based on a standardized way to start and manage processes and services, be it for boot or usage.

It does help a lot, but when first party documentation is lacking there’s sometimes not much you can do without consulting an expert. And sadly I work on my servers in the middle of the night when the FreeIPA IRC channel is dead :')