Date: Tue, 12 Mar 2002 12:53:20 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Harti Brandt <brandt@fokus.gmd.de>, Robert Watson <rwatson@FreeBSD.ORG>, Julian Elischer <julian@elischer.org>, arch@FreeBSD.ORG Subject: Re: Increasing the size of dev_t and ino_t Message-ID: <3C8E6AC0.A51444E1@mindspring.com> References: <60373.1015917340@critter.freebsd.dk> <p05101551b8b3c1f14df9@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn wrote: > Now for suggestion part #2: > > Once we get to a 64-bit (u)dev_t, we could reserve one byte of > that for the "type of filesystem" (loosely speaking). A value > of 0 for local hard disks > 1 for NFSv2-mounted > 2 for NFSv3-mounted (maybe this isn't necessary...) > 3 for OpenAFS or ARLA mounted > 4 for CODA-mounted > 5 for something appletalk-ish, if we ever did that > 6 for something netware-ish, if we ever did that > > This way, any one system could choose whatever method it wants > to build the rest of the dev_t entry, and it knows it can not > conflict with the dev_t values that would be generated by any > other major filesystem type. man statfs. The answer is that it's possible to get the FS mount type already. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C8E6AC0.A51444E1>