On Thu, Aug 29, 2019 at 2:18 PM Japheth Cleaver <cleaver@xxxxxxxxxxxxxx> wrote: > > On 8/29/2019 8:10 AM, Adam Williamson wrote: > > On Wed, 2019-08-28 at 23:13 -0400, Christopher wrote: > >> On Wed, Aug 28, 2019 at 8:56 PM John Harris <johnmh@xxxxxxxxxxxxx> wrote: > >>> It might be okay to be a GNOME-specific thing, as that's the only spin of > >>> Fedora which is affected by this decision. > >>> > >> The default firewall config affects every user of that edition, even > >> if they never use GNOME (or even use graphical boot). So, I don't know > >> if this would be adequate. > > Why would you install Workstation if you didn't intend to use GNOME? > > That would seem to be a reasonable question, but if it's possible to do > so then it is bound to happen... It may be a symptom of unclear definition. 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. 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. > > If Workstation is going to require a graphical environment for > reasonable usage/administration/whatever, then it should be made > mandatory somehow. It would also help clarify that the Workstation, 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. > Server, and <null> Products must be treated distinctly... and that you > shouldn't just point your kickstart file at whatever ISO you happen to > have laying around. 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. _______________________________________________ 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
