nbd goes via the networking layer and deadlocks if looped. The loop driver
is also much faster. Partitioned loop doesnt seem hard.
> nbd devices already do partitioning, I'm fairly certain.
Not when I checked.
> > the Tivo are examples of that. Interworking requires byteswapping and the
> > ability to handle byteswapped partition tables.
> Note that THAT case is an architecture issue, and should probably be
> handled by just making the IDE "insw" macro do the byteswapping natively.
> That way you don't get the current "it can actually corrupt your
> filesystem on SMP" behaviour.
Thats still not enough. If you have the ide insw macro then control
transfers come out wrong. And to maximise the pain - some Amiga controllers
are backwards some are not.
"The use of excessive force has been authorised in the ..."
And then people stick TiVo disks in their PC's in order to prep them for
various TiVo hackery.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/