From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting tar to keep going
Date: Tue, 05 Nov 2024 16:55:58 +0000 [thread overview]
Message-ID: <5837657.DvuYhMxLoT@cube> (raw)
In-Reply-To: <a3dcd444-885a-80db-c8a2-421f725ccf4f@gentoo.tnetconsulting.net>
On Tuesday 5 November 2024 16:27:57 GMT 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.
Yes, I thought it might raise a laugh...
> The tar error will be related to the restore / write to disk, not
> reading from ""tape or command error.
I see what you mean: in my case, tar needs an --ignore-failed-write option.
> You might explore an option to cause tar to exclude /etc/resolv.conf
> from the restore job. I'm not sure what that would look like as I'm
> usually only messing with exclude during backups.
There is an --exclude option; I can use that.
> You might be able to mess with some even more esoteric (bind) mount
> options, but that will be quite similar to the chattr dance.
>
> I'd go smack Network Manager with a bigger bat.
I'll hold your coat... :)
--
Regards,
Peter.
next prev parent reply other threads:[~2024-11-05 16:56 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 [this message]
2024-11-05 18:11 ` Dale
2024-11-05 18:25 ` Eli Schwartz
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=5837657.DvuYhMxLoT@cube \
--to=peter@prh.myzen.co.uk \
--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