John Dangler schreef: > I just did an emerge –uDv world… > > > > during the course of the 22 packages (a lot considering I just loaded > this last night), I got some messages saying “please make sure you run … > (I couldn’t read it all since it went by so fast)… I got a couple of > these before it was over. Is there a way to view that output after the > fact? I didn’t see it in either dmesg or any of the /var/log files… > > > > Thanks for the input. >
Idea #1: if you know the name of the file or files that had an einfo message (if you don't know the names, try looking at the end /var/log/emerge.log to see the packages most recently emerged), just open the ebuild in a text editor and read it at your leisure. Idea #2: In whatever console you use, change the size of the scrollback buffer to something that seems ridiculously high (my buffer is 30000 lines). For most emerges -- even in groups of 20 or more-- this should be enough to allow you to scroll back and read any einfo messages that you may have noticed. This won't so much work for emerges that are themselves more than 30000 lines (for instance, if I emerge gcc and then glibc, I won't be able to scroll back and see any messages I missed in the gcc emerge once the glibc emerge is an hour or so in, but usually it's good enough). Idea #3: there is a way (and possibly more than one) to tail out the einfo messages, either to a file, or to the console, but unfortunately I don't remember what they are atm.... Oh, wait, they're listed on the Wiki: http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage I think what you might want is portlog-info, which is in the Informational Utilities section. HTH, Holly -- gentoo-user@gentoo.org mailing list
