I would like to reserve judgement until I see the episode
I saw the episode last night, and to say that it was anti-gamer is total BS.
The CSI shows always have a range of psycopaths, sociopaths, mobs and generally not-nice people on it. So, what do you expect when the plot "hook" is video games? Mother Teresa playng Pac Man?
There does, though, have to be some h/w support for shared-disk. Cluster Interconnect, anyone????
What, like SCSI? FC?;) It would re-complexify the situation, but you can just hook up a bunch of SCSI controllers to a chain. Typically this is used for a Hot/Cold situation, but some solutions are Hot/Hot.
Huh? A chain? That's the least-redundant topology.
In 32-bit mode you can still accees the upper and lower halves of the lower 16-bits as [abcd]h and [abcd]l. There is also a command to swap the lower 16 bits with the upper 16-bits
Note that when you want to synchronize nodes that are not collocated, then a SAN does not work anymore.
But you can replicate IO across (high-end) SANs up to several hundred km. Totally OS-independent.
We'e talking serious money though...
This looks like a religious war between shared-disk and shared-nothing solutions but a SAN and its admin cost is usually not compatible with someone seeking for an open source solution. If you can afford the SAN, why not just using Oracle RAC?
SAN isn't the only way to do shared-disk clusters. VMS has been doing it for 20 years, and obviously SANs weren't around back then.
There does, though, have to be some h/w support for shared-disk. Cluster Interconnect, anyone????
You can fit two 16 bit integers in the space of a 32-bit register or any other memory device.
In 16-bit "mode", the x86 lets you access the upper and lower halves of the [abcd]x registers as [abcd]l and [abcd]h.
While the registers were extendex to the 32-bit e[abcd]x registers, and the lower 16 bits are still accessible via [abcd]x, there is not, TTBOMK, any way to access the upper 16 bits.
This chap is asking about the server, not the desktop.
But presumably the video-editing desktop will also be plugged into outlets in the same house that the server is in, thus drawing electricity from the same limited supply of electricity.
Hopefully the desktop CPU is an Athlon64, a Pentium M or a PowerPC.
Our shop ran for over a year before we had to do a full restore for one of the upper management... the incrementals were fine, but the fulls weren't, so we couldn't get shit back)
Shame on your shop for not testing the backups. But you know that now...
plug the firewire disks into it, and have an image up within 30 minutes.
How long does it take to back up "many terabytes" to disk?
And how often do you back it up?
We need to back up 3TB every other night, and keep the those backups for a month. Even with the new 500GB drives, that would mean a minumum of (3000/500)*30 = 180 drives. Because you won't be completely filling each disk, it would be more like 200+ drives. Managing that many drives would be a royal hassle. (Compression, you say, would cut the number of disks needed. But that compression is done on the host, which would cut into the amount of CPU available to the nightly batch processing.)
That's why robot silos and bar-coded tapes are so useful. A dozen tape drives (with built-in h/w compression), a silo with 140 tapes and a cron job that backs up the data in the middle of the night. Come in the next morning, remove last night's tape, and box them up for Iron Mountain, which swings a delivery van around retuning the "today - 1 month" tapes while picking up today's tapes.
Windows, SQL Server, IIS,.NET, ActiveX & IE are all created by a single company, the s/w colossus Microsoft.
The vituperation that should be aimed at MSFT is often wrongly aimed at "Windows". If IIS, SQL Server & IE were all written by separate non-MSFT companies, and MSFT only built the base OS (no IE, no WMP, no Office) and VisualStudio, then MSFT would obviously take a lot less heat.
For multi-TB systems, why aren't you all using multiple high-end (LTO 6 or SDLT-320) tape drives? With autoloaders, you kick them off at night, come in the next morning, take them off site and you're done.
Slashdot Mirror
I would like to reserve judgement until I see the episode
I saw the episode last night, and to say that it was anti-gamer is total BS.
The CSI shows always have a range of psycopaths, sociopaths, mobs and generally not-nice people on it. So, what do you expect when the plot "hook" is video games? Mother Teresa playng Pac Man?
If it were me, I'd keep my mailbox on a USB drive and physically move it between each machine.
Now that's a clever idea.
Better encrypt it, though, since those things get lost easy.
How will this interact with the Do Not Call bill
DNC is for unsolicited calls originated by the seller.
This service implies, by definition, that you are soliciting a call from them.
most OSS projects have about a dozen key programmers who do 99.999999% of all the work.
Because big, complicated systems are, well, big and complicated, and it takes time to learn the ins and outs of the code.
And I'd change it to 99% of the work.
As far as I know, MS hasn't been in trouble over their office suite w/the ftc, why would they do this?
RTFA. They don't want to lose gov't business.
And how much of your soul will you have to sign away in order to use this?
.NET to ECMA, and it didn't have any license fees attached to it, so that might be a good sign.
The question then to ask is what the ECMA policy is on licensing standards.
MSFT also submitted part of
AMD has beaten Intel where marketing makes a difference, at Retail.
I don't agree with that. A majority of home computers are sold by mail order, and the 800 lb gorilla in that space is Dell.
There does, though, have to be some h/w support for shared-disk. Cluster Interconnect, anyone????
;) It would re-complexify the situation, but you can just hook up a bunch of SCSI controllers to a chain. Typically this is used for a Hot/Cold situation, but some solutions are Hot/Hot.
What, like SCSI? FC?
Huh? A chain? That's the least-redundant topology.
I was agreeing with you.
In 32-bit mode you can still accees the upper and lower halves of the lower 16-bits as [abcd]h and [abcd]l. There is also a command to swap the lower 16 bits with the upper 16-bits
Ok, yeah, you're right.
Still, there's no way to access the high 16-bits.
Besides, this ("That can't have happened because we have no evidence that it did.") is just logically wrong.
Any mathematician will tell you that.
Note that when you want to synchronize nodes that are not collocated, then a SAN does not work anymore.
But you can replicate IO across (high-end) SANs up to several hundred km. Totally OS-independent.
We'e talking serious money though...
This looks like a religious war between shared-disk and shared-nothing solutions but a SAN and its admin cost is usually not compatible with someone seeking for an open source solution. If you can afford the SAN, why not just using Oracle RAC?
SAN isn't the only way to do shared-disk clusters. VMS has been doing it for 20 years, and obviously SANs weren't around back then.
There does, though, have to be some h/w support for shared-disk. Cluster Interconnect, anyone????
You can fit two 16 bit integers in the space of a 32-bit register or any other memory device.
In 16-bit "mode", the x86 lets you access the upper and lower halves of the [abcd]x registers as [abcd]l and [abcd]h.
While the registers were extendex to the 32-bit e[abcd]x registers, and the lower 16 bits are still accessible via [abcd]x, there is not, TTBOMK, any way to access the upper 16 bits.
The same goes for the 64-bit r[abcd]]x registers.
This chap is asking about the server, not the desktop.
But presumably the video-editing desktop will also be plugged into outlets in the same house that the server is in, thus drawing electricity from the same limited supply of electricity.
Hopefully the desktop CPU is an Athlon64, a Pentium M or a PowerPC.
Our shop ran for over a year before we had to do a full restore for one of the upper management ... the incrementals were fine, but the fulls weren't, so we couldn't get shit back)
Shame on your shop for not testing the backups. But you know that now...
plug the firewire disks into it, and have an image up within 30 minutes.
How long does it take to back up "many terabytes" to disk?
And how often do you back it up?
We need to back up 3TB every other night, and keep the those backups for a month. Even with the new 500GB drives, that would mean a minumum of (3000/500)*30 = 180 drives. Because you won't be completely filling each disk, it would be more like 200+ drives. Managing that many drives would be a royal hassle. (Compression, you say, would cut the number of disks needed. But that compression is done on the host, which would cut into the amount of CPU available to the nightly batch processing.)
That's why robot silos and bar-coded tapes are so useful. A dozen tape drives (with built-in h/w compression), a silo with 140 tapes and a cron job that backs up the data in the middle of the night. Come in the next morning, remove last night's tape, and box them up for Iron Mountain, which swings a delivery van around retuning the "today - 1 month" tapes while picking up today's tapes.
Well, no.
See, there are 2 factors here:
it's many terabytes
For multi-TB systems, why aren't you all using multiple high-end (LTO 6 or SDLT-320) tape drives? With autoloaders, you kick them off at night, come in the next morning, take them off site and you're done.
but in this case the OP isn't pretending that a single RAID array counts as backup.
Ah, yes, you're right. My eyes passed right over the " It is backed up nightly onto a large raid system.
My first thought would be external firewire disks that "you" bring home.
It is backed up nightly onto a large raid system, and then once a week it is backed up to dvd from the raid.
And if on the 6th day the RAID controller goes haywire and screws up your data, you've lost 6 days of inserts/updates/deletes.
Maybe your data is pretty static, but for most 99.9% of businesses, daily backups are essential.
No, not free-hand, of course not. Pardon if that's what I implied.
Ever tried cutting a perfect (well, as close to perfect as you can get) with a manual machine?
People were cutting perfect circles for 100 years before CNC machines became available. It and straight lines are probably the simplest things to cut.
According to TFA it was donor sperm - which implies that papa knew.
According to RFA, his donor had been anonymous.
I figure the US owes me
Ah, the key phrase. You feel entitled. Yes, you would be happier in a Nanny Society.
Bon Voyage.
I am probably less likely to get in trouble in a less corrupt country.
That is so guileless, it's heartwarming and sad at the same time.
Bad comparison, DEC has been gone from the business for quite a while. DEC went under
No, that's the point. Unlike MSFT, DEC actually was a sinking ship that, unlike IBM, was unable to adjust to the New World Order.
OP thinks that is sinking just like DEC was.
HP is probably sinking too, FWIW.
Thanks, Bob & Carly, for killing 2 great companies!!!