DSLR's tend to have pretty beefy batteries (and even beefier battery packs), in addition to generally using less power than standard digicams. Used in RAW mode, you can probably fill 5G and still have plenty of battery to spare.
Set your camera to RAW mode, I dare say you'll be lucky to get 15 shots out of your 256M card. At that size, 5G is around 300 shots; not even enough to drain the battery of a D70, and the amount of information from CCD's is only going to go up, not just in resolution, but in dynamic range.
You're right generally, of course, but plenty of even portable applications can use this kind of storage (and more).
Not that I'd know, not having a GigE switch, or indeed any other GigE devices, but since it comes bundled on most new motherboards I can at least look forward to my HD's no longer outpacing my LAN many times over next time I upgrade my server.
Erm, no. By "DVD video stream" I should have been more specific; I meant *uncompressed*. That ~30MBps raw stream compresses to a 3-4Mbps MPEG-2 stream; a ratio of about 70:1. At 1.2Mbps, it's approaching 200:1, and that's without a professional human tweaking the encoder for each scene.
Certainly passable for general use, but bah; give me a DVR which saves the raw MPEG-2 stream direct from my cable line;)
Still pretty low, yes; given a DVD video stream makes up about 30MBps, this is looking at a compression ratio of nearly 200:1. As a user who has most of his music in FLAC format, you can imagine my response to that;)
"Gentoo or FreeBSD (both being somewhat "cathedral like" in their organization) may have the quality of Debian, but they can't match the political stability"
Huh? How is Debian more politically stable than FreeBSD or Gentoo, and why should we care? Or do you just not like Gentoo or FreeBSD users?;)
You mean they park the drive heads when they detect, say, they've just entered freefall? Nifty; is that a feature of the specific HD's they use or what?
This graph (from this Xserve G5 page) suggests the G5's thermal characteristics are similar to the AMD64 HE range; ~55W max. Whether the same chips are used in the iMac, I don't know.
I'd say the exact opposite; getting a call from a random number I don't recognise is rarer and more noticable ("wtf is that? am I expecting any calls? what area code is that?") than one which lacks the information entirely (which is common enough even when it's not deliberate, but maybe it's a little more reliable in the US).
If you're spoofing a number I *do* recognise to trick me into answering your call, that's fraud and should be treated as such.
PI's and co can withhold their caller ID. Practical jokes are likely to be limited to spoofing known numbers, which is moving into pretty dubious territory; otherwise the user's just going to get a number they don't recognise,, not "God-The Almighty Himself".
I dunno; the only reference I can find comparing them is this, where the FreeBSD driver is said to be using a faster technique. What's your system load when network's saturated?
My machines all have NetGear FA311's, which seem to hasis0: Applying short cable fix (reg=5)ve a few of their own problems, but at least they don't have pages of pained commentary in their drivers on how awful the developers think the hardware is;)
* The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is * probably the worst PCI ethernet controller ever made, with the possible * exception of the FEAST chip made by SMC. The 8139 supports bus-master * DMA, but it has a terrible interface that nullifies any performance * gains that bus-master DMA usually offers.
Hopefully RealTek have improved matters with their more recent offerings, especially with the new consumer level GigE chips, one of which I'm using right now...
High average FPS suggests decent minimum refresh, which is what matters; at 200FPS you can bump up AA/AF, resolution, model complexity etc and still hope to achieve a decent frame rate even in the worst cases.
Plus 200FPS in one game doesn't mean 200FPS in every game; I dare say my card can push 300FPS in Quake 3, but I'm lucky to get 30 in Doom 3, and I've even dropped the resolution for it.
Personally, I'm happy to keep VSYNC on and have my GPU idling 50% of the time; I get nervous when it passes 100c. Like with CPU and network, it's the burst speed which matters typically, not whether it's all being used right this second; if my GPU/CPU can pump out frames and still have time left to manage by background tasks, that's *good*.
If ReiserFS "breaks" it replays the affected transactions, it does not need to fsck. If your drive is bad, or your installation broken, then it's unsafe with *any* filesystem, not just ReiserFS.
Right; disk and RAID controllers screw up, cables fail, memory goes bad, power failures mess up out of order and track at once writes, and all sorts of other issues can cause a filesystem to break in ways a journal cannot protect you from -- that's the entire point; it's all well and good being able to replay a journal and have it work fine 9 times out of 10, but when things go wrong I'd rather be using something mature with good, proven recovery tools than the latest and greatest just-released filesystem.
Whatever; you can have your few percentage points better performance, and I can have my quarter of a century of use and development, and we'll both try to remember to keep backups of anything important either way;)
I have the original version of this keyboard; the caps lock key on it is stiffer than the other keys and has a sloped right hand side so it's harder to hit by accident. It sounds good on paper, but in reality it's actually a bit too firm; you're certainly not going to be engaging it with a light tap.
As for the rest of the keyboard, well, it's exactly what it looks like; there's a load of keys either side of the usual ones, so for the first few days with it every time you aim for Ctrl you'll probably hit the Copy key. On the plus side, you can configure said Copy key to be Ctrl, but then the action on the outer keys is so bad even that will annoy you. I've learnt to just ignore them.
Action on the main keys is reasonable, if a bit loud for my tastes; I prefer it to most cheapo ones I've used, but I dare say you can do better.
"I don't know about XFS and ext3, but ReiserFS does not require fsck"
Duh; no filesystem *needs* fsck if you don't mind fixing it yourself with a hex editor when it breaks. Hardware failure, filesystem bugs, and entropy are all virtually guaranteed to hit you sooner or later, and then you're going to *really* want a good well tested and mature fsck tool.
"FUD!"
Yup; Fear, Uncertainty and Doubt are the three most important things when it comes to evaluating new filesystems, especially ones with a recent history of data loss, broken fsck, and moronic vendors. ext2/3 must be pretty bad to make you lot want to switch so badly:/
I humoured you, and I'm again disappointed; it still feels clunky, the URL bar doesn't behave like a normal Windows text gadget, it still needs plenty of extensions to even come close to Opera, and I still experience the odd profile munging issue despite barely even using the browser day to day.
Opera does what I want, how I want, and does it better than Firefox. And it does it without turning me into a rabid fanboi:P
If it were licensed under BSD, then companies such as MS, Apple, etc. could take the kernel, use it, change it or whatever w/o showing the changes... just like Apple has done with much of the FreeBSD code.
Both those lines should be on the same level of indent; i.e. they both have the same number of tabs in front of them, and the second line is padded with spaces to line up with the first; it'll be aligned fine whatever the tabstop.
That's a bit unfair; Ruby's libraries tend to be of high quality, and they cover a fairly respectable amount of ground even if they are a little more limited in numbers. Two or three excellent implementations is better than two or three reasonable ones and a thousand crappy ones.
It's been shown to be slower than some other languages; however speed hasn't been an issue with me yet
Slower how? Certainly development time wise Ruby is one of the fastest languages on the planet; when it comes to runtime performance it's about on par with PHP. Finding hotspots isn't difficult with the various profiling, benchmarking and testing modules about, and you'll struggle to find a language where writing a C extension to optimize out a hotspot is so easy.
Scope is broken in some cases; this is the biggest problem with Ruby and Matz admits it
Slashdot Mirror
FreeBSD has battery monitor tools galore, and supports CPU frequency scaling through ACPI and the sysctl interface. There's also an experimental port of the linux powernow-k7 module.
FreeBSD's UFS2 snapshots work quite well too. You can even fsck them :)
That statement's true about pretty much every driver framework in existance.. what's broken?
DSLR's tend to have pretty beefy batteries (and even beefier battery packs), in addition to generally using less power than standard digicams. Used in RAW mode, you can probably fill 5G and still have plenty of battery to spare.
Set your camera to RAW mode, I dare say you'll be lucky to get 15 shots out of your 256M card. At that size, 5G is around 300 shots; not even enough to drain the battery of a D70, and the amount of information from CCD's is only going to go up, not just in resolution, but in dynamic range.
You're right generally, of course, but plenty of even portable applications can use this kind of storage (and more).
Filesharing at 1000Mbps > filesharing at 100Mbps.
Not that I'd know, not having a GigE switch, or indeed any other GigE devices, but since it comes bundled on most new motherboards I can at least look forward to my HD's no longer outpacing my LAN many times over next time I upgrade my server.
Erm, no. By "DVD video stream" I should have been more specific; I meant *uncompressed*. That ~30MBps raw stream compresses to a 3-4Mbps MPEG-2 stream; a ratio of about 70:1. At 1.2Mbps, it's approaching 200:1, and that's without a professional human tweaking the encoder for each scene.
;)
Certainly passable for general use, but bah; give me a DVR which saves the raw MPEG-2 stream direct from my cable line
Argh, damn case sensitive languages ;)
;)
Still pretty low, yes; given a DVD video stream makes up about 30MBps, this is looking at a compression ratio of nearly 200:1. As a user who has most of his music in FLAC format, you can imagine my response to that
That's around 160kbps; barely enough for decent audio, never mind video.
Huh? How is Debian more politically stable than FreeBSD or Gentoo, and why should we care? Or do you just not like Gentoo or FreeBSD users?
You mean they park the drive heads when they detect, say, they've just entered freefall? Nifty; is that a feature of the specific HD's they use or what?
Some good documentation.
This graph (from this Xserve G5 page) suggests the G5's thermal characteristics are similar to the AMD64 HE range; ~55W max. Whether the same chips are used in the iMac, I don't know.
I'd say the exact opposite; getting a call from a random number I don't recognise is rarer and more noticable ("wtf is that? am I expecting any calls? what area code is that?") than one which lacks the information entirely (which is common enough even when it's not deliberate, but maybe it's a little more reliable in the US).
If you're spoofing a number I *do* recognise to trick me into answering your call, that's fraud and should be treated as such.
PI's and co can withhold their caller ID. Practical jokes are likely to be limited to spoofing known numbers, which is moving into pretty dubious territory; otherwise the user's just going to get a number they don't recognise,, not "God-The Almighty Himself".
I dunno; the only reference I can find comparing them is this, where the FreeBSD driver is said to be using a faster technique. What's your system load when network's saturated?
;)
My machines all have NetGear FA311's, which seem to hasis0: Applying short cable fix (reg=5)ve a few of their own problems, but at least they don't have pages of pained commentary in their drivers on how awful the developers think the hardware is
High average FPS suggests decent minimum refresh, which is what matters; at 200FPS you can bump up AA/AF, resolution, model complexity etc and still hope to achieve a decent frame rate even in the worst cases.
Plus 200FPS in one game doesn't mean 200FPS in every game; I dare say my card can push 300FPS in Quake 3, but I'm lucky to get 30 in Doom 3, and I've even dropped the resolution for it.
Personally, I'm happy to keep VSYNC on and have my GPU idling 50% of the time; I get nervous when it passes 100c. Like with CPU and network, it's the burst speed which matters typically, not whether it's all being used right this second; if my GPU/CPU can pump out frames and still have time left to manage by background tasks, that's *good*.
Right; disk and RAID controllers screw up, cables fail, memory goes bad, power failures mess up out of order and track at once writes, and all sorts of other issues can cause a filesystem to break in ways a journal cannot protect you from -- that's the entire point; it's all well and good being able to replay a journal and have it work fine 9 times out of 10, but when things go wrong I'd rather be using something mature with good, proven recovery tools than the latest and greatest just-released filesystem.
Whatever; you can have your few percentage points better performance, and I can have my quarter of a century of use and development, and we'll both try to remember to keep backups of anything important either way
I have the original version of this keyboard; the caps lock key on it is stiffer than the other keys and has a sloped right hand side so it's harder to hit by accident. It sounds good on paper, but in reality it's actually a bit too firm; you're certainly not going to be engaging it with a light tap.
As for the rest of the keyboard, well, it's exactly what it looks like; there's a load of keys either side of the usual ones, so for the first few days with it every time you aim for Ctrl you'll probably hit the Copy key. On the plus side, you can configure said Copy key to be Ctrl, but then the action on the outer keys is so bad even that will annoy you. I've learnt to just ignore them.
Action on the main keys is reasonable, if a bit loud for my tastes; I prefer it to most cheapo ones I've used, but I dare say you can do better.
Duh; no filesystem *needs* fsck if you don't mind fixing it yourself with a hex editor when it breaks. Hardware failure, filesystem bugs, and entropy are all virtually guaranteed to hit you sooner or later, and then you're going to *really* want a good well tested and mature fsck tool.
Yup; Fear, Uncertainty and Doubt are the three most important things when it comes to evaluating new filesystems, especially ones with a recent history of data loss, broken fsck, and moronic vendors. ext2/3 must be pretty bad to make you lot want to switch so badly
I humoured you, and I'm again disappointed; it still feels clunky, the URL bar doesn't behave like a normal Windows text gadget, it still needs plenty of extensions to even come close to Opera, and I still experience the odd profile munging issue despite barely even using the browser day to day.
:P
Opera does what I want, how I want, and does it better than Firefox. And it does it without turning me into a rabid fanboi
Yup, Apple suck for refusing to share the code they stole.
Both those lines should be on the same level of indent; i.e. they both have the same number of tabs in front of them, and the second line is padded with spaces to line up with the first; it'll be aligned fine whatever the tabstop.
That's a bit unfair; Ruby's libraries tend to be of high quality, and they cover a fairly respectable amount of ground even if they are a little more limited in numbers. Two or three excellent implementations is better than two or three reasonable ones and a thousand crappy ones.
Slower how? Certainly development time wise Ruby is one of the fastest languages on the planet; when it comes to runtime performance it's about on par with PHP. Finding hotspots isn't difficult with the various profiling, benchmarking and testing modules about, and you'll struggle to find a language where writing a C extension to optimize out a hotspot is so easy.
Do you have a ruby-talk reference?