From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 4811 invoked from network); 30 Jan 2023 19:09:48 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 30 Jan 2023 19:09:48 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 419F742641; Tue, 31 Jan 2023 05:09:43 +1000 (AEST) Received: from mail-lf1-f46.google.com (mail-lf1-f46.google.com [209.85.167.46]) by minnie.tuhs.org (Postfix) with ESMTPS id 34A6742640 for ; Tue, 31 Jan 2023 05:09:38 +1000 (AEST) Received: by mail-lf1-f46.google.com with SMTP id j17so20584679lfr.3 for ; Mon, 30 Jan 2023 11:09:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=k3COktc2Maxa+15nqy9ZWe2rjiUIYAOIQqBbOV5hTpQ=; b=Rs8EP9LiOrjNTNUGXevalRD8a0lInEq3+JjCxNDiDRyQmHbylJCaTTQe5OPQWvuwHL zT3stNgnHftGmr6U8E+TYcEgRv8oEGW4ar4dx9tU4jjzrJwQCDORA1cpZcb9DDzH1C8R PTZgXU/5aVGkxg1jrl4APpHTjAZiz72cJkQwjd6Bae5Gsd654eSa3wWiYkr49AH14okJ 0i6Dt5jM+TolKg3DusdS5TgoJITdYWFTpgoEz48HejJLtoUUA4dpw4T1xdyu+EgtcWyC +zHfnDd/0ofMNb/q/K7xQiLW/wbxlWbnTM251wxXOMVyuNfgTJ4h6kHi8+GCgg9xl2P0 9YJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=k3COktc2Maxa+15nqy9ZWe2rjiUIYAOIQqBbOV5hTpQ=; b=NuFzCluO6n2XuujwTj/8WbjSSlAgPY667Or8aAi7lAop02W9AiOs+CP98faQoyztQs EHbgFO1GzhSSe4sq8COvsA0n1yMD+VYwrM8qpzsxkoV9IhYOWR3RCImhrEooc25hnwAe /QZxBjPGcB9YB9OLzMBP89zDB/3Qx5QH9dC/RoxKB7+nhpLEHMetzJ155VZse/08NOgw QhEarle+cWrOZX1VfF03f7s8EdtfYbAT3F7k+mgmFX461Yo4blZ+jNx2a5gRCJnM+vkH Nji0zC+8jjMbx4OS/D1lS/KtzWiuLaL+hminQJkdn1zlN0f3OnjQiRIH3GFtw34PmtPp EsEw== X-Gm-Message-State: AFqh2kqLIDv2/x6VUbG69PUCBXx0a+LImP5jXMGk4VAhm+lyAX4iLPpZ PEm6GZu9nvsMRQGgTP8gsBOLEvxmOH7I69qQ+wA6wnJW X-Google-Smtp-Source: AMrXdXu4gonOLR1nHOWmu9LxeKXBEh7k0pYWovZ/lYF286qAk181R53pgrwdrZlSYSW0Qdpen04yzFLaiCIhJXdnsU0= X-Received: by 2002:a05:6512:2141:b0:4b5:7607:3191 with SMTP id s1-20020a056512214100b004b576073191mr3301109lfr.93.1675105716320; Mon, 30 Jan 2023 11:08:36 -0800 (PST) MIME-Version: 1.0 References: <38B1D4CE-C239-4777-B606-FC641655DBCB@iitbombay.org> <20230130161857.F2F371FB2F@orac.inputplus.co.uk> In-Reply-To: <20230130161857.F2F371FB2F@orac.inputplus.co.uk> From: Dan Cross Date: Mon, 30 Jan 2023 14:07:59 -0500 Message-ID: To: Ralph Corderoy Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Message-ID-Hash: 5KDGC2E2J5J6H2JWHTZCZPC47WLSGMXL X-Message-ID-Hash: 5KDGC2E2J5J6H2JWHTZCZPC47WLSGMXL X-MailFrom: crossd@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: FD 2 List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, Jan 30, 2023 at 11:19 AM Ralph Corderoy wro= te: > > > There was no job control on plan9 and I can't say I ever missed it. > > > > Just yesterday I realized running two =E2=80=9Cmake -j 8=E2=80=9D in pa= rallel was > > making them both go real slow so I stopped one of them with ^Z and > > continued it once the other make finished. This use case can=E2=80=99t= be > > handled with more windows. > > If I lacked job control in that situation, I'd either SIGSTOP one of the > two with kill(1) for a later SIGCONT or renice it to hardly get a look > in until its peer had finished. (The TTY's susp character for job > control is SIGTSTP.) I think that Bakul's point was that there wasn't an analogue for SIGTSTP in plan 9. You _could_ drop a `stop` into a process's /proc/$pid/note, which was the Unix equivalent of sending `SIGSTOP` (and I was a bit wrong earlier; that was handled by the proc driver, not the process). I don't believe there was a binding for that in the window system, though. It's funny, as I thought about it a bit more, the existence of the window system model sort of proves that there's nothing intrinsic about how it worked that would preclude one writing, basically, a terminal-driver in user space. No one was ever motivated to do so, but I don't see why one couldn't have implemented job control as a userspace primitive building on top of the existing proc/note machinery. - Dan C.