I've wondered that myself. It would seem that drinking cold water (or ice!) would be an excellent way to lose weight, but it doesn't seem to be that way...
Is that any better than just pumping diesel exhaust into the air? At least with the waste from a reactor, it's all in one place - you can move it around at will. Fossil fuels, OTOH, make us breathe the crap in, plants absorb it, it pollutes EVERYTHING.
I'd rather have it in a giant bucket than in my lungs, in my food, in my water... It can still leak from its container, but that's more easily managed than dumping it directly into the atmosphere!
I don't think you can count XP as "win2k+0.1" because win2k was designed to be a workstation and server OS, whereas XP is useless as a server. Win2k was the latest server OS until very recently (with Win2k3 floating around.)
The significant difference between booting to login-screen and booting to the desktop comes from all the apps set to load for a user, such as aim, icq, msn, some virus scanners (most should load as a service), volume control apps, video driver helpers, not to mention explorer itself! Ever used a person's computer and seen 95371 systray apps? They (well, most) load on login, not on boot.
Linux starts its services before it brings up the password prompt. Windows loads, displays the login prompt and continues starting services in the background.
I've never seen that problem. You may want to try one of the other clients, and see if that helps - there are several "experimental" clients that you could try. Just ask google for bittorrent experimental.
That was an extremely good article on that particular phenomenon/conspiracy. I've run across "chemtrail" sites before, and was frightened - not from the "data", but the people.
A single torrent can contain multiple files, and they're all downloaded at once as part of a single torrent (BT doesn't differentiate between a set of files and a single file).
There's still the issue that multiple torrents will trample on each other's bandwidth, but that's a problem that faces all P2P apps. eMule's solution is to change the priority of shared files dynamically based on the number of requests for each file. The more a file is requested, the lower the priority gets so all its requests don't prevent the transfer of "rare" files.
Comparison of the data confirmed the modified shape of the test aircraft altered the sonic boom as expected.
They're modifying the shape of the aircraft, comparing it to the old design and seeing how the data changes between runs. Saying "Wow that means it sucks" is reading too much into it, IMHO. Any experiment has a control to eliminate unexpected varaibles, in this case that could be atmospheric differences between runs (temperature and pressure, for example).
They're measuring the shape and magnitude, like the article says, with equipment so that they can demonstrate their hypothesis. They're not just listening to it and saying "Yup sounds different."
I think this would be much more useful when you're away from an internet connection.
Photographers with digital cameras out on photo shoots can have a 20, 40, whatever gb drive on their belt and a camera that uploads their images.
Your MP3 player is the headphones and accesses 20gb of mp3s.
All of a sudden your PDA has 40gb of storage instead of a tiny compactflash card.
You could store a hell of a lot of contacts for your cell phone.:)
Integrate the server with a cell phone and now your camera can upload images to your ftp site, your PDA can surf the net via bluetooth, your MP3 player gets Shoutcast streams...
It's like a NAS for your body.
Re:Could be used on cellphones, too.
on
MIT Roofnet
·
· Score: 2
My cellphone gets 120 hours of standby time but only about 160 minutes of actual talk time. I, for one, will not sacrifice nearly a week's worth of standby time just so I can relay between a tower and some guy out in the woods for a couple of hours.
This would require that not only you had enough wind/solar/etc power to run your home during the day, but also to split water during the day, enough of it to run your home at night.
Would it not be easier to have enough wind/solar/etc power to run your home during the day, selling the excess to the power company and then pulling from the grid at night? You wouldn't have the up-front cost of electrolysis/fuel cell equipment, and you wouldn't pay for the power at night since you were being paid all during the day (at peak rates, even).
Right, they slow down when they get dangerously hot. This only makes a defective system less prone to crashes.
Really, if someone's going to try to damage a system, cpuburn is the last thing they're going to install.
For one, a server that runs important services will be monitored closely, and will probably have a fairly high load as it is. Running cpuburn on it will either do nothing at all, or alert the sysadmins that something's not quite right. It will have no damaging effect on hardware.
Even in the worst case scenario, where a server has no ventilation and a heatsink caked with dust and somehow hasn't already crashed itself, cpuburn would merely lock it up. Once the cpu locks up, it will cease executing instructions and begin to cool off. No damage will occur.
If a worm wants to be malicious, cpuburn is not going to do the trick.
I think they would notice if they "threw a fan", as all decent hardware has fan and temp monitoring built in. Hell, anything newer than a Pentium II board will have fan monitoring.
I still believe that a cpu load testing tool such as cpuburn is just as damaging, or not, as a distributed client such as seti@home or any of the distributed.net projects.
No, actually, you're wrong. Read CPUburn's own documentation:
If sub-spec, your system may lock up after 2-10 minutes. It shouldn't. burn* are just an unpriviliged user processes. But it probably means your CPU is undercooled, most likely no thermal grease or other interface material between CPU & heatsink. Or some other deficiency.
So, in essence, if cpuburn crashes your system, your system is defective to begin with.
1) The Linux development team have been using BitKeeper so far.
2) The Linux development team have been developing Linux.
3) The BK servers do not run Linux.
How does this pertain to Joe Handless not being able to use a screwdriver? Seems like the Linux dev team are doing just fine. BK may not be the right tool, but it isn't (as the original poster was trying to say) because it isn't running under Linux.
The BitKeeper servers were being maintained for free, for the Linux developers! THE BITKEEPER SERVERS DO NOT NEED TO RUN LINUX in order for them to STORE the Linux source!
Why the Hell would the BitKeeper servers need to run Linux?
If a person is physically unable to use a screwdriver, then a screwdriver is not the right tool for the job.
If I have no fingers and I have to type up a report, should I just say "Well, gotta use this keyboard somehow!", or do I go find some other tool that works better for me? If you can't use a tool, it isn't the right one for the job.
This is getting quite OT - I was originally replying to someone who thought BK was the wrong tool because it didn't run on Linux. If it is the wrong tool, it's not because it runs on "the wrong OS".
Slashdot Mirror
I've wondered that myself. It would seem that drinking cold water (or ice!) would be an excellent way to lose weight, but it doesn't seem to be that way...
Is that any better than just pumping diesel exhaust into the air? At least with the waste from a reactor, it's all in one place - you can move it around at will. Fossil fuels, OTOH, make us breathe the crap in, plants absorb it, it pollutes EVERYTHING.
I'd rather have it in a giant bucket than in my lungs, in my food, in my water... It can still leak from its container, but that's more easily managed than dumping it directly into the atmosphere!
I thought the color signals were backwards compatable with black&white ones. Or is this only with NTSC?
I don't think you can count XP as "win2k+0.1" because win2k was designed to be a workstation and server OS, whereas XP is useless as a server. Win2k was the latest server OS until very recently (with Win2k3 floating around.)
:)
Just IMHO. And offtopic, of course.
The significant difference between booting to login-screen and booting to the desktop comes from all the apps set to load for a user, such as aim, icq, msn, some virus scanners (most should load as a service), volume control apps, video driver helpers, not to mention explorer itself! Ever used a person's computer and seen 95371 systray apps? They (well, most) load on login, not on boot.
Linux starts its services before it brings up the password prompt. Windows loads, displays the login prompt and continues starting services in the background.
I've never seen that problem. You may want to try one of the other clients, and see if that helps - there are several "experimental" clients that you could try. Just ask google for bittorrent experimental.
That was an extremely good article on that particular phenomenon/conspiracy. I've run across "chemtrail" sites before, and was frightened - not from the "data", but the people.
Anyway, thanks for posting the link.
I'm pretty sure it's a different problem.
People with nForce2 chipsets (motherboard chipsets, not video) had problems running Knoppix 3.2. I haven't tried the new Knoppix yet.
The idea is to let daemons gracefully shut down before the fs is unmounted. I think.
A single torrent can contain multiple files, and they're all downloaded at once as part of a single torrent (BT doesn't differentiate between a set of files and a single file).
There's still the issue that multiple torrents will trample on each other's bandwidth, but that's a problem that faces all P2P apps. eMule's solution is to change the priority of shared files dynamically based on the number of requests for each file. The more a file is requested, the lower the priority gets so all its requests don't prevent the transfer of "rare" files.
Quote from the article:
Comparison of the data confirmed the modified shape of the test aircraft altered the sonic boom as expected.
They're modifying the shape of the aircraft, comparing it to the old design and seeing how the data changes between runs. Saying "Wow that means it sucks" is reading too much into it, IMHO. Any experiment has a control to eliminate unexpected varaibles, in this case that could be atmospheric differences between runs (temperature and pressure, for example).
They're measuring the shape and magnitude, like the article says, with equipment so that they can demonstrate their hypothesis. They're not just listening to it and saying "Yup sounds different."
In fact, the article states that they had to compare a "traditional" sonic boom to the "new" sonic boom to verify that there was a change.
Yes, it's called "having a control". They measured them both to see the difference. It's common sense.
I think this would be much more useful when you're away from an internet connection.
:)
Photographers with digital cameras out on photo shoots can have a 20, 40, whatever gb drive on their belt and a camera that uploads their images.
Your MP3 player is the headphones and accesses 20gb of mp3s.
All of a sudden your PDA has 40gb of storage instead of a tiny compactflash card.
You could store a hell of a lot of contacts for your cell phone.
Integrate the server with a cell phone and now your camera can upload images to your ftp site, your PDA can surf the net via bluetooth, your MP3 player gets Shoutcast streams...
It's like a NAS for your body.
My cellphone gets 120 hours of standby time but only about 160 minutes of actual talk time. I, for one, will not sacrifice nearly a week's worth of standby time just so I can relay between a tower and some guy out in the woods for a couple of hours.
This would require that not only you had enough wind/solar/etc power to run your home during the day, but also to split water during the day, enough of it to run your home at night.
Would it not be easier to have enough wind/solar/etc power to run your home during the day, selling the excess to the power company and then pulling from the grid at night? You wouldn't have the up-front cost of electrolysis/fuel cell equipment, and you wouldn't pay for the power at night since you were being paid all during the day (at peak rates, even).
Right, they slow down when they get dangerously hot. This only makes a defective system less prone to crashes.
Really, if someone's going to try to damage a system, cpuburn is the last thing they're going to install.
For one, a server that runs important services will be monitored closely, and will probably have a fairly high load as it is. Running cpuburn on it will either do nothing at all, or alert the sysadmins that something's not quite right. It will have no damaging effect on hardware.
Even in the worst case scenario, where a server has no ventilation and a heatsink caked with dust and somehow hasn't already crashed itself, cpuburn would merely lock it up. Once the cpu locks up, it will cease executing instructions and begin to cool off. No damage will occur.
If a worm wants to be malicious, cpuburn is not going to do the trick.
I think they would notice if they "threw a fan", as all decent hardware has fan and temp monitoring built in. Hell, anything newer than a Pentium II board will have fan monitoring.
I still believe that a cpu load testing tool such as cpuburn is just as damaging, or not, as a distributed client such as seti@home or any of the distributed.net projects.
So, in essence, if cpuburn crashes your system, your system is defective to begin with.
CPUburn would do nothing to a server. All it does is peg cpu usage at 100%. Running SETI@Home would be equally dangerous.
1) The Linux development team have been using BitKeeper so far.
2) The Linux development team have been developing Linux.
3) The BK servers do not run Linux.
How does this pertain to Joe Handless not being able to use a screwdriver? Seems like the Linux dev team are doing just fine. BK may not be the right tool, but it isn't (as the original poster was trying to say) because it isn't running under Linux.
The BitKeeper servers were being maintained for free, for the Linux developers! THE BITKEEPER SERVERS DO NOT NEED TO RUN LINUX in order for them to STORE the Linux source!
Why the Hell would the BitKeeper servers need to run Linux?
If a person is physically unable to use a screwdriver, then a screwdriver is not the right tool for the job.
If I have no fingers and I have to type up a report, should I just say "Well, gotta use this keyboard somehow!", or do I go find some other tool that works better for me? If you can't use a tool, it isn't the right one for the job.
This is getting quite OT - I was originally replying to someone who thought BK was the wrong tool because it didn't run on Linux. If it is the wrong tool, it's not because it runs on "the wrong OS".
... then a screwdriver will obviously not be the right tool. I don't see how that changes anything.
The parent poster was expressing his concern that the kernel developers were using a versioning system that (gasp) didn't run on linux! Heaven forbid.
Quick, somebody make sure Linus' microwave runs linux! Linus must not be tainted!
I simply find BK an obsurd choice for linux development considering it doesn't even run under linux
Right tool for the right job. What it runs under is irrelevant.