> But the reason we did this was to reduce the amount of damage badly
> written signal handlers could do. Not to encourage people to actually
> use the *printf(3) family of functions in signal handlers.
Well... we had to use something..
On Fri, May 24, 2013 at 11:35:15AM +0300, Alexey Suslikov wrote:
> Hi tech@.
>
> Are uvideo(4), bktr(4) and similar also MP safe or they somewhat different
> in terms of a technique used to make audio MP safe?
They are mp safe since they use the global kernel_lock; It's used
for everything, inclu
> From: Theo de Raadt
> Date: Thu, 23 May 2013 21:38:57 -0600
>
> > On Thu, May 23, 2013 at 05:05:45PM -0400, Ted Unangst wrote:
> > > I was looking at mandoc and noticed it has too many strlcats (a common
> > > affliction affecting quite a few programs.) It's faster and simpler to
> > > use snpr
On Thu, May 23, 2013 at 09:38:57PM -0600, Theo de Raadt wrote:
> > On Thu, May 23, 2013 at 05:05:45PM -0400, Ted Unangst wrote:
> > > I was looking at mandoc and noticed it has too many strlcats (a common
> > > affliction affecting quite a few programs.) It's faster and simpler to
> > > use snprint
Hi tech@.
Are uvideo(4), bktr(4) and similar also MP safe or they somewhat different
in terms of a technique used to make audio MP safe?
Cheers,
Alexey
hi! mark johnston (markj@freebsd) just made the following change to
rtsold(8), related to the description of -a. it looks correct, but i'd
appreciate some verification.
my diff is a slightly tweaked version of mark's - i'll forward it, if we
end up committing it.
thanks,
jmc
Index: rtsold.8
