From owner-freebsd-hackers Mon Nov 19 17: 2: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 5CDE437B416 for ; Mon, 19 Nov 2001 17:02:01 -0800 (PST) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id fAK120n34024 for hackers@FreeBSD.ORG; Mon, 19 Nov 2001 20:02:00 -0500 (EST) (envelope-from bicknell) Date: Mon, 19 Nov 2001 20:02:00 -0500 From: Leo Bicknell To: hackers@FreeBSD.ORG Subject: Re: Ok, who broke timed? Message-ID: <20011119200200.A33416@ussenterprise.ufp.org> Mail-Followup-To: hackers@FreeBSD.ORG References: <20011120003613.GA29465@student.uu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Mon, Nov 19, 2001 at 04:51:29PM -0800 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 19, 2001 at 04:51:29PM -0800, John Baldwin wrote: > That looks very promising indeed. Hrmm. I should go see if NetBSD has fixed > this. I guess having timeval be different sizes on different archs is a bit of > a pain. :( Perhaps it should use uint32_t? Or perhaps struct tsp should use > its own variant of timeval with uint32_t or some such. Ugh. If timeval is different sizes on different archs then I would recomend the work be done take it to 64 bits, not 32. It fixes a problem in about 30 years. :-) -- Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message