Actually NTFS is pretty good at keeping files unfragmented.
If a program opens a new file and them immediately seeks to the end of it to fix it's size then NTFS will look for a continuous block of free space to save it in. NTFS caches all writes so it can wait to see what the program actually does with a file before committing it to disk.
It also has a system designed to reduce the fragmenting effects of small files by being able to store their data in the same block as their metadata.
The only major fragmentation problem Windows XP has is when a machine has very little RAM and it allocates a rather small page file. It then ends up needing to expand the page file repeatedly and it gets highly fragmented causing severe slow down. I think they fixed it in Vista/7 by simply specifying a sensible minimum size and expanding it in larger chunks.
Along with research done by Mark Roth with H2S, this could save lots of people.
What's with the mods today? What exactly is redundant about this? Mark Roth is working about suspended animation using controlled oxygen depletion with H2S and CO, work which has shown quite some promise in various animal models. Interesting stuff that is completely on topic. The main problem with suspended animation, be it of whole organisms or of tissues, is oxygen damage. Mark Roth depletes the oxygen in a controlled manner, the work cited in TFA is based on adding dichloroacetate, which has been shown to prevent ischemic damage in tissue. Not sure how the two would complement each other, as I am not much of a metabolism guy. Anyway, someone mod up the parent, that downmod is undeserved.
USB Floppies work, if the server BIOS supports them - the installer leans on the BIOS for device access during the early steps in the install process, so the issue is the BIOS, not the software.
I was assembling parts to build two "identical" machines for use in teaching myself about Windows Clusters under Hyper-V, and I paused when I saw $4.99 floppy drives at the retailer... I thought about it, but in the end, I choose not to because the chassis I am planning on using doesn't have an external 3 1/2" drive bay to hold the floppy drive.
Yes, the MB has a floppy controller, though that is becoming less common these days as well.
At work I keep a stash of new, unused, 3 1/2" floppies for use when there is no other option (we use a lot of older servers and desktops - older means 5-8 years old), and maybe twice a year it is just easier to use a floppy for some thing (like random BIOS update, server firmware update, etc.)... Typically there are other options, but sometimes the floppy drive option is easiest.
A standard ethernet frame 18 bytes of headers etc plus a bit of preamble (according to one website I just looked at this is 8 bytes but I think it varies with the type of ethernet being considered). TCP/IP is another 40 bytes (or a little more if there are special options) so the overhead is going to be arround 68 bytes per packet.
For a full sized packet (1500 bytes including the IP headers but excluding the ethernet headers) that's arround 5% overhead. For small packets it's much higher.
If the line is half duplex there is further overheads from the access control stuff and from sending the acks.
I think that highly depends on how used you are to working with one large workspace with multiple documents. Personally I find it's a lot of micromanagement to get windows in their place and mostly work fullscreen. Particularly I hate windowed MDI applications, they're usually full of useful solution browsers and toolboxes and stuff that is supposed to be at the left/right/bottom of screen. So I think my ideal development station would have three screens. The center one being the IDE - I might have many source files open in the IDE but the IDE itself is maximized. To the right I'd have my documentation, either if it's specs I write by, language docs, flow diagrams or documentation I write. To the left I'd be running the application, read application logs and whatnot. That sounds like a good mental workspace to me. To the left I have what is happening, to the right I have what should be happening and in the center I'm making it happen.
Well the point is that QKD only extends a now-existing secure key exchange into the future. This means: if you assume a public key scheme is safe for lets say a few hours for breaking the code then the key which you exchanged at that time using this channel is safe also in the future *even if* the classicla key is broken.
But the simple answer to you question is: yes. usually they conveniently forget it.
Unfortunately, we are stuck with the exact same situation you describe...we just moved into a new apartment building, and everything is almost perfect...except Internet. We have a choice between Comcast Cable, or the local DSL provider. Since my fiancee is a 3rd grade teacher and does a TON of work from home, and I do a lot of online gaming, a DSL line just wouldn't cut it...so, we're stuck with Comcast.
Which blows. Really bad.
Basically... the sad reality is that if thinking I'm smarter than those people makes me an elitist, I'd rather be an elitist than an idiot. Unfortunately, the reality is that everyone of those elitists probably will have more children than me- on account of I figured out how to use condoms and even more than most of the rest of slashdot on account of actually having sex sometimes.
While the smart people are on slashdot watching porn, we're not exactly the highest reproducing members of the gene-pool anymore...
There is so much wrong with this whole post, I don't even know where to start. First of all, you come off as extremely arrogant. Second of all, you put forth the hypothesis that the smartest people on the planet are all on Slashdot watching porn (except you, who apparently gets to have sex, unlike the rest of us). I hate to burst your bubble, but the IT industry is full of people like you who are basically tech janitors with an overly exaggerated view of their own self-importance.
Trust me, there are plenty of people out there who are smart, happy, capabable, social human beings. They just aren't hanging around with you.
Not the ones I've seen. (Hospital and nuke reactor backup.)
Ever see them try to spin up a 1 MW class diesel locomotive engine in winter? Its not pretty in the best of conditions, even worse if everyone's stressed out. There's a reason they don't shut off diesel loco engines in the winter. And even in TX it does get cold on occasion.
I was told in a tour that the nuke backup engines go full power in much less than 10s, but, they keep the coolant and engine block heated to operating temp 24x7 with electrical heaters, they have bizarre oil systems that are kept pumping 24x7 yet somehow don't hydrolock the pistons, they have onsite 24x7 maintenance crews, and still they occasionally break so they need multiple ones for true redundancy. I was told the only real delay in starting is something about needing to stabilize the airflow in the intake and exhaust before throwing a huge load on, something about air tanks, pneumatic starters. and how they vent. Obviously this was more than a decade ago, after 9/11 they absolutely JUMPED at the chance to get rid of tours. I was told that they have the cleanest engine oil in the state, actually cleaner than fresh in the can, because they pump it continuously thru filters 24x7.
A battery is a lot simpler, if it will switch over at all, it'll do so in a couple milliseconds, and there's not much maintenance possible, so not much to schedule and pay for.
The trouble with money is it costs too much!