From owner-freebsd-current Thu Sep 10 04:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10781 for freebsd-current-outgoing; Thu, 10 Sep 1998 04:19:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10776 for ; Thu, 10 Sep 1998 04:19:21 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id VAA13616; Thu, 10 Sep 1998 21:19:19 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma013607; Thu, 10 Sep 98 21:19:11 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id VAA02750 for ; Thu, 10 Sep 1998 21:19:10 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id VAA16417 for ; Thu, 10 Sep 1998 21:19:10 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id VAA11892; Thu, 10 Sep 1998 21:19:08 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199809101119.VAA11892@nymph.dtir.qld.gov.au> To: freebsd-current@FreeBSD.ORG cc: syssgm@dtir.qld.gov.au Subject: utmp/wtmp and libutil Date: Thu, 10 Sep 1998 21:19:08 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may recall all the fuss back in January 1997 about the change to UT_NAMESIZE in 3.0 that broke compatibility with 2.2 binaries. Indeed, I immediately changed it back in my copy, and more or less forgot about it. Then came the proposed revamp of libutil to remove the need for applications to be so intimate with system file formats. This seems to have ground to a halt in June 1997. I have one possible weekend of coding to beat the 3.0 beta deadline. Should I even attempt to resurrect David Nugent's (apparently) abandoned code changes? The code defines new xutmp and xwtmp structures, and manipulates them in interesting ways, but does not document the overall direction. My goal is to allow old binaries to play with utmp and wtmp without breaking the rest of the system. I'm not sure where he was headed. If anyone collaborated with him on the design (I've been unable to reach him), or has any funky ideas on how binaries with different definitions of struct utmp can coexist, I'd like to hear from you. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message