Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-17 Thread Boyd Stephen Smith Jr.
On Monday 16 October 2006 15:53, maxim wexler [EMAIL PROTECTED] wrote 
about 'Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED':
 But where is CONFIG_PROTECT_MASK, since grepping
 make.conf only returns the one line, CONFIG_PROTECT?

Gentoo provides defaults for both values.  Your value in /etc/make.conf 
overrides the default(s).

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh


pgpAywddX6dNH.pgp
Description: PGP signature


Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-17 Thread Bo Ørsted Andresen
On Monday 16 October 2006 22:53, maxim wexler wrote:
 But where is CONFIG_PROTECT_MASK, since grepping
 make.conf only returns the one line, CONFIG_PROTECT?

Looking at the output of the following commands should answer your question.

# env | grep ^CONFIG_PROTECT

# find /etc/env.d | xargs grep CONFIG_PROTECT

# grep CONFIG_PROTECT /etc/profile.env

# grep -A 1 profile.env /etc/profile

-- 
Bo Andresen


pgpFGPZt5JJJ6.pgp
Description: PGP signature


Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED?

2006-10-16 Thread maxim wexler

 If you really have an empty CONFIG_PROTECT,
 dispatch-conf didn't touch
 this file, it was replaced during emerge. You must
 fix this before
 emerging anything else or you will overwrite more
 config files.
 
 What do
 emerge --info | grep CONFIG
 and
 grep CONFIG /etc/make.conf
 show?

localhost heathen # emerge --info | grep CONFIG
CONFIG_PROTECT=
CONFIG_PROTECT_MASK=/etc/env.d /etc/gconf
/etc/terminfo
localhost heathen # grep CONFIG /etc/make.conf
CONFIG_PROTECT=-*


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED?

2006-10-16 Thread Bo Ørsted Andresen
On Monday 16 October 2006 22:26, maxim wexler wrote:
 localhost heathen # grep CONFIG /etc/make.conf
 CONFIG_PROTECT=-*

WHY did you set that?? Remove it! Read the output of:

# emerge --help --config

-- 
Bo Andresen


pgp3pkcTQCinJ.pgp
Description: PGP signature


Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-16 Thread maxim wexler

Please see my reply to Neil re this thread
 
 Once you marked some directories from protection,
 emerge will, instead of 
 using the file from a package, install the file from
 a package 
 as ._cfg-filename (or somesuch).  Tools like
 dispatch-conf and 
 etc-update are then used to merge your file with the
 one(s) 
 named ._cfg-filename.

I replied(to Neil) before remembering why I put
CONFIG_PROTECT=-* in my make.conf(if that's the
problem here). Now it comes back to me. Whenever I
used to emerge something there'd inevitably be a long
followup where I had to answer y/n to a list of files
that were due to be overwritten IIRC. From a forum I
was advised to write the above CONFIG_PROTECT line.
That's when was I new to gentoo and I haven't changed
it since.

But where is CONFIG_PROTECT_MASK, since grepping
make.conf only returns the one line, CONFIG_PROTECT?

-Maxim

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED?

2006-10-16 Thread Neil Bothwick
On Mon, 16 Oct 2006 13:26:37 -0700 (PDT), maxim wexler wrote:

 localhost heathen # emerge --info | grep CONFIG
 CONFIG_PROTECT=

You've told portage to overwrite any config files in /etc, or anywhere
else, whenever you update a package. dispatch-conf certainly isn't to
blame, the damage is self-inflicted.


-- 
Neil Bothwick

Phasers don't kill people...Unless you set them too high.


signature.asc
Description: PGP signature


Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-15 Thread maxim wexler
One of the files dispatch-conf over-wrote without
telling me or leaving any record was
/etc/modules.autoload.d/kernel-2.6 which meant 8250.ko
failed to load.

 What is the output of:
 
 # portageq config_protect
 
 and
 
 # portageq config_protect_mask
 
localhost heathen # portageq config_protect

localhost heathen # portageq config_protect_mask
/etc/env.d /etc/gconf /etc/terminfo
localhost heathen #

-Maxim

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-15 Thread Neil Bothwick
On Sun, 15 Oct 2006 08:34:10 -0700 (PDT), maxim wexler wrote:

 One of the files dispatch-conf over-wrote without
 telling me or leaving any record was
 /etc/modules.autoload.d/kernel-2.6 which meant 8250.ko
 failed to load.

 localhost heathen # portageq config_protect


If you really have an empty CONFIG_PROTECT, dispatch-conf didn't touch
this file, it was replaced during emerge. You must fix this before
emerging anything else or you will overwrite more config files.

What do
emerge --info | grep CONFIG
and
grep CONFIG /etc/make.conf
show?


-- 
Neil Bothwick

mandelbug /man'del-buhg/ n.
 [from the Mandelbrot set] A
   bug whose underlying causes are so complex and obscure as to make
   its behavior appear chaotic or even non-deterministic.  This term
   implies that the speaker thinks it is a Bohr bug, rather than
   a heisenbug.  See also schroedinbug.


signature.asc
Description: PGP signature


Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED

2006-10-15 Thread Boyd Stephen Smith Jr.
On Sunday 15 October 2006 10:34, maxim wexler [EMAIL PROTECTED] wrote 
about 'Re: [gentoo-user] dispatch-conf spells disaster-RESOLVED':
 One of the files dispatch-conf over-wrote without
 telling me or leaving any record was
 /etc/modules.autoload.d/kernel-2.6 which meant 8250.ko
 failed to load.

That wasn't dispatch-conf, it was emerge since you've told it not to 
protect any configuration files.

 localhost heathen # portageq config_protect

 localhost heathen # portageq config_protect_mask
 /etc/env.d /etc/gconf /etc/terminfo

You've told portage not to protect *any* config files.  It did as you 
asked, and used the /etc/modules.autoload.d/kernel-2.6 included in a 
package.

You might consider restoring the default config_protect, or at least part 
of it.  From my system:
$ portageq config_protect
/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown 
/usr/share/X11/xkb /usr/share/config

Once you marked some directories from protection, emerge will, instead of 
using the file from a package, install the file from a package 
as ._cfg-filename (or somesuch).  Tools like dispatch-conf and 
etc-update are then used to merge your file with the one(s) 
named ._cfg-filename.

-- 
If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability.
-- Gentoo Developer Ciaran McCreesh


pgpqGNXS1EjWk.pgp
Description: PGP signature