The common platform combinations for games on steam seem to be
windows windows+mac windows+mac+linux
I've never heard of a game on steam that didn't have a windows version. Apparently there is the occasional indie title that is windows+linux but not mac but they are a tiny minority. Once you put in the effort to do windows+linux doing mac as well is not a massive jump.
So streaming mac to linux could be handy for platform compatibility in windows-free households. Streaming could also be useful to stream from a beefy PC to a less beefy one.
Not sure why i'm replying to an anonymous retard but anyway.
Water does have the strange property of expanding significantly when it freezes (and expanding slightly just before freezing). However above about 4 degrees centigrade it expands with temperature. Of the order of 0.04% per degree centigrade (depending on the current temperature)
0.04% doesn't seem like much but the oceans are about 4km deep so a 1 degree centigrade rise in average ocean temperature would be of the order of a 1.6m rise in sea level.
however the bigger concern is the release of water that is currently locked up in ice on land (ice on the water floats and so has a negigable impact on sea levels when it melts).
Afaict console game series can be divided into two main categories.
1: Those funded/published by a big publisher who is independent of the console vendors. EA, Take 2, Activision etc. These games may have a timed exclusive but if they sell well they will most likely end up on multiple platforms. 2: Those funded/published by a console vendor, these are highly unlikely to end up on any platform not controlled by that console vendor.
The downside of centralisation is when things DO go wrong they go wrong in a big way. When your centralised data storage goes on the blink or your centralised imaging system decides to reimage every machine the whole company goes down.
Of course a halfway house can be the worst of both worlds......
Sure but the test environment will almost never be absoloutely identical to the production one. So there is still room for unexpected admin screwups when deploying to the production system.
BTW, I note that the result was installing Windows 7. If it was doing that, does it mean they were running XP or Vista until just now
Reimaging machines that already have win7 on them with a new win7 image is hardly an unusual thing to do. The intended target could have been an upgrade project or it could have just been a cleanup/update job keeping the same windows version.
I suspect the machines that got accidentally reimaged were running a mixture of stuff before. Thats how things usually end up in a uni environment (at the uni I left recently I was aware of machines running NT4, 2K, XP, Vista, win7 and win8 as well as osx and multiple flavours of linux). At the time I left they were in the middle of a large scale effort to move from XP to win7 on staff/postgrad desktops (the public clusters had already been moved to win7).
That makes sense in an environment where there will be someone arround who understands how to setup database servers, how to dump and restore the data from them and so-on.
but if you are building something to "set and forget" in an environment where there will be no IT people arround after you leave and where the internet connection is likely to be spotty or nonexistent IMO a self contained single file that can be treated like a document is probablly simpler for them to deal with.
The problem with any client-server database is it's far more complex to deal with than something like access.
With a simple access DB (I guess libreoffice base is similar but I haven't used it so I don't know for sure) everything lives in the mdb file. So you can basically treat your database like a document. Back it up by copying it to an external drive, restore it by copying it back, migrate to a new computer by copying it over along with all your other documents etc. It's all stuff someone of moderate computer competance can deal with
With a client-server database setup backup and restore become far more complex, the data files, configuration of the datbase server and code/configuration of the client app (whether web based, access based, a standalone app or whatever) need to be backed up seperately from (and usually it's considered a bad idea to back up the database files just by copying them, so you have to know how the dump/restore tools for your db server work). If the restore environment isn't identical to the original you may have to reconfigure the client after restoring to get it talking to the server again.
I can deal with this and the submitter sounds like he can deal with this but it seems like the OP belives that it's unlikely else at the charity will be able to deal with it. Furthermore from the way the submission is worded it sounds like he may only be working for the charity on a short term basis.
Don't get me wrong, client-server soloutions have massive advantages in situations where you have multiple users hitting the same DB at the same time and where you have a sysadmin/DBA to look after the database but for single user "set it and forget it" setups they are the wrong tool for the job.
The other big problem with traditional raid is it only saves you if the drive either dies or reports a sector as unreadable. If it just quietly returns the wrong data then traditional raid doesn't help. That is one of the big attractions of filesystems like zfs and btrfs that combine checksuming with redundancy at the same layer.
Another poster claims that ocz had an average return rate of 5%. Some people don't return their drives because they value their privacy more than the cost of the drives or because they can't be bothered with the effort of returning them and some drives fail after the warranty runs out but before they are too small to be useful so lets suppose the overall proportion of drives has a 20% rate of "failure before becoming too small to be usable". Lets also assume that failures are independent events.
If my quick calculations are correct that would make the chance of exactly two out of three drives failing about 10%, it would make the chance of exactly zero drives failling out of 6 about 27%.
So with realistic guesses about failure rates it's very likely that there are a lot of people out there who have had multiple OCZ drives die and also a lot of people out there who have owned a moderate number of OCZ drives and had none of them die.
"So they had to force specific cables to reduce the risk of users frying stuff to acceptable levels (even with the existing "USB power delivery" standard there are combinations of cables and nonstandard adaptors that will allow such scenarios but they are much less likely than they would be with a standard that supported existing cables)."
Sure but everyone knows or should know that sticking random metal objects in electrical sockets is a bad idea, neverthless many countries now require safety shutters to make it harder to do this. While I have heard of people making cables with two household plugs joined to a single higher power socket i've never heard of anyone selling them and those who do make and use them will know they are dealing with something seriously dodgy.
Contrast this to the USB situation where using cables that have two A plugs with the power wires paralelled were very often included with USB hard drives with the obvious intent (sometimes even explicitly stated in the manual) that you would plug them into two USB ports to get more power for your drive. You don't want to create a situation where a user doing what they have always done with the cables they have always used but a new computer and drive fries stuff.
The problem is there are a heck of a lot of standard violating USB cables, adaptors etc out there. So they had to force specific cables to reduce the risk of users frying stuff to acceptable levels (even with the existing "USB power delivery" standard there are combinations of cables and nonstandard adaptors that will allow such scenarios but they are much less likely than they would be with a standard that supported existing cables).
Lets consider a hypothetical "USB high voltage" standard that was similar to the "USB power delivery" standard but worked with standard USB cables. Now suppose an end user takes one of those cables that has a second A plug with it's power pins connected in parallell with the main A plug. They plug the host plug into a "USB high voltage" source, the device plug into a "USB high voltage" device and the power plug into a conventional USB host port. The "USB high voltage" source and device negotiate 20V and fry the conventional host port.
If the plugin is running in a tight sandbox it should be easy to modify the sandbox to send the video to somewhere other than the screen without the plugin having any way to detect that this is going on.
Of course this way you will have to re-encode so there will be a performance and quality cost but it should be easilly doable and work for any website that uses this drm infrastructure.
And if you do want to hack the plugin itself (to avoid re-encoding) I can't imagine it will be too hard to poke a hole in the sandbox as well.
This is what is used in London (Oyster), at least for public transport. No change required, but no issue with battery life.
I'm pretty sure oyster is only for public transport.
Contactless debit has got very common this year.
Which brings us to one of the problems with contactless cards. When you are carrying exactly one contactless card that will work for a given system it's great, you can just slam your wallet on the reader and go.
But if you are carrying more than one that doesn't work so well. Sometimes it sees both and refuses to continue, sometimes it sees the wrong one first resulting in unexpected charges.
Note that "active lines of service" is likely to be significantly more than the number of phones in regular use since in many countries it costs very little to keep an old phone active on payg.
There is a mechanism in the GSM standard for making emergency calls on a network the phone has not authenticated with and i've never heard of a phone not supporting it.
Whether the network actually routes such calls is down to network policies and/or local laws. AIUI in the early days of mobile phones in the the did routed the but they stopped doing so due to a large number of hoax calls from such phones.
Normally, that added price somewhat does go into buying improved mechanisms
It's kinda extraordinary how accurately we have been able to measure time but even the best mechanisms are poor timekeepers compared to what can be achived with a relatively cheap quartz crystal.
last time I checked it was also illegal to kill people like you do in most other games.
Note that nintendo is primerally a maker of childrens/family games. That means that when considering what to include in a game they not only have to think about whether it will make the game illegal but about what it will do to the age rating of the game in various countries arround the world. They also have to think about what parents will think of it.
Notice how in games for little children you tend to kill monsters instead of people and in games for mid teenagers if you kill people it's in certain situations where it's either accepted by society (e.g. war) or far removed from current reality (e.g. the enemies have been possessed by aliens). There are games where you kill people in a gangland setting but they have higher age restriction on them.
Slashdot Mirror
The common platform combinations for games on steam seem to be
windows
windows+mac
windows+mac+linux
I've never heard of a game on steam that didn't have a windows version. Apparently there is the occasional indie title that is windows+linux but not mac but they are a tiny minority. Once you put in the effort to do windows+linux doing mac as well is not a massive jump.
So streaming mac to linux could be handy for platform compatibility in windows-free households. Streaming could also be useful to stream from a beefy PC to a less beefy one.
Not sure why i'm replying to an anonymous retard but anyway.
Water does have the strange property of expanding significantly when it freezes (and expanding slightly just before freezing). However above about 4 degrees centigrade it expands with temperature. Of the order of 0.04% per degree centigrade (depending on the current temperature)
0.04% doesn't seem like much but the oceans are about 4km deep so a 1 degree centigrade rise in average ocean temperature would be of the order of a 1.6m rise in sea level.
however the bigger concern is the release of water that is currently locked up in ice on land (ice on the water floats and so has a negigable impact on sea levels when it melts).
Afaict console game series can be divided into two main categories.
1: Those funded/published by a big publisher who is independent of the console vendors. EA, Take 2, Activision etc. These games may have a timed exclusive but if they sell well they will most likely end up on multiple platforms.
2: Those funded/published by a console vendor, these are highly unlikely to end up on any platform not controlled by that console vendor.
Afaict this one falls into the latter category.
Fortunately, we are no longer creating more messes like Hanford, Rocky Flats, etc.
How do you know? Did the general public know what was going on at hanford when it was active? or did the horrible details only come out later?
The downside of centralisation is when things DO go wrong they go wrong in a big way. When your centralised data storage goes on the blink or your centralised imaging system decides to reimage every machine the whole company goes down.
Of course a halfway house can be the worst of both worlds......
Sure but the test environment will almost never be absoloutely identical to the production one. So there is still room for unexpected admin screwups when deploying to the production system.
BTW, I note that the result was installing Windows 7. If it was doing that, does it mean they were running XP or Vista until just now
Reimaging machines that already have win7 on them with a new win7 image is hardly an unusual thing to do. The intended target could have been an upgrade project or it could have just been a cleanup/update job keeping the same windows version.
I suspect the machines that got accidentally reimaged were running a mixture of stuff before. Thats how things usually end up in a uni environment (at the uni I left recently I was aware of machines running NT4, 2K, XP, Vista, win7 and win8 as well as osx and multiple flavours of linux). At the time I left they were in the middle of a large scale effort to move from XP to win7 on staff/postgrad desktops (the public clusters had already been moved to win7).
That makes sense in an environment where there will be someone arround who understands how to setup database servers, how to dump and restore the data from them and so-on.
but if you are building something to "set and forget" in an environment where there will be no IT people arround after you leave and where the internet connection is likely to be spotty or nonexistent IMO a self contained single file that can be treated like a document is probablly simpler for them to deal with.
The problem with any client-server database is it's far more complex to deal with than something like access.
With a simple access DB (I guess libreoffice base is similar but I haven't used it so I don't know for sure) everything lives in the mdb file. So you can basically treat your database like a document. Back it up by copying it to an external drive, restore it by copying it back, migrate to a new computer by copying it over along with all your other documents etc. It's all stuff someone of moderate computer competance can deal with
With a client-server database setup backup and restore become far more complex, the data files, configuration of the datbase server and code/configuration of the client app (whether web based, access based, a standalone app or whatever) need to be backed up seperately from (and usually it's considered a bad idea to back up the database files just by copying them, so you have to know how the dump/restore tools for your db server work). If the restore environment isn't identical to the original you may have to reconfigure the client after restoring to get it talking to the server again.
I can deal with this and the submitter sounds like he can deal with this but it seems like the OP belives that it's unlikely else at the charity will be able to deal with it. Furthermore from the way the submission is worded it sounds like he may only be working for the charity on a short term basis.
Don't get me wrong, client-server soloutions have massive advantages in situations where you have multiple users hitting the same DB at the same time and where you have a sysadmin/DBA to look after the database but for single user "set it and forget it" setups they are the wrong tool for the job.
The other big problem with traditional raid is it only saves you if the drive either dies or reports a sector as unreadable. If it just quietly returns the wrong data then traditional raid doesn't help. That is one of the big attractions of filesystems like zfs and btrfs that combine checksuming with redundancy at the same layer.
Not really
Another poster claims that ocz had an average return rate of 5%. Some people don't return their drives because they value their privacy more than the cost of the drives or because they can't be bothered with the effort of returning them and some drives fail after the warranty runs out but before they are too small to be useful so lets suppose the overall proportion of drives has a 20% rate of "failure before becoming too small to be usable". Lets also assume that failures are independent events.
If my quick calculations are correct that would make the chance of exactly two out of three drives failing about 10%, it would make the chance of exactly zero drives failling out of 6 about 27%.
So with realistic guesses about failure rates it's very likely that there are a lot of people out there who have had multiple OCZ drives die and also a lot of people out there who have owned a moderate number of OCZ drives and had none of them die.
In many such systems there is simply no such thing as "your encryption key", a key is agreed for the session and then discarded afterwards.
Indeed, I already said that.
"So they had to force specific cables to reduce the risk of users frying stuff to acceptable levels (even with the existing "USB power delivery" standard there are combinations of cables and nonstandard adaptors that will allow such scenarios but they are much less likely than they would be with a standard that supported existing cables)."
Sure but everyone knows or should know that sticking random metal objects in electrical sockets is a bad idea, neverthless many countries now require safety shutters to make it harder to do this. While I have heard of people making cables with two household plugs joined to a single higher power socket i've never heard of anyone selling them and those who do make and use them will know they are dealing with something seriously dodgy.
Contrast this to the USB situation where using cables that have two A plugs with the power wires paralelled were very often included with USB hard drives with the obvious intent (sometimes even explicitly stated in the manual) that you would plug them into two USB ports to get more power for your drive. You don't want to create a situation where a user doing what they have always done with the cables they have always used but a new computer and drive fries stuff.
The problem is there are a heck of a lot of standard violating USB cables, adaptors etc out there. So they had to force specific cables to reduce the risk of users frying stuff to acceptable levels (even with the existing "USB power delivery" standard there are combinations of cables and nonstandard adaptors that will allow such scenarios but they are much less likely than they would be with a standard that supported existing cables).
Lets consider a hypothetical "USB high voltage" standard that was similar to the "USB power delivery" standard but worked with standard USB cables. Now suppose an end user takes one of those cables that has a second A plug with it's power pins connected in parallell with the main A plug. They plug the host plug into a "USB high voltage" source, the device plug into a "USB high voltage" device and the power plug into a conventional USB host port. The "USB high voltage" source and device negotiate 20V and fry the conventional host port.
I'd say the opposite
If the plugin is running in a tight sandbox it should be easy to modify the sandbox to send the video to somewhere other than the screen without the plugin having any way to detect that this is going on.
Of course this way you will have to re-encode so there will be a performance and quality cost but it should be easilly doable and work for any website that uses this drm infrastructure.
And if you do want to hack the plugin itself (to avoid re-encoding) I can't imagine it will be too hard to poke a hole in the sandbox as well.
This is what is used in London (Oyster), at least for public transport. No change required, but no issue with battery life.
I'm pretty sure oyster is only for public transport.
Contactless debit has got very common this year.
Which brings us to one of the problems with contactless cards. When you are carrying exactly one contactless card that will work for a given system it's great, you can just slam your wallet on the reader and go.
But if you are carrying more than one that doesn't work so well. Sometimes it sees both and refuses to continue, sometimes it sees the wrong one first resulting in unexpected charges.
Note that "active lines of service" is likely to be significantly more than the number of phones in regular use since in many countries it costs very little to keep an old phone active on payg.
There is a mechanism in the GSM standard for making emergency calls on a network the phone has not authenticated with and i've never heard of a phone not supporting it.
Whether the network actually routes such calls is down to network policies and/or local laws. AIUI in the early days of mobile phones in the the did routed the but they stopped doing so due to a large number of hoax calls from such phones.
http://www.redcross.org.uk/Wha...
IMO what really needs to happen is a decoupling of ISPs from monopoly or near-monopoly last mile communication providers.
They all have transformers in them. The transformers are much smaller and lighter because of the high frequency operation but they are still there.
Normally, that added price somewhat does go into buying improved mechanisms
It's kinda extraordinary how accurately we have been able to measure time but even the best mechanisms are poor timekeepers compared to what can be achived with a relatively cheap quartz crystal.
Do you have a link for that vulnerability, some googling isn't turning up anything much of relavence.
and the expense of building a 100+ mile bridge in some of the harshest environment known to man.
And lets not forget the expense of building the feeder infrastructure on both sides.
last time I checked it was also illegal to kill people like you do in most other games.
Note that nintendo is primerally a maker of childrens/family games. That means that when considering what to include in a game they not only have to think about whether it will make the game illegal but about what it will do to the age rating of the game in various countries arround the world. They also have to think about what parents will think of it.
Notice how in games for little children you tend to kill monsters instead of people and in games for mid teenagers if you kill people it's in certain situations where it's either accepted by society (e.g. war) or far removed from current reality (e.g. the enemies have been possessed by aliens). There are games where you kill people in a gangland setting but they have higher age restriction on them.