From: "Rodrigo G. López" <rgl@antares-labs.eu>
To: 9front@9front.org
Subject: Re: [9front] Drawterm on Void Linux
Date: Sat, 23 Feb 2019 12:58:10 +0100 [thread overview]
Message-ID: <1c66-5c713580-7-3eadd7c0@253752096> (raw)
In-Reply-To: <CAFSF3XP7dGfmhpJTEyGb-bfwN=8eUyQVN+myAemPCOKCXgxS4A@mail.gmail.com>
I didn't actually try that, I thought about writing a udev rule to change the path but I don't really use it outside of drawterm. I also thought it would need some other flag for open(2), but it seems it gets redirected just fine.
On Saturday, February 23, 2019 08:14 CET, hiro <23hiro@gmail.com> wrote:
> would ln -s /dev/dsp1 /dev/dsp be an alternative?
next prev parent reply other threads:[~2019-02-23 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:27 Rodrigo G. López
2019-02-22 18:55 ` [9front] " mikan
2019-02-23 7:14 ` hiro
2019-02-23 11:58 ` Rodrigo G. López [this message]
2019-02-24 6:26 ` [9front] " hiro
2019-02-24 19:21 ` Ethan Gardener
2019-02-25 1:06 ` hiro
2019-02-25 1:13 ` Kurt H Maier
2019-03-03 12:22 ` Ethan Gardener
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=1c66-5c713580-7-3eadd7c0@253752096 \
--to=rgl@antares-labs.eu \
--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).