OpenBSD: Two remote vulnerabilities in the default install in ~12 years. None in the last 2 years.
Running a 2 year old copy of OpenBSD still safe (unless you make it otherwise). Your Linux ISO from 2 weeks ago is already vulnerable.
Size has no bearing, except that it helps to determine the friction coefficient of moving through another material. Almost anything dropped from that height would reach terminal velocity quickly, and I would imagine an iPhone's is quite high.
Also, as others have pointed out, the rate of deceleration upon impact determines the damage to the phone (as the saying goes: speed doesn't kill; acceleration does). Various substances provide different deceleration times. Hitting a rubber roof would be significantly less damaging than a cement sidewalk.
While your home server might use SATA-III with consumer SSDs; there's a wide variety of reasons not to use SSDs in production servers (except very particular niche cases) and no self respecting server would use SATA in the first place when SAS is available.
Is my old data on a cloud based system considered abandoned if I continue to actively use the system but don't touch some items?
This is one of the problems the ISPs want clarified; the law doesn't specify if the whole account has to be inactive, or just certain items. The law has many other problems because of changes in modern technology.
1. Someone already did; products don't just come into being, someone wrote a spec, a developer implemented it, ya ya.
2. Don't even pretend like you don't understand how your competitors products work without seeing their drivers' source code.
3. The idiots are idiots already, and still will be, nothing will change.
4. If you don't tell the C*O, see #5.
5. You just lost $3 from that other guy; and $30 from me and my whole family that I buy for; and who knows how many other people. Explain *that* to your C*O.
It's the combination of flexible game play, long and detailed story lines, and a general theme of blending modern world technology with old world magic. FF7 and FF8 were the epitomes of the FF series IMHO.
FF7 had breakthrough graphics (which look kind of clunk these days) and still holds the title for plot/storyline, I think. FF8 has the title in terms of character development and interaction, the story suffered a bit due to that but it's still one of the greats.
I think he meant torch like acetylene torch, or blow torch; not a medieval torch.
Either word isn't very descriptive as to what the product actually is.
You can not directly control the computer or the programs that it runs. You merely interact with it. Your idea of control is an illusion. With snail-mail you have paper, you can directly control that paper. With e-mail the computer has bits and bytes, you have what it shows you.
I think you missed my point entirely. I never said anythign about how things "should" have been. I was talking about where we go from here. Too many people get caught in how things have been done, why they were done. Instead we need to focus on where we go from here and how we get there fastest/easiest/take you pick.
I don't need a lesson in unix timesharing advancements. That isn't where we are now. I'm posing the question "How do we get to the next 'level' of computing, where is it, what are the options for getting there?", Questions like "Where did we start, how did we get here, what were designers *sure* of 10, 20, 30 years ago" makes little difference today.
I should be common knowledge that working together we can acheive more than any single person. The open source effot makes that plainly clear. So why do we not work together *more*? As I see it, there is no coordinating body. I'm not talking about a dictatorial type orginization who decices what the right standard is. But rather an orgizination that keeps track of many projects. Highlighting what each project does, what it's stong points are, and weaknesses. A directory that is searchable and flexable could enable programmers, or administrators and users, to find projects that suit thier needs. At the same time a coordinated effort to bring APIs in common projects together. I imagine that in many cases these are already similar.
Perhaps this will happen naturally some day. For now most poeple are too political and self-oriented to fully accomplish this sort of idea. At least somebody read my post.::sigh::
You have Cost, Performance/Features, and Time. When requesting anything you pick two and the other is determined by what you pick. You have picked all three. You want low cost, fast performance, and in a reasonable time. It doesn't exist. Pick two and try again.
There's nothing essentially wrong with MySQL running in a high capacity environment. It would need to by properly maintained, and database design will matter a lot. Speaking of DB design, wanting to separate the reporting and dialing databases, which are functionaly connected, sounds like it rubs against the grain a bit. I don't know much about your specific environment, so take my opinion with a large grain of salt.
I've thought to myself before that much more progress could be made if fairly standard APIs could be agreed on for more things. Printing for example, how many unix "printing" solutions exist? It's no wonder than the desktop environments don't have the same ease in setting up and using printers as Windows does. A significantly higher level of cooperation, coordination, agreement, and standardization could take the linux/bsd/*nix platforms a long way.
I'm not some crazy saying we need to decide on a single widget set or should merge Qt and Gtk. But a flexable and extensible layer that is stable and mature would make developing easier. I think something generally eqivelent to Visual Basic would help too. The platforms would be much more attractive in general if there was some really "easy" development tool; Windows capitalized on this in the 90s; learn a lesson.
I don't pretend to have all the answers, but working together more sure seems like a good start.
Give one of the BSDs a try. FreeBSD and NetBSD are both extremely flexable for embedded installs (Free more so to x86 based systems). Linux seems random and haphazard after you've worked with a BSD for a while.
IANARS! Having an astronaut literally throw a typical size bag of trash toward the Earth would be sufficient acceleration (or deceleration depending on your point of view) to cause it to burn up within a couple weeks. And better yet it would instantly be in a non-intersecting orbit with the ISS.
In the past they haven't done this because it will cause the ISS to be accelerated into a higher orbit. The difference would be minimal, but certainly measurable. The ISS is not very well equipped to deal with such problems (remember that it is technically falling all the time normally). Apparently NASA has decided that this effect is minimal enough that it would not be detrimental to the ISS orbit.
A second motherboard is not necessary. But some kind of logic board is if you want the information on the second screen to be dynamic. A static display doesn't need any processing ability.
I'm a little concerned with the hundreds of hours of display time. The display is one of the leading power suckers in laptops (the cpu is ususally the prime culprit). Unless it's a reflective lcd display (think calculator type where there is no backlight) it should drain the batter in a few hours.
But Windows 2K+, Linux, and most Unicies have full IPSec built in that will do 3DES encrypted VPN with SSL Cert authentication. Might want to check out what you have already. I know from experience it can be a b*tch to get cross-platform working correctly, but it certainly can be done.
How is Microsoft lowering TCO when one small continent will need over half a million more people just to keep Windoz running? Sounds like one more piece of ammo for Linux, the BSDs, or even Apple.
"Other than building the machine itself, the main challenge for us has been getting the computer systems to talk to each other and then to interact with all the hardware," said Mr Shipman.
These guys are pretty piss-poor scientists. Having troubles with an overly and unnecessarily complex system. Trying to use finesse to gain distance when additional power is highly available. Flings 6 boots; have they thought about counterweight problems, balance, efficiency, etc. These guys need a large dose of KISS engineering if they want to produce a winner.
Definately agree with that, both opinions would be the most useful. But if you have to choose one over the other, which would you rather have (remember it will be published on/.)?
I would rather take the experienced user over the student in most cases. The OP seems to see things differently.
Slashdot Mirror
OpenBSD: Two remote vulnerabilities in the default install in ~12 years. None in the last 2 years.
Running a 2 year old copy of OpenBSD still safe (unless you make it otherwise). Your Linux ISO from 2 weeks ago is already vulnerable.
Size has no bearing, except that it helps to determine the friction coefficient of moving through another material. Almost anything dropped from that height would reach terminal velocity quickly, and I would imagine an iPhone's is quite high. Also, as others have pointed out, the rate of deceleration upon impact determines the damage to the phone (as the saying goes: speed doesn't kill; acceleration does). Various substances provide different deceleration times. Hitting a rubber roof would be significantly less damaging than a cement sidewalk.
I thought R-ing TFA disqualified you from commenting on /.
While your home server might use SATA-III with consumer SSDs; there's a wide variety of reasons not to use SSDs in production servers (except very particular niche cases) and no self respecting server would use SATA in the first place when SAS is available.
Is my old data on a cloud based system considered abandoned if I continue to actively use the system but don't touch some items?
This is one of the problems the ISPs want clarified; the law doesn't specify if the whole account has to be inactive, or just certain items. The law has many other problems because of changes in modern technology.
"exposed by rain" doesn't exactly fit my definition of "heavily protected"
Better for the CIA, triangulating your location based on your 3G connection should make finding enemies of the state a breeze.
And how long before the processors call home with their current location or other juicy tidbits?
1. Someone already did; products don't just come into being, someone wrote a spec, a developer implemented it, ya ya.
2. Don't even pretend like you don't understand how your competitors products work without seeing their drivers' source code.
3. The idiots are idiots already, and still will be, nothing will change.
4. If you don't tell the C*O, see #5.
5. You just lost $3 from that other guy; and $30 from me and my whole family that I buy for; and who knows how many other people. Explain *that* to your C*O.
It's the combination of flexible game play, long and detailed story lines, and a general theme of blending modern world technology with old world magic. FF7 and FF8 were the epitomes of the FF series IMHO.
FF7 had breakthrough graphics (which look kind of clunk these days) and still holds the title for plot/storyline, I think. FF8 has the title in terms of character development and interaction, the story suffered a bit due to that but it's still one of the greats.
I think he meant torch like acetylene torch, or blow torch; not a medieval torch. Either word isn't very descriptive as to what the product actually is.
You can not directly control the computer or the programs that it runs. You merely interact with it. Your idea of control is an illusion. With snail-mail you have paper, you can directly control that paper. With e-mail the computer has bits and bytes, you have what it shows you.
Human Beings *can* live without TVs...
I think you missed my point entirely. I never said anythign about how things "should" have been. I was talking about where we go from here. Too many people get caught in how things have been done, why they were done. Instead we need to focus on where we go from here and how we get there fastest/easiest/take you pick.
::sigh::
I don't need a lesson in unix timesharing advancements. That isn't where we are now. I'm posing the question "How do we get to the next 'level' of computing, where is it, what are the options for getting there?", Questions like "Where did we start, how did we get here, what were designers *sure* of 10, 20, 30 years ago" makes little difference today.
I should be common knowledge that working together we can acheive more than any single person. The open source effot makes that plainly clear. So why do we not work together *more*? As I see it, there is no coordinating body. I'm not talking about a dictatorial type orginization who decices what the right standard is. But rather an orgizination that keeps track of many projects. Highlighting what each project does, what it's stong points are, and weaknesses. A directory that is searchable and flexable could enable programmers, or administrators and users, to find projects that suit thier needs. At the same time a coordinated effort to bring APIs in common projects together. I imagine that in many cases these are already similar.
Perhaps this will happen naturally some day. For now most poeple are too political and self-oriented to fully accomplish this sort of idea. At least somebody read my post.
You have Cost, Performance/Features, and Time. When requesting anything you pick two and the other is determined by what you pick. You have picked all three. You want low cost, fast performance, and in a reasonable time. It doesn't exist. Pick two and try again. There's nothing essentially wrong with MySQL running in a high capacity environment. It would need to by properly maintained, and database design will matter a lot. Speaking of DB design, wanting to separate the reporting and dialing databases, which are functionaly connected, sounds like it rubs against the grain a bit. I don't know much about your specific environment, so take my opinion with a large grain of salt.
I've thought to myself before that much more progress could be made if fairly standard APIs could be agreed on for more things. Printing for example, how many unix "printing" solutions exist? It's no wonder than the desktop environments don't have the same ease in setting up and using printers as Windows does. A significantly higher level of cooperation, coordination, agreement, and standardization could take the linux/bsd/*nix platforms a long way.
I'm not some crazy saying we need to decide on a single widget set or should merge Qt and Gtk. But a flexable and extensible layer that is stable and mature would make developing easier. I think something generally eqivelent to Visual Basic would help too. The platforms would be much more attractive in general if there was some really "easy" development tool; Windows capitalized on this in the 90s; learn a lesson.
I don't pretend to have all the answers, but working together more sure seems like a good start.
Give one of the BSDs a try. FreeBSD and NetBSD are both extremely flexable for embedded installs (Free more so to x86 based systems). Linux seems random and haphazard after you've worked with a BSD for a while.
IANARS!
Having an astronaut literally throw a typical size bag of trash toward the Earth would be sufficient acceleration (or deceleration depending on your point of view) to cause it to burn up within a couple weeks. And better yet it would instantly be in a non-intersecting orbit with the ISS.
In the past they haven't done this because it will cause the ISS to be accelerated into a higher orbit. The difference would be minimal, but certainly measurable. The ISS is not very well equipped to deal with such problems (remember that it is technically falling all the time normally). Apparently NASA has decided that this effect is minimal enough that it would not be detrimental to the ISS orbit.
A second motherboard is not necessary. But some kind of logic board is if you want the information on the second screen to be dynamic. A static display doesn't need any processing ability.
I'm a little concerned with the hundreds of hours of display time. The display is one of the leading power suckers in laptops (the cpu is ususally the prime culprit). Unless it's a reflective lcd display (think calculator type where there is no backlight) it should drain the batter in a few hours.
But Windows 2K+, Linux, and most Unicies have full IPSec built in that will do 3DES encrypted VPN with SSL Cert authentication. Might want to check out what you have already. I know from experience it can be a b*tch to get cross-platform working correctly, but it certainly can be done.
Eep! I should have known better than to post at 8:05 am.
Where's the edit button.....
How is Microsoft lowering TCO when one small continent will need over half a million more people just to keep Windoz running?
Sounds like one more piece of ammo for Linux, the BSDs, or even Apple.
"Other than building the machine itself, the main challenge for us has been getting the computer systems to talk to each other and then to interact with all the hardware," said Mr Shipman.
These guys are pretty piss-poor scientists. Having troubles with an overly and unnecessarily complex system. Trying to use finesse to gain distance when additional power is highly available. Flings 6 boots; have they thought about counterweight problems, balance, efficiency, etc. These guys need a large dose of KISS engineering if they want to produce a winner.
Not to mention: Just because I drop a hammer on you, and you experience pain, does not mean that you or the hammer exist.
/.
This is a Philosophy 101 level material. I would think more people would have taken it. Of course, this is
Definately agree with that, both opinions would be the most useful. /.)?
But if you have to choose one over the other, which would you rather have (remember it will be published on
I would rather take the experienced user over the student in most cases. The OP seems to see things differently.