From owner-freebsd-doc  Thu Apr 23 15:50:03 1998
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA12849
          for freebsd-doc-outgoing; Thu, 23 Apr 1998 15:50:03 -0700 (PDT)
          (envelope-from owner-freebsd-doc@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA12839;
          Thu, 23 Apr 1998 15:50:01 -0700 (PDT)
          (envelope-from gnats)
Date: Thu, 23 Apr 1998 15:50:01 -0700 (PDT)
Message-Id: <199804232250.PAA12839@hub.freebsd.org>
To: freebsd-doc
Cc: 
From: Tim Vanderhoek <ac199@hwcn.org>
Subject: Re: conf/3590
Reply-To: Tim Vanderhoek <ac199@hwcn.org>
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR conf/3590; it has been noted by GNATS.

From: Tim Vanderhoek <ac199@hwcn.org>
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: Re: conf/3590
Date: Thu, 23 Apr 1998 18:47:00 -0400 (EDT)

 Okay, perhaps I should have read through the whole thread first,
 but the following seems to be the concensus reached...
 
 
 --
  tIM...HOEk
 OPTIMIZATION: the process of using many one-letter variables names
               hoping that the resultant code will run faster.
 
 ---------- Forwarded message ----------
 Date: Wed, 22 Apr 1998 11:29:38 -0500 (EST)
 From: John Fieber <jfieber@indiana.edu>
 To: Mike Smith <mike@smith.net.au>
 Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>,
     Dag-Erling Coidan Smørgrav <dag-erli@ifi.uio.no>,
     Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>,
     "Alok K. Dhir" <adhir@worldbank.org>, current@FreeBSD.ORG
 Subject: Re: Disappearing keyboard 
 
 On Wed, 22 Apr 1998, Mike Smith wrote:
 
 > > > This is evil and should never have been suggested in the docs.
 > > 
 > > Why?  It's always worked just great for me and I've had it like
 > > this for over 3 years.
 > 
 > "Because if your X server crashes it just loops forever"
 > 
 > At least that's the pathetic excuse that I've heard most often.
 
 And not even correct.  If *xdm* immediately crashes, it will loop
 a couple times but then init notices something is amiss and stops
 trying to start it.
 
 If your *X server* crashes, xdm restarts it. Whether you started
 xdm int /etc/ttys or by some other mechanism has nothing to do
 with it with this behavior. 
 
 
 
 -john
 
 
 To Unsubscribe: send mail to majordomo@FreeBSD.org
 with "unsubscribe freebsd-current" in the body of the message
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message