From owner-freebsd-hackers Thu Jun 19 10:08:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06167 for hackers-outgoing; Thu, 19 Jun 1997 10:08:31 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06160 for ; Thu, 19 Jun 1997 10:08:28 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id MAA26166 for ; Thu, 19 Jun 1997 12:07:50 -0500 (CDT) Date: Thu, 19 Jun 1997 12:07:48 -0500 (CDT) From: Craig Johnston To: hackers@freebsd.org Subject: sad UT_HOSTSIZE of 16 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If we're even going to store the remote hostname in utmp, in this day and age of ridiculously long hostnames, shouldn't we go for a bit more than 16 chars? 16 chars is not enough for a human to be able to figure out many entire addresses these days, much less a program. For example: ip119.harvey.la. It'd be nice to know that we were dealing with ip119.harvey.la.pub-ip. psi.net, no? 16 for display purposes might be just fine, but it'd be nice to have 255 chars or so of remote hostname stored in the utmp file. Sure, we can find out more other ways, but I think it should be in utmp. Of course the question is: what breaks? -Craig