Date: Fri, 22 Aug 97 15:29:32 +0100 From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr> To: dima@tejblum.dnttm.rssi.ru Cc: root@mantar.slip.netcom.com, freebsd-current@freebsd.org Subject: Re: Can't start X with new kernel Message-ID: <9708221429.AA07572@cabri.obs-besancon.fr> In-Reply-To: <199708220931.NAA00692@tejblum.dnttm.rssi.ru> (message from Dmitrij Tejblum on Fri, 22 Aug 1997 13:31:56 %2B0400)
next in thread | previous in thread | raw e-mail | index | archive | help
This seems to be caused by the last change in ufs_vnops.c:
revision 1.53
date: 1997/08/21 01:42:47; author: dyson; state: Exp; lines: +7 -1
Performance improvment to minimize delayed write output of files
that have been deleted.
Submitted by: Peter M. Chen <pmchen@eecs.umich.edu>
I reverted to rev. 1.52 and X starts again.
>>>>> Dmitrij Tejblum writes:
>> I can not start up an xsession with current kernel.
>> xdm starts alright but when i login the login screen resets itself after
>> a few seconds.if i disable xdm and run xinit no problem.I'm using the
>> newest release of XFree86 (3.3.1). A kernel built Monday of this week
>> works fine.
>>
>> -r-xr-xr-x 1 root wheel 1358774 Aug 21 19:55 kernel-from-monday O.K.
>> -r-xr-xr-x 1 root wheel 1354328 Aug 21 22:40 kernel-from-today N.G.
>>
>> i get these errors in .xsession-errors:
>>
>> Xlib: connection to ":0.0" refused by server^M
>> Xlib: Client is not authorized to connect to Server^M
> [...]
> Same here. It is because xdm failed to write file .Xauthority. It always have
> zero length with new kernel.
> I am still using XFree86 3.2.
> Dima
Jean-Marc
_____________________________________________________________________________
Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex
PGP Key: finger jmz@cabri.obs-besancon.fr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9708221429.AA07572>