On 2023-04-27 13:12, Patrick Shanahan wrote:
* Darryl Gregorash <raven@accesscomm.ca> [04-27-23 14:44]:
On 2023-04-27 11:56, Carlos E. R. wrote: ...
Because it has been able to configure the network, for decades. It just can't with network manager.
Yeah, I think I figured that out, Carlos, way back in the 1990s when I first installed SuSE 6.(something) after IBM dumped OS/2 Warp. And if I hadn't back then, then surely I had it figured out when I dumped NM and fully configured wicked, in YaST.
Oh, it does configure firewalld, albeit incompletely. I'm not sure this instant if it configured SuSEfirewall2.
"It does configure firewalld, albeit incompletely." If it cannot _completely_ configure something, then it cannot be said to configure it at all -- configuration implies that, once you are done, you are good to go. At least, that's the meaning of "configuration" in my books.
well, you are rather demanding there. Always there will be edge cases that are not determined worth a programmer's time will not be provided for in many gui configuration apps including yast.
And here I thought that a system configuration/etc tool would not be considered complete unless it included the capability to fully configure a network. That task hardly seems like an "edge case" to me.