Re: Do they have spare parts?
There are a couple of companies making PDP11 addin boards for PCs that emulate a PDP11.
What's on the board is a PDP. The PC is just its fancy I/O system.
3982 posts • joined 8 Oct 2009
when the 32-bit clock counter rolls over and we find ourselves back in the 1970's.
Depends. Real-time systems don't necessarily need to be aware of the current wall-clock time. "There's an item coming down the assembly line, it needs to be sprayed/welded/have a barcode stuck on/whatever", is not a task that requires the robot to know whether it's 19-jun-2013, 1-jan-1970 or 19-jan-2038.
In the run-up to Y2K, I was told several routers had to be replaced because their firmware was not Y2K-compliant and they couldn't be upgraded to handle the then-current firmware version that was. After a brief check I reported that the longest-running router had still 42 months to go before *it* would hit that particular date which was roughly half a year away on our calender, and that one which had just been rebooted happily lived in late 1993 with no ill effects. From which I deduced that if any of them would ever reach their Y2K-rollover, the worst that would happen was that they wouldn't be routing for a few minutes until they had finished rebooting, just as with any other interruption, the chance of which occurring would be way greater.
No routers were replaced that year.
You didn't read the article, did you?
Eadon's not unlike aManFromMars, being triggered by particular words in the article, no matter their syntactical relation. The difference however is that aManFromMars does not appear to try to make sense, while Eadon does appear to try and fails miserably every time.
The only RPN calculators still available from HP are a handfull of financial models that they've been making for 30 years with maybe a tweak here or there. No HP41-like powerhouses, not even a general purpose programmable model.
And RPN IS awesome. HP however, has long ago forsaken that moniker.
$ cnt = 99
$ msg = f$fao("!UB month!1%C!%Es!%F of VMS support", cnt)
$ write sys$output f$fao("!AS on the wall!/!-!AS", msg)
$ write sys$output "Take one down and pass it around"
$ cnt = cnt - 1
$ if cnt .gt. 0
$ msg = f$fao("!UB month!1%C!%Es!%F of VMS support", cnt)
$ write sys$output f$fao("!AS on the wall!/", msg)
$ wait 00:00:02
$ goto loop
$ write sys$output "No more months of VMS support on the wall"
Yeah, there was a wealth of info there, and not just technical. Most of the notesfiles had no official status, but at least they were a searchable source, and could point you to the right FCOs, SPDs etc. It's never even been ported to Alpha, AFAIK, which baffles me.
I think the closest comparison, functionality-wise, would be Usenet, but with one central server instead of being distributed, and with infinite retention.
All you'd need to do was after the first purge change the version limit property of the directory to 1.
That would need a rather crafty setup, as any directory from your home directory down would be owned by you, so you'd be able to change the file limit back, and he'd need to have a batchjob running that sets the file limit on any directory you've created that day, plus purge the files in it anyway. Having directories not owned by you but writable by you (so you can't change the file limit) requires more acl-fu than I'd care to think up after working hours.
So do you we need an 'industrial archaeology' of computing?
It's good to know what wheels have been invented already, what their flaws and strengths are, and in what contexts they work best.
That way you might not end up with the Microsoft Triangular Wheel: Now With 33% Less Bumps Per Rotation than the Microsoft Square Wheel*)
*) Sale of the Microsoft Square Wheel Gold WIth Rounded Corners withdrawn pending a patents dispute with Apple.
In the cluster internals the node number is a single byte, which can't be 0 or 255 (and 254, I think), so theoretically you could go up to 253, but that includes cluster storage controllers.
You'll need a serious amount of kit, and need to spend some time on storage and interconnect layout, but after that it'll Just Work.
Whether a sane setup needs a cluster that big is another matter entirely, but the IT definition of 'sane' is anything but, anyway.
The iCharger an iPhone owner has at home is most likely the original iCharger, or else one of the bazillion clones all looking almost exactly like an original iCharger You, wanting to perform nefarious activities, just have to buy one of those, and for good measure just a few of the other models of the aftermarket iPhone chargers, modify them, and replace the found iCharger with that one of yours looking just like it.
Just one burglary needed
The "You can't 3D-print a gun" was written by Lewis Page, someone who's been dealing with things that go boom for quite a few years, and is able to tell about it. This one's written by Simon Sharwood, right at the other end of the globe, and essentially relates to a test by the Aus police force and their publicity. Which, from this admittedly small sample has shown that the chances of such a gun not working as intended is one in two, which not at all contradicts Lewis' assertions.
Well, they'd have to stand right next to you, as the idea is to have the drone hover just a few feet above the net, then, once it'd had ascertained it was the right pole, drop the can.
But if there was an 11-foot Pole standing next to me, trying to get my beer, I think I would simply let him.
An insect net on a ten-foot pole (what else?) which has an RFID-like tag fitted. The drone then should have a camera and tag reader (one that can read the tags from about a meter away) fitted, allowing it to release the can into the right recipient's net. Also, because of the net and the drone's proximity to it, it can just drop the can and be done, no need for a parachute (I take it they don't want to fly right at the recipient for fear of people grabbing the drone).
Which is that it can rapidly (FSVO) make one-off parts (or a small series of), obviously with certain limitations regarding shape and size, including, but not limited to, parts needed to build a 3D printer.
If you think that means they can make all the parts needed to build one, there's a bridge I'd like to sell you.
Nope, you said that 300 quid wouldn't get you a 3D printer. No statement modifiers to the effect that that 3D printer would have to be able to print a gun that would be comparable to a milled one. And the gun under discussion here CAN be printed on that £300 printer, no ifs and buts.
From the article: " there's going to be nothing in the design that makes the metal addition crucial, ". Evidently, it's not the chamber.
The gun is made from ABS, a stupendously tough plastic; they make lifeboats out of it. Also, it's got an extremely short barrel; the bullet will be out of it, allowing the gases to escape, before the chamber has time to deform appreciably (which is what happens before it ruptures). Apparently that's what makes using a plastic chamber feasible.
This was about the third world, and why they weren't producing cheap weapons themselves. If you had bothered to read the comment this was a reply to, you might have gotten that bit.
And also, if you had used the 'reply' button next to the post you're replying to (which you are, evidenced by the quote), your reply would end up where it's pertinent.
you could have a CNC up and running for less than £300, try getting a 3D printer fot that cost
Fail yourself. My 3D-printer, a Mendel90, has ended up costing roughly £350, and there were several ways I could have shaved those 50 quid from the bill, like scavenging printers and scanners for materials, something I simply couldn't be bothered to do.
You can't put useful security on the serial port itself, there isn't the CPU (or the bandwidth) in most devices.
Bollocks. The common problem is not that it can't be done (show me a reasonably current embedded system that has less processing power than a MicroVax II, and even then it's not a problem), but that it simply isn't done properly, if at all: fixed usernames and passwords are all too common.
If your gravity detector is (close to) horizontal, vector math shows that there's some fierce accelerating going on, and as a result of that there's a pulling force on the spring + cord, significantly larger than the pull by gravity. If the acceleration stops, the weight will drop into a vertical position with respect to the rig again; it will not 'overtake' the rig (except for a short moment when it will not yet have started to fall, and the force of the spring will start to reel it in). Only if the turbulence is such that the rig gets actively stopped and/or pushed downwards there's a possibility that the weight can slam into the rig. But I think those are conditions you wouldn't want to launch under.
OK, but then, if it didn't have any (or just a few short) runs, the whole kaboodle would be falling for those 30 seconds before firing. That's quite a distance (2..4.5km, at 20..30 secs runtime) and it will have picked up an impressive speed too (200..300m/s, not counting drag and the deployment of the parachute). I don't think that would be a suitable condition to have LOHAN in at the moment supreme.
Biting the hand that feeds IT © 1998–2019