My source is not being a fucking idiot. Yes, the guys with the Mao and Castro avatars whose entire personality is being MLs just chose that domain by chance. Jfc you are either so dumb or so disingenuous.
My first account on Lemmy got banned for suggesting that ml was for marxist-leninist even though it clearly is.
Like why do you think Lemmygrad, the explicitly tankie instance, chose the same domain? Coincidence?
Just keep telling them all to kill themselves and hopefully they will get the idea and leave eventually.
I'm surprised there is anywhere fentanyl hasn't got to yet. No matter where I live I would be cautious about that.
It also adds to the deployment complexity even more. Just from memory, to run Mastodon you need:
- any number of Rails web servers (horizontally scalable)
- any number of Sidekiq worker processes (horizontally scalable)
- a PostgreSQL database for persistent storage (vertically scalable modulo sharding)
- a Redis server for caching and Sidekiq (vertically scalable modulo sharding)
- a Elasticsearch server for full text search (vertically scalable modulo sharding)
So this is at least 5 different server processes to manage, In reality for almost all deployments, Redis and Elasticsearch are unnecessary; the database can be used for jobs and full text search. Further, it could even be SQLite for all but large instances.
The deployment story for Mastodon is a nightmare and a substitute like Pleroma or even better something in Rust is necessary.
His manner of death was unspecified
Well, you got #1 out of 3 accurate. With a 33% level of integrity they just might hire you.
Yes to rsync. It will update the destination files in place without deleting the source files (unless you provide that flag -- don't.)
You might actually be screwed if you ended up overwriting the EFI variables in /sys/firmware/efi/efivars. See https://unix.stackexchange.com/questions/414799/efi-variable-entries-in-sys-firmware-efi-efivars.
If you still have all your files backed up, it might be easiest to reinstall the base system and then selectively copy back over the directories you want with cp -a. Sorry to be the bearer of bad news, but if you can't even attempt to boot, that's not good.
I don't live under and don't want to live under either, because I am a radical anarchist and don't believe in states or borders. So, I did kind of answer your dumb, misdirecting, whataboutist false dichotomy with my first reply. Hope you are happy with the answer. It's bedtime now.
About to be one more. (In case it was unclear, this is a metaphor and an alt.)
You asked a completely irrelevant question to deflect to a different subject, presumably because you thought I was American. Unfortunately I've slayed a lot of tankies and I know your tricks. I'm not falling for your misdirection.
I haven't even said any propaganda. All of my comments are just telling you to fuck off: I'm being hostile because you've been disingenuous from your first comment and I don't engage with tankies. Anyway, go back to bed. Ideally forever.
No, I want you to shut the fuck up and go back to bed. I don't care what you fall for except maybe out a window.
What the fuck are you even talking about. Go back to bed. I'm not an idiot and I'm not falling for your shit.
Do you seriously think I don't know what a whataboutism is? Fuck off with this disingenuous bullshit tankie.
I'm not even a goddamn american!
I'm not sure if this is the problem, but it might be that cp -r creates the new files according to the current user's umask and uid/gid. Which, if done from a live CD, would be a user that does not exist on the system when you try to boot it. What you want is cp -a.
https://unix.stackexchange.com/questions/44967/difference-between-cp-r-and-cp-a
You might be able to correct this without re-copying everything by using rsync. I don't recall the incantation off-hand (you'll want to google it) but I think you want rsync --partial --archive.
https://serverfault.com/questions/141773/what-is-archive-mode-in-rsync
Edit: Would also help to know if you are getting any error messages at boot time.
That's usually from credential stuffing, which I guess you could consider botting, but what I was referring to was automatically creating accounts. Sorry for the miscommunication.
Yes, I'm a radical anarcho-feminist.