From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no job control; thank you!
Date: Thu, 18 Jul 2002 16:02:45 +0100 [thread overview]
Message-ID: <2bcd7eda708abfabe83b034959559f58@vitanuova.com> (raw)
> Suppose you start some long-running task but soon realize that it's
> going to run out of disk space. It is very useful to be able to
> temporarily stop the task, rearrange files on the disks to make room,
> then resume the task. Some form of control over an executing process
> is required for such things.
is there any reason one couldn't send a "stop" message to
a rio window just as an "interrupt" message is sent currently?
> Systems like TOPS-10 had a nifty feature whereby one could start
> a job on one terminal, detach the terminal, and log in elsewhere
> and reconnect to the detached job. Not "job control", but in the
> same vein.
there's no essential reason why you couldn't do that under plan 9,
i think. just put a level of indirection above the draw device.
i used to like that feature of "screen" - i could keep several programs
going in one session and remain logged in for days despite
logging in from several different terminal rooms.
acme dump is ok, but has certain lacks.
i think rob's got some ideas on this...
rog.
next reply other threads:[~2002-07-18 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 15:02 rog [this message]
2002-07-18 14:13 ` Sam
2002-07-18 16:19 ` matt
2002-07-18 16:34 ` Lucio De Re
2002-07-18 21:37 ` Chris Hollis-Locke
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 16:18 David Gordon Hogan
2002-07-30 5:11 Russ Cox
2002-07-18 14:53 forsyth
2002-07-18 3:49 rob pike, esq.
2002-07-18 14:21 ` Douglas A. Gwyn
2002-07-18 3:23 Geoff Collyer
2002-07-18 18:30 ` Chet Ramey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2bcd7eda708abfabe83b034959559f58@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).