SELinux was a product of the NSA. Maybe the best thing that agency has done.
SELinux was a product of the NSA. Maybe the best thing that agency has done.
Using rm -rf scares me. Is there a reasonable way to delete git repos without it?
I don’t know what to tell you, that’s the command you need to use.
If you’re that worried you’re going to nuke important stuff, make backups, and don’t use sudo
for user files.
No clue what that means. I was thinking more along the lines of how there’s 3+ techniques for async functions. Or that there’s a handful of syntax implementations, versions, and supersets of the language. Or that there are many interpreters all with different standard libraries and quirks.
It’s an annoyingly flexible language.
Oh, and there’s at last 2 other ways to do it too.
It no more says that than hosting an HTTP mirror currently does.
Dulwich is decent. Has some good porcelain functions. But it’s organized kind of weird. I sort of recall it’s the only one that isn’t a wrapper on the git CLI?
Anyway, they all kind of suck in my experience.
It’s a privilege escalation.
The vulnerability, tracked as CVE-2024-1086 and carrying a severity rating of 7.8 out of a possible 10, allows people who have already gained a foothold inside an affected system to escalate their system privileges. It’s the result of a use-after-free error, a class of vulnerability that occurs in software written in the C and C++ languages when a process continues to access a memory location after it has been freed or deallocated. Use-after-free vulnerabilities can result in remote code or privilege escalation.
Reply to the wrong person? What does shell history have to do with zfs?
I was originally worried this would dedupe the entire history file, eliminating occasionally useful historical context. Apparently from what I’ve read, it only compares it to the most recent entry in the history file. Might have to include this one too. Thanks
HISTSIZE=50000
HISTFILESIZE=200000
# Append history after every command
export PROMPT_COMMAND='history -a'
I can’t count on how many times in the past that I’ve had long running systems crash or OOM kill basically everything and I just lose my entire history for the week. Now I’m free to overtax my system as much as I want.
A rolling release distro is basically a requirement for me. I abhor major release upgrades. They’re usually labor intensive and often break things.
The Python docs are outstanding and I would definitely recommend giving that a try before moving to something perceived as more approachable.
That might be what I believed when I first started but it’s so far from the truth…
So what problem is this solving? What are some event-driven systems that need to interoperate? Seems like even if you have a common encapsulation method, you still need code to understand and deal with the message body. Just seems like an extra layer around a JSON blob.
SMTP is actually a pretty great protocol for real time communication.
remembers greylisting is a common thing
When do you consider a system to be bloated?
When I see a service or process running and I have no idea what it’s for.
Disk space isn’t so much of a concern for me so package size and count is fairly irrelevant (this system is above 1500) because a lot of it is just things I use rarely.
It’s just a question. Any implications or tone you perceive here is likely your own projection.
Try and read it assuming the poster is asking in good faith.
Don’t downvote people asking questions.
Really is a good WM though. Thankfully I haven’t had to interact with the community yet.
As a very long time Arch user I wouldn’t say “easy” like everyone else seems to. I absolutely would not suggest it for a first distro for someone, which is what I would classify as the “easy” level.
But if you’re comfortable with using Linux, the terminal, and being able to follow written documentation you’ll be able to do it just fine maybe with a little frustration the first time. If you’re installing to a laptop, make sure to look up your model on the wiki first.