[gentoo-user] dispatch-conf spells disaster

[gentoo-user] dispatch-conf spells disaster

[maxim wexler]

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 on COM1) no longer exists
although in udev-rules the rule exists to create
/dev/ttyS*. But there is no such thing under /dev.
Attempts to dial-out lead to "unrecognized option
'dev/ttyS0'"

Speaking of udev, according to

http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html

the only thing I left out of my setup was 

#rc-update add hotplug boot. 

So I did it, but it didn't help. Under "PPP Device" on
that same page it says to 

#mknod -m 660 /dev/ppp c 108 0

But that didn't work either.

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?

Also /dev/parport0 no longer exists, or /dev/lp*.

Further, could it be this has nothing to do with
dispatch-conf at all. Afterall, a check of /etc/*conf
shows many files with the timestamp corresponding to
emerge baselayout's timestamp in portage. I didn't run
#dispatch-conf for another 5 mins after that. 

-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

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

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 init scripts are symlinks 
to /etc/init.d/net.lo.

[SNIP]
> Further, could it be this has nothing to do with
> dispatch-conf at all. Afterall, a check of /etc/*conf
> shows many files with the timestamp corresponding to
> emerge baselayout's timestamp in portage. I didn't run
> #dispatch-conf for another 5 mins after that.

What is the output of:

# portageq config_protect

and

# portageq config_protect_mask

?

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

[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?

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 232 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Alexander Skwar]

· Bo Ørsted Andresen <bo.andresen@zlin.dk>:

> On Monday 16 October 2006 22:26, maxim wexler wrote:
>> localhost heathen # grep CONFIG /etc/make.conf
>> CONFIG_PROTECT="-*"
> 
> WHY did you set that??

He already said, why he did that. He was annoyed by the
list of files that he's got to check after emerges, and
somebody in the forum gave him this "hint".

Well, it's correct - after setting this, he doesn't have
to check any files at all anymore.

Alexander Skwar
-- 
Wait a minute, Marge.  I saw "Mrs. Doubtfire."  This is a man in drag!

                -- Homer Simpson
                   Simpsoncalifragilisticexpiala(annoyed grunt)ocious


-- 
gentoo-user@gentoo.org mailing list

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

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

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

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

On Sunday 15 October 2006 10:34, maxim wexler <blissfix@yahoo.com> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[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

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

On Monday 16 October 2006 15:53, maxim wexler <blissfix@yahoo.com> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 425 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

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

[Justin Patrin]

On 10/14/06, maxim wexler <blissfix@yahoo.com> 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 you expect this and, if you expected it, why didn't you take
steps to back things up.

dispatch-conf normally works just fine. Perhaps you set some incorrect
options in your dispatch-conf conf file, such as auto-updating of all
files. You also should have set up RCS backups of your conf files so
that you can move back.

-- 
Justin Patrin
-- 
gentoo-user@gentoo.org mailing list

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

[Justin Patrin]

On 10/18/06, Justin Patrin <papercrane@gmail.com> wrote:
> On 10/14/06, maxim wexler <blissfix@yahoo.com> 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 you expect this and, if you expected it, why didn't you take
> steps to back things up.
>
> dispatch-conf normally works just fine. Perhaps you set some incorrect
> options in your dispatch-conf conf file, such as auto-updating of all
> files. You also should have set up RCS backups of your conf files so
> that you can move back.
>

nm, looks like the FUD has been dealt with in further replies.

-- 
Justin Patrin
-- 
gentoo-user@gentoo.org mailing list