642 karma · joined January 19, 2015
battery: ?
flight time: ~20min
max. load: 2 persons... 150kg?
weight: under 450kg fully loaded
price: ~300k EUR
permission needed: difficult... no airclass yet for those things except. "ultra light"
Those figures are from a presentation of the VC200 and might not be exactly right for the 2X.
Red light with green arrow means you may turn right if you feel like it or wait for green. Just park your car in front of the traffic light... it'll be fine.
Well the shuttle is a big heavy glider with little wings. One try, and down from 30,000 feet to ground in 3 minutes. Not problematic, but very special.
https://www.hetzner.de/us/hosting/produkte_rootserver/ex51ss...
60$/month for 16GB, 1CPU, 20GB disk for VPS... in comparison a root server with real remote console access, 16GB, 4 core AMD, 4TB disks, unlimited traffic costs me 30EUR/month (30$/month).
Or for 60EUR/month (60$) I could get a root server with 64GB Ram, 2x500GB SSD, i7-6700, 30TB traffic.
At least Galileo is a competitor, and the political/military discourse about it is still ongoing.
https://en.wikipedia.org/wiki/Galileo_(satellite_navigation)...
Works very well in english and other European languages.
Uuindouu... One cant help but make a w sound.
Vvindovv... Not so much.
http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Reno/src...
Personally I'm more worried about the function returning obuf, a pointer to a stack variable in link_ntoa.
reallocarr changes the semantics. Equally easy in new pieces of code and a little harder when converting existing code.
Like reallocarray(3) does?
buf = malloc(x * y);
// becomes
buf = reallocarray(NULL, x, y);
newbuf = realloc(buf, (x * y));
// becomes
newbuf = reallocarray(buf, x, y);OpenBSD: https://github.com/android/platform_bionic/search?q=openbsd
Also:
# rm /bin/true && true && echo success
success /* Note true(1) will return EXIT_FAILURE in the edge case where writes fail with GNU specific options. */
If you can't program a bug free true(1), please stop with whatever you think you are doing. buf=malloc(128);
free(buf, 256);
seems dangerous, if free can't check the size.But kernels sometimes do just that ( free(ptr, size) ), for performance reasons and because "kernel writers know what they are doing".
[0] https://www.joyent.com/manta But the youtube videos with Bryan Cantrill are even better at explaining.
Edit: /dev/random on OpenBSD also does not block.