From owner-freebsd-questions  Tue Apr 15 20:45:41 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA03699
          for questions-outgoing; Tue, 15 Apr 1997 20:45:41 -0700 (PDT)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03692
          for <questions@freebsd.org>; Tue, 15 Apr 1997 20:45:38 -0700 (PDT)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id UAA14411; Tue, 15 Apr 1997 20:45:29 -0700 (PDT)
Date: Tue, 15 Apr 1997 20:45:29 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Mike Tancsa <mike@sentex.net>
cc: questions@freebsd.org
Subject: Re: 2.2.1 RELEASE and X... is the utmp stuff still an issue?
In-Reply-To: <3.0.1.32.19970415123445.00b07880@sentex.net>
Message-ID: <Pine.BSF.3.96.970415204452.13247A-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 15 Apr 1997, Mike Tancsa wrote:

> >For some reason the X included with 2.2.1 (which I think is symlinked from
> >ftp.freebsd.org:/pub/XFree86) has the utmp patches, which plays hell with
> >non-current systems. 
> >
> >Someone needs to rebuild X again on a 2.2 system and not on a -CURRENT
> >system.
> >
> 
> I just upgraded to 2.2.1 RELEASE and was wondering if the above mentioned
> issue is still a problem?

I think it's been fixed.  The symlink was moved and it hasn't been causing
problems on the systems we installed it on.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major