GENTOO.. "etc-update" versus Manual update opinions..
Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"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:
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,
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.)
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:
Quote:
* 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.
End Quote:
So would the correct thing to do in this (Specific) case, being inside the /etc directory, too:
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
Rather than using cp and rm, use mv. It'll do the exact same thing only in one command (eg mv /etc/._cfg0000_make.globals /etc/make.globals).
make.globals should never need user editing but to answer your question I'll using make.conf (where the user options go instead). In short, what I do here is open up the old make.conf, select everything but the lines I've added (which in my case are a set of custom USE variables, a VIDEO_CARDS line, an ALSA_DRIVER line and a custom mirror list), delete those lines, cat the remnants of make.conf onto the end of the new file (cat make.conf >> ._cfg0000_make.conf) open up the new one, restoring the added lines to their right locations, uncommenting the default entries I use but don't change, save the new file and then mv it to become the new make.conf. Variations on this procedure can be used for any of the files that usually get user edited (such as rc.conf, although all I really do there is change the time fromat from UTC to Local and enable the windowskeys keymap). For the files that I've never edited personally, I just mv the new over the old.
Also when you're updating it's best to do emerge -uD world not system.
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.
The reason that I did "emerge -uD system" was because I just installed off the CD and got internet access for he first time. This was kindof explained in the "Portage Users Guide" at the very beginning, so I was just following the directions.
Anyways, thanks for your suggestions. I still learned something from your post that I didn't know before. Appreciate it.. :P
Thanks,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.