From owner-freebsd-alpha Sat Apr 7 20: 9:16 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 698C937B422 for ; Sat, 7 Apr 2001 20:09:13 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f3839DM84110 for ; Sat, 7 Apr 2001 20:09:13 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 213D1380A; Sat, 7 Apr 2001 20:09:13 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: leclercn@videotron.ca Cc: Greg Lehey , freebsd-alpha@FreeBSD.ORG Subject: Re: Vinum status In-Reply-To: <3ACFD185.9010005@videotron.ca> Date: Sat, 07 Apr 2001 20:09:13 -0700 From: Peter Wemm Message-Id: <20010408030913.213D1380A@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tcn wrote: > > I think that if it works on the alpha, it'll work on the ia64. But > > I'm prepared to be proven wrong. > > I don't think that this will be wrong on the ia64. But I beleive that > there will be a lot more mixups like this one when we will go totally > from 32 to 64 bits. ia64 is just like Alpha. int = 32 bits. long and pointers are 64 bit. > > that dev_t was defined one way (the POSIX way, so unchangeable) in > > userland, and another way in the kernel. I still consider this to be > > a bug. > > This is something I don't understand. Why dev_t is something in > kernel and something else in userland? POSIX defines dev_t as a uint32, > shouldn't is be the same in kernel? Like you are saying, this is a bug. POSIX covers userland only. In the kernel dev_t is an opaque "thing" that just happens to be a pointer to a struct. minor(dev_t), major(dev_t) etc appear to work just the same in the kernel as they do as integers in userland. We could go an do a global s/dev_t/kdev_t/ in the kernel in -current, but that just upsets device driver authors because they have two radically different device API's to deal with between -current and RELENG_4. As I recall, Greg was one of those that had complained about this before. IMHO, It would be better to do this at about the point that we change the devsw abstraction. Lets not diverge -current and RELENG_4 just yet when it is easy to work around it in the few places that get broken. > Normand Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message