![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
I tried using Bazzite since I didn’t want to fuss with Wayland on Nvidia with Arch.
I had more gripes and more issues with an immutable distro than I ever did with my Arch install.
Stuck it out with Arch. It has taught me a lot.
The problem many folks have with Arch is the fact they don’t want to read or learn; well, newsflash, if you read and learn Arch isn’t exactly all that hard to use, setup, or maintain. It has better documentation than Bazzite and other newer distros. In fact, Arch Wiki has saved me hassle for other distros.
Your mileage may vary. However, I wouldn’t recommend an immutable distribution nec3ssarily to someone coming from Windows unless they want to shift from one paradigm to another.
Switching from Windows to something with such a vastly different approach in many cases will turn users away from using Linux. Their experience can dictate they switch away because of lack of knowledge and then proced to conflate every distro as just one “Linux” experience and not want to look back at it.
I still stand by one thing you will always hear me say: use the right tool for the job.
I am not sure if there is a good way to do it without scripting, and a router that would allow for taking variable input from an external script. But theoretically if the router would support it, you could script a port change at times there are no one on the server.
Essentially the server port is in a text file, you could use some command line utilities, and write a script leveraging something like sed to change the port in place.
But I am overcomplicating it. lol