On Tue, Mar 21, 2006 at 11:15:21AM +0100, viq wrote:
> On Tuesday 21 March 2006 11:02, Joachim Schipper wrote:
> > On Tue, Mar 21, 2006 at 02:47:41AM +0100, viq wrote:
> > > On Tuesday 21 March 2006 02:27, Steve Shockley wrote:
> > > > viq wrote:
> > > > > I'm playing with OpenBSD in a virtual machine (VMWare) on my linux
> > > > > box. The box has two CPUs, so every once in a while I try to set the
> > > > > machine to have two as well - which every singe time ends in a crash
> > > > > after some time. Any hints as to how I could get the trace etc out of
> > > > > it short of typing it all on the 'real' computer? Or is that error
> > > > > unlikely to be a sign of a real problem?
> > > >
> > > > I know using GSX for Windows you can save all the serial output to a
> > > > file (on the host), then set the guest's console to output to serial.
> > > > Of course that doesn't help you type "trace" and "ps", but maybe
> > > > there's a way to automate that output.
> > >
> > > There is an option for the serial line to be connected to a named
> > > pipe. Now if I only knew what to do with that information ;)
> >
> > 'mkfifo fifo && tee log < fifo & cat > fifo' would be the easiest
> > solution, if the above was not written in jest.
>
> No, I really don't know yet what to do with serial lines. Yes, I have
> a lot to learn, I know ;) So all suggestions are welcome, thank you.
I don't know much about serial lines, either, but the above will work
for filesystem-based pipes, which are mightily useful.
Joachim
