How to display CLI output on another machine

Les hlhowell at pacbell.net
Mon Jan 8 07:57:33 UTC 2007


On Sun, 2007-01-07 at 23:20 +0100, Nigel Henry wrote:
> On Sunday 07 January 2007 23:29, Aaron Konstam wrote:
> > On Sun, 2007-01-07 at 19:40 +0100, Nigel Henry wrote:
> > > On Sunday 07 January 2007 18:24, Manuel Arostegui Ramirez wrote:
> > > > El Domingo, 7 de Enero de 2007 18:09, Nigel Henry escribió:
> > > > > I can ssh into my other machine ok, and can edit files, etc, which is
> > > > > no problem.
> > > > >
> > > > > What I would like to do is to have access to what is currently
> > > > > displayed on the CLI (Konsole) on machine B. As an example. I run
> > > > > apt-get update, then apt-get dist-upgrade on machine B, which runs to
> > > > > completion. The history is still on the CLI.  I now need to post the
> > > > > history from the CLI on machine B to a mailing list. The email client
> > > > > (Kmail) is on machine A.
> > > > >
> > > > > Is there a way to display the history that's on the CLI on machine B
> > > > > on machine A, so that I can simply highlight the text, then paste it
> > > > > to Kmails composer on machine A?
> > > > >
> > > > > Both machines are next to one another, but at the moment I have to
> > > > > save the CLI history on machine B as a text file, ssh into B from A,
> > > > > and use nano to display the text file, before I can highlight, and
> > > > > paste the text into Kmails composer.
> > > > >
> > > > > Nigel.
> > > >
> > > > Well, If I didn't misunderstand your scenario, what if you use, for
> > > > instace
> > > >
> > > > >> in order to redirect output of machine B and then copy it to machine
> > > > >> A?
> > > >
> > > > By scp or whatever.
> > > > That's to say, using your example above: 'apt-get update && apt-get
> > > > dist-upgrade >> foo.txt'
> > >
> > > I may be wrong, but don't think that will work. I have already run
> > > apt-get update, and apt-get dist-upgrade, and the upgrade has completed.
> > > All I have left on the CLI is the output from what has been done. If I
> > > run those commands again I will have an output showing no further
> > > updates.
> > >
> > > > Maybe you could use 'screen -RD', which will allow you to see what
> > > > happened on machine B even if you're not in front of the computer of
> > > > machine A, or just machine A is not turned on.
> > > > I supposed you to know how screen works, don't you?
> > >
> > > No I'm not familiar with screen.
> > >
> > > Perhaps I didn't explain the problem too well. I need to be able to view
> > > what is currently displayed on the CLI (KDE's Konsole) on machine B. I am
> > > working on machine A, and need to view KDE's Konsole on machine B.
> > >
> > > Nigel.
> >
> > One of us is confused. If you ssh from B to A then what you do on A is
> > seen in the terminal window on B. I assume the reason you just don't
> > copy it from  the terminal window on B into your kmail mail message is
> > you can't see all of the putput at the same time. Another option is the
> > script command which will allow everything that happens in the terminal
> > window be captured in a file called typescript.
> >
> > --
> > Aaron Konstam <akonstam at sbcglobal.net>
> 
> Ok. I'll try this again. I have text on machine B's Konsole, and wish to view 
> this text from machine A so that I can use some of it as a reply to a mailing 
> list. If I downloaded email to machine B, as well as machine A this wouldn't 
> be a problem, but I don't, and all the email arrives on machine A.
> 
> This would appear to be a lost cause, and wish I hadn't started this thread, 
> but that's the way it goes I suppose.
> 
> Nigel.
Hi, Nigel,
If the data is still on the screen (has not scrolled off), then you
might be able to do a screen capture to retrieve it as a graphic.  You
might read up on how to accomplish that.  I thik, though, if you have
somehow logged into the users machine, set the display to his, run
snapshot and save it as a file, then return to your display you may be
able to pull it off.  It would probably have to be a snapshot of the
entire screen, and would no doubt require editing, but it would all be
there.

Regards,
Les H




More information about the fedora-list mailing list