tko

joined 1 year ago
[–] [email protected] 5 points 1 week ago (1 children)

I hear you... it's definitely not about one tasting better than others, but maybe more about the eating experience. I do think there's a legitimate argument about how different pasta shapes encourage different pasta to sauce ratios, but at the end of the day it's just the two elements coming together and the taste is what it is. We should all enjoy it the way we want to! I just wanted to explain why some people talk about certain sauces and certain pasta shapes "belonging" together.

[–] [email protected] 6 points 1 week ago (9 children)

It has everything to do with the consistency of the sauce and how well it sticks to the pasta. For example, spaghetti with a meat sauce isn't a great choice because the meat won't actually stick to the pasta and you'll have to scoop up that meat "manually." Better is pappardelle, which has a huge surface area that causes the meat to stick to the pasta.

[–] [email protected] 2 points 1 month ago

Indeed. A wise wizard once said: "It is a curious thing, Harry, but perhaps those who are best suited to power are those who have never sought it."

[–] [email protected] 2 points 2 months ago

It was not a prediction of victory... it was a 71% chance of winning the electoral college. Said another way, they gave her a 29% chance of losing.

https://projects.fivethirtyeight.com/2016-election-forecast/

[–] [email protected] 0 points 2 months ago

ahhhh yes, that makes perfect sense... thank you for pointing that out! Especially since I'm not good enough with vi to know how to bulk delete the first character in specific lines, I had to manually arrow and delete.

[–] [email protected] 0 points 2 months ago (2 children)

I successfully migrated postgres 15 to 16. I followed the general idea of the guide you posted, but I found it a little easier to do a slightly different process. Here's what I did:

  1. docker-compose down for the lemmy instance
  2. edit the docker-compose.yml file and comment out all of the services except postgres. In addition, add a new volume to the postgres service that looks something like this: - ./volumes/miscfiles:/miscfiles
  3. docker-compose up -d for the lemmy instance (the only container running at this point will be postgres)
  4. docker exec -it [container name] pg_dumpall -U [username] -f /miscfiles/pgdumpall20240628 (I think this will work, but it's not exactly what I did... rather, I ran docker exec -it [container name] bash, and then ran pgdumpall -U [username] -f /miscfiles/pgdumpall20240628. The end result is a dumpall file saved in the ./volumes/miscfiles directory on the host machine)
  5. docker-compose down
  6. mv ./volumes/postgres ./volumes/postgresBAK20240628 (move your existing postgres data to a new directory for backup purposes)
  7. mkdir ./volumes/postgres (re-create an empty postgres data folder. make sure the owner and permissions match the postgresBAK20240628 directory)
  8. edit the docker-compose.yml and update the postgres image tag to the new version
  9. docker-compose up -d (you'll now have a brand new postgres container running with the new version)
  10. docker-exec -it [container name] psql -U [username] -f /miscfiles/pgdumpall20240628 (again, I think this will work, but I bashed in and ran the command from within the container. This also allows you to watch the file execute all of the commands... I don't know if it will do that if you run it from the host.)
  11. docker-compose down
  12. edit the docker-compose.yml and un-comment all of the other services that you commented out in step 2
  13. docker-compose up -d

Hopefully that helps anyone that might need it!

[–] [email protected] 6 points 2 months ago

I agree... I was simply clarifying that Nate Silver did NOT predict that Hillary would win (nor is he predicting that Trump will win this election), which is a common misunderstanding about probability. For these types of models to be meaningful to the public, there needs to be literacy on what is meant by the percentages given. Really, I'm just reinforcing rodneylives' point from another angle!

[–] [email protected] 11 points 2 months ago (3 children)

I don't remember him predicting that she would win. His model (https://projects.fivethirtyeight.com/2016-election-forecast/) gave her a 71% chance of winning. 71% is a long way from 100%, and the result of that election definitely fit within the model.

That said, you are absolutely correct... we need to keep shining a light on the realities of each of these candidates, because in the light of day Biden is a much better choice than Trump.

 

The release notes for 0.19.4 mention that this version requires an upgrade to both pictrs and postgres, but there isn't any information about what versions of those are supported. Is there someplace else I should be looking for this information? Or should I just YOLO with the latest version of each?

[–] [email protected] 3 points 2 months ago

Stop j'terrorizing me!

[–] [email protected] 2 points 3 months ago

Depending on what exactly you're looking for, Photostructure might be a good option. It's got a great UI for viewing photos, and it's meant to play well with other Metadata software.

[–] [email protected] 2 points 3 months ago

I don't think I'd call them assholes... more just shortsighted about the realities of selling an album, specifically in how you refer to the album both in speech and in writing.

[–] [email protected] 2 points 4 months ago

There's lots of youtube content on this subject... here's a decent jumping off point, if you're interested: https://www.youtube.com/watch?v=7Nw6qyyrTeI

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

My favorite new feature of 6.12 is the "Exclusive Shares" concept. Here's a rundown:

Background

Unraid user shares are a FUSE, which allows data on multiple drives to be presented as a single file system. This idea is at the heart of Unraid's Array, as well as the concept of "Cache Pools" (now known as Named Pools). Any time you see a path that starts with /mnt/user in Unraid, that's a FUSE (prior to 6.12, that is).

FUSE is great for giving us this transparent way to view our files without having to worry about which physical drive those files reside on. However, this comes at a cost... and that cost is reduced performance for applications running on an SSD Named Pool.

This performance penalty wasn't always noticeable, but it would sometimes rear it's ugly head in unexpected ways (exampes: graylog and duplicati). There was a workaround, assuming your appdata user share was stored entirely on one Named Pool: you could update your docker bind mounts to /mnt/[poolname]/appdata instead of /mnt/user/appdata. This bypassed the FUSE.

Exclusive Shares

With Unraid 6.12, Limetech introduced "Exclusive Shares" as part of the Share Storage Conceptual Change. This gives us a built-in way to bypass FUSE on an entire user share.

In order for a share to be designated an Exclusive Share, the following must be true:

  • "Primary Storage" must be a Named Pool
  • "Secondary Storage" must be set to none
  • Files for that share must exist entirely on the Primary Storage device

Setup

In order to use Exclusive Shares, you first have to enable them. Go to Settings > Global Share Settings and change the Permit Exclusive Shares setting to Yes. You'll have to stop your array in order to make this change.

Next, make sure that your appdata share is stored entirely on the Named Pool. Go to Shares and click Compute in the Size column for your appdata share. This will tell you how much data for this share is saved on each drive. If the only drive reported is your Named Pool, you're all set. If you've got more than one drive, you'll need to disable docker in settings, and then run the mover.

Once your sure that your entire appdata share is saved on your Named Pool, you need to change your appdata share settings. On the Shares tab, click on appdata to bring up the settings. Change the Secondary Storage option to None.

If you did it correctly, after you Apply the changes you will see the Exclusive Access field on the appdata share change from No to Yes.

Finally, if any of your docker container bind mounts use mnt/[poolname]/appdata/..., you can change those to mnt/user/appdata/....

I hope this helps anybody who might have been frustrated with the appdata FUSE performance in the past! If you have any questions, let me know!-

view more: next ›