From: Will Day <willday@rom.oit.gatech.edu>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: zsh under BeOS?
Date: Mon, 26 Jul 1999 03:04:27 -0400 [thread overview]
Message-ID: <19990726030426.A18265@rom.oit.gatech.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1537 bytes --]
Has anyone been able to get zsh working under BeOS? I can't seem to get
anything done on the system without my favorite shell around. :)
So far, with version 3.1.6-test3, I have it kinda-working. It's worth
nothing that it compiled with a lot less effort than did 3.0.5, or 3.1.5
(which kept failing sed's during configure). Had to #undef JOB_CONTROL,
#include <sys/socket.h>, and work around the lack of link() in
lockhistfile(). After that, I seem to be stuck in waitforpid() and
waitjob().
I made a little progress after noting that kill(pid, 0), does not return
ESRCH for a non-existant process, but returns EINVAL instead, so I worked
around that in waitforpid() and killjb().
Now, I'm stuck. When running a command from the prompt, it loops in
waitjob(), as jn->stat is never cleared. From tracing through with bdb,
it looks almost like handler() isn't getting called on SIGCHLD, and I
can't seem to find an explanation for that.
I haven't quite run out of things to try, but I figured I'd ask around
for hints or in case anyone had already done the work, before I really
started digging into it.
--
Will Day <PGP mail preferred> OIT / O&E / Technical Support
willday@rom.oit.gatech.edu Georgia Tech, Atlanta 30332-0715
-> Opinions expressed are mine alone and do not reflect OIT policy <-
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
Benjamin Franklin, Pennsylvania Assembly, Nov. 11, 1755
[-- Attachment #2: Type: application/pgp-signature, Size: 344 bytes --]
reply other threads:[~1999-07-26 7:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990726030426.A18265@rom.oit.gatech.edu \
--to=willday@rom.oit.gatech.edu \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).