As you know the world's biggest branding revolution starts January 2012.
What direct implications does it have for your organization? What do your
teams need to know now and what must they be prepared for in advance to face
the tidal wave?
This White Paper provides an in-depth overview and can
Hi tech,
I have a simple diff for ksh(1) which takes
care to not read past the end of the static
buffer 'holdbuf' where the length of 'pat'
is greater than the buffer.
Does anyone think this is worthwhile? If not,
should we remove the XXX comment altogether?
- Michael
Index: vi.c
Hi,
this diff was already suggested by matthew@ some time ago. It renders
clang++ usable with gcc's C++ include files, see:
http://marc.info/?l=openbsd-techm=130229126704450w=2
I don't expect any fallout, but just to be sure, can this go through a
bulk build on affected platforms (gcc4)?
Janjaap van Velthooven janj...@stack.nl wrote:
For some obscure reason this gave successes. After splitting up
alpha/rtld_machine.c into 2 or mor parts, any combination where the
1st and the 3rd function (_dl_md_reloc and _dl_md_reloc_got) were
not in the same source allowed the split-up
Christian Weisgerber wrote and mailed:
Janjaap van Velthooven janj...@stack.nl wrote:
For some obscure reason this gave successes. After splitting up
alpha/rtld_machine.c into 2 or mor parts, any combination where the
1st and the 3rd function (_dl_md_reloc and _dl_md_reloc_got) were
not
Sure, looks good, I'll use your version.
On Wed, Nov 16, 2011 at 02:00:51PM +0100, Stefan Sperling wrote:
On Tue, Nov 15, 2011 at 11:09:08PM +, Nicholas Marriott wrote:
Hi
libedit miscalculates the amount of space needed for constructing it's
wchar_t version of argv, causing it to
On Thu, Nov 17, 2011 at 09:48:36PM +0800, Michael W. Bombardieri wrote:
Hi tech,
I have a simple diff for ksh(1) which takes
care to not read past the end of the static
buffer 'holdbuf' where the length of 'pat'
is greater than the buffer.
holdbuf is zero-terminated, so strcmp() won't go
Moving this to tech@
Hi,
I was studying the scheduler code after watching tedu's talk, I'd like
to expose this statistics to userland so that I can try playing with
cache affinity in the future:
gimli:src: sysctl kern.schedstat
On 2011 Nov 17 (Thu) at 21:18:24 -0200 (-0200), Christiano F. Haesbaert wrote:
Moving this to tech@
Hi,
I was studying the scheduler code after watching tedu's talk, I'd like
to expose this statistics to userland so that I can try playing with
cache affinity in the future:
gimli:src:
On Fri, Nov 18, 2011, Thordur Bjornsson wrote:
On 2011 Nov 17 (Thu) at 21:18:24 -0200 (-0200), Christiano F. Haesbaert
wrote:
Moving this to tech@
Hi,
I was studying the scheduler code after watching tedu's talk, I'd like
to expose this statistics to userland so that I can try playing with
On 17 November 2011 23:39, Ted Unangst t...@tedunangst.com wrote:
On Fri, Nov 18, 2011, Thordur Bjornsson wrote:
On 2011 Nov 17 (Thu) at 21:18:24 -0200 (-0200), Christiano F. Haesbaert
wrote:
Moving this to tech@
Hi,
I was studying the scheduler code after watching tedu's talk, I'd like
On 18 November 2011 00:59, Christiano F. Haesbaert
haesba...@haesbaert.org wrote:
On 17 November 2011 23:39, Ted Unangst t...@tedunangst.com wrote:
On Fri, Nov 18, 2011, Thordur Bjornsson wrote:
On 2011 Nov 17 (Thu) at 21:18:24 -0200 (-0200), Christiano F. Haesbaert
wrote:
Moving this to
On Fri, Nov 18, 2011, Christiano F. Haesbaert wrote:
What is the line between sysctl vs globals ?
Checking again, it makes sense having the sysctl IMHO.
We have something very similar in kern.forkstat, kern.nchstats, and
the protocol stats.
I think those stats are useful for a sysadmin to
13 matches
Mail list logo
