Date: Sun, 30 Mar 1997 12:13:00 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> Cc: hgoldste@bbs.mpcs.com, freebsd-questions@FreeBSD.ORG Subject: Re: 2.2.1-RELEASE and xdm Message-ID: <Pine.BSI.3.94.970330121136.242K-100000@localhost> In-Reply-To: <Mutt.19970328162635.kuku@gil.physik.rwth-aachen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Mar 1997, Christoph Kukulies wrote: > Howard Goldstein writes: > > In article <Pine.BSI.3.95.970326234212.17129B-100000@resnet.uoregon.edu>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.970330121136.242K-100000>