Re: Fwd: Re: modules.autoload

On Wednesday 16 October 2002 07:44 am, Kerin Millar wrote:
> >><snip>
>
> Well, I try :-)
> My favoured method is to use find to determine any newer
> baselayout/config files, then to use the diff command to see
> what the differences are. etc-update is supposed to automate
> the inclusion of customisations from the old to the new, but
> here's the problem: computers aren't human. etc-update has been
> known to trash people's customisations, although I am sure it
> gets more intelligent with each new incarnation. The thing is,
> for most users, 9 times out of 10 you don't really need to
> preserve anything from the old files anyway. Often it's just
> things like your USE flags from make.conf and the odd tweak
> here and there.
>
> If the manual method sounds like too much hard work, then by
> all means continue to use the etc-update method. Just ensure
> you make regular backups of you /etc directory. There's a nice
> shell script in the "Documentation, Tips & Tricks" section of
> the Gentoo Forums which does just that (think the subject is
> "keep your /etc from getting toasted").

I haven't experienced any problems with etc-update myself. But,
I've only started using it in the last two weeks. I keep my gentoo
systems very 'fresh', so I'm certain I've been using only the latest
version.

I will incorporate the shell script you mentioned as I always like
to include backups and safety features :)

I've found etc-update useful as it's been an easy way for me to
see where enhancements have been added to Gentoo.

Best regards!
-- 
People whom think M$ software is mediocre don't know the half of it.