You can record tracks with (I think) both Organic Maps and CoMaps. If you are interested in the social aspects of sharing tracks https://wanderer.to/ and a few others offer imports of GPX and other track formats.
I’ve seen a tick in Wisconsin every month of the year over the past five years or so. That is I’ve seen a January tick one year, February tick that same year or another year, etc. Whenever there is a bit of a warm spell they appear. Presumably small upward trends in temperature allows such warm spells to happen more frequently.
Whenever someone recommends removal using tweezers, I wonder if the person offering this advice has ever removed a well attached tick. I’ve found tools like a Tick Tornado work better, but are still problematic with smaller ticks.
I’m not optimistic this will be all that helpful. Just because the tick you found is negative, that tells you nothing about those you did not find. Just because a tick is positive, that does not mean that it has infected whoever it was attached to.
My understanding is that the ticks only transmit disease after they have been attached long enough to become engorged. None of the ticks shown were engorged.
A big consideration for efficiency and TCO calculations is the number of servers required to house the drives. NVMe drives tend not to be in external JBOF enclosures.
Fewer servers means fewer cpus, less RAM, fewer fans, and maybe fewer switches.
In the late 80s I worked in an industrial controls shop. This is the type of place that makes the cabinets with all the buttons, switches, and lights commonly associated with nuke plant controls. Only we did mostly controls for paper making machinery for Kimberly-Clark, Appleton Papers, etc.
Most of our green cabinets were spotlite green. Seafoam green was rare. Both paint colors were prepared by our local sherwin Williams. The colors looked pretty much the same to me.
I record them in a different system that is more likely to survive shifts in technology, business relationships, and arbitrary expiration date changes to save money.
In Navy boot camp the person reviewing my security clearance application (which was filled out weeks before) was very helpful in the way he asked the critical question. “It says here you tried marijuana once. Is that true?”
Back in 1997 or so I bought an ATI video card that also had a Weezer video on the CD. I remember being amazed that it could play the video at 1024x768 with just a little bit of tearing.
Exactly. I question why the parent says you have to re-encrypt the drive.
Microsoft has the KEK or passphrase that can be used to derive the KEK. The KEK protects the DEK which is used to encrypt the data. Rotating the KEK (or KEKs if multiple slots are used) will overwrite the encrypted DEK, rendering the old KEK useless.
Or does BitLocker work differently than typical data at rest encryption?
And if you don’t use a lot of data, at least US Mobile has a by the gig plan. My family has three phones on it for a total $30 per month. Those months that we go over, it automatically charges $2 for each extra GB, with data pooled between the lines.
It is easy to switch between Verizon, AT&T, and T-Mobile as well. This was helpful for me as all three of the networks normally have one bar or less at my house. T-mobile WiFi calling works more reliably than Verizon.
Mirroring between s3 providers would seemingly give protection against your account being locked at one of them.
I expect this becomes most interesting with l2arc and cache (zil) devices to hold the working set and hide write latency. Maybe would require tuning or changes to allow 1m writes to use the cache device.
Per the definition of volatile write cache in the standard I quoted, pretty much any drive TLC drive in the hyperscalar, datacenter, or enterprise product lineup will have great write performance. They have a DRAM cache that is battery-backed, and as such is not a volatile write cache.
A specific somewhat dated example: Samsung 980 Pro (consumer client), PM9A1 (OEM client), and PM9A3 (datacenter) are very similar drives that have the same PCI ID and are all available as M.2. PM9A3 drives have power loss protection and the others don’t. It has very consistent write latency (on the order of 20 - 50 μs when not exceptionally busy) and very consistent throughput (up to 1.5 GB/s) regardless of how full it is. The same cannot be said of the client drives without PLP but with tricks like TurboWrite (aka pseudo-SLC). When more than 30% of the NAND is erased, the client drives can take writes at 5 GB/s but that rate falls off a cliff and gets wobbly when the pseudo-SLC cache fills.
It seems pointless to issue flush commands when writing to an NVMe drive with a direct IO implementation that functions properly. The NVMe spec says:
> 6.8 Flush command
> …
> If a volatile write cache is not present or not enabled, then Flush commands shall complete successfully and have no effect.
And:
> 5.21.1.6 Volatile Write Cache
> …
> Note: If the controller is able to guarantee that data present in a write cache is written to non-volatile media on loss of power, then that write cache is considered non-volatile and this feature does not apply to that write cache.