On 10/18/06, Justin Patrin <[EMAIL PROTECTED]> wrote:
On 10/14/06, maxim wexler <[EMAIL PROTECTED]> wrote:
> Hello group,
>
> As I expected it would, dispatch-conf
> over-wrote/corrupted a lot of files without giving me
> a chance to stop it. It left no log(file was empty)in
> /var/log/dispatch-c
On 10/14/06, maxim wexler <[EMAIL PROTECTED]> wrote:
Hello group,
As I expected it would, dispatch-conf
over-wrote/corrupted a lot of files without giving me
a chance to stop it. It left no log(file was empty)in
/var/log/dispatch-conf.log. or any record of its
passing that I can find.
Why did
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
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
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 sel
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- (or somesuch). Tools like
> dispatch-conf and
> etc-update are then used to merge your file
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
> 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 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
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 a
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_
On Sunday 15 October 2006 04:09, maxim wexler wrote:
[SNIP]
> FWIW this all took place after emerge
> baselayout-1.12.5-r1 which issued a warning to
>
> /bin/ls /etc/init.d/net.* | grep -v '/net.lo$' | xargs
> -n1 ln -svfn net.lo
>
> Could that have done it?
No that just ensures that all your net
Hello group,
As I expected it would, dispatch-conf
over-wrote/corrupted a lot of files without giving me
a chance to stop it. It left no log(file was empty)in
/var/log/dispatch-conf.log. or any record of its
passing that I can find.
Worst of all I can no longer dialout.
/dev/ttyS0(external modem
13 matches
Mail list logo
