Take a look at our nice little project to change the face of storage on Linux, with snapshotting, replicating, NFS and Samba serving, and loads of cutting edge storage technology. Plenty of kernel and userspace code still to design and implement, to make our already-working system better, faster, shinier. 3D gui? Sure, we'll take it.
Props to LG for going beyond the call of duty in crediting their suppliers. That is sort of required by the licences. If you distribute binaries, you need to mention the GPL and make available any source for modifications (or something like that). Not exactly "beyond the call of duty". There were not required to dedicate the entire back page of the manual to GPL credits. I thought well of LG when I saw that.
I find all the 'reporting' on OOXML very hard to belive. I don't see how its possible to publicly bribe so many board member in so many countries and get away with it. The truth must surely be a little more plain -- that the process is working (at least the same as it would for any other standard) and nobody is greasing anybody's palm. So you think Microsoft cannot order its "partners" to stuff meetings and vote for its proposals by offering sweeter deals on Microsoft licenses, and implying license price increases ahead for those who do not cooperate? You are naive. Especially since Microsoft has been found guilty in federal court of employing similar tactics more than once.
I never quite understand the comments along the lines of "The only thing this little machine has going for it is size" - isn't that exactly what it needs to have going for it? That and flash disk.
...and by the way, note that the pcworld reviewer who wrote that negative review got 483 thumbs down for his efforts. On Amazon the set is highly rated, and I am more than pleased with it. Ideal match for a PS3.
The LG TV I picked up last week runs Linux, which I noticed because the last page of the manual credits various GPL and open source software used in the TV, including Linux and Busybox and other projects. Props to LG for going beyond the call of duty in crediting their suppliers.
Sixteen Gigabytes of memory, Eight 6 GHz 64 bit processors, 3.2 Terabytes of disk, 9,000 x 5,000 resolution. Otherwise not much different. Still only 4 hours worth of battery.
You would prefer Microsoft's completely closed, completely proprietary platform to defeat Microsoft's open-to-all, zero-cost-of-entry platform? Microsoft's platform is far from open to all, you have to run Windows to use it and millions of people prefer not to do that. So yes, I would prefer that Microsoft cannibalize itself into oblivion and have fun doing it.
What utopia do you live in, and do you have room for one more? I like my utopia, thankyou, it feels good. It is the land of the free and the home of the brave. The one thing I really missed in open source is the game scene, but now thanks to PS3 I have a very nice way to cover the dark times between where the open source game software scene is now and where it needs to be.
There are already encouraging signs: you now see cross-platform libraries out there like Speed Tree and Havok that are so good that every game house licenses them instead of coding their own. Both of these examples will eventually be superseded by open source libraries because it is just makes a lot of financial sense to the game houses to support that, now that they can no longer afford the time to develop such common components themselves.
WELL - It sounds INCREDIBLY like the SuperDisk/SuperVolume program which has existed for Windows NT-based OS' since 1995 or so is all, & why I commented here on it There are similarities, which is not surprising since the concepts of writeback and writethrough caching are older than the hills. Remember Smartdrv? And you can be sure IBM and others were doing both way, way earlier.
But: The system administrator chooses the desired mode at installation, this means the superdisk guys (you?) did not have that essential bit that allows ramback to be used with data that has to be perserved, and has to support transactions at ramdisk speeds. This is the notion that you can put the virtual disk into a flush mode, and it will later go synchronous when flushing completes. The "depends on a UPS" bit.
The game play speed on Unreal Tournament III for the PS3 runs 15% slower than the Windows version. This is to say that independent of actual system or frame rate, perceptually the PS3 version will not feel as fast. However the controls should respond in a similar way. Interesting, didn't know that. But it is obvious why it should be so: aiming with a 3/4 inch joystick using delta control is just a much slower process than aiming with a mouse, using direct control. Hence the need to slow the game down to achieve similar perceptual difficulty. I don't think it was a response to Halo at all, just that the same problem is solved in the same way.
I would like to see the joysticks on Sony's controller just a little longer next time round, or maybe a rev of the current generation. I would certainly repurchase to get a controller I can operate with higher precision.
I just want to say, I have been wooed away from the traditional mouse+keyboard PC control system for first person games. I like playing with a console controller equally well now, and basically it comes down to, I can play the console sitting on the sofa but I need to sit at a desk to play a PC game. Both fun, but really, sitting at the desk reminds me of work. Give me my potato time please, and give it to me with a console controller.
I really don't like the idea that this is racing with the UPS. When the battery gets old it's ability to hold a charge drops and a timeout that was sufficient in the old days won't be now. I've also had situations where the battery was supposed to tide you over till the generator kicked in; but the system was never tested for the generator failing at exactly the wrong moment. That is why you use dual power supplies with independent UPS units on each so you can regularly swap out the UPS unit for a known-good one, and then test the swapped-out unit. Preemptive maintenance. For good measure, raid1 the whole arrangement, giving a total of 4X redundant UPS units. Still worried? Then I sincerely hope you do not get hit by a meteorite tonight.
The flaw in your atomic commit proposal is that after a period of continuous writing the ramdisk will outrun the physical disk and then ramdisk writes will have to start waiting on physical disk completions, dropping your transaction rate down from microseconds range to milliseconds range.
Not that I have any faith either in that guy, but sure would love PC gaming to win over consoles. Except that it is not PC gaming, it is Windows gaming. So given that choice, I would prefer that Windows gaming be defeated by PS3, Wii, and yes, even XBox 360.
And return stronger as genuine, cross-platform PC gaming.
2. The console may not display the error since I'm running nvidia X11 drivers. Just say no to buggy closed source secret interface spec drivers and buy AMD for your next MythTV box. Turn the NVidia box into a firewall or something.
All the standards process means is that if OOXML is accepted and someone wants to claim their product is OOXML they have to comply with the spec. It does not mean that its open, unencumbered or any good. It does not even mean that it has to work. It does not mean that you have to use the result. But it should mean that proper procedure was followed in formalizing a standard, which does not appear to the case with OOXML.
Surely, running "cat/dev/backing >/dev/null" should populate the buffer cache as fast and well as populating a Ramback Except that in Linux, file data is cached in the "page cache" (per-inode disk mapping) not the buffer cache. So pre-populating the buffer cache does you no good at all, you need to individually populate each file. A big mess to implement efficiently.
If you are planning on having a few minutes' worth of UPS backup then why would you need to write to the hard drive continuously? Keep the hard drive spun down (saving power). If the system is being shut down, or AC power fails, then spin up the drive and make a backup of your ramdisk, thus being ready to restore when the power comes back up. Good point. The main reason for continuous flushing to disk is to keep the dirty cache flush window as small as possible in case line power does go out. But since you know the window is big enough for the worst case, then why not just suspend writeback entirely until needed? This probably deserves to be a driver option.
One very small reason for keeping the disk spinning: the most common failure mode for a disk is quite possibly failure to spin up.
The distinction seems to be that this 'innovation' makes calling 'sync' a lie. Not at all. By calling sync you tell ramback to be sure to get that data onto disk before power goes out.
...this means that both all your read and all your write operations will go splendidly fast. It also means that you lose if you have a sudden powerloss. With dual power supplies connected to independent UPS units, how are you going to have a sudden power loss?
Slashdot Mirror
Take a look at our nice little project to change the face of storage on Linux, with snapshotting, replicating, NFS and Samba serving, and loads of cutting edge storage technology. Plenty of kernel and userspace code still to design and implement, to make our already-working system better, faster, shinier. 3D gui? Sure, we'll take it.
...and by the way, note that the pcworld reviewer who wrote that negative review got 483 thumbs down for his efforts. On Amazon the set is highly rated, and I am more than pleased with it. Ideal match for a PS3.
Except for the European antitrust investigation, and other investigations.
The LG TV I picked up last week runs Linux, which I noticed because the last page of the manual credits various GPL and open source software used in the TV, including Linux and Busybox and other projects. Props to LG for going beyond the call of duty in crediting their suppliers.
I can assure you. Otherwise, I enjoyed that entertainment system a lot, and for that matter, flying on Virgin America. Recommended.
Sixteen Gigabytes of memory, Eight 6 GHz 64 bit processors, 3.2 Terabytes of disk, 9,000 x 5,000 resolution. Otherwise not much different. Still only 4 hours worth of battery.
You wonder why your linux box panicks? Regard that nividia binary hack with extreme suspicion.
There are already encouraging signs: you now see cross-platform libraries out there like Speed Tree and Havok that are so good that every game house licenses them instead of coding their own. Both of these examples will eventually be superseded by open source libraries because it is just makes a lot of financial sense to the game houses to support that, now that they can no longer afford the time to develop such common components themselves.
But: The system administrator chooses the desired mode at installation, this means the superdisk guys (you?) did not have that essential bit that allows ramback to be used with data that has to be perserved, and has to support transactions at ramdisk speeds. This is the notion that you can put the virtual disk into a flush mode, and it will later go synchronous when flushing completes. The "depends on a UPS" bit.
I would like to see the joysticks on Sony's controller just a little longer next time round, or maybe a rev of the current generation. I would certainly repurchase to get a controller I can operate with higher precision.
I just want to say, I have been wooed away from the traditional mouse+keyboard PC control system for first person games. I like playing with a console controller equally well now, and basically it comes down to, I can play the console sitting on the sofa but I need to sit at a desk to play a PC game. Both fun, but really, sitting at the desk reminds me of work. Give me my potato time please, and give it to me with a console controller.
The flaw in your atomic commit proposal is that after a period of continuous writing the ramdisk will outrun the physical disk and then ramdisk writes will have to start waiting on physical disk completions, dropping your transaction rate down from microseconds range to milliseconds range.
And return stronger as genuine, cross-platform PC gaming.
Did that Windows code know anything about a UPS or power management events,
or how to fully populate the cache on startup?
One very small reason for keeping the disk spinning: the most common failure mode for a disk is quite possibly failure to spin up.
...this means that both all your read and all your write operations will go splendidly fast. It also means that you lose if you have a sudden powerloss. With dual power supplies connected to independent UPS units, how are you going to have a sudden power loss?