Can confirm it is terrible. I bought a pack from Amazon and both of them have terrible DAC artifact noises. Should have gone with the Apple one.
2xsaiko
The disks are the most uggo part. They’re a bunch of old disks of varying sizes with a RAID+LVM setup to make the most use of them while still being redundant.
lsblk output of the whole thing
saiko@vineta ~ % lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 512M 0 part /Volumes/Boot
└─sda2 8:2 0 111.3G 0 part /nix/store
/
sdb 8:16 1 372.6G 0 disk
└─sdb1 8:17 1 372.6G 0 part
└─md1 9:1 0 1.5T 0 raid5
└─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
sdc 8:32 1 465.8G 0 disk
├─sdc1 8:33 1 372.6G 0 part
│ └─md1 9:1 0 1.5T 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
└─sdc2 8:34 1 93.1G 0 part
└─md2 9:2 0 279.3G 0 raid5
└─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
sdd 8:48 1 4.5T 0 disk
├─sdd1 8:49 1 372.6G 0 part
│ └─md1 9:1 0 1.5T 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
├─sdd2 8:50 1 93.1G 0 part
│ └─md2 9:2 0 279.3G 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
├─sdd3 8:51 1 465.8G 0 part
│ └─md3 9:3 0 931.3G 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
└─sdd4 8:52 1 3.6T 0 part
└─md4 9:4 0 3.6T 0 raid1
└─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
sde 8:64 1 7.3T 0 disk
├─sde1 8:65 1 372.6G 0 part
│ └─md1 9:1 0 1.5T 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
├─sde2 8:66 1 93.1G 0 part
│ └─md2 9:2 0 279.3G 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
├─sde3 8:67 1 465.8G 0 part
│ └─md3 9:3 0 931.3G 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
└─sde4 8:68 1 3.6T 0 part
└─md4 9:4 0 3.6T 0 raid1
└─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
sdf 8:80 1 931.5G 0 disk
├─sdf1 8:81 1 372.6G 0 part
│ └─md1 9:1 0 1.5T 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
├─sdf2 8:82 1 93.1G 0 part
│ └─md2 9:2 0 279.3G 0 raid5
│ └─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
└─sdf3 8:83 1 465.8G 0 part
└─md3 9:3 0 931.3G 0 raid5
└─storagevg-storage 254:0 0 6.3T 0 lvm /Volumes/storage
sr0 11:0 1 1024M 0 rom
Meeeeh, that sucks though compared to iCloud. I haven’t tried it but it seems like it will upload only and not download, and it will not store the entire Photos database (including faces, etc.).
Would be cool if this results in being able to store the Photos library in Nextcloud. Not holding my breath though.
The article starts with a table of contents with the change highlights as the first item.
Sounds like exactly the right way to talk about physical buttons to me.
Now that I think about it, dovecot drops permissions for security reasons (login runs as the "dovenull" user). It's probably not a good idea to try to circumvent that actually.
What do you mean by “more powerful” wrt CMake?
CMake is a turing-complete language with some APIs that Meson either doesn't have an equivalent yet because it's comparatively new (for example, until 2023, there was no built in way to get a relative path from two paths, and if you wanted that you had to shell out to an external program), or they aren't going to add because it doesn't fit their design.
Meson is (intentionally) limited in terms of extensibility, instead it tries to come with everything built in that you need, even down to specific library support like Qt, from what it seems like to me. For example, you cannot define your own functions, it ships builtin modules but does not allow other packages to provide their own (for example like KDE's Extra CMake Modules), to name a few that I'm familiar with and why I was put off using it so far.
I have yet to see how actually limiting that is, going to try to move the project I've been working on for years that relies on some of these CMake features to Meson soon and see how it fares. But considering that big projects like GNOME use it all over the place it's probably workable in practice, I'll just have to rethink the existing approach a bit.
Is that considered bait?
Wasn't it? Go's build system is very much not what I would call an example of good design (exhibit A: load-bearing comments and file names).
Nice!
I meant that for my one IP address, I set it to have a PTR to multiple domain names.
Don't do that, yeah. If set it should always point to one domain name, the canonical name for that host, and the domain name should resolve back to that IP.
See https://serverfault.com/questions/618700/why-multiple-ptr-records-in-dns-is-not-recommended
Try Meson first, it should support compiling GNU assembly via the C compiler from what I can find. I've been using CMake for years because it is more powerful (finally trying out Meson though for a new project) but in contrary to Meson it is easy to use the wrong way if you don't know what you're doing. Meson is very clean in comparison, and also very easy to get started with. (And both these are absolutely better than autotools)
(If only c++ build systems caught up to Golang lol)
Terrible bait
I’ve been using Linux for maybe 8 years before getting a Mac and found it to be great to use pretty much immediately. So there’s not really much I can tell you here. Except maybe to install the GNU coreutils from homebrew (and that itself if you don’t have it yet), the ones it comes with suck.
I don’t think there is a way to download Xcode without an Apple ID. The App Store also needs one though you could get by without that. You could just make the account only for downloading Xcode and only sign in in the browser for it, I suppose.
Edit: Oh yeah, get Mac Mouse Fix if you plan on using it with a normal mouse. The standard scrolling behavior is abysmal.