It doesn't have to be at all heavy, the article mentions 6 kg. Remember that kinetic energy is proportional to the square of the velocity, so doubling rotational speed lets you cut weight by three quarters. Also, gyroscopic forces won't be a problem, you just mount the wheel horizontally.
Containing the stored energy in case of an accident likely requires some engineering thought, however. I suppose you would design the system so that it brakes the flywheel if it gets busted, converting the energy into heat just like normal braking.
The technical difference is that while your Core i3 has its GPU as a separate die in the same packaging, AMD Fusion has the GPU(s) on the same die as the CPU(s). The Intel approach makes for shorter and faster interconnects, the AMD approach completely removes the interconnects. The main advantage is probably (as is alluded to in the summary) related to power consumption.
The trick isn't using/dev/zero, the trick is using the seek parameter. The dd command skips nearly 8 GiB into a newly created file and writes something there. This creates a file that is 8 GiB large, but with no data (not zero, just nothing at all) in the first 8191 MiB. Therefore, the system doesn't actually write anything there, and doesn't even allocate the storage. If you read from these blocks, you will get generated zeros. This is called a sparse file.
I am still running Azureus 2 on my server, and am very happy with it. It works great and has a good selection of UI and other plugins. I haven't noticed any drawbacks from the release of Vuze. On my laptop, I run Azureus 3, which was released with Vuze. Per personal preference, I don't run the Vuze layer, though. I am very happy with that version too.
Now there's a version 4 out, which supposedly boasts a lot of enhancements specifically for users of the classic GUI. Azureus is still based on an extensive plugin system, and there are lots of interfaces to choose from, Vuze being one of them.
Surely, the craft itself doesn't need to bob? A large ship sitting more or less motionless on the water could have floats on beams sliding up and down along the sides of the hull. The fins would be attached to these beams.
Perhaps a more complex power transmission would be useful on that scale, generating electricity.
I did the same thing, or rather, the database crashed or something and my password was reset like three days after my old email address died. I used to be 7963, though, so not quite as low. I was too paranoid to register at the start.
I used to work with Windows tech support, and our experience there was that documents needed to be split in smaller pieces if they were to grow beyond 300 pages or so. I worked at a government agency and we sometimes worked with documents att 800-1000 pages, and there was no way Word could handle that.
A comparison: At my very first job, we used FrameMaker on Unix, and at that place we had 1200-page long technical documents that were snappy and responsive to edit on a SparcStation 10 with a 55 MHz CPU and 128 MB Ram (They consisted of master documents with several subdocuments, but that was pretty much seamless).
Same thing here in Sweden, as in pretty much every system. First, the case goes to the local court, tingsrätten. If you are unhappy with the verdict, you can appeal to the regional court, hovrätten. From there you can appeal to the supreme court, högsta domstolen, who only take cases they reckon will have bearing on future cases. This particular case might very well end up there.
Juries, however, are only used in cases concerning freedom of speech. In other cases, the local court's (tingsrätten) decisions are made by one or two judges and three or four "nämndemän". These are sort of like jurors, except they are appointed for the duration of a political term (four years) and are typically locally active politicians. The nämndemän and the judge(s) together decide whether the defendant is guilty and what the consequences should be.
That's 1 million writes per bit. With perfect load balancing, that would mean that a 1GB flash could handle 1PB of data throughput. Let's just grab a number from thin air and assume we get 1% of that, 10TB.
As I understand it, it's not swap memory on flash, but disk pagecache on flash (the sixth column in the output from 'free' on your GNU/Linux box). This means A) data isn't written as much as read, and B) if a portion of the flash gets worn out, no data is lost.
With 1GB USB pen drives available for 15 Euro, if it boosts your performance at all, it's worth it.
[...] look at Windows 2003 Server and Vista. Versioning does happen at the FS level [...] Cool, I've missed that feature completely (I read up on it at Wikipedia just now). Just goes to show how extensible the system is, I guess. Now, I have always been impressed by NTFS, but saying "versioning far beyond any *nix filesystem" in a FUSE thread was just trolling (nothing wrong with that, of course).
I used to long for proper versioning in the file system, but FUSE has shown that it can be handled beautifully in userspace. This means I can pick any underlying FS, retaining full compatability with legacy systems on a movable disk. And that's just one tiny example of what FUSE can do. It is some really nice technology, to be sure.
I reckon you are probably just trolling, but for the benefit of other readers I will respond anyway. Now, I haven't used NTFS since v1.2 (NT4) and am not a developer, so I might be way off here.
I am pretty sure NTFS does not support versioning, although it could of course be implemented in userspace by using reparse points. The standard *nix file systems don't do versioning either, by the way. Zip and RAR are not implemented in the file system, which means you cannot access zip files as directories from the command prompt, for example.
In any case, I don't think you realize what FUSE is if you compare it to a filesystem, any filesystem. NTFS can be (and has been) implemented in FUSE. While NTFS is a feature rich and extensible filesystem, it is still just a file system. See my example of seamless ssh integration - hop into a FUSE directory and voilà! You are in a directory on another box connected via ssh. Check out that list I linked to and you'll get the picture.
I must admit however that the foot is a very appealing unit in that it can be easily measured using common body parts such as the hand-elbow distance or the foot. I disagree. I am studying physics in Sweden, and am from here as well. I have no intuituve feel for any of the imperial units, although I am quick enough at doing conversions in my head. However, having done some hobbyist carpentry, I know the distance from my elbow to my middle finger is 49 cm. The distace from my thumb to my middle finger is 20 cm. I can accurately identify the size of a drill to the nearest half millimeter with my teeth. And so on.
As you mention in your last paragraph, it is all about what you are accustomed to. No system is inherently more intuitive than the next. My foot is way shorter than a foot, and if I am wearing shoes it will vary with what shoes I am wearing.
Women tend to not have as much hair on their legs as men (armpits are pretty much the same), so that has never occurred yet. But I suppose what you were really asking was if I find hairy legs and armpits inattractive, to which I'll reply; not at all.
Actually, it detects rotation and translation along three axes, and also has two dual-axis thumb levers. So that's seven axes, and ten degrees of freedom.
I have an Ati 9250 in my desktop machine, and an integrated Intel 855 in my laptop. Both run perfectly with open drivers, and the Intel is slightly better performing. The desktop has slightly more CPU power (1.8GHz Barton vs 1GHz Pentium-M) and a gig more RAM, and 3D apps run pretty much the same, with a slight edge to the Intel.
I would expect the 965 to be much better performing than the 855.
Slashdot Mirror
It doesn't have to be at all heavy, the article mentions 6 kg. Remember that kinetic energy is proportional to the square of the velocity, so doubling rotational speed lets you cut weight by three quarters. Also, gyroscopic forces won't be a problem, you just mount the wheel horizontally.
Containing the stored energy in case of an accident likely requires some engineering thought, however. I suppose you would design the system so that it brakes the flywheel if it gets busted, converting the energy into heat just like normal braking.
"Who said that? I'll kill them with my power!" - Homer Simpson, S19E03
Indeed. The future of x86 seems to lie in cell-like heterogenous multicore. This is probably what will happen with Larrabee as well.
The technical difference is that while your Core i3 has its GPU as a separate die in the same packaging, AMD Fusion has the GPU(s) on the same die as the CPU(s). The Intel approach makes for shorter and faster interconnects, the AMD approach completely removes the interconnects. The main advantage is probably (as is alluded to in the summary) related to power consumption.
The trick isn't using /dev/zero, the trick is using the seek parameter. The dd command skips nearly 8 GiB into a newly created file and writes something there. This creates a file that is 8 GiB large, but with no data (not zero, just nothing at all) in the first 8191 MiB. Therefore, the system doesn't actually write anything there, and doesn't even allocate the storage. If you read from these blocks, you will get generated zeros. This is called a sparse file.
IMDb lists 438,664 theatrically released movies.
Source: IMDb statistics page
I am still running Azureus 2 on my server, and am very happy with it. It works great and has a good selection of UI and other plugins. I haven't noticed any drawbacks from the release of Vuze. On my laptop, I run Azureus 3, which was released with Vuze. Per personal preference, I don't run the Vuze layer, though. I am very happy with that version too.
Now there's a version 4 out, which supposedly boasts a lot of enhancements specifically for users of the classic GUI. Azureus is still based on an extensive plugin system, and there are lots of interfaces to choose from, Vuze being one of them.
Surely, the craft itself doesn't need to bob? A large ship sitting more or less motionless on the water could have floats on beams sliding up and down along the sides of the hull. The fins would be attached to these beams.
Perhaps a more complex power transmission would be useful on that scale, generating electricity.
I did the same thing, or rather, the database crashed or something and my password was reset like three days after my old email address died. I used to be 7963, though, so not quite as low. I was too paranoid to register at the start.
I used to work with Windows tech support, and our experience there was that documents needed to be split in smaller pieces if they were to grow beyond 300 pages or so. I worked at a government agency and we sometimes worked with documents att 800-1000 pages, and there was no way Word could handle that.
A comparison:
At my very first job, we used FrameMaker on Unix, and at that place we had 1200-page long technical documents that were snappy and responsive to edit on a SparcStation 10 with a 55 MHz CPU and 128 MB Ram (They consisted of master documents with several subdocuments, but that was pretty much seamless).
Same thing here in Sweden, as in pretty much every system. First, the case goes to the local court, tingsrätten. If you are unhappy with the verdict, you can appeal to the regional court, hovrätten. From there you can appeal to the supreme court, högsta domstolen, who only take cases they reckon will have bearing on future cases. This particular case might very well end up there.
Juries, however, are only used in cases concerning freedom of speech. In other cases, the local court's (tingsrätten) decisions are made by one or two judges and three or four "nämndemän". These are sort of like jurors, except they are appointed for the duration of a political term (four years) and are typically locally active politicians. The nämndemän and the judge(s) together decide whether the defendant is guilty and what the consequences should be.
I admin a varied collection of sites in Swedish. The metrics for a couple of these over the last month follow.
University amateur theater (spex) site: 73.4% Firefox, 22.0% IE, 1.4% Opera, 0.2% Safari
Family discussion board and photo album: 85.9% Firefox, 7.8% IE, 1.8% Safari
Professional photographer's site: 49.4% IE, 32.9% Firefox, 13.1% Safari
Linux laptop installation instructions (English): 49.1% Firefox, 38.2% IE, 2.8% Safari, 2.8% Opera
Personal page about my boat: 59.6% IE, 35.8% Firefox, 2.2% Safari, 0.4% Opera
Woohoo! I got a point!
Sorry, but I can't resist: This would mean that you did get the penultimate processor, as penultimate means just that.
That's 1 million writes per bit. With perfect load balancing, that would mean that a 1GB flash could handle 1PB of data throughput. Let's just grab a number from thin air and assume we get 1% of that, 10TB.
As I understand it, it's not swap memory on flash, but disk pagecache on flash (the sixth column in the output from 'free' on your GNU/Linux box). This means A) data isn't written as much as read, and B) if a portion of the flash gets worn out, no data is lost.
With 1GB USB pen drives available for 15 Euro, if it boosts your performance at all, it's worth it.
I used to long for proper versioning in the file system, but FUSE has shown that it can be handled beautifully in userspace. This means I can pick any underlying FS, retaining full compatability with legacy systems on a movable disk. And that's just one tiny example of what FUSE can do. It is some really nice technology, to be sure.
I reckon you are probably just trolling, but for the benefit of other readers I will respond anyway. Now, I haven't used NTFS since v1.2 (NT4) and am not a developer, so I might be way off here.
I am pretty sure NTFS does not support versioning, although it could of course be implemented in userspace by using reparse points. The standard *nix file systems don't do versioning either, by the way. Zip and RAR are not implemented in the file system, which means you cannot access zip files as directories from the command prompt, for example.
In any case, I don't think you realize what FUSE is if you compare it to a filesystem, any filesystem. NTFS can be (and has been) implemented in FUSE. While NTFS is a feature rich and extensible filesystem, it is still just a file system. See my example of seamless ssh integration - hop into a FUSE directory and voilà! You are in a directory on another box connected via ssh. Check out that list I linked to and you'll get the picture.
FUSE is a general Filesystem-in-userspace driver, supporting a long list of filesystems.
So with FUSE ported, Windows users can also enjoy in-filesystem versioning, seamless ssh integration, RAR files as folders and so on.
As you mention in your last paragraph, it is all about what you are accustomed to. No system is inherently more intuitive than the next. My foot is way shorter than a foot, and if I am wearing shoes it will vary with what shoes I am wearing.
Women tend to not have as much hair on their legs as men (armpits are pretty much the same), so that has never occurred yet. But I suppose what you were really asking was if I find hairy legs and armpits inattractive, to which I'll reply; not at all.
Right on. I never did understand this Lolita thing.
Actually, it detects rotation and translation along three axes, and also has two dual-axis thumb levers. So that's seven axes, and ten degrees of freedom.
Shoudln't that read Apple iGene?
It's still on the front page, for crying out loud!
500 Miles on a 5-Minute Recharge?
An anecdotal comparison:
I have an Ati 9250 in my desktop machine, and an integrated Intel 855 in my laptop. Both run perfectly with open drivers, and the Intel is slightly better performing. The desktop has slightly more CPU power (1.8GHz Barton vs 1GHz Pentium-M) and a gig more RAM, and 3D apps run pretty much the same, with a slight edge to the Intel.
I would expect the 965 to be much better performing than the 855.