|From:||"Simon 'corecode' Schubert" <corecode@xxxxxxxxxxxx>|
|Date:||Tue, 27 Feb 2007 02:03:05 +0100|
The alternative is to set a specific endianess for the filesystem in
stone, just like the 'network byte order' concept locked in a particular byte ordering for packets. People today STILL hate the
fact that they have to translate certain protocols to network byte
order even when the machines on both ends use the same byte order,
but one that happens to not be 'network' byte order.
read data if (need_conversion) convert_data use data if (need_conversion) convert_data_back write data
read data convert_data use data convert_data_back write_data
We're not making that same mistake, hence the filesystem will be speced for endian neutrality even if the code isn't written to support it right off the bat.
-- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Description: OpenPGP digital signature