public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting tar to keep going
Date: Tue, 5 Nov 2024 13:25:09 -0500	[thread overview]
Message-ID: <66a792d5-d1cc-42b6-a264-20a638643f44@gentoo.org> (raw)
In-Reply-To: <a3dcd444-885a-80db-c8a2-421f725ccf4f@gentoo.tnetconsulting.net>


[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]

On 11/5/24 11:27 AM, Grant Taylor wrote:
> On 11/5/24 9:38 AM, Peter Humphrey wrote:
>> The Network Manager man page says to 'chattr +i /etc/resolv.conf', so
>> I did, and that one move enabled the wireless network to work as it
>> should.
> 
> What?!?!?!  Network Manager can't be made to keep it's hands off of /
> etc/resolv.conf so the workaround is to leverage file system features to
> break Network Manager's hands when it tries to touch the file?
> 
> That's a hell of a bad design in my opinion.


Yeah, and it's also nonsense as far as I can tell. Here's what the man
page for Network Manager actually says:

dns
        Set the DNS processing mode.

        none: NetworkManager will not modify resolv.conf. This implies
        rc-manager unmanaged


rc-manager
        Set the resolv.conf management mode. This option is about how
        NetworkManager writes to /etc/resolv.conf, if at all.


        If you configure dns=none or make /etc/resolv.conf immutable
        with chattr +i, NetworkManager will ignore this setting and
        always choose unmanaged (below).


        symlink: If /etc/resolv.conf is a regular file or does not
        exist, NetworkManager will write the file directly.

        file: NetworkManager will write /etc/resolv.conf as regular
        file.

        unmanaged: don't touch /etc/resolv.conf.


-- 
Eli Schwartz

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  parent reply	other threads:[~2024-11-05 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 15:38 [gentoo-user] Getting tar to keep going Peter Humphrey
2024-11-05 16:27 ` Grant Taylor
2024-11-05 16:55   ` Peter Humphrey
2024-11-05 18:11     ` Dale
2024-11-05 18:25   ` Eli Schwartz [this message]
2024-11-05 22:23   ` Arsen Arsenović
2024-11-05 23:41   ` Grant Taylor
2024-11-06  0:08     ` Eli Schwartz
2024-11-06  2:11       ` Peter Humphrey

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=66a792d5-d1cc-42b6-a264-20a638643f44@gentoo.org \
    --to=eschwartz@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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