@Fabby Terminology: "asexual" has two meanings. In biology it means what you think it means: something which does not posess a sex. For example, bacteria reproduce asexually. But when applied to humans [sentient beings] it is a sexual orientation, like heterosexual and homosexual. It means neither homosexual nor heterosexual.
You can fit "homo", "hetero", "bi", and "a" in a 2×2 matrix in the obvious way.
So it isn't a gender identity and has no bearing on what pronouns would be used to refer to you.
To express that you do not identify with any gender, you have to say agender, also known as gender neutral, or neutrois. Which is a subcategory of genderqueer.
And that's where it gets complicated.
But the vast majority of transgender people (and cisgender people for that matter) aren't so complicated as to get into the realm of genderqueerness. They're just regular male or female.
Actually, once a binary (= either male or female, not genderqueer) transgender person has finished transitioning, it becomes really quite simple. For most purposes you (and they!!!) can even just forget about the fact that they're trans.
I'll leave it at that. It's a rich topic with lots of twists but hardly related to Unix & Linux.
Update (Dec. 17): We're going to push the transition date to Feb. 1, 2016 to allow for more time to collect community feedback on the proposed terms, which you can read all about below.
CC-BY-SA is an ideal license for a crowdsourced knowledge base. We’ve benefited immensely from it, our com...
@FaheemMitha ...and that's why we can't run modern operating systems on computers with 128KiB of RAM which used to run contemporary OSes just fine thank you very much.
@derobert Sure, such bugs in grub should be fixed and the fixes deployed, but I consider that if someone has console access to a server (even serial console access), they already have control.
@Celada Servers, yes. But Linux isn't just for servers.
E.g., the application I have is that our community pool has a laptop used for checking passes, etc. It's locked down as much as is reasonably possible—BIOS password set, configured not to boot from anything but HDD, grub password set, strong passwords in Linux.
It has to be used by the guards who are, err, semi-trusted. They can't be allowed to (for example) install random stuff on the machine, or change the settings and use it to browse Facebook.
It's also in a pool house where, honestly, physical security is not the best. E.g., would not be too hard to distract a guard and get 5 minutes with the machine.
(Facebook will be more of a problem this coming year, when we get an unfortunately expensive cell data plan for it.)
I've got to imagine anyone deploying Linux for any sort of publicly-accessible machine (e.g., in a library, school computer lab, etc.) has similarly locked things down.
Hey,Thanks for the help, my final goal is to understand the software flow between the SATA Host(HBA) and a SATA device driver(SATA Hard Disk).To understand the flow I need to go through the SATA Host and Device driver code .I know AHCI can be used as a HBA in linux kernel which is at "linux-xlnx-xilinx_v2.6.30/drivers/ata/" but I am not sure about the SATA device driver.Can you point out which device driver code should I look in kernel tree to understand the device code flow or Can you point me somewhere I can get the sample SATA device driver code to undestand Host and Device communication? — Hemant3 hours ago