Date:Sun, 24 Oct 2010 16:00:46 +0100
From:Matthias Scheler t...@netbsd.org
Message-ID: 20101024150046.ga...@colwyn.zhadum.org.uk
| It doesn't have to be a macro anyway as it used only ones.
Yes, I meant to ask about that, simply written inline would be no problem.
On Mon, Oct 25, 2010 at 12:24:14AM +0700, Robert Elz wrote:
Date:Sun, 24 Oct 2010 16:00:46 +0100
From:Matthias Scheler t...@netbsd.org
Message-ID: 20101024150046.ga...@colwyn.zhadum.org.uk
| It doesn't have to be a macro anyway as it used only ones.
Yes, I
(adding tech-kern because this seems likely to become lengthy; if
following up please drop source-changes-d)
On Sun, Oct 24, 2010 at 11:30:43AM +0100, David Laight wrote:
[mmap mode disabled in cp due to long vnode lock waits]
Because individual write() calls are supposed to be atomic,
On Mon, Sep 13, 2010 at 01:32:38PM +1000, matthew green wrote:
Should we make perror() produce a warning so people will stop using it?
No, as it is not a NetBSD specific API.
Neither is gets()
using perror() doesn't lead to fatal security flaws.
i don't see any good reason to
