@7666 I'm not moving completely away yet. If the LUX nodes end up in NL, I'm moving those immediately, the rest will stay unless Hannan proves he's a nontransparent money seeking retard like I sort of expect.
If I end up migrating completely, it will be a massive pain in the ass and self-hosting at home isn't really a painless option either thanks to the EU being stupid like they've always been.
@7666 The owner of Cloudzy AI (and .com) and Fran know each other since before BuyVM existed and BuyVM is using some of their infra already, so it isn't a completely random company that bought the brand name. However since Cloudzy is operated from UAE a lot of question around UAE laws and US laws come into question. What about free speech, government involvement in infiltrating the infra and much more. And since neither Fran nor Hannah (the owner of Cloudzy) answered any question about that for more than a week, I'm kinda worried. UAE isn't really the perfect country where you want to have your hosting business registered.
@7666 I wouldn't worry about paying up for bandwidth _for your current services_. The contract they signed includes a clause where BuyVM has to have the same policies as they did before acquisition with the same pricing. However new services might be priced differently.
It might be that the same pricing and features must also apply to newly bought services, but I would have to read the hundreds of messages on Discord again for that. obrazek.png
@7666 I'm honestly having my doubts about BuyVMs future without him, because he said multiple times he isn't as interested in running a VPs provider as he used to. His main thing now is Namecrane (email and cpanel hosting)
@xianc78@rher You are barking at the wrong tree. These people will never change nor understand. That's why they are only worthy of getting laughed at. Especially Suiseiseki.
@p@Suiseiseki@xianc78 It does suck, but it's still better than being source-available. The worst part of is probably the requirement to publish your modified source even when used privately. It's not FSF approved, because they disagreed with that part of the license.
@Suiseiseki@p@xianc78 >>The main problem of "FreeDOS" is that you can't compile it without a proprietary compiler. >https://www.freedos.org/about/devel/ >https://github.com/FDOS/kernel/blob/master/build.bat#L10 >https://gitlab.com/FreeDOS/base/fdisk/-/blob/master/SOURCE/FDISK/Makefile (OpenWatcom) >https://gitlab.com/FreeDOS/base/fdisk/-/blob/master/SOURCE/FDISK/Makefile.gcc (I16 Gcc) >OpenWatcom (OSI approved, ie not proprietary) >NASM (BSD 2-clause, ie not proprietary) Again, you don't even know what you are talking about.
Networking was not supposed to be dynamic on servers and change whenever Network Manager feels like it
Do you want your newly plugged in RJ-45 to just work automagically? We have a tool for that: It is called "dhcpcd"
Yes please modify 305184b2-fcd5-40e7-837f-6aad9feab8bc. Just type nmcli connection modify 305184b2-fcd5-40e7-837f-6aad9feab8bc <setting>.<property>
Forgot what the proper setting and property syntax is? Just type nmcli connection show 305184b2-fcd5-40e7-837f-6aad9feab8bc and hope you remember what the proper syntax for removing parts of a setting is without rewriting it completely
LOOK at what networking tech have been demanding your Respect for all this time, with all the routers & switches we built for them (This is a REAL network manager, done by REAL networkers):
Today's systems and networks must be dynamic and respond to changes automatically - ???????????
@fwc@j@prettygood It would probably yell at you for having a v16 cluster and fail anyway. A dump and restore makes more sense here. And if you make an improper dump and left the v12 cluster alone, you still have a working backup of it that you can dump again.
>I'm reading though the pg_upgrade instructions and some of the steps might as well be in Chinese. The general instruction are: 1. Backup the whole cluster 2. Stop PostgreSQL 3. Install the upgrade package (postgresql-server-upgrade or similar) and upgrade to newer version 4. Initialize the a new cluster with the newer version with the same settings the old cluster has 5. pg_upgrade --old-bindir=<location of old PostgreSQL binaries provided by the upgrade package> --new-bindir=<location of the new PostgreSQL binaries> --old-datadir=<location of old data files> --new-datadir=<location of new data files (from the newly initialized cluster> --check (remove --check after it checked the cluster and didn't throw any errors) 6. Start PostgreSQL again 7. su postgres -c '/var/lib/postgresql/X/analyze_new_cluster.sh' or su postgres -c 'vacuumdb --all --analyze-in-stages'
Some distros provide an easier script for DB cluster upgrades that do the new cluster init and pg_upgrade for you. RHEL for example has postgresql-setup --upgrade, Debian might also have something.
@fwc@prettygood You want to move the database from v12 to the v16 cluster without upgrading? Wouldn't a dump from v12 and restore to v16 be enough for that since you already have v16 running anyway?
>What am I supposed to see here because it loads on my end. There's no content tho so that's maybe what you mean ? I've disabled unauth access and forgot about it, sorry. See screenshots bellow.
>This has been a thing for many many years. Not in Chromium and Chrome. Those features do not exist there.
>Which one ? because as you can see in the screen recording I don't see anything you can't move. The one on the far left next to the first tab and the one on the far-right which is supposed to be for searching tabs or something. image.png image.png image.png
@mangeurdenuage@japananon@zaitcev Instead of arguing about it, here are some examples of Firefox being broken as of recently. It took almost no effort to find my posts and they are probably a few more.
You know how many bugs I encountered in Chromium and Brave every time I tried them for a month when FF was unusable for me? Zero. Not even a memleak that FF likes to do every few months after an update.
And with Brave, many of the lacking options in base Chromium were added like blocking AutoPlay. There are only two things I don't like about Brave. They are an ad company and they crypto/AI BS baked right into the browser (can be disabled in brave://flags; the equivalent of about:config). And all the annoying new buttons that are in Brave can be hidden, while the new annoying buttons with zero purpose added to FF cannot be hidden without hiding them via userChrome.css.