From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: [9front] Re: drawterm patches
Date: Thu, 27 Jan 2022 16:44:00 -0800 [thread overview]
Message-ID: <CAHwi9bzdH9TOZ71fqZenO1cqXT12pTAS2q=oUprRbKKgyqMRiw@mail.gmail.com> (raw)
In-Reply-To: <CAHwi9byuxj6LE5g2B7C8GBKc8s0f02yUORHDXNm+og17pTBYJg@mail.gmail.com>
it still may need some de-stupifying, but I just can't tell the
difference between bugs, being completely insane, and having an
internet connection and PC flagged to be unable to play DVDs etc
On Thu, Jan 27, 2022 at 4:24 PM Eli Cohen <echoline@gmail.com> wrote:
>
> this one seems to work better, at least on my system
>
> On Thu, Jan 27, 2022 at 4:08 PM Eli Cohen <echoline@gmail.com> wrote:
> >
> > sorry, wait... I don't think the alsa patch is quite right after further testing
> >
> > On Thu, Jan 27, 2022 at 3:59 PM Eli Cohen <echoline@gmail.com> wrote:
> > >
> > > I have attached a couple more drawterm patches that may be of
> > > interest, and a Make.alsa configuration file
> > >
> > > the alsa patches change devaudio.c a little bit to add audiodevread
> > > support which (only) devaudio-alsa.c uses
> > >
> > > the bindflags patch adds -R and -C options to not bind /mnt/term/root
> > > and /mnt/term/cmd respectively for a slightly more secure drawterm
> > > session. I tried to do the same for -I with /mnt/term/net to disallow
> > > using drawterm's networking but then it just wouldn't connect at all
prev parent reply other threads:[~2022-01-28 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:59 [9front] " Eli Cohen
2022-01-28 0:08 ` [9front] " Eli Cohen
2022-01-28 0:24 ` Eli Cohen
2022-01-28 0:44 ` Eli Cohen [this message]
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='CAHwi9bzdH9TOZ71fqZenO1cqXT12pTAS2q=oUprRbKKgyqMRiw@mail.gmail.com' \
--to=echoline@gmail.com \
--cc=9front@9front.org \
/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).