Find the answer to your Linux question:
Results 1 to 5 of 5
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    GENTOO.. "etc-update" versus Manual update opinion

    Just fishing here..+ acouple of questions.

    ************************************************** ****

    "My Goal" in this posting:
    Is to learn how-to correctly manually update the files without the use of "ect-update".

    How to do this correctly, I'm unsure of so far.

    Being new I want to take the time to manually diff each file to see what the differences are of
    which I know how to do,(using "diff" at its most basic level that-is) and is good practice for me
    to get used to using "diff" as well as looking at the contents of these files to be more familiar
    with my Gentoo surroundings/environment. I figure, if I know how to manually update the needed
    files, VERSUS using "etc-update", that this will make my Gentoo experience that much more
    fullfilling/enlightened, so to say..

    Please correct my thinking where you see fit. :P

    So with that being said, this is where I'm at so far:

    ************************************************** *****

    I ran,
    bash-2.05b# emerge -uD system
    After this runs for a few hours, (dialup,:P,), I get back:

    * Regenerating GNU info directory index...
    * Processed 56 info files.
    * IMPORTANT: 25 config files in /etc need updating.
    * Type emerge --help config to learn how to update config files.

    After looking at the info in "emerge --help config" I run,
    bash-2.05b# find /etc -iname '._cfg????_*'

    ************************************************** ********

    Now, this is where my questions come in.

    Again, "My Goal", to manually update the files without the use of "ect-update".

    How to do this correctly I'm unsure of and want confirmation of, please.

    ************************************************** ********

    At this point, I'm just manually "diff"ing each file, one by one. (Any suggestions on using "diff"
    and "cp" in a better way than I'm using will be helpful & appreciated as well.)

    ************************************************** ********

    For example:
    bash-2.05b# diff make.globals ._cfg0000_make.globals
    < # $Header: /home/cvsroot/gentoo-src/portage/cnf/make.globals,v 1.48 2003/07/17 04:46:52 carpaski
    Exp $
    > # $Header: /home/cvsroot/gentoo-src/portage/cnf/make.globals,v 1.49 2003/08/21 01:01:26 carpaski
    Exp $
    < FEATURES="sandbox ccache"
    > FEATURES="sandbox ccache autoaddcvs"

    ************************************************** ******

    At this point, (1)I know logically that I've never messed with this file and, (2)its obvious that
    I want the new file in replace of the old one. Not only is it obvious but I was told so:

    * NOTICE: PLEASE *REPLACE* your make.globals. All user changes to variables
    * in make.globals should be placed in make.conf. DO NOT MODIFY make.globals.

    * Feature additions are noted in help and make.conf descriptions. Update
    * them using 'etc-update' please. Maintaining current configs for portage
    * and other system packages is fairly important for the continued health
    * of your system.

    So would the correct thing to do in this (Specific) case, being inside the /etc directory, too:

    bash-2.05b# cp ._cfg0000_make.globals make.globals
    bash-2.05b# rm ._cfg0000_make.globals
    Now my other question is:

    Assuming that this were the only file that had differences (hypothectically speaking), WHAT, if
    anything do I need to do to next to let Gentoo know I've made the changes manually instead of
    using "etc-update"? Again, correct my thinking of this where you see fit...if it fits.. :P


  2. #2
    Oh boy..

    I feel pretty silly now.

    Does everything that I needed to do manually. The solution was starring me right in the face is all. With a little nap I'm all good to go now.


  3. #3
    Just Joined!
    Join Date
    Jun 2003
    Helsinki, Finland
    If you like use vi or vim, you could try
    # vimdiff /etc/._cfg0000_make.conf /etc/make.conf
    Which will bring up both files, with the difference highlighted. Of course, you'll need to be able to use vim to edit the files. You can probably do the same thing with emacs. I've heard that it's almost as powerful as vi.

  4. $spacer_open
  5. #4
    Linux Guru
    Join Date
    Oct 2001
    Täby, Sweden
    Emacs is "almost" as powerful as vi? Watch your language! =)

  6. #5

    To funny Dolda..

    Actually Caffeine, "etc-udpate" does exactly that.. Vimdiff...,

    I just didn't realize it till I tried it out. Thats why I said I felt silly.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts