Re: Well, it would certainly kill
I think if LOHAN drifts into Oregon's airspace then the mission will have wildly exceeded Lester's expectations :-)
3036 posts • joined 10 Jun 2009
I think if LOHAN drifts into Oregon's airspace then the mission will have wildly exceeded Lester's expectations :-)
Unit cock up. 28000km, or 17000 miles.
Was good out west. The ISS was brighter than an aeroplane at about 7pm to the naked eye, but didn't have any binoculars with me to see anything else :-(
I couldn't listen to the (visual) voicemails, but could dial any number I liked.
Yeah that Sky Crane malarkey was positively pedestrian....
There's a difference between "cutting edge" and "tested and built to extremes with redundancies" :-)
Nokia phones have had their share of bugs too though.
Most companies I've seen have those free coffee vending machines, but I've never seen inside them to confirm it's coffee. It's my theory that they've employed someone with a prostate problem to stand in the machine all day, p1ssing into cups on demand. All evidence certainly points that way anyway.
The alternative theory regards the plumbing system and the machines' proximity to the lavatories.
I'm no coffee snob (well I am, but can happily drink instant), but "free" coffee is usually free for a reason.
I assume MS saw that the iPad was non-upgradeable and that was doing well, so instead of making their's non-upgradeable, they just welded it shut as tightly as they could. :-)
Bit of a half-assed attempt at making their device like Apple's, but gotta love it when they try
"If the cheapy GPS receivers in a mobile phone are only accurate to 10m, how does it (usually reliably) know which lane I'm in"
Sorry, which GPS is actually giving you an indication of which *lane* you're in? It might know "northbound" vs "southbound" or similar (which is carriageway information, not lane) but it knows that purely from your actual direction. Sat navs "snap-to" roads, allowing them to be very accurate. Try coming off a road onto a farm track and watch it lose its way quite quickly.
Even when not snapping-to a known location where it expects you to be (roads), it can use fuzzy logic to determine where you are, as the 10m accuracy will vary over time, and a GPS knows that you'll roughly travel quite consistently. If your reading jumps from 5m side to side, it's more likely the error has varied rather than you've moved erratically.
@frank ly - bugger! School boy error of assuming root(i) was -i :-(
There are always 4 roots of a quadratic root (^1/4). In this instance the answers are:
1 + i
1 - i
sqrt(2) . i
- sqrt(2) . i
And the answer(s) to -4^(1/4) is +/-sqrt(2)i from my memory, where i is the imaginary number equal to sqrt(-1). There is also 1 +/- i.
Yup, it's retro, therefore cool to code badly like that I suspect.
Unless you're a raving anti-Linux type, in which case it's all Linux's fault for existing. :-)
Easy as it might be to call this a QA issue, it probably wasn't in their spec to test LINUX installs on this hardware.
However, if this is indeed exploitable via one of the "supported" OS'es,
Ah, excellent, *still* trying to suggest that a bad or unsupported OS could be to blame. This isn't about an OS, it's about conforming to the UEFI spec. QA at this level doesn't involve an operating system, the test harness around this level of hardware interaction is and always should be OS independent.
Even if this was a case of an OS making a bad or malformed UEFI call (it wasn't), the laptop shouldn't be damaged by it. This is basic bounds checking, and falls firmly into the category of QA. In this particular instance, it appears to be a buffer overrun, which has been bad programming since forever.
@Khaptain "Linux was written by inquisitive programmers that like to hack any and all given APIs, interfaces in the quest for knowledge or functionality."
This wasn't a hack or an unusual use of an API or interface though. At a basic level it's a buffer overflow issue with Samsung's implementation of the UEFI.
Incidentally, I think what you point out (Linux more likely to trigger a bug) isn't quite correct, I think it's more nuanced than that. I suspect that Linux is more likely to trigger a bug that the public can then hear about. Windows devs working for MS were just as likely to trigger this overflow (especially as it's an acceptable UEFI call FWIU), but the symptoms, bug report and fix wouldn't be made public.
But I recall that any anti-Windows comment he may have posted on this particular topic was overwhelmed by a flood of 'AC's with such helpful suggestions as "Well if you will run freeware crap, you get what you pay for...".
Yeah I'm also noticing the rather muted response from the anti-Linux crowd on this article. It's like they've applied logic and realised they're wrong.
Or they're just not up yet - give it time.
@Fred Flintstone - we're talking about the pre-Momentus range from Samsung that didn't really show much of a performance boost.
@Dana W - that's not a hybrid drive, so unsure of your point?...
"So Seagate started the hybrid disk drive ball rolling, with its Momentus XT in May 2010"
We're ignoring the failed attempt to get hybrid laptop drives in about 2007 then? I recall they were a bit of a flop mind, but the idea was there.
Not to mention the rather obvious use-case of putting SMR into a hybrid flash drive which it seems perfect for.
Pimental said SMR drives would be introduced later this year, and enable a 20 - 25 per cent areal density increase. Taking a 4TB 3.5-inch drive and giving it an SMR upgrade would bump capacity up to 4.8TB to 5TB.
Thanks for working out what 20 and 25% of 4TB is for me ;-)
@PaulR79 - I assume we silver badge holders are just considered impotent*.
Indeed. I do like the ominous advice that just says "don't download it", and no mention of "you've downloaded it? bad luck then"
It's tricky to strike the balance though. On my desktop I allow the autoupdates to apply themselves, primarily due to MS having a surprisingly good track record of these updates of late. 5 years ago, maybe not, but today I'm reasonably confident MS won't blow my machine out of the water, and in the world of zero-day exploits it's worth that risk.. Plus I can usually roll-back a patch if need be.
However on my good lady wife's iPhone, I believe it's set by default to notify you of any updates, and ask you whether to install or not. She clicked "ok". Fingers crossed there's no issue, as on that particular platform there's no rollback possible.
iOS upgrades aren't "free", certainly not forever. There is a limited number you get included with any device, about 3.5 by my reckoning (3 full ones, then a "limited" version that doesn't have all features, like multi-tasking, or Siri as two prime examples).
Repeat though, "RAID is not a backup, RAID is not a backup..."
The bitrot problem is going to be heeeeeuuuuuge on that array.
"If so, why haven't they found us and made contact yet?"
Easy, because we've only made an outwardly observable presence for the last 100 years or so (EM signals). So at most, they'd have to be within 100 light years to have been alerted to our presence. Half that for them to signal us. Not to mention we might not even recognise the contact.
"so spectacular that it may achieve a brightness of an apparent magnitude of -16, which would greatly outshine the brightest Moon"
Looking forward to that, if only so I can point up at it and mutter ominously "that's no moon..."
If only it were due to happen on May the 4th...
"39 certainly used to be prime. "
But then the number 3 came along, and divided the sceptics. And the number 39..
"Usual caveats, highly specialised problem, highly tuned code probably non portable etc"
Yup, testing a prime number is an "embarrassingly parallel" activity I believe, so translates incredibly well to CUDA. When you consider the number of cores in a GPU it's rather unsurprising.
T'COK-A-RIM, great name. And if they do formally change, I trust you'll call them Blackberry - Otherwise Formerly As RIM - or BOF-A-RIM
This would be the only thing that puts me off going the ISS, someone playing the guitar somewhere. Though I think it's a rule of any property where you have flatmates - one of them is going to be a musician. Glad to see it's a universal law that extends beyond our atmosphere.
Oh, as for Twitter leaders of ex-Trekkers, may I submit Wil Wheaton with around 2.3m followers on Twitter?
What, are you paid by the comment or something?? Can't argue with your Picard choice, but would happily debate the order of the rest.
^^ that. I can understand him being p1ssed off at missing out on a bonus, and at a stretch imagine him doing it once. But to hold a grudge for three years and keep up that level of malice?? That's bordering on, erm, "difficulties in the gray matter"!
The host instruction set shouldn't matter. From what I can tell it's running on an Android emulator, and is working to translate Win API calls to Android API calls. This isn't new, there was a version of WINE running on Mac PowerPCs before they switched to x86 (DarWINE?)
Yup. But doesn't stop the down-votes flooding in for the same thing I suggested above.
The obligatory analogy - you were given a key to the back door of a house by virtue of showing them you had a front door key. The front door key has now been stolen, but was stolen in a tightly locked box that will take a good deal of effort to break open. So they've changed the front door lock lest that ever happen. The lock for the back door hasn't been compromised, and there's no way to use the stolen front door key to either open the front door, or be granted a new back door key, even if the front door key is broken out of the box.
"There was no gap between hackers getting the username/password (why wasn't it encrypted - was it?) and twitter locking the accounts?"
Was it encrypted? Yes. The risk was if they ever decrypted it, it would then be worthless.
To revoke the Oauth logins would have revoked it for every user of the app. Crap implementation maybe, but the risk assessment is pretty much zero.
@Richard 12 - they can't log in as you using one of these apps. New logins aren't accepted, they still require the user/pass combo (which would fail), only pre-existing logins work. These apps are permanently logged in, and don't store passwords on the device, relying instead on this one-time token which was unaffected by the breach. To log in a different app on a different device would require a generation of a new token which would be issued on submission of the correct password, which would no longer work. The article says as much, namely logging out of the Twitter app (destroying the old OAuth token).
The title of the article is misleading "Twitter clients stay signed in with pre-breach passwords", it's not "with" pre-breach passwords. It's with a token unaffected by the breach.
On first reading, it seems that there isn't an issue. Potentially usernames and passwords were leaked (though salted, and emphasis on "potentially"), which has no bearing on the tokens used by the Twitter API which uses, in effect, a unique one-time password that exists between client and server.
The only criticism is that some affected users wouldn't know they'd been affected, but the only risk to them would be if they shared passwords across different services.
"A spare disk? Are they saying they didn't have a HDD onsite for this (assumed) server?"
No, they're saying they've used a spare disk ("the replacement disk has been inserted into the Glasgow machine") and are sending a replacement for that spare disk. For all you know there are x spare disks on site and they are now down to x-1.
I know why RSOs exist, was merely pointing out their existance to demonstrate an accepted risk of the entire stack going wrong, which astronauts are aware of.
It's thought that at most they would have had 30 seconds of knowledge, when the main hydraulics failed, probably even less. Events up until that point had been nominal. The decompression event that followed loss of hydraulics would have lead to loss of consciousness pretty much instantly.
Unlike the Challenger disaster where it's thought the crew survived until impact, 2 minutes 45 seconds later.
Also, I used to know one of the ISS designers (or a designer of an earlier version of it.) She said about the Shuttle - 'You'll never get me in that thing. I've seen the plans.'
There's clearly risk in spaceflight, astronauts know and accept this. As an example, it's a relatively little known fact that the Space Shuttle had a self-destruct mechanism (utilised in the Challenger disaster) controlled by the Range Safety Officer.
What astronauts probably don't expect and expect though, is that the risks are really poorly managed in the case of both shuttle disasters.
@Stratman - no idea who'd vote you down for a square being a rectangle?? A square is also a parallelogram and a quadrilateral. And a polygon for that matter. And a closed polygonal chain :-)
"No other shop will be able to have smug looking "cool" staff wandering around doing anything other than actually selling anything."
Abercrombie & Fitch got there waaaay before Apple did on that front.
Yes but their tables are perpendicular to the wall, instead of parallel. Phew!
Christ, even Gap has a similar layout to this.
"(with the obligatory offers to install crapware at the same time)."
Urgh, that. 100x that. Not so much that it offers, but that the Yahoo (!) tool bar is selected for install by default is beyond annoying.
I think it is based on inflatable buildings, and they are spraying it with some form of cement - that's what the "printer" is doing - but a cement made of moon rock.
The difference is all they need to take to the moon is the binding agent, the base material is free in effect.
I missed out the other condition as it was less relevant, but it also has to support 1.4kN point weight, so you'll be fine standing on one foot ;-)
And yes, as pointed out already 400kg would be fine in a room, but only if it were spread out over the whole floor, which it probably wouldn't be. And it won't necessarily happen the instant you subject it to that weight.
Source, BS 6399:
You'll see in that doc that server rooms have to be rated to 3.5kN/m^s and 4.5kN point weight - about 3x the strength of a domestic floor.