I've 'protected' /etc and /dev, right?

deornoth · n00b Joined: 04 Jul 2002 Posts: 13

First things first, I edit /etc/make.conf and add the line:

CONFIG_PROTECT="/etc /dev"

I then start running through the 'emerge rsync' and /usr/portage/scripts/bootstrap.sh, and check on /etc and /dev in another terminal... and it looks like emerge is still fscking with them. What's up? I thought that CONFIG_PROTECT was supposed to prevent that! ...right?

-Deornoth
_________________
"If you want code to be portable, you shouldn't necessarily create an abstraction layer to achieve portability. Instead you should just program intelligently."
-- Linus Torvalds

fghellar · Posted: Sat Jul 06, 2002 4:12 pm Post subject:

The bootstrap script reverts it to CONFIG_PROTECT="". You can edit it and comment it out to force your previous protecion to work.
_________________
| www.gentoo.org | www.tldp.org | www.google.com |

delta407 · Posted: Sat Jul 06, 2002 6:11 pm Post subject:

Bootstrapping does lots of interesting things to get GCC to build itself, and it will mess with your configuration in order to do so. Don't worry, that's normal, expected, and necessary.

Portage does obey them... usually.

_________________
I don't believe in witty sigs.

deornoth · n00b Joined: 04 Jul 2002 Posts: 13

Yeah, I figured that out. For my purposes, an emerge inject baselayout-x.y.z, emerge glibc, emerge gcc, and emerge system, followed by an emerge -e system did it.

-Deornoth
_________________
"If you want code to be portable, you shouldn't necessarily create an abstraction layer to achieve portability. Instead you should just program intelligently."
-- Linus Torvalds

delta407 · Posted: Sun Jul 07, 2002 1:01 am Post subject:

Why did you do that?
_________________
I don't believe in witty sigs.

deornoth · n00b Joined: 04 Jul 2002 Posts: 13

delta407 · Posted: Sun Jul 07, 2002 3:26 am Post subject:

Ah. Well, in that case, may the force be with you.

_________________
I don't believe in witty sigs.