* Re: [9front] Re: [9front] Drawterm on Void Linux
@ 2019-02-25 9:38 k0ga
0 siblings, 0 replies; 6+ messages in thread
From: k0ga @ 2019-02-25 9:38 UTC (permalink / raw)
To: 9front
>> would ln -s /dev/dsp1 /dev/dsp be an alternative?
I use "aoss drawterm" and it works out of the box without any
change to the makefile.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [9front] Drawterm on Void Linux @ 2019-02-23 7:14 hiro 2019-02-23 11:58 ` Rodrigo G. López 0 siblings, 1 reply; 6+ messages in thread From: hiro @ 2019-02-23 7:14 UTC (permalink / raw) To: 9front would ln -s /dev/dsp1 /dev/dsp be an alternative? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Drawterm on Void Linux 2019-02-23 7:14 hiro @ 2019-02-23 11:58 ` Rodrigo G. López 2019-02-24 6:26 ` [9front] " hiro 0 siblings, 1 reply; 6+ messages in thread From: Rodrigo G. López @ 2019-02-23 11:58 UTC (permalink / raw) To: 9front 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? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Re: [9front] Drawterm on Void Linux 2019-02-23 11:58 ` Rodrigo G. López @ 2019-02-24 6:26 ` hiro 2019-02-24 19:21 ` Ethan Gardener 0 siblings, 1 reply; 6+ messages in thread From: hiro @ 2019-02-24 6:26 UTC (permalink / raw) To: 9front just suggested it cause i guess void linux is doing it wrong, and that might be the right way to fix it on their side. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Re: [9front] Drawterm on Void Linux 2019-02-24 6:26 ` [9front] " hiro @ 2019-02-24 19:21 ` Ethan Gardener 2019-02-25 1:06 ` hiro 0 siblings, 1 reply; 6+ messages in thread From: Ethan Gardener @ 2019-02-24 19:21 UTC (permalink / raw) To: 9front On Sun, Feb 24, 2019, at 6:27 AM, hiro wrote: > just suggested it cause i guess void linux is doing it wrong, and that > might be the right way to fix it on their side. Years ago, it seemed to be the normal way to select which device node was the CD-ROM, etc. It made some sense to do it that way, using common tools and recording the choice right there in /dev, but I guess it's no good when nodes get renumbered. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Re: [9front] Drawterm on Void Linux 2019-02-24 19:21 ` Ethan Gardener @ 2019-02-25 1:06 ` hiro 2019-02-25 1:13 ` Kurt H Maier 0 siblings, 1 reply; 6+ messages in thread From: hiro @ 2019-02-25 1:06 UTC (permalink / raw) To: 9front why would they get renumbered, there should be only one audio device normally, or? ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Re: [9front] Drawterm on Void Linux 2019-02-25 1:06 ` hiro @ 2019-02-25 1:13 ` Kurt H Maier 2019-03-03 12:22 ` Ethan Gardener 0 siblings, 1 reply; 6+ messages in thread From: Kurt H Maier @ 2019-02-25 1:13 UTC (permalink / raw) To: 9front On Mon, Feb 25, 2019 at 02:06:25AM +0100, hiro wrote: > why would they get renumbered, there should be only one audio device > normally, or? Between on-motherboard soundcards, pci soundcards, hdmi audio, and usb audio, that's not a safe assumption. khm ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9front] Re: [9front] Drawterm on Void Linux 2019-02-25 1:13 ` Kurt H Maier @ 2019-03-03 12:22 ` Ethan Gardener 0 siblings, 0 replies; 6+ messages in thread From: Ethan Gardener @ 2019-03-03 12:22 UTC (permalink / raw) To: 9front On Mon, Feb 25, 2019, at 1:13 AM, Kurt H Maier wrote: > On Mon, Feb 25, 2019 at 02:06:25AM +0100, hiro wrote: > > why would they get renumbered, there should be only one audio device > > normally, or? > > Between on-motherboard soundcards, pci soundcards, hdmi audio, and usb > audio, that's not a safe assumption. Indeed. I currently have my display duplicated between monitor and TV, one or the other of which may be turned off at any one time. Only the TV supports HDMI audio. If you asked me how the computer should number the device corresponding to the HDMI audio, I'd have a hard time deciding. Actually, that's not true. I'd say it shouldn't number it at all, it should present its name, even if it means long and slightly clumsy file names. Here's a more or less worst-case mock-up, it's not terrible: # ls /dev/dspall samsung__2-nvidia_high_definition_audio_ speakers__realtek_high_definition_audio_ The names are lower-cased with parens and spaces repaced by '_'. What to do if there are multiple devices with the same name? Well, then you have to number them, but not before. Huh... Linux can do this for disks, so why not audio? ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-03-03 12:22 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2019-02-25 9:38 [9front] Re: [9front] Drawterm on Void Linux k0ga -- strict thread matches above, loose matches on Subject: below -- 2019-02-23 7:14 hiro 2019-02-23 11:58 ` Rodrigo G. López 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
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).