On Mon, Mar 03, 2025 at 05:13:35PM -0800, Paul Goyette wrote:
> But I've always been confused with what appears to be a plethora of
> moving parts to make sound work. It doesn't seem to be as easy as
> just-plug-in-the-speakers!
On machines with just one audio interface (and a well working driver
On 3/3/2025 18:34, Ted Spradley wrote:
Just give it a try. Good luck.
I also agree.
I run NetBSD 10 on a Pine64 RockPro64 (among other devices) with a USB
speaker and it has been solid. That device I specifically stream audio.
-Joel
On Mon, 3 Mar 2025 17:13:35 -0800 (PST)
Paul Goyette wrote:
> a plethora of
> moving parts to make sound work.
audio(4) is a good place to start, it will point you toward the other
man pages and devices you need to be aware of, but it's not as
complicated as it looks. The only thing that caused
The mpg123 package might be useful to you. I’ve used it to play mp3 files
solely thru the terminal.
>
> On Mar 3, 2025, at 8:13 PM, Paul Goyette wrote:
>
> I've never bothered to use NetBSD to play music, but I'd like to get
> the windoze laptop off my desk!
>
> But I've always been confuse
I've never bothered to use NetBSD to play music, but I'd like to get
the windoze laptop off my desk!
But I've always been confused with what appears to be a plethora of
moving parts to make sound work. It doesn't seem to be as easy as
just-plug-in-the-speakers! Vague memories seem to hint at th
mlel...@serpens.de (Michael van Elst) writes:
>mlel...@serpens.de (Michael van Elst) writes:
>>the direct struct doesn't use the d_namlen field, it's always zero.
>Correction, it apparently uses a 16bit d_namlen field and d_type is missing.
>This is the OLDDIRFMT.
Eh voila:
% ls -l /mnt
total
mlel...@serpens.de (Michael van Elst) writes:
>the direct struct doesn't use the d_namlen field, it's always zero.
Correction, it apparently uses a 16bit d_namlen field and d_type is missing.
This is the OLDDIRFMT.
mlel...@serpens.de (Michael van Elst) writes:
>So far:
>it's a 2048 byte superblock (we insist on having 8192 bytes).
>the old_flags field isn't known and we try to intrpret it.
>the sblockloc field isn't known and validation fails.
>the maxsymlinklen field isn't known and the 'value' triggers a
net...@precedence.co.uk (Stephen Borrill) writes:
>Interestingly, Linux reads it just fine (copied from another forum):
>a680v1: Unix Fast File system [v1] (little-endian), last mounted on /,
>last written at Thu Nov 21 13:09:49 2002, clean flag 0, number of blocks
>40960, number of data blocks
On Fri, 28 Feb 2025, Michael van Elst wrote:
net...@precedence.co.uk (Stephen Borrill) writes:
dumpfs recognises it as a FFSv1 filesystem (mildly surprised as wasn't
sure of partitioning, if any).
file system: /dev/vnd0a
format FFSv1
endian little-endian
magic 11954 timeThu
10 matches
Mail list logo
