From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262728AbTDUXhc (ORCPT ); Mon, 21 Apr 2003 19:37:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262731AbTDUXhc (ORCPT ); Mon, 21 Apr 2003 19:37:32 -0400 Received: from smtpzilla1.xs4all.nl ([194.109.127.137]:41478 "EHLO smtpzilla1.xs4all.nl") by vger.kernel.org with ESMTP id S262728AbTDUXhb (ORCPT ); Mon, 21 Apr 2003 19:37:31 -0400 Date: Tue, 22 Apr 2003 01:49:24 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: Linus Torvalds cc: Christoph Hellwig , "David S. Miller" , , Subject: Re: [PATCH] new system call mknod64 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, 21 Apr 2003, Linus Torvalds wrote: > > Not anymore for blockdevices. And now that Al's back not anymore soon > > for charater devices, too :) > > Actually, we still do it for both block _and_ character devices. > > Look at "nfs*xdr.c" to see what's up. This is actually a good example to show how problematic the major/minor split is. It depends very much on the nfs server which bits you actually get back and it requires some guessing from the client side which bits it can use. A linux-2.2 server will happilly truncate that value to 16 bit, BSD will give you a 8:24 value back. It's very unlikely that you can use a 64bit dev_t reliably with nfs in the foreseeable future. bye, Roman