As long as you only copy off the disk, you can just reboot and the whole system in RAM vanishes and the normal system boots again for the second try.
InnerScientist
FYI you can use kexec and a prepared initrd to do something similar with only one command.
One I remember is memberships and event tickets, though if they're that useful compared to a normal database is debatable.
Or encrypt it before uploading
Would this even cause a kernel panic? I think this just causes a userland "panic"
That's fine as long as it can self reference.
You need a phone, tablet, or other device that’s been rooted.
Damit
And to calculate the offset needed to get them all synced up involves calculating time dilation, which involves knowing/assuming the speed of light. These synchronizations work just as well if the two way speed of light is different than the one way speed of light.
To know the speed of light you assume the speed of light is c, but you're trying to calculate c so all those clocks aren't verified synced.
Just read through the wiki or Harvard's books if you'd like, this is an unsolved "problem" in physics for a reason or do you think no one cares about how fast c is?
See also This or, more accessibly "Synchronization conventions"
It is impossible to synchronize the clocks in such a way that you can actually measure the speed of light with it due to time dilation unless you define beforehand how fast the speed of light is to calculate that time dilation.
See also This or, more accessibly "Synchronization conventions"
The very accurate clock needed in this case is physically impossible as far as we know, there's no way to measure it as far as our current understanding of physics goes.
Though if you can figure out a way you should publish a paper about it.
And further down:
Unfortunately, if the one-way speed of light is anisotropic, the correct time dilation factor becomes
, with the anisotropy parameter κ between -1 and +1.[17] This introduces a new linear term,
(here
), meaning time dilation can no longer be ignored at small velocities, and slow clock-transport will fail to detect this anisotropy. Thus it is equivalent to Einstein synchronization.
Something I don't get is, why try to make all browser look the same when you can do the easier thing and just make each browser session have a new fingerprint?
A unique fingerprint doesn't matter much if it's only valid till I close that website, right? So why not change a lot of variables by some small amount to make the data useless?