Re: ksh: tab completion fix (again)

2012-09-26 Thread LEVAI Daniel
On cs, szept 27, 2012 at 01:42:25 +0400, Alexander Polakov wrote: > I sent this diff in 2011 (?) with a bunch of other diffs. > It fixes tab completion for filenames containing special > characters like [], () and so. > > This code affects interactive mode only, and I don't know a way > to do auto

Re: Threads related SIGSEGV in random.c (diff, v2)

2012-09-26 Thread Philip Guenther
On Thu, 27 Sep 2012, Alexey Suslikov wrote: > Removing only local variables part reverts us to previous behavior (i.e. > crashes). My guess is your program is calling srandom(), srandomdev(), initstate() or setstate() as well. Your diff doesn't protect the alteration of state, end_ptr, fptr, a

Re: Intel azalia(4) and MSI

2012-09-26 Thread Stuart Henderson
On 2012/09/24 03:49, Brad Smith wrote: > I've always wondered why this workaround was not removed once MSI > support was added. This was added before we had MSI support to > workaround some Intel azalia(4) being setup by the BIOS as far > as I know to use MSI and thus interrupts on system that were

Incompatibility between 'rthread' and 'uthread' implementation of function 'pthread_stackseg_np'.

2012-09-26 Thread Christian Schulte
The 'rthread' implementation of function 'pthread_stackseq_np' returns stack information including the default guard page in 'stack_t *sinfo' whereas the 'uthread' implementation of that function does not include the default guard page. The following patch makes the 'rthread' implementation behave

hardware VLAN tagging for vr(4)

2012-09-26 Thread Darren Tucker
Hi all. This diff adds hardware 802.1q VLAN tagging support to vr(4) (just tag/untag, it doesn't do anything with the VLAN CAM filters). As far as I know, the capability is only in the VT6105M Rhine III chip which is used, amongst other places, in the pcengines ALIX machines. If anyone has a vr(

Re: make -j and errors

2012-09-26 Thread Ted Unangst
On Thu, Sep 27, 2012 at 00:05, Marc Espie wrote: > You probably don't see the difference, because you run short stuff with > not enough jobs. But for long running stuff, you will sometimes have an > error, and notice it only a few minutes afterwards, 5000 lines of scrollback > later, when they oth

Re: Threads related SIGSEGV in random.c (diff, v2)

2012-09-26 Thread Ted Unangst
On Thu, Sep 27, 2012 at 00:18, Alexey Suslikov wrote: > On Wed, Sep 26, 2012 at 9:51 PM, Ted Unangst wrote: >> On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote: >>> Hi. >>> >>> Any news on that? >> >> Can we do it without the local variables for speed part? I am not >> interested in making th

Re: ksh: tab completion fix (again)

2012-09-26 Thread Aaron Bieber
On Thu, Sep 27, 2012 at 01:42:25AM +0400, Alexander Polakov wrote: > I sent this diff in 2011 (?) with a bunch of other diffs. > It fixes tab completion for filenames containing special > characters like [], () and so. > > This code affects interactive mode only, and I don't know a way > to do aut

Alert! Your email will be blacklisted soon.

2012-09-26 Thread i...@spamcop.com
Dear tech@openbsd.org, We received complaints about spam coming from your network. Spam bots are sending bulk emails, for the security reasons your email will be blacklisted. To avoid blacklisting please check your Sent folder for unknown emails and prove that you are human by entering this code

Re: make -j and errors

2012-09-26 Thread Marc Espie
On Wed, Sep 26, 2012 at 12:41:10PM -0700, Philip Guenther wrote: > On Wed, Sep 26, 2012 at 12:01 PM, Ted Unangst wrote: > > I don't see what we gain by killing jobs. If the scheduler dice had > > come down differently, maybe those jobs would finish. > > > > Here's a downside, albeit maybe a stret

ksh: tab completion fix (again)

2012-09-26 Thread Alexander Polakov
I sent this diff in 2011 (?) with a bunch of other diffs. It fixes tab completion for filenames containing special characters like [], () and so. This code affects interactive mode only, and I don't know a way to do automated testing of this. Suggestions welcome. Index: edit.c ===

Re: Threads related SIGSEGV in random.c (diff, v2)

2012-09-26 Thread Alexey Suslikov
On Wed, Sep 26, 2012 at 9:51 PM, Ted Unangst wrote: > On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote: >> Hi. >> >> Any news on that? > > Can we do it without the local variables for speed part? I am not > interested in making this function faster. > Removing only local variables part rever

Re: make -j and errors

2012-09-26 Thread Philip Guenther
On Wed, Sep 26, 2012 at 12:01 PM, Ted Unangst wrote: > I don't see what we gain by killing jobs. If the scheduler dice had > come down differently, maybe those jobs would finish. > > Here's a downside, albeit maybe a stretch. What if the job doesn't > like being killed? You're changing behavior

gem(4): simplify gem_attach_pci() variant detection code a bit

2012-09-26 Thread Brad Smith
Simplify the gem(4) variant detection code a bit. OK? Index: if_gem_pci.c === RCS file: /home/cvs/src/sys/dev/pci/if_gem_pci.c,v retrieving revision 1.31 diff -u -p -r1.31 if_gem_pci.c --- if_gem_pci.c15 Oct 2009 17:54:56 -0

Re: make -j and errors

2012-09-26 Thread Ted Unangst
On Wed, Sep 26, 2012 at 18:21, Marc Espie wrote: > I've been thinking some more about it. > > POSIX says very little about parallel makes. > > The more I think about it, the more I think gnu-make's approach on this is > stupid: if a job errors out in a fatal way, what do we gain if we keep > goin

Re: Threads related SIGSEGV in random.c (diff, v2)

2012-09-26 Thread Ted Unangst
On Wed, Sep 26, 2012 at 11:18, Alexey Suslikov wrote: > Hi. > > Any news on that? Can we do it without the local variables for speed part? I am not interested in making this function faster.

Re: make -j and errors

2012-09-26 Thread Darrin Chandler
On Wed, Sep 26, 2012 at 06:21:34PM +0200, Marc Espie wrote: > "but what about commands that take a long time to run ?" > Well, make already has a standard mechanism to flag those, that's called > .PRECIOUS What if most everything takes a fairly long time to run? Say, largish C++ sources or whateve

Re: make -j and errors

2012-09-26 Thread Kenneth R Westerback
On Wed, Sep 26, 2012 at 06:21:34PM +0200, Marc Espie wrote: > I've been thinking some more about it. > > POSIX says very little about parallel makes. > > The more I think about it, the more I think gnu-make's approach on this is > stupid: if a job errors out in a fatal way, what do we gain if we

make -j and errors

2012-09-26 Thread Marc Espie
I've been thinking some more about it. POSIX says very little about parallel makes. The more I think about it, the more I think gnu-make's approach on this is stupid: if a job errors out in a fatal way, what do we gain if we keep going ? Especially for high -j values, the quicker we die, the bet

Re: Re-evaluation of smtpd queue entries

2012-09-26 Thread Alexander Hall
On 09/26/12 12:50, Gilles Chehade wrote: On Wed, Sep 26, 2012 at 11:20:31AM +0200, Alexander Hall wrote: Hi! Hi, When setting up your first host or hosts to use smtpd it is inevitable to make some mistakes here and there, which e.g. could cause delivery attempts of an email to the wrong ho

Re: Re-evaluation of smtpd queue entries

2012-09-26 Thread Gilles Chehade
On Wed, Sep 26, 2012 at 11:20:31AM +0200, Alexander Hall wrote: > Hi! > Hi, > When setting up your first host or hosts to use smtpd it is > inevitable to make some mistakes here and there, which e.g. could > cause delivery attempts of an email to the wrong host ("relay via > boo.hoo"). > > Now,

Re: Fw: scaffolding & formwork

2012-09-26 Thread jasonyiu520
Thanks ! we may interest in engineered concrete fromwork www.hengxingpvc.com

Re-evaluation of smtpd queue entries

2012-09-26 Thread Alexander Hall
Hi! When setting up your first host or hosts to use smtpd it is inevitable to make some mistakes here and there, which e.g. could cause delivery attempts of an email to the wrong host ("relay via boo.hoo"). Now, that is obviously not a problem per se, but after fixing the config, I cannot se

Re: Threads related SIGSEGV in random.c (diff, v2)

2012-09-26 Thread Alexey Suslikov
Hi. Any news on that? On Friday, September 21, 2012, Alexey Suslikov wrote: > On Fri, Sep 21, 2012 at 10:36 AM, Alexey Suslikov > > wrote: > > On Wed, Sep 19, 2012 at 10:24 PM, Ted Unangst > > > > wrote: > >> On Wed, Sep 19, 2012 at 18:50, Alexey Suslikov wrote: > >>> On Wednesday, September 19