Followup to: <200304142218.h3EMIKIO017775@turing-police.cc.vt.edu>
By author: Valdis.Kletnieks@vt.edu
In newsgroup: linux.dev.kernel
>
> --==_Exmh_-1812532000P
> Content-Type: text/plain; charset=us-ascii
>
> On Mon, 14 Apr 2003 15:11:10 PDT, Joel Becker said:
>
> > I guess I'm wondering what made you choose "consistency across
> > legacy filesystems" over "consistency across our expanded device space".
>
> I'm going to take a wild stab in the dark and say that being able to
> boot using the /dev on an iso9660 CD is a requirement for most distros?
>
Not really, but it's certainly a nice capability. However, iso9660
(RockRidge, actually) has 64 bits of dev_t space; it's actually split
into two 32-bit entries specified as "high 32 bits" and "low 32 bits."
I'm not positive if Linux expects those to contain major:minor or
0:<16-bit-dev_t>.
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64 - 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/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:19 EST