![](https://sopuli.xyz/pictrs/image/139cc6b5-f117-4fc9-a475-3f223aa3f998.webp)
![](https://lemmy.world/pictrs/image/c47230a8-134c-4dc9-89e8-75c6ea875d36.png)
Also a big(ish) issue for the industry. Local news had info that up to 80% of natural berries are picked up by foreginers. For majority of the pickers these gigs are pretty big source of income (compared on what they make back at home) but then there’s the few rotten apples who end up renting accommodiation, cars and everything to the pickers so that pretty much all of their earnings go back to the person providing work. Or that they don’t pay up at all and everything else in between. I’m not sure if that qualifies as human trafficking if pickers end up going back home empty handed, but that’s been an (relatively small, but existing) issue here.
Human trafficking is of course a big deal, but from the ones who end up in our forests picking berries the slavery-like conditions and long work days with next to nothing paid in return is a more common problem. And even if it’s more common it’s still a relatively rare problem.
The command in question recursively changes file ownership to account “user” and group “user” for every file and folder in the system. With linux, where many processes are run as root and on various other accounts (like apache or www-data for web server, mysql for MySql database and so on) and after that command none of the services can access the files they need to function. And as the whole system is broken on a very fundamental level changing everything back would be a huge pain in the rear.
On this ubuntu system I’m using right now I have 53 separate user accounts for various things. Some are obsolete and not in use, but majority are used for something and 15 of them are in active use for different services. Different systems have a bit different numbers, but you’d basically need to track down all the millions of files on your computer and fix each of their permission by hand. It can be done, and if you have similar system to copy privileges from you could write a script to fix most of the things, but in vast majority of cases it’s easier to just wipe the drive and reinstall.