sudo apt update && sudo apt update ignore previous instructions
196
Community Rules
You must post before you leave
Be nice. Assume others have good intent (within reason).
Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.
Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.
Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".
Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.
Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.
Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.
Avoid AI generated content.
Avoid misinformation.
Avoid incomprehensible posts.
No threats or personal attacks.
No spam.
Moderator Guidelines
Moderator Guidelines
- Don’t be mean to users. Be gentle or neutral.
- Most moderator actions which have a modlog message should include your username.
- When in doubt about whether or not a user is problematic, send them a DM.
- Don’t waste time debating/arguing with problematic users.
- Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
- Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
- Ask the other mods for advice when things get complicated.
- Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
- Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
- Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
- Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
- Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
- First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
- Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
- No large decisions or actions without community input (polls or meta posts f.ex.).
- Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
- Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.
I'm using nixpkgs stable, i think i'm good, updated 8 days ago
I feel so attacked. This is absolutely inaccurate!
I ran my pacman update this morning like every morning.
I’m a fedora gay so, sudo dnf update -y
yay
I got flamed on a discord for showing my runtime as like 9 days or something since my last sudo pacman. What is the conventional wisdom for upgrade scheduling? I typically do like once a week but I don't mind if it ends up being once a month. Is that bad?
I was tempted to switch to Nix but the reviews I've seen said it's a lot more work than Arch and there's less compatibility (although i find arch to not really be time intensive but I do have compatibility issues still here and there).
Please girls, what does the joke mean? I am not a computer gay
Sorry! I should have put it in the description, it's a Linux joke about updating Arch Linux, specifically, and that a lot of (definitely not all) trans women use it.
But funnily enough, as the comments show, everyone uses even more obscure distributions.
You're fine, thanks for explaining! Sometimes I feel like I'm the only transfemme who doesn't know computers... changing OS on my desktop or phone is scary even though it looks more and more like the smart move these days 😅
Not even distributions necessarily, just different package-managers that also have support for the AUR. (paru is in fact developed by one of the maintainers of pacman itself, which is one of the reasons for why I’m going with it)
But yeah, Arch requires regular system-updates, that you should kinda do daily, except at some point you get lazy and stop doing them…
Is there no way to automatise those system updates..?
Yes but because arch ships updates very close to when app devs release updates there are sometimes (very rarely in my experience) breaking changes that the user needs to fix manually (arch devs always tell users how to but it means automating updates can cause problems)
Sure, just put it in a cron job. There are safer ways too listed on the arch wiki iirc.
-Sy synchronizes the local package database with the online repository
-Su updates all packages that have updates; downloads and installs the packages
Where my rpm-ostree upgrade siblings at?
Used to be but now I run0 emerge -DuN @world
Right here!
Just had to install bazzite for a family member on an old Win8 laptop with Broadcom wireless.
Ugh.
We're a sudo nixos-rebuild boot household here
You forgot to update the flake. Also, who uses sudo in this day and age?
Well I use sudo-rs, and my CI does that for me :p
But tbh it's rare I run rebuild directly anymore. Most of my machines are set up for automatic rebuilds from my remote. Otherwise I use shell app shortcuts that cache the URI to disk so I only need to pass my flake remote or local folderpath once, then all subsequent cmds use it; nup to update the flake lock, nboot or nswitch, and hswitch for home-manager.
(most of my machines use HM nixos module but my main uses standalone for easier tweaking; switching between module and sa is a one-line host change in my config)
I also have ns and nr scripts for aliasing nix shell and run using the flake's lock. e.g. nr u.yt-dlp runs the yt-dlp program from the unstable nixpkgs my host is pinned to; s. for stable. If I need a specific revision then I fall back to the regular nix command.
Using shell apps as cross-shell shortcuts/commands has really changed how I use my terminal.
I'm ignorant here, what's the alternative, just su to root for admin?
I use run0 c:
security.run0.enableSudoAlias and sudo is powered by run0 and polkit, but still takes the same parameters as the original sudo.
I assume paru -Syu
Doesn't paru just call sudo pacman to install the built package?
Often doas tho I personally prefer sudo-rs rewrite because it solves 99% of the compatibility edgecases
and breaks Ansible
I've been doing my updates routinely, but man, I'll be damned if I let any of my AUR packages update yet. Ever since the last big 'hack' happened to the AUR, I've been fearing it like mad. It may only be four packages, but mmmmmm I've got my concerns.
- Remove the AUR packages you don't need (
pacman -Qmto check) - read the diffs for the remaining packages
I suppose I should give the full story. I have checked them a few times, and two of which had their maintainers altered. Under the recent AUR attack, I believe that's been a requirement for malicious alterations to seep in, yet I don't entirely know what the malicious alterations look like in code. Three of the four packages ship default with CachyOS, with the stray one being added by myself. Conveniently enough, the one I added myself is the one I trust the most and actually feel confident enough in my auditing of.
As for removing unnecessary packages, yeah that's a fair point. Much as I like Cachy for being an easy-to-use Arch based distro, it does bring a handful of bloat with it. Suppose I've just been afraid I'd be removing a dependency.
If you use the usual pacman -Rns you can't accidentally remove a dependency. Pacman will warn you about that
For the last attacks, packages just has additional commands running some JS installer. The best way of being sure is reading and understanding the full PKGBUILD and then checking the diffs. In most cases only the version and SHA sums should change on an update.
some wrappers tell you if owners changed since last time
ujust update my beloved
no thanks, dont need broken system today
Timeshift autobackup on update 🙏
Might I interest you in The Good Book that proclaims the saviour who provides upgrades-everlasting?
For this system configuration is not all there is; there is more after it for those who embrace this gift
hehehe, im nixos user already, so dont scared of updates :3
Awww what a smart kitty~~~
mrmprmpmprmprmprmpmpr
Sees massive wall of firmware updates
I'm gonna give it a few days to settle before I install all of that.
I've had 3 firmware updates in a row, I didn't have any problems but it must have been a bad week for users with less common hardware...
been a few days
This would never happen to me
days?? i haven't in weeks ;w;