I got an advance copy of Ken Brown's book. I think it is still under embargo, so I won't comment on it. Although I am not an investigative reporter, even I know it is unethical to discuss publications still under embargo.
What is meant by embargo here? I'd think free speech would let one comment on a book at any time.
Unfortunately you can't do that as there isn't a notion of negative offsets from the end of a file in HTTP. So in the general case you cannot do better than read the whole thing.
There is, however, a nifty thing called a HEAD request, which gets all the headers and none of the data. Observe:
I hope that is a typo, delivering 1TB of Email is plain crazy. Counting all the spam i ever received, and all the legit mail i dont even think i come close to 1TB. Thats like - a Life time of Mail (TM)
That is exactly why they can do this - nobody is going to use even a fraction of that. I'm just wondering when they'll uncap it entirely.
That won't help if it's integrated into a laptop's case, and you don't know where. Moreover the signal's usually too strong to be completely blocked that easily.
The vorbis encoder lets you pick a VBR quality level between 1 and 9, with 3 being default. Or you can specify ABR or CBR with a bitrate, though this generally is less efficient. Why not try -q5 or -q3 and see if it sounds all right?
Incorrect. You'd have a 124.5 kilobit.wav at a bitrate of 1.5Mbps. The bitrate of the codec is determined by total size divided by time - if you just truncate it the bitrate won't change. You can downsample of course, but 16kHz mono with 8-bit samples sounds even worse than 128kbit MP3 (or any other lossy codec)
Aliasing 'rm' to 'rm -i' in your shell will only work if the person who writes the virus is kind enough to run your shell and let it load your aliases.
Some of the images were found in unallocated file space, and would have to have been placed there deliberately since cached images from browsing sessions wouldn't have been stored in unallocated space.
All that means is that the cache got full, and those pictures were deleted. There's no point in putting data in unallocated space to begin with, and anyone with the technical skills to do so (add data without allocating a file) wouldn't be caught so easily.
Can you say, "emulator"? Or, for that matter, a JIT compiler to the new CPU arch from the old GBA's opcodes. Sure, you'll throw away performance, but as long as the system's fast enough that shouldn't be a problem. There are two CPUs, I've heard, and if that's the case one can work on precompiling the code and the other executing, for instance.
Modern computers have more than enough CPU power than is needed to decode and decompress audio data in real time, and a portable player can use a hardware 3DES chip or something.
Linux implements shared-memory operations with mmaped files in a 'shmfs' memory filesystem, which supports all normal filesystem operations, including directories and etc.
For a temporary filesystem (like/tmp or some temporary RAM disk with unimportant contents) ext2 is often very fast because it lacks all the journaling stuff which is unimportant for a temporary filesystem.
Even faster and more memory efficient is something like ramfs or tmpfs, which store the data in the cache directly, avoiding filesystem issues entirely (also, if they're not full, the leftover ram can be used for programs!). They won't work for an initrd, but you can copy from an initrd to ramfs, then pivot_root and umount the ram disk.
True, and with some tweaking you can do it - the wondershaper basically makes a high priority class that gets most of the bandwith, an everything else class with a tiny bit, then lets them use the other's unused bandwith. Keep it below your maximum upstream slightly, and you won't have any long queues.
Well, I am now.
There's a e2defrag program but you shouldn't normally need it. Also, I can't vouch on how safe it is. Safest would be a tar/untar.
That is exactly why they can do this - nobody is going to use even a fraction of that. I'm just wondering when they'll uncap it entirely.
You of course mean +5, troll. And I'll be darned if I can't get +5, offtopic, too.
Unless you're just in range of a wifi hotspot somewhere, and it autoconfigures.
That won't help if it's integrated into a laptop's case, and you don't know where. Moreover the signal's usually too strong to be completely blocked that easily.
And if you're on a wireless LAN?
How about this? Or this? That took only about a minute of googling to find.
Konqueror 3.2.1 handles the slashdot user pages perfectly. Which version are you using?
The vorbis encoder lets you pick a VBR quality level between 1 and 9, with 3 being default. Or you can specify ABR or CBR with a bitrate, though this generally is less efficient. Why not try -q5 or -q3 and see if it sounds all right?
Incorrect. You'd have a 124.5 kilobit .wav at a bitrate of 1.5Mbps. The bitrate of the codec is determined by total size divided by time - if you just truncate it the bitrate won't change. You can downsample of course, but 16kHz mono with 8-bit samples sounds even worse than 128kbit MP3 (or any other lossy codec)
Even then, -f overrides -i.
They only have one rack, which is 100 TB.
Can you say, "emulator"? Or, for that matter, a JIT compiler to the new CPU arch from the old GBA's opcodes. Sure, you'll throw away performance, but as long as the system's fast enough that shouldn't be a problem. There are two CPUs, I've heard, and if that's the case one can work on precompiling the code and the other executing, for instance.
Modern computers have more than enough CPU power than is needed to decode and decompress audio data in real time, and a portable player can use a hardware 3DES chip or something.
Comparisons of filesytem are only meaningful with the same hardware, benchmarks, and kernel, so it's currently impossible.
Linux implements shared-memory operations with mmaped files in a 'shmfs' memory filesystem, which supports all normal filesystem operations, including directories and etc.
Even faster and more memory efficient is something like ramfs or tmpfs, which store the data in the cache directly, avoiding filesystem issues entirely (also, if they're not full, the leftover ram can be used for programs!). They won't work for an initrd, but you can copy from an initrd to ramfs, then pivot_root and umount the ram disk.
True, and with some tweaking you can do it - the wondershaper basically makes a high priority class that gets most of the bandwith, an everything else class with a tiny bit, then lets them use the other's unused bandwith. Keep it below your maximum upstream slightly, and you won't have any long queues.
Here you go:
* Lots of technical stuff fixed, some thingys that get those boxes that hook up to the hard drive to work added, maybe it'll go faster.