I'm 'mad' (disgusted) at the idea of sexually exploiting a women shaped object for as long as you can until they attain sentience and (he imagines) kill you for being that kind of person.
I'm annoyed by the idea, commonly held by slavers and abusers (they wrote this down!), that the people you've enslaved will focus on violent retribution and not survival and the joy of freedom in the world after slavery.
It's so utterly self-centered to imagine that freed people will only think about and act against you once they are free. Vile to project that mindset of wanton violence onto everyone.
If you've every gotten out of a bad situation, did you fantasize about endless revenge or were you happy to be safe and free for the first time in years?
Also, not for nothing 'foid' (f[emale human]oid, slur) is common parlance in the incel/looksmaxxing world.
Sure except you have your car when you get there, packing is more convenient and it follows you schedule and goes directly between your desired endpoints.
Depending on the destination of course, I often find having a car in a city like having an albatross around my neck. The benefits or features get outweighed by traffic and parking. I'll take good public transit and a set of headphones.
Not technically related to atomicity, but I was looking for a way to do arbitrary filesystem operations based on some condition (like adding a file to a directory, and having some operation be performed on it). The usual recommendation for this is to use inotify/watchman, but something about it seems clunky to me. I want to write a virtual filesystem, where you pass it a trigger condition and a function, and it applies the function to all files based on the trigger condition. Does something like this exist?
The challenge with that approach is memory: trigger conditions, if added irresponsibly, can result in unbounded memory and (depending on implementation) potentially linear performance degradation of filesystem operations as well. Unbounded kernel memory growth leads to stability or security risks.
That tradeoff is at the root of why most notify APIs are either approximate (events can be dropped) or rigidly bounded by kernel settings that prevent truly arbitrary numbers of watches. fanotify and some implementations of kqueue are better at efficiently triggering large recursive watches, but that’s still just a mitigation on the underlying memory/performance tradeoffs, not a full solution.
Sounds half baked. What context does this function run in? Is it an interpreted language or an executable that you provide?
Inotify is the way to shovel these events out of the kernel, then userspace process rules apply. It's maybe not elegant from your pov, but it's simple.
I know this is trivial to do programmatically, but I was looking for a way this will be handled by the filesystem. For instance, if I have some processes generating log files, and I have a script that converts them to html, I wanted the script to be called every time a log file is updated, without having a daemon running in the background to monitor the directory, just some filesystem mount. This would have made some deployments easier.
Thanks, I didn't find this when I was looking for a solution for my problem. This is pretty much the exact solution for my usecase, though for some reason inotify feels more complicated than some kind of filesystem mount solution for me.
What do you suggest as an alternative? Some kind of app store that periodically updates everything? The biggest thing package managers resolve is having everything be updated in the background, I'm tired of taking 5 minutes apart to update Wireshark everytime I use it.
It’s a truncated cone. It extends infinitely away from us but is aligned such our view is perfectly tangent with the sides, so it appears as only a circle to us.
This makes no sense. Israel calls everyone killed a Hamas operative. If GP's 10:1 ratio were true, it would be within the 20,000 Israel said they've killed.
reply