We need to support partitioning on loopback devices in that case.
> The only reason byteswapping exists is a rather historical one: Linux did
> the wrong thing for "insw/outsw" on big-endian architectures at one point
> (it byteswapped the data).
A small number of other setups people wired the IDE the quick and easy
way and their native format is indeed ass backwards - some M68K disks and
the Tivo are examples of that. Interworking requires byteswapping and the
ability to handle byteswapped partition tables.
Given the ability to see partitions on loop devices all works out I think
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/