No war in history has completely avoided any civilian casualties or attacks on civilian populations, as even limited conflicts often involve indirect harm (e.g., from stray fire, blockades, or displacement), and larger wars almost inevitably affect non-combatants.
Curious how the concept of the 'war crime' is weaponized by the pacifist and largely ignored by the non-pacifist that knows how proper deescalation can take place.
I wonder didn't they used VDO thin provisioning with LVM2.
Also, a few years ago I've implemented VM management tool called 'vmess', in which the concept is to maintain a tree of QCOW2 files, which R/W snapshots are at the leafs and R/O snapshots are the nodes of the tree. The connection up to the root is made via QCOW2 backing-file store mechanism, so a newly created leaf starts a 0 space. I did this because libvirt+qemu impose various annoying limitations surrounding snapshots-with-in-qcow2, and I liked the idea of file-per-snapshot.
It is very unlikely that Israel will ever withdraw its 500,000 citizens from Judea and Samaria, given the result from the 8,000 citizen withdrawall from Gaza.
An equal territorial exchange is much more realistic, as part of a two-state comprehensive package. However, "63% of Palestinians, 65% of Israeli Jews, and 13% of Israeli Arabs are opposed to this two-state comprehensive package.', see https://pcpsr.org/en/node/989 .
Equal territory exchange seems reasonable to me, borders needed to be negotiated; moving borders may be easier than moving population. Ensuring equal territory is equal is a hard problem, and perceived unfairness could lead to future conflicts, but any chosen border could be perceived as unfair.
In my mind, if both sides are equally opposed to it, it's probably fair... But that poll also offers hope; it said there were steps each side could take unilaterally or paired that would get to majority support.
I didn't see list of those steps, except the two paired options which they said could individually make a big difference (anti-incitement, especially in textbooks and mutual employment authorization).
There are various hardware singletons that need to be managed for this to work properly. This raises many questions.
Which of the kernel does the PCI enumeration, for instance, and how it is determined which kernel gets ownership over a PCI device? How about ACPI? Serial ports?
How does this architecture transfers ownership over RAM between each kernel, or is it a fixed configuration? How about NUMA-awareness? (Likely you would want to partition systems so that RAM is along with the CPUs of the same NUMA node).
Looks to me that one kernel would need to be have 'hypervisor'-like behavior in order to divvy up resources to other kernels. I think PVM (https://lwn.net/Articles/963718/) would be a preferred solution in this case, because the software stack of managing hypervisor resources can already be reused with it.
Note that it has one pitfall that is hard to notice: if you a use per-invocation `-o SendEnv`, that gets ignored in favor of the background ssh persistent connection that is keeping the session up. In other words, your connection bear the `SendEnv` of that initial connection and not of the new ones you are creating. No warning is printed.
I dislike flash cards, preferring to answer open questions instead, where you have to fill a word in a sentence. Open questions also prevent rot learning.
LLMs are really good at generating such open questions.
E.g. "The committee was ______ to the proposal, provided that a few minor adjustments were made to address public concerns." - I generated this using a simple prompt. Guess the word that needs to be filled in :)
This is a good tactic. It's difficult for me to memorize vocabulary this way. I usually have to translate it into my native language and learn it thoroughly. But then, filling in the blanks works better for me.
I am on my 6th smartphone, it is the first phone of which the screen accumulates scratches. Google Pixel 9. None of my previous phones needed a screen protector.
> Unlike how rpm or apk packages are done, the deb package sources by design avoid having one massive procedural packaging recipe.
I think that one massive recipe of a well documented preprocessed language such as RPM is exactly what makes RPM maintenance a breeze compared to DEB. The inputs and outputs of each stage are clear. The expansion of the macros. The idea that you only need to execute a single command `rpmbuild` and everything is neatly wrapped from underneath it.
Curious how the concept of the 'war crime' is weaponized by the pacifist and largely ignored by the non-pacifist that knows how proper deescalation can take place.