Github messages for voidlinux
 help / color / mirror / Atom feed
From: TeusLollo <TeusLollo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: (Not technically a bug, yet very counter-intuitive and prone to breakage) Runit nftables service imports "/etc/nftables.conf" instead of the more sensible "/etc/nftables/nftables.conf"
Date: Thu, 15 Dec 2022 10:57:49 +0100	[thread overview]
Message-ID: <20221215095749.pBS-oVvOU-hBuNMR1AgHJB8dVwiUyExm5FShNP5q-Rc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41100@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

New comment by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/41100#issuecomment-1352816670

Comment:
Never mind, then. 

I must have miss-read that part (After two hours and a half of bickering with configurations, I must have been exhausted), and assumed the `/etc/nftables/` directory was meant for the nft ruleset. I guess most users too would assume so going in first-time into nft configuration. 

Still, it's kinda weird having one mostly-empty `/etc/nftables/` directory, while the really critical nft ruleset is expected to reside into `/etc/nftables.config`. At least it's documented, unless you end-up miss-reading like I did. 

I presume there must be some reason for establishing such a setup, although I'm not familiar enough with Void packaging to know for sure. I may eventually learn more. 

Thus, since there's technically not a bug, and since it's actually intended to work this way, I'm closing this. 

Thanks to everyone for their efforts, regardless. 

  parent reply	other threads:[~2022-12-15  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  0:32 [ISSUE] " TeusLollo
2022-12-15  6:56 ` paper42
2022-12-15  7:47 ` paper42
2022-12-15  9:57 ` TeusLollo [this message]
2022-12-15  9:57 ` [ISSUE] [CLOSED] " TeusLollo
2022-12-15 10:06 ` paper42
2022-12-15 10:06 ` [ISSUE] [CLOSED] " paper42

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221215095749.pBS-oVvOU-hBuNMR1AgHJB8dVwiUyExm5FShNP5q-Rc@z \
    --to=teuslollo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).