Date: Fri, 28 Mar 1997 16:26:35 +0100 From: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) To: hgoldste@bbs.mpcs.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: 2.2.1-RELEASE and xdm Message-ID: <Mutt.19970328162635.kuku@gil.physik.rwth-aachen.de> In-Reply-To: <199703271551.KAA07149@bbs.mpcs.com>; from Howard Goldstein on Mar 27, 1997 10:51:44 -0500 References: <199703271551.KAA07149@bbs.mpcs.com> <Pine.BSI.3.95.970326234212.17129B-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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? > > What advice do you have for someone running X 3.1.2? Should I wait > on taking the plunge into 2.2.1R until X is fixed? > -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970328162635.kuku>