• 0 Posts
  • 34 Comments
Joined 2 years ago
cake
Cake day: June 4th, 2023

help-circle



  • You can mess up android by installing third party apps, using shizuku, or rooting. If there is a distro as strict as vanilla android is for the average user, then you are right. I’m talking no root, no sudo, only official flatpak apps can be installed and only user’s home directory is r/w.

    Even for an intermediate user, immutable might be a good choice, but it is extra unneeded complexity for a beginner, according to my experience with those type of distro in the past.

    But people are different. Some might feel right at home.



  • My advice would be, only use vanilla/default/official versions of the most popular distros. Ubuntu, not Ubuntu Studio, Fedora, not (I don’t know what variants there are) Fedora. Do not use specialized distros, for example a gaming distro. Do not use 3rd party repos. Do not manually install any packages from anywhere. If you want something and official repos of your official distro cannot do it, just don’t do it. Do not try to find a workaround and make it happen.

    After using Linux for a while you’ll become more comfortable with it and you’ll slowly start moving outside the above limitations. The best and worst thing about Linux is that your OS is yours and you can tinker with all of its parts. But you shouldn’t, at the beginning. If you were to tinker with Windows like that, it would also break.





  • I attempted a few times. Setting up additional repositories and/or enabling testing repos declaratively was not possible. you had to do it via command line before setting the system. checked back some time later, still was the case. Also there are many ways to do the same thing, what are flakes, how to declaratively manage home (again there were multiple ways to do that). Are some of those ways deprecated, are some in testing, which one is assumed to be the default? etc.

    If I ever need to manage multiple machines, and I have to setup a new machine every 6 months or so I’ll get to work and learn. Other than that, isn’t really worth the trouble.

    But still tempting :)







  • Its approach to the /etc dir was great. I haven’t used it but read the documentation. Basically, all software come with default config files in /usr/lib/config or some directory like that. You create a config file in /etc only if you want to override some defaults, and if you want to reset all configuration you simply delete all files in /etc. I think it is a great system. Removes the clutter from among the user created config files and enables one to make an etc-files repo and keep track of system configuration via git, just like people do with their dot files and user configuration. But other than that, I had no reason to try it.