Not hazardous? With the notable exception that the 5.2 tons of Uranium per 1000MW per year coal plant goes up into the air.
Yes, we just said the same thing. I was referring to GPs questions about individual concrete blocks. The amount of radioactive material in a single block, or a whole building built from these blocks, is almost non-existent. At the scale require to generate 1GW of power, the radioactive material is significant.
A quick google says coal ranges from 1 to 10 ppm (parts per million) of Uranium (in the US). Up to 20 ppm is rare, but happens (in the US). Your drinking water contains 2 to 3 ppm of Chlorine, one of the deadliest gases known. It's safe to drink, but I wouldn't want to start evaporating a couple million tons of water.
The radiation hazard is negiligable. The amount of radioactive material per ton of coal is nearly 0. It's only a significant source of radioactive material when you burn a couple billion tons of it a year. Burn a couple billion tons of any solid and it will be a significant source of radioactive material. Coal does have more radioactive material per ton than most solids, but it's still a tiny amount per ton.
You get pretty much the same amount of radioactive material in blocks using fly ash as you would get from a block of stone.
Mostly people using these tapes have a robot, so they write until a tape is full, then start on the next tape. Units holding 10 tapes are pretty cheap for a company to buy.
Limit the email the account can send, and you reduce the desire for the account. Reduce the usefullness of the account, and you reduce the desire to crack the captcha on new account signups, or at least the profitability in doing so.
Doesn't this increase the desire to get more accounts faster?
My co-workers were giving me this same crap about homeschooling. After I point out that my wife is a liscensed teacher, they drop the acedemic arguments, and bring out the socialization arguments. After they meet my kids, the whole discussion never comes up again.
Everybody in our homeschooling circle is aware that homeschoolers can be improperly socialized. It's our job to make sure they are properly socialized, and it's a job we accepted when we decided to homeschool.
I will propose a counter argument: When I break down all that "social" time I had in public school, it was about 35 hours of lecture, and 5 hours of real social activity. My kids get way more interactive social time with many more children than I had in public school.
Free (beer) closed source volume manager and Filesystem. High performance and High reliability. The Enterprise version saved my ass more times than I can count, and I can count some extremely unlikely scenarios.
The only drawback (the reason I don't run it at home) is the low limits:
This free version is limited to 4 user-data volumes, and/or 4 user-data file systems, and/or 2 processor sockets in a single physical system.
I think a better comparison would be: do you prefer drinking your favorite coffee nice and hot in a ceramic mug, or cold in a leaky paper cup with boogers floating in it.
You haven't really tasted coffee until you've tasted it from a CoffeePhile(tm) Platinum Coffee Mug.
I will often use the pointed tip of my knife to "stab" a food item if the food (like, say tomatoes) resists my initial slice attempts (e.g. looks like it's going to squish instead of slice cleanly).
Offtopic, but you either need to sharpen your knives or use the right knife. Probably both.:-)
A freshly sharpened chefs will cut tomatoes, but not for long. Using the steel hone will prolong this, but it's still not the right blade for that. I pull out a scalloped or serrated blade, and that works wonders. Even so, I need to get mine sharpend.
10 years ago, you would've said the same thing about GigE. Now I can buy Cat5e cables and a US$20 switch, and do the whole house for under under a US$100.
Sorry, I'm on one of those platforms that replaced vi with vim years ago. I incorrectly use them interchangably. Please substitute all references of vi in my previous post with vim.
I have not benchmarked vi in this area for at least 6 years, so I won't talk about vi.
because they understand their typical problems better than you do
Very likely. I can only offer my own experience.
When I open a large file in vim, I'll usually wait a few seconds and then start writing a sed, awk, or perl script to accomplish the same goal. I'll drop awk and perl for the rest of the discussion, because they do not have a very shallow learning curve that sed has for an existing vi/vim user.
I find that I can usually write the sed scripts and execute them before my vim edits are complete. Sometimes before vim finishes loading. I give high priority to vim and only write the sed commands while vim is processing. If vim finishes first, I've lost nothing by writing the sed script. If sed finishes first, I saved time.
I don't write one monolithic sed script. I belive I've written a.sed file once. Most of the time, I just run a couple sed -i.bak -e 'command1' -e 'command2' -e 'command3' file commands in quick succession.
Loading and saving the file took a while, but once the file had loaded moving from one end to another, searching for strings, making edits, etc. were pretty damn fast.
I'm with you until the making edits. It all depends on what edits your trying to do. Which the original poster did not specify.
Some counter examples:
Try deleting the 2nd half of your 3.1GB file. In vim, I'd move halfway down, and hit 'dG'. And wait. I can accomplish this quite a bit faster using several different CLI tools, one of which is sed. I've done this many times, usually when I'm interested in a particualr time range from a log file.
If I want to do my original example of vim's:%s/hamburger/cheeseburger/g. After I ran the command, I noticed that hamburger appears on pretty much every line in my 3.1GB file (think 'Mozilla' in an apache access_log). In this case, the sed script will be way faster. I can't quantify that, because I've never waited for vim to complete. I always end up kill -9'ing vim because Ctrl-C takes too long to abort.
I'm not saying that sed is perfect for every job. The original poster said that vim is the only tool he has that works. I'm giving him a bigger toolbox so he can pick the tool he wants to use.
"sed" - could work, but why bother if vim works? Personally, I can never remember the sed syntax.
*sputters* You can't remember the sed syntax? It's the same as vi.
Mostly likely, if you're editting a several gig text file, you're doing bulk edits, not single edits. ala:
:%s/hamburger/cheeseburger/g
Well, here's the sed script to do that:
sed 's/hamburger/cheeseburger/g' < infile > outfile
They're so similiar, I suspect that they're related... yup. The Sed History says that "Sed was first written in 1977 as a stream adaptation of the ed editor".
And since vi is just a fancy tui on top of ed, you already know sed.
Why bother? Just because vi can edit large files, it's still painfully slow. Large and/or many edits are very slow to apply and undo. The same commands executed in sed can be done order of magnitude faster. I believe (but have never taken the time to prove it) that it's related to the undo buffer. And yes, my anecdotal evidence took place on machine with enough RAM that no swapping was required for vi or sed.
Now if you want to get really productive, we can talk about taking your vi commands, wrapping them in a sed script, then running it through sed2perl. Oh the Thinks you will have Thunk.
Or why not ask your physician who, I would think, knows a bit more than a writer who does the bare minimum of research, if any, to meet his deadline.
Several years ago, when the issue with Thimerosal was under investigation, I did exactly that. I was paranoid, since I display several Aspbergers symptoms. I didn't know if this predisposed my children to be more sensitive to the mercury. And the doctor didn't either. We discussed it with our Physician, and decided to wait on vaccinations.
Once Thimerosal was statistically disproven to be an Autism cause, I waited a while to make sure an equally reputable study didn't contradict it.
At the time we made the decision, it was not an easy or clear decision. Given the information I had then, I would still make the same decision.
I'm fairly certain now that at least one of my children has just as much Aspbergers as I do, and he has had 0 vaccinations.
Much research has been done since then. Things are clearer now, and I believe it is time to have my children vaccinated.
When it comes to something that may seriously harm your computer, whether it be a virus or the anti-virus software, it is your responsibility as an internet user to not go off half-cocked and to make extremely sure that you have all the facts before you make a decision regarding the welfare of your computer. If you're not up to that responsibility, then you shouldn't be allowed on the internet. Plain and simple.
Between "computer works, but slightly slower" and "computer is slightly faster but might not boot back up if it crashes at the wrong time", users will prefer the first.
I think we're talking about different users here. Most of the users I'm thinking of would pick the slightly faster machine. That's something they can see and feel immediately. How many people re-install windows after it gets so hosed it won't boot anymore? That's the kind of user I'm thinking of.
If everybody made informed rational decisions, they would pick good filesystems, mortgages and presidential candidates. Until this shining utopia arrives, I'm glad we protect the apathetic from themselves by default. I'm wholly in support of Journaled FS, and wouldn't run non-journaled on any rw mount point (well, maybe a USB drive). There are some good for-pay fully journalled Filesystems that are faster than ext2. I've used Veritas FS, and really wish I could use it for / and/boot too. From what I understand, JFS and VxFS have a lot in common.
Do you honestly believe that they're going to risk having their files corrupt on an unexpected power outage for a fraction of a percent increase in meaningful speed?
Does the file system wave at them from the system tray? Maybe with a cool woobly effect?
No? Then nobody cares about the FS.
--
Still running FVWM. Get your fancy Desktop Environment off my lawn.
Slashdot Mirror
Not hazardous? With the notable exception that the 5.2 tons of Uranium per 1000MW per year coal plant goes up into the air.
Yes, we just said the same thing. I was referring to GPs questions about individual concrete blocks. The amount of radioactive material in a single block, or a whole building built from these blocks, is almost non-existent. At the scale require to generate 1GW of power, the radioactive material is significant.
A quick google says coal ranges from 1 to 10 ppm (parts per million) of Uranium (in the US). Up to 20 ppm is rare, but happens (in the US). Your drinking water contains 2 to 3 ppm of Chlorine, one of the deadliest gases known. It's safe to drink, but I wouldn't want to start evaporating a couple million tons of water.
We'll fully commit ourselves to nuclear and finally have the ammo we need to silence the anti-nuclear crowd?
We'll have tons of depleted uranium rounds.
The radiation hazard is negiligable. The amount of radioactive material per ton of coal is nearly 0. It's only a significant source of radioactive material when you burn a couple billion tons of it a year. Burn a couple billion tons of any solid and it will be a significant source of radioactive material. Coal does have more radioactive material per ton than most solids, but it's still a tiny amount per ton.
You get pretty much the same amount of radioactive material in blocks using fly ash as you would get from a block of stone.
No. This is what I want to happen when ideology meets reality. He could've gone all GreenPeace on us. Then we'd be really screwed.
My only question is, where is Vista SP2? Last I checked, it was not yet released.
The Security feature will be cut before release.
LTO4 Tapes are 800G
Mostly people using these tapes have a robot, so they write until a tape is full, then start on the next tape. Units holding 10 tapes are pretty cheap for a company to buy.
Limit the email the account can send, and you reduce the desire for the account. Reduce the usefullness of the account, and you reduce the desire to crack the captcha on new account signups, or at least the profitability in doing so.
Doesn't this increase the desire to get more accounts faster?
My co-workers were giving me this same crap about homeschooling. After I point out that my wife is a liscensed teacher, they drop the acedemic arguments, and bring out the socialization arguments. After they meet my kids, the whole discussion never comes up again.
Everybody in our homeschooling circle is aware that homeschoolers can be improperly socialized. It's our job to make sure they are properly socialized, and it's a job we accepted when we decided to homeschool.
I will propose a counter argument: When I break down all that "social" time I had in public school, it was about 35 hours of lecture, and 5 hours of real social activity. My kids get way more interactive social time with many more children than I had in public school.
Veritas Storage Foundation Basic
Free (beer) closed source volume manager and Filesystem. High performance and High reliability. The Enterprise version saved my ass more times than I can count, and I can count some extremely unlikely scenarios.
The only drawback (the reason I don't run it at home) is the low limits:
I think a better comparison would be: do you prefer drinking your favorite coffee nice and hot in a ceramic mug, or cold in a leaky paper cup with boogers floating in it.
You haven't really tasted coffee until you've tasted it from a CoffeePhile(tm) Platinum Coffee Mug.
I will often use the pointed tip of my knife to "stab" a food item if the food (like, say tomatoes) resists my initial slice attempts (e.g. looks like it's going to squish instead of slice cleanly).
Offtopic, but you either need to sharpen your knives or use the right knife. Probably both. :-)
A freshly sharpened chefs will cut tomatoes, but not for long. Using the steel hone will prolong this, but it's still not the right blade for that. I pull out a scalloped or serrated blade, and that works wonders. Even so, I need to get mine sharpend.
It was obvious it was coming, just not when. I thought it was going to go belly up 2 years earlier than it did.
Maybe that's just my perspective, working for a .com and owning a house in Southern California.
10 years ago, you would've said the same thing about GigE. Now I can buy Cat5e cables and a US$20 switch, and do the whole house for under under a US$100.
There are some modules aimed at code folding, but they all appear to be line based.
I'm not very expienced with folding, so I might be missing something. Maybe if you explore the depths of Folding by Syntax or Folding by Expression.
Sorry I couldn't be more help.
vi are pretty much irrelevant to a thread on vim
Sorry, I'm on one of those platforms that replaced vi with vim years ago. I incorrectly use them interchangably. Please substitute all references of vi in my previous post with vim.
I have not benchmarked vi in this area for at least 6 years, so I won't talk about vi.
because they understand their typical problems better than you do
Very likely. I can only offer my own experience. When I open a large file in vim, I'll usually wait a few seconds and then start writing a sed, awk, or perl script to accomplish the same goal. I'll drop awk and perl for the rest of the discussion, because they do not have a very shallow learning curve that sed has for an existing vi/vim user.
I find that I can usually write the sed scripts and execute them before my vim edits are complete. Sometimes before vim finishes loading. I give high priority to vim and only write the sed commands while vim is processing. If vim finishes first, I've lost nothing by writing the sed script. If sed finishes first, I saved time.
I don't write one monolithic sed script. I belive I've written a .sed file once. Most of the time, I just run a couple sed -i.bak -e 'command1' -e 'command2' -e 'command3' file commands in quick succession.
Loading and saving the file took a while, but once the file had loaded moving from one end to another, searching for strings, making edits, etc. were pretty damn fast.
I'm with you until the making edits. It all depends on what edits your trying to do. Which the original poster did not specify.
Some counter examples:
Try deleting the 2nd half of your 3.1GB file. In vim, I'd move halfway down, and hit 'dG'. And wait. I can accomplish this quite a bit faster using several different CLI tools, one of which is sed. I've done this many times, usually when I'm interested in a particualr time range from a log file.
If I want to do my original example of vim's :%s/hamburger/cheeseburger/g. After I ran the command, I noticed that hamburger appears on pretty much every line in my 3.1GB file (think 'Mozilla' in an apache access_log). In this case, the sed script will be way faster. I can't quantify that, because I've never waited for vim to complete. I always end up kill -9'ing vim because Ctrl-C takes too long to abort.
I'm not saying that sed is perfect for every job. The original poster said that vim is the only tool he has that works. I'm giving him a bigger toolbox so he can pick the tool he wants to use.
"sed" - could work, but why bother if vim works? Personally, I can never remember the sed syntax.
*sputters* You can't remember the sed syntax? It's the same as vi.
Mostly likely, if you're editting a several gig text file, you're doing bulk edits, not single edits. ala:
Well, here's the sed script to do that:
sed 's/hamburger/cheeseburger/g' < infile > outfile
They're so similiar, I suspect that they're related... yup. The Sed History says that "Sed was first written in 1977 as a stream adaptation of the ed editor".
And since vi is just a fancy tui on top of ed, you already know sed.
Why bother? Just because vi can edit large files, it's still painfully slow. Large and/or many edits are very slow to apply and undo. The same commands executed in sed can be done order of magnitude faster. I believe (but have never taken the time to prove it) that it's related to the undo buffer. And yes, my anecdotal evidence took place on machine with enough RAM that no swapping was required for vi or sed.
Now if you want to get really productive, we can talk about taking your vi commands, wrapping them in a sed script, then running it through sed2perl. Oh the Thinks you will have Thunk.
Enjoy your backbreaking cancer ray tube.
Backbreaking? Finish puberty, noob.
'Course, CRTs *did* shave off a few pounds by the time I finished puberty. They no longer required a forklift to move around.
I'm also curious as to why 1980 is the epoch, but that's not as important.
MS-DOS defines the epoch as Jan 1, 1980.
I use TiVo to cover this. I'll just disable the season pass, and the kids can watch the same 5 episodes over and over until the channels return.
Too late. The Energy bubble is already starting.
Or why not ask your physician who, I would think, knows a bit more than a writer who does the bare minimum of research, if any, to meet his deadline.
Several years ago, when the issue with Thimerosal was under investigation, I did exactly that. I was paranoid, since I display several Aspbergers symptoms. I didn't know if this predisposed my children to be more sensitive to the mercury. And the doctor didn't either. We discussed it with our Physician, and decided to wait on vaccinations.
Once Thimerosal was statistically disproven to be an Autism cause, I waited a while to make sure an equally reputable study didn't contradict it.
At the time we made the decision, it was not an easy or clear decision. Given the information I had then, I would still make the same decision.
I'm fairly certain now that at least one of my children has just as much Aspbergers as I do, and he has had 0 vaccinations.
Much research has been done since then. Things are clearer now, and I believe it is time to have my children vaccinated.
When it comes to something that may seriously harm your computer, whether it be a virus or the anti-virus software, it is your responsibility as an internet user to not go off half-cocked and to make extremely sure that you have all the facts before you make a decision regarding the welfare of your computer. If you're not up to that responsibility, then you shouldn't be allowed on the internet. Plain and simple.
*Unix User*
rsync -avP ./ /path/to/directory/
Remove the -P for less verbosity.
Remove the -vP for no verbosity.
It'll work over ssh if your destination is user@host:/path/to/directory/
I stopped using cp long time ago.
Between "computer works, but slightly slower" and "computer is slightly faster but might not boot back up if it crashes at the wrong time", users will prefer the first.
I think we're talking about different users here. Most of the users I'm thinking of would pick the slightly faster machine. That's something they can see and feel immediately. How many people re-install windows after it gets so hosed it won't boot anymore? That's the kind of user I'm thinking of.
If everybody made informed rational decisions, they would pick good filesystems, mortgages and presidential candidates. Until this shining utopia arrives, I'm glad we protect the apathetic from themselves by default. I'm wholly in support of Journaled FS, and wouldn't run non-journaled on any rw mount point (well, maybe a USB drive). There are some good for-pay fully journalled Filesystems that are faster than ext2. I've used Veritas FS, and really wish I could use it for / and /boot too. From what I understand, JFS and VxFS have a lot in common.
Do you honestly believe that they're going to risk having their files corrupt on an unexpected power outage for a fraction of a percent increase in meaningful speed?
Does the file system wave at them from the system tray? Maybe with a cool woobly effect?
No? Then nobody cares about the FS.
--
Still running FVWM. Get your fancy Desktop Environment off my lawn.