From owner-freebsd-current@freebsd.org Sat May 14 04:50:29 2016 Return-Path: Delivered-To: freebsd-current@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 F3758B3A13C for ; Sat, 14 May 2016 04:50:29 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by mx1.freebsd.org (Postfix) with ESMTP id 883A31E65 for ; Sat, 14 May 2016 04:50:28 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp14-2-37-105.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.37.105]) by ipmail06.adl2.internode.on.net with ESMTP; 14 May 2016 14:20:27 +0930 Subject: Issue mentioned on questions list References: <5736A988.5020603@ShaneWare.Biz> To: FreeBSD Current From: Shane Ambler X-Forwarded-Message-Id: <5736A988.5020603@ShaneWare.Biz> Message-ID: <5736AE91.7030108@ShaneWare.Biz> Date: Sat, 14 May 2016 14:20:25 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <5736A988.5020603@ShaneWare.Biz> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 May 2016 04:50:30 -0000 I'm not expecting a reply to this, it was something that come up discussing building custom kernels. Just wondering if someone may be interested in looking at the possibility of changing username length to a sysctl. As the number of people using computers is increasing, it is now common for web sites/mail servers to use your full email as your username, keeping that consistent through all username usage doesn't seem like an unreasonable request. I would expect a username length sysctl value would only be allowed to be set in the loader.conf at boot time, similar to zfs.arc_max -------- Forwarded Message -------- Subject: Re: Custom kernel for NAT and PF ? Date: Sat, 14 May 2016 13:58:56 +0930 From: Shane Ambler To: Doug McIntyre , FreeBSD Questions On 14/05/2016 04:40, Doug McIntyre wrote: > 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. I would report that as a bug and see if it can be improved. > 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. While I don't have that issue, it does sound like an old time limitation that should be considered for rework. Maybe it could be made into an adjustable sysctl. -- FreeBSD - the place to B...Software Developing Shane Ambler