From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Mon, 14 Mar 2005 22:24:24 -0600 [thread overview]
Message-ID: <1110860664.11759.3.camel@matrix.brianandsara.net> (raw)
In-Reply-To: <4236004E.1010007@gentoo.org>
On Mon, 2005-03-14 at 13:21 -0800, Donnie Berkholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Vitaly Ivanov wrote:
> > I found the comments of Nicholas Jones in bug
> > http://bugs.gentoo.org/show_bug.cgi?id=52415
> >>> Portage makes the assumption that if you're installing
> >>> into a new root, then you're building a system and
> >>> shouldn't bother with config protection. It's not
> >>> documented either way, so it's undefined behavior.
>
> I disagree with that logic, because people may be maintaining systems in
> a ROOT with modified config files. Updating those systems trashes the
> files. Thank you for pointing out this behavior now, because it walks
> all over plans I have for a diskless cluster.
I mentioned this to the portage guys the other day. Either they didn't
care, or they didn't hear me. Either way, probably need to file a bug
about it (or stir up that other one).
--Iggy
--
gentoo-dev@gentoo.org mailing list
WARNING: multiple messages have this Message-ID (diff)
From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] CONFIG_PROTECT and ROOT!='/'
Date: Mon, 14 Mar 2005 22:24:24 -0600 [thread overview]
Message-ID: <1110860664.11759.3.camel@matrix.brianandsara.net> (raw)
Message-ID: <20050315042424.bvHZaLHzy-fTh4QChJUyaBItoLgSvw3wHUaTlAfu83o@z> (raw)
In-Reply-To: <4236004E.1010007@gentoo.org>
On Mon, 2005-03-14 at 13:21 -0800, Donnie Berkholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Vitaly Ivanov wrote:
> > I found the comments of Nicholas Jones in bug
> > http://bugs.gentoo.org/show_bug.cgi?id=52415
> >>> Portage makes the assumption that if you're installing
> >>> into a new root, then you're building a system and
> >>> shouldn't bother with config protection. It's not
> >>> documented either way, so it's undefined behavior.
>
> I disagree with that logic, because people may be maintaining systems in
> a ROOT with modified config files. Updating those systems trashes the
> files. Thank you for pointing out this behavior now, because it walks
> all over plans I have for a diskless cluster.
I mentioned this to the portage guys the other day. Either they didn't
care, or they didn't hear me. Either way, probably need to file a bug
about it (or stir up that other one).
--Iggy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-15 4:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 16:45 [gentoo-dev] CONFIG_PROTECT and ROOT!='/' Vitaly Ivanov
2005-03-14 21:21 ` Donnie Berkholz
2005-03-15 4:24 ` Brian Jackson [this message]
2005-03-15 4:24 ` Brian Jackson
2005-03-15 6:56 ` Georgi Georgiev
2005-03-15 14:26 ` Brian Jackson
2005-03-15 16:14 ` Georgi Georgiev
2005-03-15 18:01 ` Brian Jackson
2005-03-15 23:05 ` Georgi Georgiev
2005-03-16 3:17 ` Brian Harring
2005-03-16 3:35 ` Georgi Georgiev
2005-03-16 4:11 ` Brian Harring
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=1110860664.11759.3.camel@matrix.brianandsara.net \
--to=iggy@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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