Date: Tue, 12 Mar 2002 23:00:49 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Garance A Drosihn <drosih@rpi.edu> Cc: Terry Lambert <tlambert2@mindspring.com>, 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: <26044.1015970449@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 12 Mar 2002 16:56:20 EST." <p05101558b8b426ace9ca@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <p05101558b8b426ace9ca@[128.113.24.47]>, Garance A Drosihn writes: >At 12:53 PM -0800 3/12/02, Terry Lambert wrote: >>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 >> > 3 for OpenAFS or ARLA mounted >> > 4 for CODA-mounted [...etc...] >> >>man statfs. >> >>The answer is that it's possible to get the FS mount type >>already. > >This would not be to get the fs mount type, it would be to avoid >duplicate values for st_dev. By using one byte to explicitly >indicate the "pool of numbers" one is picking values for, each >"pool" can pick whatever values it wants for the remaining bits. You know, I find it rather theoretical what to do with the udev_t if(&when) it gets expanded to 64 bits, in particular considering that we appearntly have no active maintenance of AFS in FreeBSD at all... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?26044.1015970449>