Re: cannot disable output processing in pseudo-terminal (between openpty(3) parent and child)

2023-07-31 Thread pouya+lists . netbsd
Valery Ushakov writes: > > The fact that TERM affects this is a sign that you likely have > something like a shell with line-editing interfering as RVP suggested > in another message. This indeed seems to have been the case. Issuing stty raw ; cat file as a single command instead of two in the

Re: cannot disable output processing in pseudo-terminal (between openpty(3) parent and child)

2023-07-31 Thread pouya+lists . netbsd
RVP writes: > On Sun, 30 Jul 2023, pouya+lists.net...@nohup.io wrote: > You'll have to turn off the NL -> CRNL output processing the kernel > does on your behalf (after all, this is still a "terminal" we're > talking about and not a simple pipe). Don't set the ONLCR bit in > the output-modes of the

Re: zfs pool behavior - is it ever freed?

2023-07-31 Thread Greg Troxel
I took your patch and have been adding comments to help me understand things, as well as debug logging. I also switched how it works, to have an ifdef for netbsd approch vs others, to make it less confusing -- but it amounts to the same thing. (I understand your intent was to touch as few lines a

Re: cannot disable output processing in pseudo-terminal (between openpty(3) parent and child)

2023-07-31 Thread Valery Ushakov
On Mon, Jul 31, 2023 at 06:41:13 +, pouya+lists.net...@nohup.io wrote: > One difference I see with your code is that you don't seem to change > the controlling terminal in the child with setsid(2) and a TIOCSCTTY > ioctl(2). I only need to feed some input to the terminal emulation code, so th

Re: cannot disable output processing in pseudo-terminal (between openpty(3) parent and child)

2023-07-31 Thread pouya+lists . netbsd
Valery Ushakov writes: > FWIW, I have a simple program I've been using to debug kernel vt100 > emulator, and: > > $ ./wsemul -- printf '\n' > $ hexdump -C wsemul.raw > 0d 0a |..| > 0002 > $ ./wsemul -- sh -c 'stty raw; printf "\n";' > $ hex