EEPROMs as flash RAM or firmware is old, very old. But the idea of a processor being field reprogrammable *is* new. It's so new, nobody has anything that would benefit yet. Think of something like Cisco booting based off the startup config, then optimizing the processors based on the config.
Let's see if Cisco can "optimize" IOS to not crash because of stupid memory leaks & buffer overruns first:-)
Did any of the news organizations offering this reactionary reporting actually check with the local authorities to see if the helicopters were being used in for a movie shoot?
A local electronics/computer chain (now bankrupt) had all their security webcams on an open wifi network, and all the webcams had the default administrator password ("admin" of course). From a bench outside I was able to see everything going on in the store without even guessing the admin password.
This is the kind of stuff that they need. Even Iran- or China-level internet access (open by default but filter the crap out of everything & spy on the rest) would be a massive improvement for NK 'net users, which could be more aptly referred to as the "Kimternet". If it ain't on the NK propaganda network, they don't have access to it.
Not that I'm advocating that model of course, but it'd be an improvement over what they have now.
The majority of recent American mass shootings have been commited by mentally unstable people, most of whom were identified as such by people around them.
Perhaps if the care these people really needed was not so far out of their financial reach that they or someone close to them would have considered treatment then at least a few of them would have been avoided?
So it's just a matter of time until they can be audited for PCI compliance then?
Well, passing such an audit would certainly lend legitimacy to Bitcoin, but I think they'd have a lot of hurdles to jump through before they got there...
Well, if you've got admin access to a decent sized network, go install NetDot, which gives you a visualization of all your gear & how it's connected at the physical & logical level, and will draw nice little network maps for you showing the paths between devices on the fly.
“The nuclear characteristics and thermal power level of the experiment are remarkably similar to our space reactor flight concept,” said Los Alamos engineer David Poston. “The biggest difference between DUFF and a possible flight system is that the Stirling input temperature would need to be hotter to attain the required efficiency and power output needed for space missions.”
Though successful, the Stirling engine system used in the experiment isn't considered enough for practical purposes. For missions beyond Jupiter, much more power is needed. “The heat pipe and Stirling engine used in this test are meant to represent one module that could be used in a space system,” said Marc Gibson of NASA Glenn. “A flight system might use several modules to produce approximately one kilowatt of electricity.”
With the right hardware I could build a nice little server farm that runs on a kilowatt... Or even better give me a flywheel that I can charge with the excess mechanical energy generated during off-peak periods and tap during peaks, and double the peak load of the system.
We are moving from a heat driven passive reactor to a heat driven mechanical generator... seems like step back and a new point of failure for modern space vehicles...
Stirling Engines are actually quite reliable. They're often used on things like waste heat recovery systems to power remote oil & gas installations, where they have to run for extended periods in nasty environments.
The main limitation to more popular use of Stirling-cycle engines vs. the ICE is that they need an external source of motion to get them going (well, ICEs do too), and they take a while to "warm up" before they reach operational efficiency. Ford messed with them for a while in the 70's when the gas crisis hit and managed to get the start/warmup cycle to down to about 30 seconds.
So not an excellent candidate for applications with a lot of start/stop activity, but very good for generators that just need to sit there & run forever.
What about printing Firearms (AR-15 Lowers) or objects copyright holders will sue over object? How will they decide what to approve for printing and what to deny?
Well, in this case a firearm receiver fabbed from paper probably wouldn't be too useful for anything other than a wallhanger, so they've avoided having to dead with that issue for now.
Regarding copyright issues, it's no different from people making 2D prints (as others here have mentioned).
It's not terribly clear what exactly you're trying to accomplish, but have a good look at NetDisco (designed for college campuses, mostly for tracking MAC addresses & the devices that know about them) and NetDot (designed more generically for wide-area networks but not so much for tracking end stations). They're both excellent pieces of software that keep track of everything on your network for you in a clean multivendor way. I particularly like NetDot as it has the much-sought-after feature of a plugin framework that generates config files for the other tools you already use. Think of it as sort of a control panel/dashboard for your network management apps & you start to get the idea.
For pretty much all fowl, the tastiest way I've had them is on a spit in front of a wood fire.
I stuff our turkey full of spice-covered peeled oranges & stick the spit through them, which keeps it juicy as the oranges ooze juice as they cook. I got my rotisserie motor off Amazon for fifteen bucks & it runs on two D batteries so it works anywhere.
Get the fire nice & hot and keep it that way. Put a drip tray under the bird and use a siphon to pump the juice back onto the bird every 20 minutes or so. Get the bird as close as you can to the fire without burning it. A 6-7 kilo turkey takes about four hours, so make sure you don't run out of wood.
Note that this is basically a horizontal riff on beer can chicken.
Weeelll, the problem with #2 in NYC was that the city wouldn't let fuel trucks for the datacenters in lower Manhattan into the area until the debris for their were cleared (which makes sense as they didn't want to have to deal with stuck fuel trucks too). Most of the NYC DCs that ran out of fuel ran out because of this reason.
Which brings up a few common rules for ultra-high availability datacenters:
- don't build them in the middle of a city (riots, strikes, traffic, WTC being kamikazied, etc)
- build them in a low disaster risk zone (e.g. flood, tsunami, earthquake, forest fires, plane crash, etc).
- available power sources should include at least *two* technologies that don't require a truck roll to refuel (e.g. utility electric, utility natural gas, wind/solar/hydro)
- or if that's really not available or "too expensive" then store at a week's worth of fuel on-site.
For bonus points you can run your DC off of whichever power technology is most economical at any given time during the day. This includes cranking up your diesel during the most expensive peak hours of the day when your fuel costs you less than utility electric. For extra bonus points, sell your surplus power back to the utility during these peaks. It's also a nice way to prove to your clients that your generator works:-).
News Flash: Theo is hard to deal with...
on
OpenBSD 5.2 Released
·
· Score: 3, Insightful
...film at 11.
We all know that. But do not confuse "the man" with "the OS". Theo probably maintains less control over OpenBSD than Linus does over Linux (a lot of what he does involves maintaining the project's resources and logistics so that the developers can get on with their work rather than dealing with hardware and sysadmin stuff). Yes, he's the founder & leader of the project, but OpenBSD developers are amazing and could easily continue the project without him if required (not that that's at all likely to happen any time soon). Corporations would kill to have this consistent level of developer talent.
Which is why I've been using OpenBSD for 15 years for critical systems, and have no plans to change that.
...I don't want it in my datacenter. If you have no budget for non-revenue-generating boxes for services like DNS, NTP, etc. then upgrade the server hardware you tore out of production after the last upgrade cycle with SSDs and low-wattage processors & put it back into service for your internal needs.
Otherwise get a few Dell R210s or some other small cheap rack server with an IPMI 2.0 BMC and get on with your business. Any money saved by buying "mini-PCs" (or whatever you want to call them) for any datacenter computing hardware you plan to rely upon at all will be burned the first time you have to drive to the datacenter and physically babysit some cheap machine because it didn't have IPMI.
This is almost certainly for a SeaMicro-based architecture. The GPU might be mildly irrelevant in this market today but will continue to gain importance as more tasks transition to being executable via OpenCL & its cousins.
What you are looking at is a small box densely packed with lots of cores. Another flavor will likely come as a box with a few weak ARM CPUs used to control a large quantity of GPUs for HPC applications.
The thing that will make or break ARM in a SeaMicro style chassis is whether they can get a successful OpenStack port to it done in time for the launch. My guess is that they will, as OpenStack development is going gangbusters at the moment.
Slashdot Mirror
EEPROMs as flash RAM or firmware is old, very old. But the idea of a processor being field reprogrammable *is* new. It's so new, nobody has anything that would benefit yet. Think of something like Cisco booting based off the startup config, then optimizing the processors based on the config.
Let's see if Cisco can "optimize" IOS to not crash because of stupid memory leaks & buffer overruns first :-)
Did any of the news organizations offering this reactionary reporting actually check with the local authorities to see if the helicopters were being used in for a movie shoot?
"efforting?"
If you're going to troll, at least use real words...
A local electronics/computer chain (now bankrupt) had all their security webcams on an open wifi network, and all the webcams had the default administrator password ("admin" of course). From a bench outside I was able to see everything going on in the store without even guessing the admin password.
probably because they haven't installed DPI boxes to monitor the new link, and they'd likely need bigger ones given the bandwidth.
But they likely only want to see the messages going out anyway...
This is the kind of stuff that they need. Even Iran- or China-level internet access (open by default but filter the crap out of everything & spy on the rest) would be a massive improvement for NK 'net users, which could be more aptly referred to as the "Kimternet". If it ain't on the NK propaganda network, they don't have access to it.
Not that I'm advocating that model of course, but it'd be an improvement over what they have now.
If so then all griping here about the lack of free certificates is for naught...
Best thread today :-)
I'd mod you higher if I could. Just a few stats for y'all:
http://www.washingtonpost.com/blogs/wonkblog/wp/2012/12/14/nine-facts-about-guns-and-mass-shootings-in-the-united-states/?wprss=rss_business
The majority of recent American mass shootings have been commited by mentally unstable people, most of whom were identified as such by people around them.
Perhaps if the care these people really needed was not so far out of their financial reach that they or someone close to them would have considered treatment then at least a few of them would have been avoided?
beat me to it by just a few minutes...
So it's just a matter of time until they can be audited for PCI compliance then?
Well, passing such an audit would certainly lend legitimacy to Bitcoin, but I think they'd have a lot of hurdles to jump through before they got there...
Dude, you have issues... Your ex-wife was deciding what motherboard you could buy?
Well, if you've got admin access to a decent sized network, go install NetDot, which gives you a visualization of all your gear & how it's connected at the physical & logical level, and will draw nice little network maps for you showing the paths between devices on the fly.
Hmm, 24 Watts.
FTFA:
“The nuclear characteristics and thermal power level of the experiment are remarkably similar to our space reactor flight concept,” said Los Alamos engineer David Poston. “The biggest difference between DUFF and a possible flight system is that the Stirling input temperature would need to be hotter to attain the required efficiency and power output needed for space missions.”
Though successful, the Stirling engine system used in the experiment isn't considered enough for practical purposes. For missions beyond Jupiter, much more power is needed. “The heat pipe and Stirling engine used in this test are meant to represent one module that could be used in a space system,” said Marc Gibson of NASA Glenn. “A flight system might use several modules to produce approximately one kilowatt of electricity.”
With the right hardware I could build a nice little server farm that runs on a kilowatt... Or even better give me a flywheel that I can charge with the excess mechanical energy generated during off-peak periods and tap during peaks, and double the peak load of the system.
We are moving from a heat driven passive reactor to a heat driven mechanical generator... seems like step back and a new point of failure for modern space vehicles...
Stirling Engines are actually quite reliable. They're often used on things like waste heat recovery systems to power remote oil & gas installations, where they have to run for extended periods in nasty environments.
The main limitation to more popular use of Stirling-cycle engines vs. the ICE is that they need an external source of motion to get them going (well, ICEs do too), and they take a while to "warm up" before they reach operational efficiency. Ford messed with them for a while in the 70's when the gas crisis hit and managed to get the start/warmup cycle to down to about 30 seconds.
So not an excellent candidate for applications with a lot of start/stop activity, but very good for generators that just need to sit there & run forever.
What about printing Firearms (AR-15 Lowers) or objects copyright holders will sue over object? How will they decide what to approve for printing and what to deny?
Well, in this case a firearm receiver fabbed from paper probably wouldn't be too useful for anything other than a wallhanger, so they've avoided having to dead with that issue for now.
Regarding copyright issues, it's no different from people making 2D prints (as others here have mentioned).
It's not terribly clear what exactly you're trying to accomplish, but have a good look at NetDisco (designed for college campuses, mostly for tracking MAC addresses & the devices that know about them) and NetDot (designed more generically for wide-area networks but not so much for tracking end stations). They're both excellent pieces of software that keep track of everything on your network for you in a clean multivendor way. I particularly like NetDot as it has the much-sought-after feature of a plugin framework that generates config files for the other tools you already use. Think of it as sort of a control panel/dashboard for your network management apps & you start to get the idea.
For pretty much all fowl, the tastiest way I've had them is on a spit in front of a wood fire.
I stuff our turkey full of spice-covered peeled oranges & stick the spit through them, which keeps it juicy as the oranges ooze juice as they cook. I got my rotisserie motor off Amazon for fifteen bucks & it runs on two D batteries so it works anywhere.
Get the fire nice & hot and keep it that way. Put a drip tray under the bird and use a siphon to pump the juice back onto the bird every 20 minutes or so. Get the bird as close as you can to the fire without burning it. A 6-7 kilo turkey takes about four hours, so make sure you don't run out of wood.
Note that this is basically a horizontal riff on beer can chicken.
Weeelll, the problem with #2 in NYC was that the city wouldn't let fuel trucks for the datacenters in lower Manhattan into the area until the debris for their were cleared (which makes sense as they didn't want to have to deal with stuck fuel trucks too). Most of the NYC DCs that ran out of fuel ran out because of this reason.
Which brings up a few common rules for ultra-high availability datacenters:
- don't build them in the middle of a city (riots, strikes, traffic, WTC being kamikazied, etc)
- build them in a low disaster risk zone (e.g. flood, tsunami, earthquake, forest fires, plane crash, etc).
- available power sources should include at least *two* technologies that don't require a truck roll to refuel (e.g. utility electric, utility natural gas, wind/solar/hydro)
- or if that's really not available or "too expensive" then store at a week's worth of fuel on-site.
For bonus points you can run your DC off of whichever power technology is most economical at any given time during the day. This includes cranking up your diesel during the most expensive peak hours of the day when your fuel costs you less than utility electric. For extra bonus points, sell your surplus power back to the utility during these peaks. It's also a nice way to prove to your clients that your generator works :-).
Sounds like an S.E.P. field to me...
Better article here: http://www.express.co.uk/posts/view/340486/Coo-blimey-Riddle-of-Percy-the-pigeon-and-a-wartime-mission
...film at 11.
We all know that. But do not confuse "the man" with "the OS". Theo probably maintains less control over OpenBSD than Linus does over Linux (a lot of what he does involves maintaining the project's resources and logistics so that the developers can get on with their work rather than dealing with hardware and sysadmin stuff). Yes, he's the founder & leader of the project, but OpenBSD developers are amazing and could easily continue the project without him if required (not that that's at all likely to happen any time soon). Corporations would kill to have this consistent level of developer talent.
Which is why I've been using OpenBSD for 15 years for critical systems, and have no plans to change that.
...I don't want it in my datacenter. If you have no budget for non-revenue-generating boxes for services like DNS, NTP, etc. then upgrade the server hardware you tore out of production after the last upgrade cycle with SSDs and low-wattage processors & put it back into service for your internal needs.
Otherwise get a few Dell R210s or some other small cheap rack server with an IPMI 2.0 BMC and get on with your business. Any money saved by buying "mini-PCs" (or whatever you want to call them) for any datacenter computing hardware you plan to rely upon at all will be burned the first time you have to drive to the datacenter and physically babysit some cheap machine because it didn't have IPMI.
This is almost certainly for a SeaMicro-based architecture. The GPU might be mildly irrelevant in this market today but will continue to gain importance as more tasks transition to being executable via OpenCL & its cousins.
What you are looking at is a small box densely packed with lots of cores. Another flavor will likely come as a box with a few weak ARM CPUs used to control a large quantity of GPUs for HPC applications.
The thing that will make or break ARM in a SeaMicro style chassis is whether they can get a successful OpenStack port to it done in time for the launch. My guess is that they will, as OpenStack development is going gangbusters at the moment.
Any CP/M systems?
& more importantly, does anyone care?
sorry :-)