The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software - to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
Note that there are 2 Version of the GPL - V2 and v3 that are used at the moment.
Check the Full Paper in the related Files Section. 

 As I searched for a domain name - I didn't find anything suitable for stargate (Server system). Everything was used already, but the abbreviation for the Solar System (solsys) did still exist. 

 Of course everyone knows that 1 Kilobyte equals to 1.024 bytes. Well - this is wrong !

A kibibit (a contraction of kilo binary digit) is a unit of information or computer storage, abbreviated Kibit, or sometimes Kib. (Note that the abbreviation is capitalized, while kbit is not.)

1 kibibit = 2¹⁰ bits = 1,024 bits
1 kibibit = 2⁷ bytes = 128 bytes

The kibibit is closely related to the kilobit, which can either be a synonym for kibibit, or refer to 103 bits = 1,000 bits, depending on context.
The National Institute of Science and Technologies notes that

it is important to recognize that the new prefixes for binary multiples are not part of the International System of Units (SI), the modern metric system.

It should also be noted that they are not in general use among professional software and electrical engineers, who generally use decimal prefixes when referring to binary quantities.

In short - we need to make the difference between the Metric Prefix system - this one handles the comon Kilo naming convention, and the Binary prefix systems - which is the real definition for binary formats as found on harddisks.

The following table shows you the comon namings and sizes

BTW - same also applies to the Byte fraction

By looking at these 2 previous tables - you might ask yourself - but what is the difference. Well - really only if you handle Bytes or Bits. This is the main differenciator.
So - what does this mean for us ? Check for yourself with some examples:

 This has mainly to do with the number of memory address lanes available to the system, and how the OS uses and addresses the memory itself. But first off - if you have 4GiBytes of Memory in your system, chances are you will see only 3.25GiBytes available.

This is mainly due to the fact, that all PCI/PCI-eX Devices allocate some memory for mapped IO Calls / DMA accesses, and to be able to access this reserved memory in a linear way, you need to be able to talk to these in 32 bit mode - thus the 4GiBytes limit. Note that the missing memory has been mapped by the physical extension cards starting from the upper 4GiByte limit downwards. Means the more memory a card allocates and the more extension cards you have, the more memory will be missing.

Even on 64Bit CPU/OS's combinations you may see this beheavior. Many extension cards still use 32Bit registers. These can only address the first 4GiByte linearly, thus allocate memory from 4GiByte on downwards - recreating the problems due to backwards compatibility.