Messages in this thread | | | Date | Thu, 17 Jul 2003 02:15:15 -0700 | From | Joel Becker <> | Subject | Re: [PATCH] print_dev_t for 2.6.0-test1-mm |
| |
On Thu, Jul 17, 2003 at 10:47:08AM +0200, Roman Zippel wrote: > It's not just NFS2, with NFS3 and later it also depends on how many and > which bits the server keeps. They usually use the standard major/minor/ > makedev macros, so you only get back what the platform supports. > Splitting dev_t in major/minor numbers can be lots of fun...
Well, exporting devices over NFS is always tricky, because if the server isn't an identical OS, you can't even trust the numbers. As you point out, you get the platform's idea of a device number, and that doesn't map to your local OS. It is no different than today. You have to make sure that the server's filesystem stores device numbers valid for the client if the client wants to use those device nodes.
Joel
--
"In the room the women come and go Talking of Michaelangelo."
Joel Becker Senior Member of Technical Staff Oracle Corporation E-mail: joel.becker@oracle.com Phone: (650) 506-8127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |