> Date: Wed, 14 Nov 2012 22:30:48 -0500
> From: Brad Smith
>
> On Fri, Sep 28, 2012 at 12:07:31AM -0400, Brad Smith wrote:
> > On Fri, Sep 28, 2012 at 04:06:32AM +0200, Mark Kettenis wrote:
> > > > Date: Mon, 24 Sep 2012 03:49:41 -0400
> > > > From: Brad Smith
> > > >
> > > > I've always wonder
On Fri, Sep 28, 2012 at 12:07:31AM -0400, Brad Smith wrote:
> On Fri, Sep 28, 2012 at 04:06:32AM +0200, Mark Kettenis wrote:
> > > Date: Mon, 24 Sep 2012 03:49:41 -0400
> > > From: Brad Smith
> > >
> > > I've always wondered why this workaround was not removed once MSI
> > > support was added. Th
splimp -> splnet
OK ?
Index: altq.9
===
RCS file: /cvs/src/share/man/man9/altq.9,v
retrieving revision 1.14
diff -u -p -r1.14 altq.9
--- altq.9 31 May 2007 19:20:00 - 1.14
+++ altq.9 14 Nov 2012 19:11:03 -
@@ -2
On Wed, Nov 14, 2012 at 03:39:48PM +0100, Reyk Floeter wrote:
> pf currently only supports the round-robin and least-states methods
> when using dynamic address pools like tables or interface pools. The
> following diff adds support for source-hash and random with dynamic
> pools. source-hash can
Hi!
pf currently only supports the round-robin and least-states methods
when using dynamic address pools like tables or interface pools. The
following diff adds support for source-hash and random with dynamic
pools. source-hash can be used in some cases as an alternative to
"sticky-address" to g
On Tue, 13 Nov 2012 11:02:00 +0100, Alexander Hall wrote:
> Since I switched to SMTPD I noticed a few cron emails being marked as
> spam by spamassassin, largely caused by the From: and To: headers not
> containing a domain part.
Sendmail will add the domain if the always_add_domain feature is
en
On Tue, Nov 13, 2012 at 03:14:40PM -0500, sven falempin wrote:
> 2012/11/9 Kenneth R Westerback
>
> > Those of you following -current or running very recent snaps may have
> > noticed a lot of changes to dhclient in the last couple of weeks.
> >
> > Aside from some major clean up, these changes r
> Date: Tue, 13 Nov 2012 21:02:24 -0500
> From: James Turner
>
> I was actually able to add support myself with the following diff.
Great!
Committed an improved diff that also adds the "other" 6030 variant.
> Index: if_iwn.c
> ===
Anybody around with the (currently non-working) Intel WiFi Link 1030
wireless hardware that can test the following diff? You'll need an
up-to-date firmware pckage and a bleeding edge -current tree.
Cheers,
Mark
Index: if_iwn.c
===
