From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-204957-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 970FE158042
	for <garchives@archives.gentoo.org>; Tue,  5 Nov 2024 23:41:33 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 87774E0844;
	Tue,  5 Nov 2024 23:41:27 +0000 (UTC)
Received: from tncsrv06.tnetconsulting.net (tncsrv06.tnetconsulting.net [IPv6:2600:3c00:e000:1e9::8849])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 3887CE0821
	for <gentoo-user@lists.gentoo.org>; Tue,  5 Nov 2024 23:41:27 +0000 (UTC)
Received: from Contact-TNet-Consulting-Abuse-for-assistance
	by tncsrv06.tnetconsulting.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id 4A5NfQp3029776
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
	for <gentoo-user@lists.gentoo.org>; Tue, 5 Nov 2024 17:41:26 -0600
Message-ID: <fbc94d9d-8b08-0ee6-edd8-9e4699bc0a74@gentoo.tnetconsulting.net>
Date: Tue, 5 Nov 2024 17:41:26 -0600
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: [gentoo-user] Getting tar to keep going
Content-Language: en-US
To: gentoo-user@lists.gentoo.org
References: <2962590.e9J7NaK4W3@cube>
 <a3dcd444-885a-80db-c8a2-421f725ccf4f@gentoo.tnetconsulting.net>
From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
In-Reply-To: <a3dcd444-885a-80db-c8a2-421f725ccf4f@gentoo.tnetconsulting.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Archives-Salt: 0f445943-598b-4997-a624-1f26aa42d2a3
X-Archives-Hash: befbf54de6634541ade18b0a8f112211

On 11/5/24 10:27 AM, Grant Taylor wrote:
> 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?

Clarifying, after some replies that I've seen.

I was surprised by, and doubted, the idea that Network Manager might not 
be able to be configured to leave /etc/resolv.conf alone.

I assumed that Network Manager can be configured to leave 
/etc/resolv.conf alone.

As such, I'd think it is better to configure Network Manager to leave 
/etc/resolv.conf alone and not fall back to something like setting the 
immutable attribute on the file to prevent it being messed with.



-- 
Grant. . . .