ultimate byteorder

Fare Rideau (rideau@ens.fr)
Sat, 6 Dec 1997 18:49:12 +0100 (MET)


Dear Kernel hackers,
I'm sorry for the mess in the mailing list triggered by my patch.
Flaming might have been fun to begin with, but the discussion has far
overpassed the length of all the considered files.

Yes there were "bugs", but now they're fixed:
* long filenames replaced by a include/linux/byteorder subdirectory
* htonl is no more a macro unless we're using optimizing gcc

Patch relative to 2.1.71 available from the following URLs:
http://www.eleves.ens.fr:8080/home/rideau/files/byteorder+ufs-2.1.71.patch.gz
http://www.eleves.ens.fr:8080/home/rideau/files/byteorder+ufs-2.1.71.tgz

Yes, I've been silly implying that (n)etwork-order could be due to Sun,
or naming a file vax_endian.h instead of nuxi_endian.h (vaxen are not even
nuxi-endian; at least recent ones are not). I'll wash my mouth.

All that to say that let's end the byteorder flamewar,
and go back to writing useful code instead.

PS:
* I'm still not subscribed to linux-kernel
* I'm curious what computers are/were nuxi-endian
* I'd prefer ufs-related feedback.

To Linus:
* the above is the same as I sent to you,
plus "fixed" nuxi-endian filename/comments.

Regards, and Happy Kernel Hacking!

== Fare' -=- rideau@ens.fr == CODE, NOT WORDS.