That’s fair. I much prefer a small vehicle with a short overhang for visibility and convenience.

In fact what I’d really like to see is a Telo truck with the modularity of the Slate. They’re already planning AWD, but the SUV/hatchback option isn’t as complete as Slate’s. Hopefully their second gen nails everything and gets the price down. It seems like it will be difficult for them to compete with the much more heavily capitalized options.

Slate has a size comparison widget on their website. You can show it with the silhouette of a current full size pickup and a circa 1985 small pickup. It’s almost exactly the same size as that generation.

Yeah, leaving the destination charge unknown for this announcement leaves a lot of uncertainty.

Very interesting indeed.

Nice. Did they have options to select at this point, or just the base truck?

I remember watching that Mythbusters episode and being convinced. But it still doesn’t fit neatly into my intuition of the thing.

In what way? It’s lighter than the average US vehicle. And the height of the grill/hood is much lower than a typical full size pickup truck. It’s only a couple of inches higher in front than a circa 1985 compact pickup.

I think it has a substantial look to it that can make it seem larger than it is. I walked around a prototype and it definitely felt closer to my VW Golf in size than to a big modern pickup or SUV.

So no image pull from docker.io, right?

For your situation I would be more likely to go with a single drive with btrfs and dup for metadata redundancy. Regular snapshots and scrubs.

Use a second drive in the same system with btrfs to store snapshots at wider scheduled intervals. These will be bigger since no CoW on the separate file system. Scheduled scrub here too.

Use a third drive with ext4 as a backup target using a separate backup mechanism.

Use the fourth drive as a spare, or in a separate location as a target to send the backups if you don’t already have an off-site solution.

Funny. I just gave away my desktop with that same chipset & CPU. It was a really good hardware generation.

No plans for a replacement in the near future.

Same. Moved from OpenWRT through OPNsense to Mikrotik. The performance per watt and per dollar is great.

What are you saving on that drive? Many data file formats already have compression of their own and don’t benefit much from file system compression. So if this is for media files, for example, it’s likely to add CPU overhead without a big benefit in transfer speed.

ZFS is not installed by default with most Linux distributions due to its license. It’s something you install after the os. Btrfs should work, but I see some discussion online of 128 or 256MB minimum volume size.

Sorry. That is what I meant.

Zero zombies here. I have a couple of Debian servers and one repeatedly upgraded Ubuntu on noble numbat that I’m too lazy to migrate to Debian. None have zombies.

Do you run a DE? Mine are headless.

Ah, but the color was named after the fruit!

Before oranges were introduced to English speaking areas the color was called yellow red. The use of orange for the color is only attested from c1500.

Debian

Ha! Mine’s the same! My job was dumping them and said take it if you want it. A v1 TP-Link TL-SG105. I don’t think I’ve used mine in at least 10 years but I can’t bear to throw it away.

Classic blue 5-port gigabit switch. Chef’s kiss!

These things will be with us until the heat death of the universe. Still chugging along.

I make coffee every morning for me and my partner. Used to say “coffee!”

After considering the wisdom of Kevin’s “why waste time, say lot word when few word do trick?”, I started pronouncing fewer of the sounds that make up the word. Eventually it became a quiet grunt. “Uh”

In the morning that still means coffee in our house.

Needless to say, if there are cognitive consequences of a reduced word count then “me dead.”

Moonraker has a similar scene.