Wait, didn’t they say there are NO files? What files are they gonna release? The inconsistencies here will blow some people’s minds.

When many who still aren’t in cities move into them. Urbanization in China has yet more runway and that drives rail utilization.

Corporate media do be like that. Still wow.

Updated ☝️ 👇

These Moto models were pretty nice.

That allows a marginal increase in density. It’s gotta be thicker. I’m being sarcastic as to how we can’t possibly get 1-2mm thicker phones in order to get longer lasting batteries from the American or Korean manufacturers.

Let me guess, it’s a couple mm thicker right?

It probably can be packaged in a flatpak but it would be more of a challenge than using the docker package. You could implement your use case today with the default docker compose setup. You could be up and running in minutes. Start it with -d and it would even start automatically on reboot. It won’t consume any more resources than a flatpak version.

Just try this in a directory somewhere: https://immich.app/docs/install/docker-compose/

As for docker itself, if you’re on Ubuntu or Debian, you can use the docker version from the stock repos. The package is docker.io and for compose you want docker-compose-v2

Yes, it prevents bit rot. It’s why I switched to it from the standard mdraid/LVM/Ext4 setup I used before.

The instructions seem correct but there’s some room for improvement.

Instead of using logical device names like this:

sudo zpool create zfspool raidz1 sda sdb sdc sdd sde -f

You want to use hardware IDs like this:

sudo zpool create zfspool raidz1 /dev/disk/by-id/ata-ST8000VN0022-2EL112_ZA2FERAP /dev/disk/by-id/wwn-0x5000cca27dc48885 ...

You can discover the mapping of your disks to their logical names like this:

ls -la /dev/disk/by-id/*

Then you also want to add these options to the command:

sudo zpool create -o ashift=12 -o autotrim=on -O acltype=posixacl -O compression=lz4 -O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa zfspool ...

These do useful things like setting optimal block size, compression (basically free performance), a bunch of settings that make ZFS behave like a typical Linux filesystem (its defaults come from Solaris).

Your final create command should look like:

sudo zpool create  -o ashift=12 -o autotrim=on -O acltype=posixacl -O compression=lz4 -O dnodesize=auto -O normalization=formD -O relatime=on -O xattr=sa zfspool raidz1 /dev/disk/by-id/ata-ST8000VN0022-2EL112_ZA2FERAP /dev/disk/by-id/wwn-0x5000cca27dc48885 ...

You can experiment till you get your final creation command since creation/destruction is nearly instant. Don’t hesitate to create/destroy multiple times till you got it right.

Yes exactly.

They can’t. Competition for capital is forcing them to extract the everliving profit out of people. Their competitors would not be far behind on this train if it increases profitability.

Basically the equivalent of RAID 5 in terms of redundancy.

You don’t even need to do RAIDz expansion, although that feature could save some space. You can just add another redundant set of disks to the existing one. E.g. have a 5-disk RAIDz1 which gives you the space of 4 disks. Then maybe slap on a 2-disk mirror which gives you the space of 1 additional disk. Or another RAIDz1 with however many disks you like. Or a RAIDz2, etc. As long as the newly added space has adequate redundancy of its own, it can be seamlessly added to the existing one, “magically” increasing the available storage space. No fuss.

This. Also it’s not difficult to expand at all. There are multiple ways. Just ask here. You could also ask for hypothetical scenarios now if you like.

• That power situation looks suspicious. You better know what you’re doing so you don’t run into undercurrent events under load.
• Use ZFS RAIDz1 instead of RAID 5.

Did he pull a Hillary “basket-of-deplorables” Clinton?

This is fucking amazing.

E: The ratio… - https://xcancel.com/ZohranKMamdani/status/1944832025652871492

So at least they’re half-honest about this not being a productivity thing. On one hand thay say - help with the turnaround (productivity), but on the other they contradict it with letting people quit voluntarily (cost saving). So then it’s pretty obvious it’s about the latter.

Final versions are an illusion. 😄

If the cost of panels drops significantly, there would be more capital available to spend on inverters, even if they stay at the current prices, still decreasing the cost of deployment. But yes. 😄

BTW, the nightly has been great for a while.

The only gripe I have with the 15 branch is there’s no way to put shortcuts from Private Space onto the home screen. I think that behaviour comes from Launcher3 and Lawnchair haven’t implemented / changed it to make it possible.