as is probably known ...

So I was on the phone the other day and the subject of my family came up. I have a brother, three years older and three inches taller than I am. (Okay, taller than that, but not that much taller.) And reasonably, my new associate asked me, as lots of folks do in the sort of getting to know that has advanced beyond cocktail chat, what my brother does for a living. Mah no! This question vexes me. I really can't say just what he does.

He's explained it, much like my Georgetown economics professor explained the sigma-algebra of measurable subsets involved in axiomatization of probability theory in stochastic processes. Nod, nod, blink, blink. (An absolute emptiness echoes between my ears.) All I know is he has done whatever he does since 1998. And that his role has to do with kernels of something (data? bytes? maybe corn? bytes of corn?) at Sun Microsystems. So I decided to Google him. The guy's everywhere. He's a technical superhero behind the curtain, speaking what passes word by word for English, but shatters into impressively prohibitive non-English when strung all together. See below for a sampling of his advice on the incomprehensible:

>> Hi,
>> I am curious if it is possible to manually configure the sub mirrors in a \ mirrored jumpstart profile? Normally we are allowed to create a profile and \ assign the mirror such as the following:
>>
>> filesys mirror:d0 c0t0d0s0 c0t1d0s0 1024 /
>>
>> But what if I wanted to assign my own sub mirrors instead of allowing them \ to be selected automatically, because as is probably known the numbers are not \ logical. For example:
>>
>> d10 1 1 /dev/dsk/c0t0d0s0
>> d20 1 1 /dev/dsk/c0t1d0s0
>> d0 -m d10
>
>I'm not aware of a way to do what you're asking from within a
>jumpstart profile. That said, you could use the metarename
>command to change the component names after the fact if they
>aren't to your liking.