From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update?
Date: Sun, 15 Oct 2006 13:27:57 +0100 [thread overview]
Message-ID: <20061015132757.283f8283@krikkit.digimed.co.uk> (raw)
In-Reply-To: <20061015044052.GB9122@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]
On Sun, 15 Oct 2006 00:40:52 -0400, Walter Dnes wrote:
> > Yes, etc-update shows it to your before asking what to do. Check the
> > contents of each file before allowing it to be overwritten, and never,
> > ever let etc-update overwrite etc/fstab, /etc/passwd or /etc/group.
>
> CONFIG_PROTECT and CONFIG_PROTECT_MASK work at the *DIRECTORY* level.
That will change soon IIRC.
> What I really want/need is a feature that allows additional protection
> *FOR INDIVIDUAL FILES*. E.g...
You don't understand what CONFIG_PROTECT means, it prevents files being
automatically overwritten during installation, leaving them to you to
update.
> - my customized /etc/conf.d/local.start or /etc/conf.d/local.stop
> should *NEVER* be replaced with an empty version
Agreed.
> - /etc/rc.conf should be left alone too. ***FOR THE UMPTEENTH TIME,
> NO I DO NOT WANT NANO REPLACING VIM AS MY "EDITOR"***
How would you know about changes to rc.conf? Either new features or changes in the way things are done would pass you by.
> And the list goes on and on. Howsabout an environmental variable
> CONFIG_PROTECT_FILES, containing a list of protected files? I'm ready
> to submit a feature request if necessary. Does anybody have additional
> comments?
As I've mentioned several times before, there was a patch to
dispatch-conf to do just this. You added the files you didn't want
touching, ever, to a line in the config file. Unfortunately, the patch
hasn't been updated for a couple of years and stopped working a while
ago. Why not re-open the bug at
http://bugs.gentoo.org/show_bug.cgi?id=68618
--
Neil Bothwick
If you think that you can truncate my sig to 75 chars, then you can just
fu
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-15 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:00 [gentoo-user] where to put mknod & chmod maxim wexler
2006-10-11 16:24 ` Alan McKinnon
2006-10-12 14:44 ` maxim wexler
2006-10-12 17:10 ` Alan McKinnon
2006-10-13 15:22 ` maxim wexler
2006-10-13 15:33 ` Neil Bothwick
2006-10-15 4:40 ` [gentoo-user] Is it possible to protect *INDIVIDUAL FILES* against etc-update? Walter Dnes
2006-10-15 7:06 ` Bo Ørsted Andresen
2006-10-16 21:57 ` Walter Dnes
2006-10-17 0:47 ` Richard Fish
2006-10-18 4:09 ` Walter Dnes
2006-10-17 13:11 ` Neil Bothwick
2006-10-15 12:27 ` Neil Bothwick [this message]
2006-10-17 13:16 ` Bo Ørsted Andresen
2006-10-17 14:28 ` Neil Bothwick
2006-10-13 23:51 ` [gentoo-user] where to put mknod & chmod Drew
2006-10-11 18:09 ` Neil Bothwick
2006-10-11 21:31 ` [gentoo-user] where to put mknod & chmo Richard Fish
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=20061015132757.283f8283@krikkit.digimed.co.uk \
--to=neil@digimed.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