On Tuesday 04 March 2003 18:57, Oliver Rahm wrote:
> Ben Sparks wrote:
> > Oliver Rahm wrote:
> >> Ben Sparks wrote:
> >>> After I "emerge -u world" everything seems fine, execpt it says
> >>> in bright yellow print "IMPORTANT: 1 config file in /etc needs
> >>> updating. Ok, not a problem right?...not so much. When I ran
> >>> the "find /ect -iname '._cfg???_*' " command it states that
> >>> /etc/._cfg0000_make.conf is the culprit, but gives no
> >>> instructions on how to update it? How do I update this config
> >>> file...or does it really need to be updated. Thanks
> >>
> >> Run 'etc-update' cos /etc might be not the only path which
> >> contains files to be updated.
> >>
> >> How to update: manually ;))
> >> You can use 'etc-update' or do that stuff on your own, which is
> >> the method I prefer (Editing two files with 'vim -d $file 1
> >> $file2' and adjusting the relevant parts or so).
> >>
> >> Regards,
> >> Oliver
> >
> > Thanks for the fast respones guys. I ran etc-update and chose
> > option 1 "delete old file replace with updated one" should I have
> > followed your method Oliver? I'll post back if there are any
> > errors.
>
> This is a question, only you may be able to answer ;)
> When /etc/make.conf contains non-default USE-flags it is always a
> good idea to copy your USE-flags from the 'old' /etc/make.conf to the
> new one. I think this is the case with most of us.
>
> Generally:
> do NOT simply copy the new config files over the new ones. Always
> have a close look at your config-files before overwriting them, cos
> the new ones are almost default-configs. YMMV.
>
> > Ben
>
> Regards
> Oliver
IIRC, XF86Config is another that you might want to back up. Though
Oliver's suggestion is best, in time you will get used to etc-update
and will notice that often the only changes to config files are
frequently header changes i.e. dates version #'s etc. but ALWAYS check
carefully before you overwrite configs look for the ++ and -- signs.
These denote lines that will be added (++) and removed (--)
It's always a good idea to cp the older but working files to
/etc/filename.old before accepting the updated file.
--
Regards, Ernie
100% Microsoft and Intel free
--
[EMAIL PROTECTED] mailing list
