Yes, i have a PC with bluray (as well as a PS3) and yes the software is pretty shit. The built in sony PS3 OS plays bluray fine, with a working remote control, supported bluray updates, etc. It also streams media from my PC, or the internet. As far as media boxes go, there is no reason to run Linux on it. If you want to mess with cell, fine - but cell is a dead platform for anything other than PS3, and you can't get supported access to all the hardware anyway. Pointless...
Rather, its a case of the process security being woefully inadequate. It should not be POSSIBLE for a dev to release something like this live without it being signed off by QA before release as certified compatible with all of the product's supported platforms. Either the QA was never performed (company policy failure - the dev has too much access to enable him to roll the def out without passing QA) OR the QA person signed off on the definition without doing their job and needs to be fired.
It requires an engineer to fuck up, AND the QA process to be completely inadequate. XP SP3 is not an uncommon platform for their AV product to run on. To diagnose one of the core OS files as "virus" on that platform, and actually push out the definition file live shows a complete lack of adequate QA.
sucks. I don't print as often as possible, not because of environmental concerns, but simply because
i can't search paper with ctrl+f, sed, or whatever
paper takes up too much space on my desk/li>
finding a particular piece of paper, and filing it is a pain in the arse
fuck paper, let it die. Sure, for things that need to be kept physically secure, a (or multiple, even) paper copy makes sense - but thats less than 1% of the information I deal with, personally.
Maybe to you quantity is more important than quality, but to me, everything Sony has done to the PS3 has made it even LESS inviting to me. The only reason I wanted it was FOR the parts they removed!
If you want a shitty underpowered linux box with insufficient RAM, i have a Pentium 4 I can sell you? Yes i agree that retroactively changing the EULA is a dick move, but to claim that people bought PS3s specifically to run linux is a bit of a stretch at best. Its a shitty linux machine.
For 99% of people there is no driving need to have much more than we currently have on the screen sizes available. For moving graphics, anti-aliasing the res we have looks plenty good enough. Throwing more pixels at the problem is going to use a lot more bandwidth and RAM to process them...
You can access the VM console through the web interface on an individual ESX host if the virtualcenter goes down. You can admin Windows over an HTTPS tunnel if you want to, or via RDP, or via the ESX web interface plugin for logging directly into the console of the Windows box.
Virtualised virtualcenter is a fully supported configuration. In fact there are benefits such as having high availability for your virtualcenter machine.
A cluster will function when virtualcenter is down, its not like if that VM dies your whole cluster shits itself.
Its not perfect, but in the scheme of things its no big deal. You can firewall off your virtualcenter so it is only visible on your management network, and the cost of a windows license in the scheme of things is fairly minimal. Rather than attempt to support all the functionality of Virtualcenter on a million different platforms, a choice was made, and guess what? it works.
Your choice of current management tools doesn't affect what you can do with the product. If all you've ever used is hammers - everything looks like a nail. Open your mind, explore the other options and you'll find that they are quite manageable.
I can and have maintained an ESX cluster over a low bandwidth link, too. You bitch about a proprietary management client OS, but ESX itself is proprietary as well?
For the record, I have managed the work clusters from my home OS X or FreeBSD box using an ipsec tunnel and RDP client just fine.
ESX does not run "on" linux. ESX (not ESXi) has a (customised RHEL based) linux virtual machine that is used to control the hypvervisor that it is running on - which you connect to via a Windows client.
The actual hypervisor is NOT linux. "ESXi" is a totally different animal and Linux is not involved at all - vmware is migrating to ESXi to get rid of the Linux VM because the vast number of ESX security updates are actually for the Linux VM used for managing the hypervisor. Windows is also required for VirtualCenter (to coordinate DRS, vmotion, etc) - but if you're running an ESX cluster then having a couple of windows boxes (VM or otherwise) is no major problem. You've spent 60-100k on a SAN, a few hosts and licenses - a couple of Windows machines to control it won't break the bank.
If you haven't put in that kind of solution (san + multiple ESX hosts + licenses) then ESX is a waste of time.
Set up a network boot windows deployment server with MDT 2010, and you can re-image machines in 20-25 minutes - 45 minutes or so including keeping user state if the OS is just fried and needs a refresh on the same good hardware.
Why root around with hypervisors, etc when all they're going to do is introduce performance problems, an additional host OS to keep updates, etc.
The new MS deployment tools (MDT 2010) are good - you can split the drivers and core OS out so that you don't need to keep creating new images for new hardware - just upload the upated drivers to your server, and bingo...
Well, the proper solution for a rootkitted box IS to replace every DLL and configuration item on the system once the rootkit is removed. Its called an OS wipe and reinstall.
You can scan them, and inspect them relatively easily for corruption. What you can't necessarily scan for with a dumb rootkit remover is modified configuration settings, modified firewall rules, added ipsec tunnels, etc - that weren't done by the rootkit, but by someone with control of it. Sure you could do that manually by going through each and every configuration item on your box, but its a lot quicker and easier to blow it away and start over.
Pretty much this. Once a machine is rooted, sure you may know what the rootkit has done, but who knows what the person with control of the rootkit has done?
Rooted machines need more than a quick patch or av scan - do that so you can secure your data, back it up and then blow it away and start over. Its the only way to be sure.
Because flash relies on adobe's shitty flash interpreter, which has more holes than swiss cheese.
Javascript/html is run by apple interpreters, which apple have QA control over.
If Flash gets exploited on the iphone and Adobe lag the typical x months before patching it, and people's iphones get owned - iphone, and thus apple, look bad.
I don't think jobs, or any sane person wants to put their company/product in that situation.
... schedule computer usage hours and maximum time with the built in user account controls on the mini. schedule internet access with SQUID on the 10 year old dell you already have.
Lock the kids out of admin/root access on the mini.
Slashdot Mirror
Yes, i have a PC with bluray (as well as a PS3) and yes the software is pretty shit. The built in sony PS3 OS plays bluray fine, with a working remote control, supported bluray updates, etc. It also streams media from my PC, or the internet. As far as media boxes go, there is no reason to run Linux on it. If you want to mess with cell, fine - but cell is a dead platform for anything other than PS3, and you can't get supported access to all the hardware anyway. Pointless...
Excuse me if I fail to take software advice from some noob who isn't capable of getting media files off a hosed XP box...
It should not be possible for the coder to skirt QA. He should not have the security access to push the change out to production.
This is going to cost McAfee a shitload.
It requires an engineer to fuck up, AND the QA process to be completely inadequate. XP SP3 is not an uncommon platform for their AV product to run on. To diagnose one of the core OS files as "virus" on that platform, and actually push out the definition file live shows a complete lack of adequate QA.
fuck paper, let it die. Sure, for things that need to be kept physically secure, a (or multiple, even) paper copy makes sense - but thats less than 1% of the information I deal with, personally.
Like banning people from xbox live for upgrading their hard drives?
If you want a shitty underpowered linux box with insufficient RAM, i have a Pentium 4 I can sell you? Yes i agree that retroactively changing the EULA is a dick move, but to claim that people bought PS3s specifically to run linux is a bit of a stretch at best. Its a shitty linux machine.
For 99% of people there is no driving need to have much more than we currently have on the screen sizes available. For moving graphics, anti-aliasing the res we have looks plenty good enough. Throwing more pixels at the problem is going to use a lot more bandwidth and RAM to process them...
...the inaugural obfuscated python programming contest...
Virtualised virtualcenter is a fully supported configuration. In fact there are benefits such as having high availability for your virtualcenter machine.
A cluster will function when virtualcenter is down, its not like if that VM dies your whole cluster shits itself.
Its not perfect, but in the scheme of things its no big deal. You can firewall off your virtualcenter so it is only visible on your management network, and the cost of a windows license in the scheme of things is fairly minimal. Rather than attempt to support all the functionality of Virtualcenter on a million different platforms, a choice was made, and guess what? it works.
Your choice of current management tools doesn't affect what you can do with the product. If all you've ever used is hammers - everything looks like a nail. Open your mind, explore the other options and you'll find that they are quite manageable.
I can and have maintained an ESX cluster over a low bandwidth link, too. You bitch about a proprietary management client OS, but ESX itself is proprietary as well?
For the record, I have managed the work clusters from my home OS X or FreeBSD box using an ipsec tunnel and RDP client just fine.
The actual hypervisor is NOT linux. "ESXi" is a totally different animal and Linux is not involved at all - vmware is migrating to ESXi to get rid of the Linux VM because the vast number of ESX security updates are actually for the Linux VM used for managing the hypervisor. Windows is also required for VirtualCenter (to coordinate DRS, vmotion, etc) - but if you're running an ESX cluster then having a couple of windows boxes (VM or otherwise) is no major problem. You've spent 60-100k on a SAN, a few hosts and licenses - a couple of Windows machines to control it won't break the bank.
If you haven't put in that kind of solution (san + multiple ESX hosts + licenses) then ESX is a waste of time.
If you do it right, hardware upgrades are no problem either in Linux or Windows. You just need to make proper use of the available tools.
Aston Martin, Bentley and Lotus are all doing fine. How are GM and Ford?
Why root around with hypervisors, etc when all they're going to do is introduce performance problems, an additional host OS to keep updates, etc.
The new MS deployment tools (MDT 2010) are good - you can split the drivers and core OS out so that you don't need to keep creating new images for new hardware - just upload the upated drivers to your server, and bingo...
Joe sixpack is a cock who needs his machine to BSOD and become unrecoverable before he learns.
Probably because it asks for the WGA tool and is incompatible with Microsoft Windows TDK edition.
Well, the proper solution for a rootkitted box IS to replace every DLL and configuration item on the system once the rootkit is removed. Its called an OS wipe and reinstall.
You can scan them, and inspect them relatively easily for corruption. What you can't necessarily scan for with a dumb rootkit remover is modified configuration settings, modified firewall rules, added ipsec tunnels, etc - that weren't done by the rootkit, but by someone with control of it. Sure you could do that manually by going through each and every configuration item on your box, but its a lot quicker and easier to blow it away and start over.
Rooted machines need more than a quick patch or av scan - do that so you can secure your data, back it up and then blow it away and start over. Its the only way to be sure.
Javascript/html is run by apple interpreters, which apple have QA control over.
If Flash gets exploited on the iphone and Adobe lag the typical x months before patching it, and people's iphones get owned - iphone, and thus apple, look bad.
I don't think jobs, or any sane person wants to put their company/product in that situation.
Its the objective-c application frameworks - and they live on quite happily in OS X, iphone, ipad, ipod, etc.
Lock the kids out of admin/root access on the mini.
Job done.
see: http://www.youtube.com/watch?v=j02b8Fuz73A
I've got an ad from 1984 for a Mac that included a SCSI port.