On 1/22/21 9:29 AM, Marc Balmer via CentOS wrote:>> Hence it is as good as dead in my mind when looking into the future, I >> am looking for future distro of choice. > > A little mentioned choice would be openSUSE, which is direction I am taking.I do not like system where configuration app can overwrite manualy set config. I started with ClarkConnect in 2005-2006 and to route public subnet into my network I had to delete last iptables command then add my own, but only after config system did it's own iptables commands. I had to learn iptables before any other Linux commands and although I mastered it, it is left in unpleasant memory (it took me weeks and help from rare Linux admins to find a solution). I did try SUSE around 2000 but it was complicated to do manual changes (if it was not provided in YAST), so after ClarkConnect I had no desire to even experiment with YAST. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant
> On Jan 22, 2021, at 5:12 AM, Ljubomir Ljubojevic <centos at plnet.rs> wrote: > > On 1/22/21 9:29 AM, Marc Balmer via CentOS wrote: >>> Hence it is as good as dead in my mind when looking into the future, I >>> am looking for future distro of choice. >> >> A little mentioned choice would be openSUSE, which is direction I am taking. > > I do not like system where configuration app can overwrite manualy set > config. I started with ClarkConnect in 2005-2006 and to route public > subnet into my network I had to delete last iptables command then add my > own, but only after config system did it's own iptables commands. I had > to learn iptables before any other Linux commands and although I > mastered it, it is left in unpleasant memory (it took me weeks and help > from rare Linux admins to find a solution). > > I did try SUSE around 2000 but it was complicated to do manual changes > (if it was not provided in YAST), so after ClarkConnect I had no desire > to even experiment with YAST.I tried SUSE maybe 2-3 years later than you (around 2003). The first thing I disliked was: they have yast on top of standard configurations. First of all, it is quite unpleasant to deal with: infinitely long single file containing all configs. Next, you change one single thing, and yast to enable your change touches all config files. Some time after you made some change you discover something (unrelated) doesn?t work anymore, and you can not use timestamps to investigate when bad change happened and how. I was joking about SUSE with my German friends: how come German tool is named as abbreviation of English (yet another system tool), not German? But what really did it for me was: stock installation from SUSE DVD (that specific release) was easily crashed by program with memory leak run by regular user. I replace SUS stock kernel with downloaded and compiled with all default option kernel from kernel.org, and it happily kills memory leaking program (even the one run by root). Not kernel shipped with SUSE. This: memory leak, out of memory condition is one of the tests I usually do when I?m testing [quite] new for me system (and some other stuff). I turned away from SUSE then, and never looked back. Just my $0.02 Valeri> > -- > Ljubomir Ljubojevic > (Love is in the Air) > PL Computers > Serbia, Europe > > StarOS, Mikrotik and CentOS/RHEL/Linux consultant > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
? 12:12 +0100 ?? 22.01.2021 (??), Ljubomir Ljubojevic ??????:> On 1/22/21 9:29 AM, Marc Balmer via CentOS wrote: > > > Hence it is as good as dead in my mind when looking into the > > > future, I > > > am looking for future distro of choice. > > > > A little mentioned choice would be openSUSE, which is direction I > > am taking. > > I do not like system where configuration app can overwrite manualy > set > config.That's why you need to use ".local" for most of the files to preserve your settings. SUSE is not another RH clone and it has it's one specifics. Best Regards, Strahil Nikolov
On 1/22/21 5:12 AM, Ljubomir Ljubojevic wrote:> On 1/22/21 9:29 AM, Marc Balmer via CentOS wrote: >>> Hence it is as good as dead in my mind when looking into the future, I >>> am looking for future distro of choice. >> >> A little mentioned choice would be openSUSE, which is direction I am taking. > > I do not like system where configuration app can overwrite manualy set > config. I started with ClarkConnect in 2005-2006 and to route public > subnet into my network I had to delete last iptables command then add my > own, but only after config system did it's own iptables commands. I had > to learn iptables before any other Linux commands and although I > mastered it, it is left in unpleasant memory (it took me weeks and help > from rare Linux admins to find a solution). > > I did try SUSE around 2000 but it was complicated to do manual changes > (if it was not provided in YAST), so after ClarkConnect I had no desire > to even experiment with YAST. > >I have no issues with OpenSUSE .. but how is OpenSUSE any better than CentOS Stream? It is not like we are rolling rawhide packages into CentOS Stream. They are updating already created Enterprise Packages in current RHEL with Bug Fixes and Security Fixes and a small number of rebases (Enhamcments Fixes). But the enhancements are not from Rawhide, they are rebases very close to the current releases. Again .. absolutely nothing wrong with using OpenSUSE (or Ubuntu or Debian, etc). I just do not see the advantage. I mean, I get it, some people are very upset with the new way CentOS is being done. And obviously people get to think what they think. But when this was announced, it was also announced that RHEL was going to be opened up early in Q1 of 2021 (which has happened and is still happening).