Re: less prints superfluous characters with --no-init

you really ought to use `type', not `which', in case it is a shell function etc.

Re: less prints superfluous characters with --no-init

"Richard Ulmer" wrote: > Hi all, > I find this behaviour unexpected: > > $ printf foo | less --no-init | xxd > : 666f 6f1b 5b41 1b5b 4b foo.[A.[K > > less prints ANSI escape codes for 'cursor up' and 'erase in line' at the > end of my message. Interestingly, when doing

Re: less prints superfluous characters with --no-init

"Richard Ulmer": > I find this behaviour unexpected: > > $ printf foo | less --no-init | xxd > : 666f 6f1b 5b41 1b5b 4b foo.[A.[K > > less prints ANSI escape codes for 'cursor up' and 'erase in line' at the > end of my message. I cannot reproduce this. $ printf foo |

Troubleshooting a spinning fork(2)

Hi. I'm looking for guidance on how to troubleshoot a piece of software which is spinning after calling fork(2). I'm working on making the s2n-tls[1] library build on OpenBSD[2]. One of the unit tests[3] does this: 1. The test framework forks the test (s2n_fork_generation_number_test) 2. The tes

less prints superfluous characters with --no-init

Hi all, I find this behaviour unexpected: $ printf foo | less --no-init | xxd : 666f 6f1b 5b41 1b5b 4b foo.[A.[K less prints ANSI escape codes for 'cursor up' and 'erase in line' at the end of my message. Interestingly, when doing the same within tmux, the result is diff

IPV6 ND and non-local prefixes

Hello misc, I'm starting to play around with IPv6 and rad(8). I've noticed that I can broadcast arbitrary prefixes via "no auto prefix" combined with "prefix ". These get assigned properly via slaac and can be used to forward packets, but if I don't assign an IP in the prefix on the broadcasting i