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
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
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?
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
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
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
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
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
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
9 matches
Mail list logo
