Date: Fri, 3 Oct 1997 01:07:37 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au> Cc: freebsd-current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: xlock: caught signal 8 while running galaxy mode. Message-ID: <19971003010737.54157@hydrogen.nike.efn.org> In-Reply-To: <34348712.F0962930@dsto.defence.gov.au>; from Matthew Thyer on Fri, Oct 03, 1997 at 03:18:02PM %2B0930 References: <34348712.F0962930@dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Thyer scribbled this message on Oct 3: > Does anyone else have this problem or can anyone confirm that it > will be solved by a newer incarnation of -CURRENT or a newer > xlockmore ? don't worry.. I have the same problem.. and my processor is a amd k5-90, and I'm pretty sure I saw it on my amd5x86-133... I think it's just a programming error.... of course I'm running it on a 2.2.1-R.. ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971003010737.54157>