On Thursday, August 29, 2019 5:29:32 PM MST Christopher wrote: > Workstation is the primary product. Some choose that not for GNOME... > but because they want to start with the most base product and > customize from there. If you start with a Spin, you may get something > pre-configured in a very weird way... and with a smaller support > community. Workstation is only the primary product because somebody decided GNOME was the best default. This should be reconsidered, so that the various Spins, the GNOME Spin, KDE Spin, XFCE Spin and so on have equal standing. At least the most common two. This obviously isn't my decision to make, nor does my position on it really matter, but that is my opinion, and I believe it isn't so unfounded. > In any case, what users do with the Workstation product isn't the > point at all. The point is that the problem at hand is the > firewalld.conf file, and *NOT* anything to do with the GNOME > experience itself, or any part of any GNOME packages. Well, the Workstation product is the GNOME Spin. It is *the* GNOME experience in Fedora. I do agree with "what users do with the Workstation product isn't the point at all", as it's not like we can predict what people will do with their system after it's installed. > Yikes! Making a particular (graphical or otherwise) environment > mandatory is a frightening idea for a Linux distro. "Have it your way" > is what separates Linux from proprietary OSes. I completely agree. It's what brought me to Fedora. > Agreed, but nobody suggested that. Writing a kickstart specifically > for the Workstation product seems like a sane thing to do if you want > to PXE boot and automate a custom install based on Workstation for > your entire office / school / library that you support as an IT > person. And, to loop it back to the main point of this thread... if > you were to do that, unless you took special steps to clobber > firewalld.conf with your own, you'd be affected by the firewalld.conf > default configuration without ever logging in to GNOME on any of those > workstations. Again, the problem isn't GNOME... it's firewalld's > default configuration in Workstation. Writing a kickstart for Workstation would require you to base your package list on that of the Workstation kickstart. The issue is not firewalld.conf, it's the package that Workstation pulls in through the group workstation-product, fedora-release-workstation. -- John M. Harris, Jr. <johnmh@xxxxxxxxxxxxx> Splentity https://splentity.com/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
