On Sat, Sep 11, 2010 at 09:39:37PM -0500, David Young wrote:
> How do I find out my ACPI BIOS release year?
pkgsrc/sysutils/dmidecode.
- Jukka.
On Mon, Sep 06, 2010 at 03:54:27PM +, Jared D. McNeill wrote:
> Log Message:
> Add support for blacklisting ACPI BIOS implementations by year. By default,
> don't use ACPI on BIOS which advertise release years <= 2000. This
> can be changed by setting option ACPI_BLACKLIST_YEAR=0 or by setting
On Tue, Aug 31, 2010 at 09:57:27PM +0200, Joerg Sonnenberger wrote:
> > /*
> > * Alpha ELF uses different (non-standard) definitions of Elf64_Sword
> > * and Elf64_Word.
> > */
> > typedef int64_t Elf64_Sword;
> > #define ELF64_FSZ_SWORD 8
> > typedef uint64_tElf64_Wo
In article <5217ce1f-57c2-40bc-9281-50f90bba0...@zhadum.org.uk>,
Matthias Scheler wrote:
>
>On 6 Sep 2010, at 23:35, Christos Zoulas 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()
christos
On 6 Sep 2010, at 23:35, Christos Zoulas wrote:
> Should we make perror() produce a warning so people will stop using it?
No, as it is not a NetBSD specific API.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
> >> -wrong initialization reported in a followup to PR bin/43336
> >> (looks harmless because it applies to zero-initialized memory, so
> >> LIST_INIT() is a no-op)
> >
> > Does malloc(3) return zero-initialized memory?
>
> Not unless you asked for it with M_ZERO.
Note it's malloc(3) inside !_K
tsugutomo.en...@jp.sony.com said:
> Does malloc(3) return zero-initialized memory?
You are right - seems that I confused the macros.
So it might make sense to pull this up. I'll ask for testers.
best regards
Matthias
