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=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32520 invoked from network); 29 Jun 2020 06:56:25 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 29 Jun 2020 06:56:25 -0000 Received: (qmail 7139 invoked by alias); 29 Jun 2020 06:56:11 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: Sender: zsh-workers@zsh.org X-Seq: 46166 Received: (qmail 1830 invoked by uid 1010); 29 Jun 2020 06:56:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-ed1-f47.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25857. spamassassin: 3.4.4. Clear:RC:0(209.85.208.47):SA:0(-1.8/5.0):. Processed in 3.723857 secs); 29 Jun 2020 06:56:11 -0000 X-Envelope-From: staal1978@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.208.47 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=DAq9UHPQLhLuQ1Gl5X96rak8QrUZeQOWi96sCOW1hM0=; b=bP8XfhLH5JqOS+lRAaRkf9+sjIKmxBryj8d65AS1jIbtZBv7maGaaBottiOJxwqlGQ y+3vuOwmw5/HQpMHeMCJJvl3nQbz9syURuhG2j4Iz+uEfF5aqAFJ+GfJBmjHC0Na7ATw obOpHZjHGc0JNvajo+Zmi++49I2GwwVWqkvXpc65NC6z55HH1FSvRkBx9ek2szlOXymY yKFTksDok4Pj2VE0x9pyoWwYS2e20VBgZlHOiKni3P8kY9sDfp5AIl8rvWfAr3WEb1t5 ID7K89njDEhyReysLjfW+U4qcfBz1M0hd6WXhiai7mQkHB/i94h1cg+jhx8BcMpkEZ3H 6tTQ== X-Gm-Message-State: AOAM532jlLBvxpk44JoRgsUYBLnhKANBOIAxb9O/SwMaOXh5IHwE0P+7 0hUS/4f2xV0J75bp5EsVNew7Kns0O1w= X-Google-Smtp-Source: ABdhPJy4b9bhn3nr1AOR97RKSZUWYMsB7KlU91xwGikeZ9Z88L7LtXIGhjc5xfIXQ3eh2XluqYNy0g== X-Received: by 2002:a50:bb48:: with SMTP id y66mr13135353ede.147.1593413733851; Sun, 28 Jun 2020 23:55:33 -0700 (PDT) Date: Mon, 29 Jun 2020 08:55:31 +0200 From: Jens Staal To: zsh-workers@zsh.org Subject: Re: best way to disable PRIVILEGED? Message-ID: <20200629065531.cebmmaewfpgcymqu@Hugin> References: <20200628121011.22lv3n75sj2j5qhc@Hugin> <20200628143127.11396dc2@tarpaulin.shahaf.local2> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200628143127.11396dc2@tarpaulin.shahaf.local2> >From: Peter Stephenson >>On Sun, 2020-06-28 at 14:10 +0200, Jens Staal wrote: >> the zsh executes but with the error: "zsh: error on TTY read: >> permission denied" >My guess here would be this is something to do with job control / >terminal sessions, which is quite hairy stuff and where different OSes >can definitely go their own way, so not related to UID settings. >However, this is just based on where I've seen problems in the >past, and I don't have any specific advice to offer. Indeed job control might definitely be something. I remember having to do -DNOPROSPECTOFWORK on mksh under Plan9. >To be clear, is this a newly assigned pseudoterminal, or are you >starting zsh within an existing terminal window? I start it within an existing terminal window. Something I am now considering is to try to give some more "meat" to my terminfo (now just stubs from old pdcurses) and I think I might get some inspiration from the vt emulation that exists on Plan9: http://man.cat-v.org/9front/1/vt I might even be able to just import some code for /sys/src/cmd/vt for that library. No idea if that will help me. I sprinkled my libterm.a stubs library with printf for every function but I could not see that one of those functions were called before the crash. I got a tip to try to debug with a tool called "acid" so I guess that is my next step... Executing zsh after activating the vt emulator did also not change the error. >pws