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
