This would be a great application of btrfs.
Copy over the boot-partition directly via cp /dev/nvme{0,1}n1p1 or similar.Then, simply add the data partition(s) to btrfs. You can then tell btrfs to migrate all data out of the old partition, and finally remove it. All in a running system.
I have migrated the rootfs on running systems before using this method, it's a super clean approach.
BTRFS also nicely handles the redundancy with its checksums. Usually you can't fix bitrot between two drives, but btrfs can tell which version is correct. Makes scrubbing easier.
Modern version would be a silicon device not using any metal, that has a very low power mechanism (perhaps mechanical/chemical) that wakes it up much later where it then works as a bug. For example.
I checked the actual code and there is no e2ee, at all.It has some of the basic setup stuff, like giving you a recovery file, and messages are seemingly encrypted, but everyone can decrypt everything and the platform has none of the structure to deal with all the issues proper e2e brings.
As a very simple test: If you write a message in a server, close the tab. Make a new account and open that chat. You can read the message. Meaning anyone can.The way actual e2ee does this is it signs messages for anyone in the chat at that moment. Anyone new can't read old messages unless an old member sends them the contents.
Also this stuff is buggy in the actual functioning.
Also it's full of trackers and weirdly loads youtube for no reason.
Also it's full of nazis, the actual state is so much worse than the screenshots shown in the post. The top channels are "4chan" and "wagnersdom".
This one is so generic it let's you get around any of that very easily.You don't even need to interact with the filesystem, you can just change a cron script or system library and let some other process execute it. Or you can change /etc/passwd to give yourself access to a root user, which iirc is what this dirtyfrag vulnerability proof of concept did.
You can pretty much write to any file on the filesystem with one syscall (that is not a write syscall) and in a way that does not count as writing in any of the normal ways, so won't even trigger file change events etc.
Sadly not, as far as I have seen all the various pagefault vulnerabilities of this wave are in obscure modules.
Desktop kernels tend to have everything installed so even unusual software will run. Android has a lot fewer modules and builtins, and also regulates what interactions can be done, usually passing such things through system components first.
None of them so far were built into android kernels. Also most of them were not in my own custom kernel either.
In addition to Linux 7.0.6 stable, the Linux 6.18.29 LTS kernel was also released today with the sole change being this same patch from Hyunwoo Kim for resolving Dirty Frag.
Most changes are updating the copyright year.After that, it's pretty much (or maybe completely, I haven't checked exhaustively) for the --help and --version flags, not for the core part of exiting with a certain exit code.
When they grind down rocks (clothes), they put them in a really big drum (washing machine) and add ball bearings (stainless steel silverware). Even though the ball bearings (stainless) is much harder, it will exit the drum ground smooth and to a fraction of its original size. The drum itself is protected due to the stuff being thrown on itself (requires adequate clothes for dampening).
You will certainly loose any coatings and your knifes and forks (and sporks) will be dull. You might after many runs loose the fork tooths entirely, and your sporks might become spoons. You will also either need to sacrifice your old shirts to the silverware gods, or need to order a few replacement drums and change early before the silverware breaches containment and explores the electric and pump sections of your washer.
I haven't checked too deeply but I think fedora dropped the affected system between kernels 6.6 and 6.12 somewhere. 6.12+ appear to not have the modules.Not too surprising given the system has been deprecated for a long time.
The difference between wedge and inclined plane is that the wedge uses friction to create a ratchet. You hit wedges but push stuff on an inclined plane.The screw is similar, it can be screwed continuously or ratcheted, and it will rest in its final position under the same friction. Though you can also see stuff like locktight lock it in place when the friction is insufficient, so in theory you could have a screw that self unscrews without that.
The pulley transfers the force/energy through it from the ropes end, For the axle, one end is combined with the axle and rotates with it. This I would say is a special case of the pulley, but also is quite bad. You need to slap a rotating lever on the end as a big handle to actually gain anything.
The pulley nor the spool give you mechanical advantage. For pulley systems the advantage comes from combining the redirection properties of pulleys, and for spools they come from the handle acting as a lever.The spool doesn't really redirect thogh, you could tie the rope directly to the handle and get the same advantage. The spool is just to collect the rope so you can keep turning without reattaching the lever. It extends your stroke.
Try to log the stdout of your services, I dare you.
openrc is just missing some pretty essential things. I'm not saying to copy journalctl, but at least dump stdout into some tmpfs file by default.
To have some sane basic logging on hand if a service breaks weirdly or is misbehavingy you'd need to edit that specific service file and restart. And most of the time look up the spec of the specific service command to remove log supression.
Unlogability alone makes openrc quite a nightmare for a lot of setups. I've wasted hours repeadedly that would have been 5min had I gotten the log upfront.
This would be a great application of btrfs. Copy over the boot-partition directly via
cp /dev/nvme{0,1}n1p1or similar.Then, simply add the data partition(s) to btrfs. You can then tell btrfs to migrate all data out of the old partition, and finally remove it. All in a running system.I have migrated the rootfs on running systems before using this method, it's a super clean approach.
BTRFS also nicely handles the redundancy with its checksums. Usually you can't fix bitrot between two drives, but btrfs can tell which version is correct. Makes scrubbing easier.