On Sunday 30 June 2002 7:16 pm, Kolbe Kegel wrote:
it sounds like he's a little confused about what ctrl-z does... he
says he uses it to send the process to the background, but that's not
what ctrl-z does at all. ctrl-z just *stops* the process. while stopped,
it can't do anything.
Yes,
I did the following:
* launch a terminal window
* from it, launch another (ie. $ aterm)
* the new terminal windows works ok, the old one is waiting for the
other to finish in order to resume
* in the first window I press ctrl-z and send the second to background
* the second window freezes and
On Sunday 30 June 2002 10:52 am, Ciprian Popovici wrote:
I did the following:
* launch a terminal window
* from it, launch another (ie. $ aterm)
* the new terminal windows works ok, the old one is waiting for the
other to finish in order to resume
* in the first window I press ctrl-z and
On Sun, Jun 30, 2002 at 12:52:13PM +0300, Ciprian Popovici wrote:
I did the following:
* launch a terminal window
* from it, launch another (ie. $ aterm)
* the new terminal windows works ok, the old one is waiting for the
other to finish in order to resume
* in the first window I press
On 30-Jun-2002 xOr wrote:
On Sun, Jun 30, 2002 at 12:52:13PM +0300, Ciprian Popovici wrote:
I did the following:
* launch a terminal window
* from it, launch another (ie. $ aterm)
* the new terminal windows works ok, the old one is waiting for the
other to finish in order to resume
* in
it sounds like he's a little confused about what ctrl-z does... he says
he uses it to send the process to the background, but that's not what
ctrl-z does at all. ctrl-z just *stops* the process. while stopped, it
can't do anything. it can't respond to input, create output, or receive
events
On Sunday 30 June 2002 7:16 pm, Kolbe Kegel wrote:
it sounds like he's a little confused about what ctrl-z does... he says
he uses it to send the process to the background, but that's not what
ctrl-z does at all. ctrl-z just *stops* the process. while stopped, it
can't do anything. it can't
