mgerdts

Even better, get rid of the mandate for ethanol and cover a portion of the ex corn fields with solar panels with native plants under and around them. A small portion of the land that is near existing transmission lines is needed to replace combustion vehicles with electric vehicles. The bulk of the rest of this land could be available for other uses, including data centers.

This gives: sustained income for landowners, CO2 reduction, power for new uses, and partially restored ecosystems that have been greatly harmed by chemical laden monocultures.

I was at the Toyota dealership today. A TRD off-road with TRD Off-Road Upgrade Package and other goodies has a MSRP of $61k and the tag hanging from the rear view mirror said the no haggle price was $54,608. Still a lot of money and it is a huge truck for the passenger and cargo payload.

https://www.smarttoyota.com/new-Madison-2026-Toyota-Tacoma-T...

AllTrails has a heat map feature as well. I think this feature is now paywalled.

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.

you squeeze their contents through their mouths

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.

https://www.zenpetusa.com/tick-tornado

https://lymealert.com/how-it-works/

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.

By any chance does this person live near Montrose CO and tend to the lawn at a church next to the Holiday Inn Express?

And out of band management, hot plug capable form factors, and a bunch of other things described in the OCP NVMe SSD spec.

https://www.opencompute.org/documents/datacenter-nvme-ssd-sp...

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.

You aren’t alone:

https://mitsloan.mit.edu/ideas-made-to-matter/working-defini...

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.

I remember similar advice.

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.

This sounds like Solaris doors. The remainder of the time slice of the door client is given to the door server.

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.

What is up with fin? Is it really just writing an int 0 in the memory right after some variable present in libc or similar?

        extern fin;

        if(getpw(0, pwbuf))
                goto badpw;
        (&fin)[1] = 0;

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.

The original idea of boot environments in Solaris came from Live Upgrade, which worked at least as far back as Solaris 8. Live upgrade was not part of Solaris, rather it was an addon that came from the services or enterprise support parts of Sun.

Solaris 11 made boot environments a mandatory part of the OS, which was an obvious choice with the transition from UFS to ZFS for the root fs. This came into Solaris development a bit before Solaris 11, so it was present in OpenSolaris and lives on in many forms of illumos.

This article is a great read explaining how this trap happens.

https://www.yesigiveafig.com/p/part-1-my-life-is-a-lie

Datacenter storage will generally not be using M.2 client drives. They employ optimizations that win many benchmarks but sacrifice on consistency multiple dimensions (power loss protection, write performance degrades as they fill, perhaps others).

With SSDs, the write pattern is very important to read performance.

Datacenter and enterprise class drives tend to have a maximum transfer size of 128k, which is seemingly the NAND block size. A block is the thing that needs to be erased before rewriting.

Most drives seem to have an indirection unit size of 4k. If a write is not a multiple of the IU size or not aligned, the drive will have to do a read-modify-write. It is the IU size that is most relevant to filesystem block size.

If a small write happens atop a block that was fully written with one write, a read of that LBA range will lead to at least two NAND reads until garbage collection fixes it.

If all writes are done such that they are 128k aligned, sequential reads will be optimal and with sufficient queue depth random 128k reads may match sequential read speed. Depending on the drive, sequential reads may retain an edge due to the drive’s read ahead. My own benchmarks of gen4 U.2 drives generally backs up these statements.

At these speeds, the OS or app performing buffered reads may lead to reduced speed because cache management becomes relatively expensive. Testing should be done with direct IO using libaio or similar.

I just stumbled across this:

Native NVMe is now generally available (GA) with an opt-in model (disabled by default as of October’s latest cumulative update for WS2025).

https://www.elevenforum.com/t/announcing-native-nvme-in-wind...

This article is talking about SATA SSDs, not HDDs. While the NVMe spec does allow for MVMe HDDs, it seems silly to waste even one PCIe lane on a HDD. SATA HDDs continue to make sense.

In addition to my other comments about parallel IO and unbuffered IO, be aware that WS2022 has (had?) a rather slow NVMe driver. It has been improved in WS2025.

Robocopy has options for unbuffered IO (/J) and parallel operations (/MT:N) which could make it go much faster.

Performing parallel copies is probably the big win with less than 10 Gb/s of network bandwidth. This will allow SMB multichannel to use multiple connections, hiding some of the slowness you can get with a single TCP connection.

When doing more than 1-2 GB/s of IO the page cache can start to slow IO down. That’s when unbuffered (direct) IO starts to show a lot of benefit.

A workload that uses only a fraction of such system can be corralled onto a single socket or portion thereof and use local memory through the use of cgroups.

Most likely other workloads will also run on this machine. They can be similarly bound to meet their needs.

With kubernetes, CPU manager can be a big help.