Re: Sound

Mike S <[email protected]>
Newsgroups gmane.linux.gentoo.ppc
Message-ID <[email protected]>
Neil Bothwick wrote:

>On Wed, 10 Aug 2005 16:48:34 -0700, Mike S wrote:
>
>  
>
>>ok I have many questions this time.  I set this variable before but for 
>>get where it was.  There is something that emerge can to to 
>>automatically write over existing configuration files.  And when I
>>first installed gentoo I set it to do that, not knowing how annoying it
>>could be.  Now I hope someone can help me in changing that back, as
>>when I ran emerge world a lot of settings were deleted, some of which
>>have been easy to change, and some not.
>>    
>>
>
>The variable is CONFIG_PROTECT_MASK, set in /etc/make.conf. It sound
>slike you set it to "/etc", which is a dangerous thing to do, especially
>when you emerge a baselayout update and your fstab and passwd files get
>overwritten. Comment out the setting in make.conf, or set it to contain
>only directories where you know it is safe for emerge to overwrite files.
>I have it set to "/etc/init.d".
>
>
>  
>
well I checked the /etc/make.conf file, and yes you were right (almost)  
I am not sure what the difference is, but I am sure that I will find out 
sooner or later, instead of CONFIG_PROTECT_MASK variable set to 
something I had CONFIG_PROTECT="-*".  So for the time being I just 
commented that line out, and will maybe change it once I learn more 
about it.

I will investigate the difference between CONFIG_PROTECT_MASK and 
CONFIG_PROTECT and see what the difference is (if any), or if they are 
merely the same variable with different names, which I have noticed on 
some distributions happens because of multiple developers not all 
keeping up to speed with each other.  Though from what I have see so far 
gentoo is one of the more professional distributions and that will 
probably not be the case.

Thanks Neil,
--Mike S
-- 
[email protected] mailing list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.