From owner-freebsd-questions Sun Mar 30 12:14:38 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA09879 for questions-outgoing; Sun, 30 Mar 1997 12:14:38 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts14-line16.uoregon.edu [128.223.150.182]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09866 for ; Sun, 30 Mar 1997 12:14:35 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id MAA00318; Sun, 30 Mar 1997 12:13:00 -0800 (PST) Date: Sun, 30 Mar 1997 12:13:00 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Christoph Kukulies cc: hgoldste@bbs.mpcs.com, freebsd-questions@FreeBSD.ORG Subject: Re: 2.2.1-RELEASE and xdm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 28 Mar 1997, Christoph Kukulies wrote: > Howard Goldstein writes: > > In article , doug > > white wrote: > > : > > : Uh, hm. Unfortunately, X is a big mess for now, I wouldn't have > > : recommended playing with it if your exsiting copy was v3.2 and working > > : properly. It's compiled for 3.0-CURRENT and will cause odd problems for > > : you if you aren't running it... > > What actually are the problems with X (F8632) in the 2.2.1R tree ? > (besides that it is a link to 3.2/binaries/FreeBSD-current) > I assume it is compiled after the wtmp/utmp changes and WRT that > 2.2.1R is in sync. So where then is the mess? 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. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major