From owner-freebsd-mobile Tue Dec 16 16:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA13675 for mobile-outgoing; Tue, 16 Dec 1997 16:05:14 -0800 (PST) (envelope-from owner-freebsd-mobile) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA13664 for ; Tue, 16 Dec 1997 16:05:07 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id KAA00308; Wed, 17 Dec 1997 10:29:27 +1030 (CST) Message-Id: <199712162359.KAA00308@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Ken Key cc: mobile@freebsd.org Subject: Re: APM suspend/resume and the "calltodo" timer list. In-reply-to: Your message of "Tue, 16 Dec 1997 16:05:39 CDT." <199712162105.QAA09933@duncan.cs.utk.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Dec 1997 10:29:26 +1030 From: Mike Smith Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi Mike, > > you were the only person to respond, so I assume the list at large doesn't > particularly care (not a surprise). ... or they just agree and thus haven't spoken up. As a general rule, silence either means you're having mail problems, or everyone agrees with you. > I have twice experienced a problem where the X server complains that > select is failing with an EINVAL, but I thought I remember X having this > failure mode before my change. I've put the old kernel back in place > and am going to try to recreate this error in an attempt to prove it's > not the result of my hack. So I'm on hold pending this proof. Ok, please keep us informed. It sounds (so far) as though the positives outweigh the negatives. mike