From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] print_dev_t for 2.6.0-test1-mm
Date: Thu, 17 Jul 2003 10:46:35 +0000 (UTC) [thread overview]
Message-ID: <bf5uqb$3ei$1@news.cistron.nl> (raw)
In-Reply-To: 20030717122600.A2302@pclin040.win.tue.nl
In article <20030717122600.A2302@pclin040.win.tue.nl>,
Andries Brouwer <aebr@win.tue.nl> wrote:
>There are many filesystems that only have room for 32 bits.
>For example, NFSv2 has "unsigned int rdev".
>So, the kernel must be able to handle 32-bit device numbers.
>
>Now about the encoding - nobody knows. This NFS filesystem was mounted
>from a FreeBSD system. It is encoded 16+8+8 with the middle 8 the major.
>Or, no, it was Solaris or Irix. Encoded 14+18. Etc.
>
>In the case of NFSv2 there is an unknown system on the other side.
So put the translation of 32 bits rdev to 32:32 in the NFS client.
Provide a mount-time option "rdev-encoding=14:18", with symbolic
names for often-used encodings: "rdev-encoding=solaris". Done.
You can do this on the NFS server side as well.. per-client,
even. If anyone still cares for NFSv2, that is.
Same goes for other filesystems, though a dynamic translation will
not be nessecary. But the filesystem driver itself
must convert from native rdev to linux 32:32.
Mike.
next prev parent reply other threads:[~2003-07-17 10:31 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 18:46 [PATCH] print_dev_t for 2.6.0-test1-mm Greg KH
2003-07-16 20:09 ` Andrew Morton
2003-07-16 21:02 ` Greg KH
2003-07-16 21:13 ` Andrew Morton
2003-07-16 21:34 ` Andries Brouwer
2003-07-16 21:39 ` Andrew Morton
2003-07-16 22:10 ` H. Peter Anvin
2003-07-16 22:20 ` Andries Brouwer
2003-07-16 22:21 ` Andrew Morton
2003-07-16 23:44 ` Andries Brouwer
2003-07-16 23:49 ` Andrew Morton
2003-07-17 8:27 ` Joel Becker
2003-07-17 8:47 ` Roman Zippel
2003-07-17 9:15 ` Joel Becker
2003-07-17 9:24 ` Andrew Morton
2003-07-17 10:10 ` Trond Myklebust
2003-07-17 11:46 ` Andries Brouwer
2003-07-17 11:52 ` Alan Cox
2003-07-17 10:26 ` Andries Brouwer
2003-07-17 10:46 ` Miquel van Smoorenburg [this message]
2003-07-17 11:19 ` Andries Brouwer
2003-07-17 11:46 ` Miquel van Smoorenburg
2003-07-17 21:55 ` Andrew Morton
2003-07-17 22:24 ` Andries Brouwer
2003-07-17 22:43 ` Joel Becker
2003-07-17 23:11 ` Andries Brouwer
2003-07-17 23:49 ` Miquel van Smoorenburg
2003-07-18 0:04 ` Andries Brouwer
2003-07-18 0:04 ` Joel Becker
2003-07-18 1:05 ` Andries Brouwer
2003-07-18 8:06 ` Joel Becker
2003-07-17 3:00 ` H. Peter Anvin
[not found] ` <200307170300.UAA24096@cesium.transmeta.com>
2003-07-17 10:43 ` Andries Brouwer
2003-07-20 14:33 ` H. Peter Anvin
2003-07-16 21:36 ` Greg KH
2003-07-16 22:00 ` Andrew Morton
2003-07-16 22:11 ` what's left for 64 bit dev_t Greg KH
2003-07-16 22:19 ` Andrew Morton
2003-07-16 22:48 ` Greg KH
2003-07-17 3:02 ` H. Peter Anvin
2003-07-17 13:59 ` Andries Brouwer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bf5uqb$3ei$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.