zwekihoyy @ zwekihoyy @lemmy.ml

Posts

0

Comments

245

Joined

2 yr. ago

typically I wouldn't recommend just moving file paths for packages, especially if you aren't sure what you're doing. assuming all you did was chsh -s, I wouldn't worry about it.

I found the "best of both worlds" setup is xfs for root fs and then btrfs for /home.

I shuddered at the mere thought of vim. why would you do that to yourself

this is how you burn potential for future relationships

tbh I'm pretty sure the issue I ran into was user error anyways, but once I finally figured out what I was doing, I decided to land on xfs for root and btrfs for home for the following reasons.

1. xfs is supposedly more performant and common in data centers
2. having a separate partition mounted at /home allows for os reinstalls or even distro swaps while retaining my home directory contents (assuming my user is the same)
3. most of the contents I want backed up are held in /home. I don't want snapshots of my entire system laying around
4. I like being extra

I've had some wild issues that I can't even begin to explain with btrfs. I landed on using xfs for / partition and btrfs on /home

true, --substitute false will compile all dependencies, down to the compiler itself, but a simple (/s)

    
nix-build "  " [package] --check
 

  

will compile just the chosen package, skipping dependencies, and compare it against the cached binary in the repo to ensure they're equivalent.

I could have gotten that nix-build command slightly off as I'm typing this from memory. I am also saying most of this in jest as they aren't really solutions to anything mentioned above and I moreso find them interesting features.

but with a simple --substitute false you can make it compile on install. I love nix

you're ignoring the very large elephant in the room known as "maintenance". r&d is only the first hurdle.

this is bait

check out the matrix room https://matrix.to/#/#nix:nixos.org. a lot of really smart and helpful people in there.

nixos is a personal love of mine.

do not use browsers from flatpak. browsers have their own built in sandbox that is crippled or sometimes fully disabled in order to make flatpaks sandboxing work, which are often less restrictive than the browser's.

flatpak is better than nothing for the average user but most packages completely ignore the sandboxing it is supposed to use and require manual changes on flatseal.

there is a difference between something being the airlines responsibility, and you still having some form of etiquette and thought for others when said airline wont fix the issue.

just because it shouldn't be your problem doesn't mean it isn't. absolute individualism is a curse

this was a great explanation. I'm fully onboard with the "fuck Google and their web drm nonsense" but there has to be a disconnect from avoiding bad actors and recognizing the reality of the industry. ty for posting.

private relay is likely using apple DNS to resolve blocked domains.

I didn't know people actually used /e/os. not meant to be a dig I'd just never seen it in the wild.

this test has been known to have problems on Firefox. 90% Firefox+ublock+nextdns, 99% after using the fix they recommend @@*$redirect-rule in your rules.

what exactly is your issue with cloudflare, I suppose I'll ask

https://madaidans-insecurities.github.io/linux.html