In the guide it instructs to do a sync of the portage tree, the only problem with this is the massive amounts of information that appears on the screen the first time this is done. My recomended alternative is perhaps a statement telling users to use "emerge --sync --quiet" This reduced this step's time on my machine from close to 20 minutes to less then 5, since most of this step is waiting for the data to scroll past on the framebuffer. Reproducible: Always Steps to Reproduce: 1. 2. 3.
i think this greatly depends on the type of terminal used to display the material. framebuffer terminals or xterms with lots of eyecandy will bork, but others take much less time. to my knowlege, the same thing could be accomplished by switching to another terminal (ctr-alt-f2,3,4,5,6) so the info doesn't have to pass through the frame buffer, but i am not 100% sure there this being said, perhaps its worth a mention, as (last time i checked, which was about 7 months ago) the gentoo install CDs use a framebuffer
Serial console at 9600 takes a while too. Mind you, on the systems I deal with, most of the wait is the system itself updating its cache, not the download itself.
Well By default the gentoo install uses a framebuffer, and both of my rather fast machines take forever on the first emerge sync, this could hopefully speed it up for some people who are allready in the process of a long gentoo install ;)
So what you're saying is to include a little bit in the docs: <note> If you wish to speed up this process, you may use <c>emerge --sync --quiet</c> instead. This will tell <c>emerge</c> to run the synchronisation process quietly, and may make a significant difference in speed when working on slower machines. </note>
Yep, just to let people know they dont have to watch it all if they dont want, and it would speed the process up
Created attachment 59082 [details] codenote added updated the relevant handbook part "/doc/en/handbook/hb-install-system.xml" with: <codenote>If you wish to speed up this process, you may use <c>emerge --sync --quiet</c> instead. This will tell <c>emerge</c> to run the synchronisation process quietly, and may make a significant difference in speed when working on slower machines. </codenote> I have no cvs access. If a relevant dev approves please add my attached update. Thanks
Stuart, I have the same issue...the cache takes longer than the download itself :) Micheal, <codenote> is deprecated, we no longer use it in the docs. I guess the docdev who puts it up (if approved) will take care of it though. Thought I'd mention it FYI :)
Created attachment 59084 [details] corrected hb-install-system.xml attachment. Sorry, I forgot we switched to the <comment> tag. Attached a correction.
how about: """ # <i>emerge --sync</i> <comment> If you wish to speed up this process, you can tell <c>emerge</c> to run the synchronisation process quietly, and may make a significant difference in speed when working on slower machines/terminals. In this case, use: </comment> # <i>emerge --sync --quiet</i> """ -> added 'terminals' along with 'machines' -> made the code more GuideXML-like
(In reply to comment #8) > Created an attachment (id=59084) [edit] > corrected hb-install-system.xml attachment. > > Sorry, I forgot we switched to the <comment> tag. Attached a correction. Curtis, sometimes it's more useful to attach a patch for the document, instead of the entire xml file ;-)
(In reply to comment #9) > how about: > """ > # <i>emerge --sync</i> > <comment> > If you wish to speed up this process, you can tell <c>emerge</c> to run the > synchronisation process quietly, and may make a significant difference in speed > when working on slower machines/terminals. In this case, use: > </comment> > # <i>emerge --sync --quiet</i> > """ Looks perfect Alin, minimal change and gets the point across :)
(In reply to comment #9) > how about: > """ > # <i>emerge --sync</i> > <comment> > If you wish to speed up this process, you can tell <c>emerge</c> to run the > synchronisation process quietly, and may make a significant difference in speed > when working on slower machines/terminals. In this case, use: Minor change for better grammar/sentences : If you wish to speed up this process, you can ask <c>emerge</c> to run the synchronisation process quietly. Doing so may have a significant increase in speed when working on slower machines/terminals.
Created attachment 59089 [details, diff] latest patch Here is the patch. The <c> tags inside <pre> were eliminated, as they are not allowed.
You should also describe what "quitely" means :-P - point out that the slow part is printing a lot of info to the terminal...
Created attachment 59129 [details, diff] take 2 here it is. hope this will point out the info about adding --quiet to emerge --sync.
Alin, so is it "syncro" or "synchro"? I'm not sure if comment in the code example is a Good Place(tm) to put such warnings/tips. And finally, I'd omit the parenthesis from last sentence and connect it with semicolon (";"), I like it better :-).
Can be made shorter :)
Fixed. Thanks for the suggestion.
