Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-20 Thread Neil Bothwick
On Sat, 20 Nov 2010 00:32:28 -0500, Walter Dnes wrote: > > But harmless. The severe delays you noticed were the result of a > > broken modem/router failing to recognise that IPv6 was not available > > and trying to use it anyway. The usual fix for such a problem is a > > firmware update. > >

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-19 Thread Walter Dnes
On Fri, Nov 19, 2010 at 09:25:18AM +, Neil Bothwick wrote > But harmless. The severe delays you noticed were the result of a > broken modem/router failing to recognise that IPv6 was not available > and trying to use it anyway. The usual fix for such a problem is a > firmware update. It's mo

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-19 Thread Neil Bothwick
On Fri, 19 Nov 2010 01:34:15 -0500, Walter Dnes wrote: > > Blaming the devs for your broken modem/router is rather unfair. If > > you'd known it was unable to handle IPv6 correctly, why didn't you > > set the flag accordingly? > > My ISP didn't support ipv6 at that time. They're now running

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-18 Thread Dale
Walter Dnes wrote: So you see, I did learn from my "experience". I do check for stuff like this now. As an additional safety measure, I also begin the USE variable with "-*". I'm starting to like the way Walter thinks. LOL Dale :-) :-)

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-18 Thread Walter Dnes
On Thu, Nov 18, 2010 at 11:21:33AM +, Neil Bothwick wrote > Blaming the devs for your broken modem/router is rather unfair. If > you'd known it was unable to handle IPv6 correctly, why didn't you > set the flag accordingly? My ISP didn't support ipv6 at that time. They're now running a bet

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-18 Thread Vincent Launchbury
On 2010/11/18 06:25AM, Neil Bothwick wrote: > How does it differ from screen? Is it sufficiently better to relearn > keystrokes etc? The major difference is that you can split the screen into panes, showing multiple ptys at the same time (similar to vim's :[v]sp, layout wise). Besides that, I thin

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-18 Thread Neil Bothwick
On Thu, 18 Nov 2010 04:46:16 +, Stroller wrote: > If you're not using a GUI terminal emulator with a scrollbar, then may > I respectfully suggest you install `tmux` (a replacement for GNU > `screen`) and use it. It takes a little while to get familiar with it, > and with its keybindings and st

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-18 Thread Neil Bothwick
On Wed, 17 Nov 2010 19:20:25 -0500, Walter Dnes wrote: > Because I don't want a repeat of the ipv6 fiasco where I had an almost > non-functional browser, mediaplayer (for internet files), etc, etc. Hardly non-functional - desperately slow maybe but far from non-functional. Blaming the devs for

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-17 Thread Stroller
On 18/11/2010, at 12:20am, Walter Dnes wrote: > On Wed, Nov 17, 2010 at 01:41:45PM +, Stroller wrote > >> It's probably fixed in one of the updates! Why are you posting before >> you checked that!?!? > > It started happening suddenly And yes, I did search bugzilla, > although I admit my se

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-17 Thread Alan McKinnon
Apparently, though unproven, at 02:20 on Thursday 18 November 2010, Walter Dnes did opine thusly: > Because I don't want a repeat of the ipv6 fiasco where I had an almost > non-functional browser, mediaplayer (for internet files), etc, etc. And > I also had to run "emerge --newuse --update wor

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-17 Thread Walter Dnes
On Wed, Nov 17, 2010 at 01:41:45PM +, Stroller wrote > It's probably fixed in one of the updates! Why are you posting before > you checked that!?!? It started happening suddenly And yes, I did search bugzilla, although I admit my searches aren't always perfect. And if "emerge --sync" out

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-17 Thread Stroller
On 17/11/2010, at 12:25am, Walter Dnes wrote: > I have a main machine and a backup machine. The main machine is 64-bit > and the backup is 32-bit, but otherwise very similar setup. I > haven't updated the backup (32-bit machine) for a while, > ... there are > 151 lines of output in file x and

Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-16 Thread Adam Carter
> do so today (115 packages emerge). I normally... > > emerge -pv --deep --update world | less > > ...before updating, to check for booby-traps. Today, the output on the > backup machine blasted to screen, and did not stop until finished. > Meanwhile, the bottom of the screen shows "lines 1-4/4 (

[gentoo-user] One machine sends "emerge" text output to stderr, not stdout

2010-11-16 Thread Walter Dnes
I have a main machine and a backup machine. The main machine is 64-bit and the backup is 32-bit, but otherwise very similar setup. I haven't updated the backup (32-bit machine) for a while, and decided to do so today (115 packages emerge). I normally... emerge -pv --deep --update world | less