15 Jun 2026, 10:39 by chet.ramey@case.edu:
> Nothing of the sort. Pipes and files are separate objects.
>
>> I'm struggling to figure out how asynchronous IO works,
>>
>
> Do you need to understand it to understand how pipes work?
>
>> There are lots of nuances of how a file descriptor is opened, filled,
>> emptied and closed that I'm discovering from error messages of "broken
>> pipes". The documentation doesn't seem to help.
>>
>
> Pipes are a basic Unix concept, so maybe an intro to Unix/Linux guide would
> help here?
>
>> The bash manual doesn't need a lengthy explanation on asynchronous IO. It
>> would be sufficient to explain the differences named pipes have from stream
>> redirectors, generally explain how named pipes can be read and written, and
>> what users should search for in their foundational research.
>>
>
> The bash manual isn't the place for an introduction to concepts like pipes;
> it assumes you know what they are and tells you how you can use them. That
> belongs in an introductory book, of which there are hundreds.
>
> Chet
>
It's likely that I'm too stupid to manipulate pipes after 20+ years of using
Linux and spending hours with an AI bot trying to get them to work. I'm not
being sarcastic. If I haven't figured it out by now, I probably won't in the
next 20. As often as I'm told that an undergraduate degree in computer science
or engineering is unnecessary to use Linux or bash, there is obviously
foundational concepts which you identified that I still lack.
I'm less concerned about what I benefit by writing gnu.org as I'm trying to
help gnu.org help everyone. Perhaps the mailing list needs an intelligence test
before writing to filter people like me out. Nevertheless, I'll let this
request die.