Linux

48310 readers

645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Is it possible to delete the default zones in Firewalld, and if not, why? (sh.itjust.works)

submitted 10 months ago* (last edited 10 months ago) by Kalcifer@sh.itjust.works to c/linux@lemmy.ml

14 comments fedilink hide all child comments

If you try to remove one of the predefined zones from Firewalld, e.g. public, you encounter the following error:

Error: BUILTIN_ZONE: 'public' is built-in zone

I don't like that Firewalld is bloated with all of these built in zones that I will never use. I want to get rid of them, but, from what I've been able to find, it appears non-trivial to do so.

EDIT (2024-01-27T01:55Z):

I came across this GitHub issue. So it appears that this is a known "issue", and it could potentially be changed in the future, albeit probably far in the future. It is a very strange initial design choice, though, in my opinion.

you are viewing a single comment's thread
view the rest of the comments

[–] SheeEttin@programming.dev 2 points 10 months ago* (last edited 10 months ago) (3 children)

Because it aligns with most people's use case. You're free to patch it out if you're so inclined.

[–] Kalcifer@sh.itjust.works 1 points 9 months ago* (last edited 9 months ago) (2 children)

Because it aligns with most people’s use case.

Sure, that is why we have defaults, but why force them? Why not create the defaults, and then allow the user to remove them if they wish?

You’re free to patch it out if you’re so inclined.

This is somewhat of a non-answer. Technically, yes, it is possible for a user to patch OSS as they see fit, but that does not excuse poor design desicions, nor is it necessarily fair to expect the user to do that.

[–] SheeEttin@programming.dev -1 points 9 months ago (1 children)

Maybe you should take it up with the maintainers. I can't tell you what they were thinking.

[–] Kalcifer@sh.itjust.works 0 points 9 months ago

Maybe you should take it up with the maintainers.

See the linked GitHub issue.