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.
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.
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().
The ASCII representations of UIDs has a Hamming distance of 6, while the more logical binary representation of the UIDs has a Hamming distance of 5.
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally).
Let me put my tinfoil hat on for a moment... Beatings aren't necessary, the US gov't can simply use the NSAKEY to decrypt anything encrypted using Microsoft libraries...
This story is about an Ubuntu laptop. I doubt any Microsoft libraries were used.
An interjection similar to “Yay!”, as in: “w00t!!! I just got a raise!” Often used for small victories the speaker dies not expect to be of special interest to anyone else. Some claim this is a bastardization of “root”, the highest level of access to a system (particularly UNIX), originated by script kiddies as a 133tspeak equivalent of “root”, and said as an exclamation upon gaining root access. Others claim it originated in the Everquest multiplayer game as an abbreviation of “wonderful loot”. Still other claim it on originated on IRC as the “Ewok victory cheer”] Adj. w00table has the sense of “cool” or “nifty”. This is one of the few leet-speak coinages to have crossed over into non-ironic use among hackers.
I don't have an Ubuntu-box (or other "sudo"-using box) at hand, so can't test it myself, but doesn't the shell try to open/dev/sda before trying to execute sudo? In other words: Before you got root permission.
I.e. the same reason sort foo >foo gives you an empty file.
Maybe something like cat/dev/urandom | sudo tee/dev/sda >/dev/null would work. I think, I used something like that last time I had to work around the shell opening std{in,out,err} before executing commands.
Poor guy. I guess sooner or later he's going to have to learn how to manage his memory and understand how the underlying physical hardware works. That must be a real toughie for anyone who learned to "program" in the Java/C# world.
Yeah, clearly PHK doesn't knows anything about memory allocation. (Except for the malloc library he wrote for FreeBSD...)
Maybe he should RTFM.
I don't have a FreeBSD system at hand, but I wouldn't be surprised if the malloc page was written by PHK.
Does that mean each system component needs a name that's unique in the whole universe?
May I suggest UUIDs as names?
"So after installing 5229a8ab-8a08-4fe1-9645-37332d8abf09, you start 15286b6e-e44d-4601-a10a-92d7b9920958 and 2d9c0817-8156-4982-8533-dd1fc466661e, then open the 'File' menu in 014e0080-a5f2-4f12-9d20-7aaea21dd8a2 and click 'Open'..."
We can even throw away the version numbers. Just generate a new UUID when you change your program.
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. ... how to locate all the files that were installed by a package
dpkg -L <package>
E.g.
dpkg -L base-files
If you want to do the reverse, you would use dpkg -S <filename> /etc/debian_version
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().
It's up and running
The problem earlier was their nameservers.
(Sorry for repeating myself from one of the submissions that wasn't accepted, but...)
#include <stdio.h>
#include <stdlib.h>
volatile int dmr=1;
int main()
{
dmr--;
printf(":-(\n");
exit(EXIT_SUCCESS);
}
It's worse than you though, in binary!
[first UID in binary]
[second UID in binary]
Both your UID numbers have 32 zeros and 24 ones...
Is there a specific reason you padded them to 56 bits?
Or why he was looking at the ASCII representation of the UIDs?
A more logical representation of the numbers would be:
(00000000)000110000101010011111101
(00000000)000110000100011011110011
12 (or 20) zeros and 12 ones.
The ASCII representations of UIDs has a Hamming distance of 6, while the more logical binary representation of the UIDs has a Hamming distance of 5.
What would have made sense to me would have been no padding (no leading zeros), or padding to 64 bits (because that's how the UIDs are probably stored internally).
32 bits would be more than enough for those UIDs.
Let me put my tinfoil hat on for a moment... Beatings aren't necessary, the US gov't can simply use the NSAKEY to decrypt anything encrypted using Microsoft libraries...
This story is about an Ubuntu laptop. I doubt any Microsoft libraries were used.
How exactly do you backup 120PB?
Easy, you just buy one of these clusters... (for arbitrary values of "easy" and "just")
What made you think this was the primary storage?
The MBR contains the partition table. If you want to resize or move a partition, you need to write a new partition table to the MBR.
Besides, civilization as we know it will end at 21:14:07 UTC on Monday, January 18, 2038
Really? That's 6 hours earlier than most estimates...
$ date -u -d @2147483647
Tue Jan 19 03:14:07 UTC 2038
Since it stands for "We Owned the Other Team"...
No, it doesn't...
The Jargon Lexicon says:
An interjection similar to “Yay!”, as in: “w00t!!! I just got a raise!” Often used for small victories the speaker dies not expect to be of special interest to anyone else. Some claim this is a bastardization of “root”, the highest level of access to a system (particularly UNIX), originated by script kiddies as a 133tspeak equivalent of “root”, and said as an exclamation upon gaining root access. Others claim it originated in the Everquest multiplayer game as an abbreviation of “wonderful loot”. Still other claim it on originated on IRC as the “Ewok victory cheer”] Adj. w00table has the sense of “cool” or “nifty”. This is one of the few leet-speak coinages to have crossed over into non-ironic use among hackers.
Mine is: Please_Share_Your_Personal_Info_With_ME
Wide open WiFi for 2 years, in a 200 unit condo, and Never had anyone log on!
Of course not. Who would want to share any kind of info with Windows ME?
Wake me up when USB can deliver 1.21 jiggawatts.
sudo cat /dev/urandom > /dev/sda
I don't have an Ubuntu-box (or other "sudo"-using box) at hand, so can't test it myself, but doesn't the shell try to open /dev/sda before trying to execute sudo? In other words: Before you got root permission.
I.e. the same reason sort foo >foo gives you an empty file.
Maybe something like /dev/urandom | sudo tee /dev/sda >/dev/null
cat
would work. I think, I used something like that last time I had to work around the shell opening std{in,out,err} before executing commands.
They don't normally have aluminium figures either.
Poor guy. I guess sooner or later he's going to have to learn how to manage his memory and understand how the underlying physical hardware works. That must be a real toughie for anyone who learned to "program" in the Java/C# world.
Yeah, clearly PHK doesn't knows anything about memory allocation. (Except for the malloc library he wrote for FreeBSD...)
Maybe he should RTFM.
I don't have a FreeBSD system at hand, but I wouldn't be surprised if the malloc page was written by PHK.
It's a UNIX system! I know this!
And what if your neighbor is Keyser Soze?
Then I would be working for my neighbor.
Does that mean each system component needs a name that's unique in the whole universe?
May I suggest UUIDs as names?
"So after installing 5229a8ab-8a08-4fe1-9645-37332d8abf09, you start 15286b6e-e44d-4601-a10a-92d7b9920958 and 2d9c0817-8156-4982-8533-dd1fc466661e, then open the 'File' menu in 014e0080-a5f2-4f12-9d20-7aaea21dd8a2 and click 'Open'..."
We can even throw away the version numbers. Just generate a new UUID when you change your program.
13 million miles of TSA pat-downs?
Oh, the humanity!
And we all know from 'statistics' that correlation does not imply causation.
...but it does waggle its eyebrows suggestively and gesture furtively while mouthing 'look over there'.