Back in my day hashtags had to do with IRC!
You must be new here.
# clearly has to do with the C preprocessor.
Or it indicates that you're logged in as root.
Or that you're about to start a nice game of Tic-Tac-Toe to stop the game of Global Thermonuclear War on the WOPR.
Or all of the above...
just use port 4000 twice. It's all binary.
4000 ain't binary. It's at least base 5.
That's not the only bad math. This is RIDDLED with bat math.
Holy hole in the doughnut, Batman! The Riddler is at it again!
Indeed. It's 1MB of RAM, in fact.
Actually, it's 1Mb.
65536 * 16 bits = 1Mbit = 128KByte
Let me demonstrate the difference with some examples.
First a normal ssh connection to a new host. Without VerifyHostKeyDNS it doesn't matter if your SSHFP records are up-to-date, since they won't be checked.
$ ssh login@example.com
The authenticity of host 'example.com (127.0.0.1)' can't be established.
RSA key fingerprint is 01:23:45:67:89:ab:cd:ef:01:23:45:67:89:ab:cd:ef.
Are you sure you want to continue connecting (yes/no)?
With "VerifyHostKeyDNS yes" and up-to-date SSHFP records, it looks like this instead. Note the extra line of output.
$ ssh -o "VerifyHostKeyDNS yes" login@example.com
The authenticity of host 'example.com (127.0.0.1)' can't be established.
RSA key fingerprint is 01:23:45:67:89:ab:cd:ef:01:23:45:67:89:ab:cd:ef.
Matching host key fingerprint found in DNS.
Are you sure you want to continue connecting (yes/no)?
And this is what you get, if the SSHFP record ain't up-to-date:
$ ssh -o "VerifyHostKeyDNS yes" login@example.com
[Cut long line of @'s. Too many 'junk' characters for
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
[Cut long line of @'s]
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
01:23:45:67:89:ab:cd:ef:01:23:45:67:89:ab:cd:ef.
Please contact your system administrator.
Update the SSHFP RR in DNS with the new host key to get rid of this message.
The authenticity of host 'example.com (127.0.0.1)' can't be established.
RSA key fingerprint is 01:23:45:67:89:ab:cd:ef:01:23:45:67:89:ab:cd:ef.
No matching host key fingerprint found in DNS.
Are you sure you want to continue connecting (yes/no)?
Compare that with the first case where you had absolutely no idea if the fingerprint was correct or not.
I'm not saying, you should just trust all SSHFP records, if you're paranoid. But even if you ain't paranoid, the warning about the mismatching SSHFP record should be enough to make you stop and think instead of just saying yes.
Add the output to your DNS and set VerifyHostKeyDNS to "yes" or "ask" in your ssh_config.
Remember to update your DNS if/when your machine gets a new SSH hostkey.
Actually, GMT includes DST. If you want time without the daylight savings, the only option is UTC (Universal Coordinated Time). Or Unix time, I suppose.
Or TAI
IIRC, the 49.7 days is 2^16 seconds
Nope, far from it... 49.7 days is 2^32 milliseconds.
Buying meat is no harder or easier in pounds or kilograms, you just need to have a sense for how much each is so you can ask for an appropriate amount.
I.e. a "Quarter pounder" or a "Royale with cheese".
but for me comparing 623 millimetres to 1.01m (1010 millimetres) not only makes the comparison easy, but I get an intuitive feel that one is a little over a third larger than the other.
FTFY.
But then I guess the difference here isn't metric vs imperial, it's more that imperial seems to prefer fractions, whereas metric favours a decimal number. You never write 1/2cm, always 0.5cm or 5mm.
FTFY too...
... trying out Ubuntu.
dpkg -L <package>
E.g.
dpkg -L base-files
If you want to do the reverse, you would use dpkg -S <filename>
E.g.
dpkg -S
Sure... You know how we use to have black&white images, then we got 8-bit color palettes, then 24 bits for RGB and later 32 bits for RGBA. This is just the next step...
8 bits for red, 8 bits for green, 8 bits for blue, 8 bits for the alpha channel, 32 bits for gamma correction, 64 bits of DRM and finally 128 bits for the IPv6 address of each pixel.
You know how to tell people who learned C before 1995 (or so) from people who learned it after?
The second category writes "x--" whenever they can, and "--x" only where they have to. The first one writes "--x" whenever they can, and "x--" only where they have to.
I started coding in C around 1990 and as far as I can remember I have almost always used the postfix version, i.e. x--;
Oh, and you can also save a couple chars here if you use puts() instead of printf() - it automatically adds "\n", and it's also faster because it doesn't have to parse the format string. ~
You're right, but for some reason I tend to avoid puts(). Probably because it reminds me too much of gets().
"And remember: Evil will always prevail, because Good is dumb." -- Spaceballs
