From owner-freebsd-questions@freebsd.org  Fri May 13 19:18:12 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 799D2B3A0BC
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Fri, 13 May 2016 19:18:12 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5CB501500
 for <freebsd-questions@freebsd.org>; Fri, 13 May 2016 19:18:11 +0000 (UTC)
 (envelope-from merlyn@geeks.org)
Received: from mail.geeks.org (localhost [127.0.0.1])
 by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 5560C110236
 for <freebsd-questions@freebsd.org>; Fri, 13 May 2016 14:10:39 -0500 (CDT)
Received: by mail.geeks.org (Postfix, from userid 1003)
 id 3468A110235; Fri, 13 May 2016 14:10:39 -0500 (CDT)
Date: Fri, 13 May 2016 14:10:39 -0500
From: Doug McIntyre <merlyn@geeks.org>
To: FreeBSD Questions <freebsd-questions@freebsd.org>
Subject: Re: Custom kernel for NAT and PF ?
Message-ID: <20160513191039.GA38861@geeks.org>
References: <CAFy1QJ=VwETucFLJYm4eQH4hPtvgW5Mv789c9nYuJ3D3V7dYdA@mail.gmail.com>
 <1463013024.29740.2.camel@michaeleichorn.com>
 <CALfReyd1+XAURbaHbMJsVHRq2Aqtb2eES-N1sRWTrkHCQP6jdg@mail.gmail.com>
 <CAE63ME76vuEAjcsvRMXMdTY8eyYtPLgO7zQXc-hq7ZJ+r2ayvA@mail.gmail.com>
 <5735596F.50302@ShaneWare.Biz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5735596F.50302@ShaneWare.Biz>
User-Agent: Mutt/1.6.0 (2016-04-01)
X-Virus-Scanned: ClamAV using ClamSMTP
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 19:18:12 -0000

On Fri, May 13, 2016 at 02:04:55PM +0930, Shane Ambler wrote:
>> Now you only need to compile a custom kernel if you want to use newer
> features.
...

Unfortunately, I have two situations where that isn't true.

For the first, I wish that just loading the PPS drivers enabled the
PPS_SYNC option in the kernel, but it doesn't seem to. (if there is
a way to enable 'option PPS_SYNC' with a generic kernel I'd like to know,
but my experients didn't lead me that working. I still have to compile
the kernel for my GPS connected NTP servers. Which makes me wonder why
the PPS drivers are a kernel loadable object. 

The second is that the username handling is still limited to 32-bytes,
which really cramps my logins for 'billyjoebobuser@somesillydomainname.com'
so I have to build a custom kernel with longer usernames patched for
the systems that need to deal with system logins like that.