Actually, I think there's nothing "natural" about bcopy or memcopy order. Those are just API, they're mostly equivalent. Switching all the time is annoying. I tend to like that memcpy works like strlcpy, miod prefers bcopy. Who cares ? those are totally equivalent APIs (in the documentation)
Of course, the fact that gcc is WAYS TOO CHUMMY with memcpy and hasn't learnt how to fuck bcopy yet means that bcopy is... less surprising, especially in kernel land.
