The cards will be available for all from 2012 but she said: "I regularly have people coming up to me and saying they don't want to wait that long."
Someone should tell Jacqui that the people who stand to make lots of money from producing ID cards for the government wanting it to be done sooner don't count as a representative sample of the British public.
8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objective support for their claims. Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings. Graphs, non-blind listening tests, waveform difference comparisons, and so on, are not acceptable means of providing support.
Filesystems are crap at managing metadata, and that includes their own; walking a directory full of files and stat()ing each one is expensive, even before you get into reading metadata from the files themselves.
I use foobar2000, and typically have it present my music to me based on my nicely organized directory structure; because it's not having to constantly ask the filesystem what said structure looks like, searches and filtering is always extremely fast (granted, I do also have a lot of in-file metadata to search), and will scale far past what would be sensible for even a patient person when dealing with a raw filesystem.
fb2k will also let you take your carefully organized directory structure and rip out metadata from the directory and file names, should you ever decide your files themselves should know things like when they were recorded. That also makes it easier to search and filter; e.g. you could use facets to make it simple to view everything recorded in a given month in a given location.
HAMMER provides similar capabilities; you can view files, directories, or entire filesystems as of specific versions. "hammer history foo" to find the history of a file, then look at foo@@[id] to view the file at any given point.
You might have a look at Sword of the Stars, from the peeps who did Homeworld Cataclysm. They just released their second expansion in GamersGate, and the original and first expansion are on Impulse.
Personally I found it more interesting than SoaSE; there's more variation between the different races.
And how many of those are a result of contaminated supplies with unpredictable strength, things that are a direct result of prohibition? It's easy to overdose when you never know how much you're going to be taking.
Yeah, and plenty of what I burned from 1999 onwards works fine. Significant chunks of it doesn't, though; some of it's degraded so far there are sizable holes in the metalic layer. Some work fine in one drive but are unreadable in another, others are readable but only very slowly. Sure, some of it's cheap-and-cheerful noname media, but quite a lot of it is high quality stuff that touts its long lifespan.
And these days they're pathetically tiny; 4.7GB? Great, I can get a pack of 100 for about 17p/each; 3.5p/GB, but only usable once, and using it all involves playing with my CD tray 200 times.
Or, I could get another HD; say, £40 for 500GB, or £80 for 1TB; 8p/GB. It's all completely accessable after plugging it in (and that's trivial with hot-swap bays), it's much faster for sequential and random access, it can all be reused and rewritten, and the drive can be repurposed for on-the-shelf backup or day to day use as I see fit.
These days, the only use I have for optical media is OS installation; I have a pack of CD-RW and DVD-RW's I can reuse, and that's it. My CD-R and DVD-R piles haven't been touched in years.
A HAMMER filesystem can be mounted with an as-of date to access a snapshot of the system. Snapshots do not have to be explicitly taken but are instead based on the retention policy you specify for any given HAMMER filesystem. It is also possible to access individual files or directories (and their contents) using an as-of extension on the file name.
Released and stable in DragonFlyBSD 2.0, and obviously BSD licensed.
Erm, unless you've given TrueCrypt the key to the hidden volume, the "safe" one will quite happily overwrite any data in it, because it doesn't know it's there.
We use Nagios in a 2 man team monitoring about 30 hosts and 200 services, including quite a few custom ones. It's not that hard, once you get used to how it works.
We store about 3 billion rows using compressed MyISAM tables. I dread to think what that'd be like using a transactional table type; MVCC generally bloats disk usage 2-4x, and compression is only supported in the very latest InnoDB.
Sure, it'd be nice to have everything in one table type, but at least some of these tradeoffs seem quite fundamental.
Like DDR2, DDR3 increases latencies to allow for higher clockrates:
While the typical latencies for a JEDEC DDR2 device were 5-5-5-15, the standard latencies for the newer JEDEC DDR3 devices are 7-7-7-20 for DDR3-1066 and 7-7-7-24 for DDR3-1333.
But remember these latencies are measured in clock cycles, so timing wise, these latencies are shorter; they just happen to have more clock ticks between them.
You could also ditch the PRNG altogether and use a standard PRNG. But that would mean a significant performance hit
How much random data does it need? An amount equal to what's being written? I guess that would be quite nasty; Yarrow can just about pump out 50MB/s given a couple of GHz of Opteron.
Problem is that the only way to detect that corruption has happened is by trying to open the files with applications understanding the format, and see them barf. However fixing the potential corruption is tricky. If I find a good solution, I am probably going to write my own storage encryption layer some day.
You could put ZFS on top of it, scrub would then pick it up. Backing the disk with multiple crypted volumes would get you redundancy. You could use block level journaling (gjournal) to help avoid partial writes, though with ZFS and ZIL that would probably be unnecessary.
GELI also supports using cryptographic hashes for authenticating data.. but of course this just means you get IO errors instead of mangled data, and it takes quite a lot of space.
Bullshit. First person cover would be fine if I could edge along a wall and peek around.
That's exactly what you do in GRAW. A single shot can kill you, so a usable cover system's vital, and it managed it without making your eyes pop out 8ft behind you.
If you want realistic vision and all that jazz, look at the relative unplayability of Op Flashpoint. Whats next, complaining that holding W doesnt have the intricicies of running over rough terrain, and that we need to use a joystick to balance the characters legs?
Oh please, there's plenty of space between Wolf3D style floating camera and Op Flashpoint style wobble-o-vision, there's no need to turn into Gears of War to make cover work. GRAW managed to make you aware of your body and your use of cover without smashing the fourth wall with a sledgehammer and without making the controls any more difficult than any other FPS.
Nano-augs were supposed to be pretty new, so they could probably explain it by saying some of the more advanced bio-mech mods just weren't ported to the new architecture.
One of the points of a FPS being first person is to add immersion; you're looking out of the protagonist's eyes, so you *are* the protagonist. Even if most of the time it's really just a floating camera, at least it's a floating camera where your eyes should be.
Now, cover systems.. fair enough. They can be done well; see, for example, GRAW. All first person, with your body actually modelled so you can see yourself, and when you enter cover you get the impression of actually.. entering cover.
But noooo, that's too hard to get right, so they're going to do what everybody else does and give you an out of body experience every time you lean against a fucking wall. None of this nonsense where entering cover is an important tactical decision because it blocks your line of sight just as much as it blocks bullets; this is a console game, so we'll make it easy and let you look around corners with magic floating vision.
And why bother spending time balancing the game when they can just give you magic regenerating health? *sigh*, they could at least make them optional augmentations, you know, like in the critically acclaimed original?
I have seen one that used extra space by mapping 32 logical sectors to 33 physical sectors, but that encryption had other problems including a weak pseudo random number generator, and potential data loss caused by the need to update two sectors which isn't done atomically
That would be GBDE. Shouldn't it be relatively easy to replace the PRNG?
Slashdot Mirror
You forgot the SSD's for ZFS secondary ARC cache. Oh, and the server.
But I thought "People 'can't wait for ID cards'":
The cards will be available for all from 2012 but she said: "I regularly have people coming up to me and saying they don't want to wait that long."
Someone should tell Jacqui that the people who stand to make lots of money from producing ID cards for the government wanting it to be done sooner don't count as a representative sample of the British public.
Frequency scaling is in the latest releases for most modernish Intel CPUs and AMD K10's.
From the HA T&C:
8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objective support for their claims. Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings. Graphs, non-blind listening tests, waveform difference comparisons, and so on, are not acceptable means of providing support.
Of course it's a blind test.
Filesystems are crap at managing metadata, and that includes their own; walking a directory full of files and stat()ing each one is expensive, even before you get into reading metadata from the files themselves.
I use foobar2000, and typically have it present my music to me based on my nicely organized directory structure; because it's not having to constantly ask the filesystem what said structure looks like, searches and filtering is always extremely fast (granted, I do also have a lot of in-file metadata to search), and will scale far past what would be sensible for even a patient person when dealing with a raw filesystem.
fb2k will also let you take your carefully organized directory structure and rip out metadata from the directory and file names, should you ever decide your files themselves should know things like when they were recorded. That also makes it easier to search and filter; e.g. you could use facets to make it simple to view everything recorded in a given month in a given location.
-watch (reruns last comand at set interval)
Linuxism:
Slightly less potentially damanging than killall, though (which on some *ix's really does kill.. all. Use pkill instead).
To be fair, Ruby had to wait for 1.9 to get GOTO support. It's right there if you build it using -DSUPPORT_JOKE.
Hey now, you know what happens when you start treating one as being better than the other.
Python: TypeError: cannot concatenate 'str' and 'float' objects
Ruby: TypeError: can't convert Float into String
Weak typing is the problem, not dynamic typing.
HAMMER provides similar capabilities; you can view files, directories, or entire filesystems as of specific versions. "hammer history foo" to find the history of a file, then look at foo@@[id] to view the file at any given point.
You might have a look at Sword of the Stars, from the peeps who did Homeworld Cataclysm. They just released their second expansion in GamersGate, and the original and first expansion are on Impulse.
Personally I found it more interesting than SoaSE; there's more variation between the different races.
Heroin/Morphine: 2,400
Cocaine: 3,300
And how many of those are a result of contaminated supplies with unpredictable strength, things that are a direct result of prohibition? It's easy to overdose when you never know how much you're going to be taking.
Yeah, and plenty of what I burned from 1999 onwards works fine. Significant chunks of it doesn't, though; some of it's degraded so far there are sizable holes in the metalic layer. Some work fine in one drive but are unreadable in another, others are readable but only very slowly. Sure, some of it's cheap-and-cheerful noname media, but quite a lot of it is high quality stuff that touts its long lifespan.
And these days they're pathetically tiny; 4.7GB? Great, I can get a pack of 100 for about 17p/each; 3.5p/GB, but only usable once, and using it all involves playing with my CD tray 200 times.
Or, I could get another HD; say, £40 for 500GB, or £80 for 1TB; 8p/GB. It's all completely accessable after plugging it in (and that's trivial with hot-swap bays), it's much faster for sequential and random access, it can all be reused and rewritten, and the drive can be repurposed for on-the-shelf backup or day to day use as I see fit.
These days, the only use I have for optical media is OS installation; I have a pack of CD-RW and DVD-RW's I can reuse, and that's it. My CD-R and DVD-R piles haven't been touched in years.
So, something like HAMMER, then?
A HAMMER filesystem can be mounted with an as-of date to access a snapshot of the system. Snapshots do not have to be explicitly taken but are instead based on the retention policy you specify for any given HAMMER filesystem. It is also possible to access individual files or directories (and their contents) using an as-of extension on the file name.
Released and stable in DragonFlyBSD 2.0, and obviously BSD licensed.
Erm, unless you've given TrueCrypt the key to the hidden volume, the "safe" one will quite happily overwrite any data in it, because it doesn't know it's there.
We use Nagios in a 2 man team monitoring about 30 hosts and 200 services, including quite a few custom ones. It's not that hard, once you get used to how it works.
Tried Munin? I was quite impressed when I installed it and found it'd auto-detected a whole bunch of locally graphable stuff.
We store about 3 billion rows using compressed MyISAM tables. I dread to think what that'd be like using a transactional table type; MVCC generally bloats disk usage 2-4x, and compression is only supported in the very latest InnoDB.
Sure, it'd be nice to have everything in one table type, but at least some of these tradeoffs seem quite fundamental.
Like DDR2, DDR3 increases latencies to allow for higher clockrates:
While the typical latencies for a JEDEC DDR2 device were 5-5-5-15, the standard latencies for the newer JEDEC DDR3 devices are 7-7-7-20 for DDR3-1066 and 7-7-7-24 for DDR3-1333.
But remember these latencies are measured in clock cycles, so timing wise, these latencies are shorter; they just happen to have more clock ticks between them.
I never played GRAW on a console, but the PC version was entirely first person.
You could also ditch the PRNG altogether and use a standard PRNG. But that would mean a significant performance hit
How much random data does it need? An amount equal to what's being written? I guess that would be quite nasty; Yarrow can just about pump out 50MB/s given a couple of GHz of Opteron.
Problem is that the only way to detect that corruption has happened is by trying to open the files with applications understanding the format, and see them barf. However fixing the potential corruption is tricky. If I find a good solution, I am probably going to write my own storage encryption layer some day.
You could put ZFS on top of it, scrub would then pick it up. Backing the disk with multiple crypted volumes would get you redundancy. You could use block level journaling (gjournal) to help avoid partial writes, though with ZFS and ZIL that would probably be unnecessary.
GELI also supports using cryptographic hashes for authenticating data.. but of course this just means you get IO errors instead of mangled data, and it takes quite a lot of space.
Bullshit. First person cover would be fine if I could edge along a wall and peek around.
That's exactly what you do in GRAW. A single shot can kill you, so a usable cover system's vital, and it managed it without making your eyes pop out 8ft behind you.
If you want realistic vision and all that jazz, look at the relative unplayability of Op Flashpoint. Whats next, complaining that holding W doesnt have the intricicies of running over rough terrain, and that we need to use a joystick to balance the characters legs?
Oh please, there's plenty of space between Wolf3D style floating camera and Op Flashpoint style wobble-o-vision, there's no need to turn into Gears of War to make cover work. GRAW managed to make you aware of your body and your use of cover without smashing the fourth wall with a sledgehammer and without making the controls any more difficult than any other FPS.
Nano-augs were supposed to be pretty new, so they could probably explain it by saying some of the more advanced bio-mech mods just weren't ported to the new architecture.
One of the points of a FPS being first person is to add immersion; you're looking out of the protagonist's eyes, so you *are* the protagonist. Even if most of the time it's really just a floating camera, at least it's a floating camera where your eyes should be.
Now, cover systems.. fair enough. They can be done well; see, for example, GRAW. All first person, with your body actually modelled so you can see yourself, and when you enter cover you get the impression of actually.. entering cover.
But noooo, that's too hard to get right, so they're going to do what everybody else does and give you an out of body experience every time you lean against a fucking wall. None of this nonsense where entering cover is an important tactical decision because it blocks your line of sight just as much as it blocks bullets; this is a console game, so we'll make it easy and let you look around corners with magic floating vision.
And why bother spending time balancing the game when they can just give you magic regenerating health? *sigh*, they could at least make them optional augmentations, you know, like in the critically acclaimed original?
I have seen one that used extra space by mapping 32 logical sectors to 33 physical sectors, but that encryption had other problems including a weak pseudo random number generator, and potential data loss caused by the need to update two sectors which isn't done atomically
That would be GBDE. Shouldn't it be relatively easy to replace the PRNG?