Actually slashdot adds nofollow to many, but not all links in comments. I am not sure what the criterion for nofollow vs dofollow but many of the links on this page are in fact dofollow.
When these kinds of services (meaning flicker et al) open up their api to public use there are always some who cant figure out why.
Well folks, this is the reason why.
I betting when the executives at flicker sat down to decide if they were going top open up the api, they had no idea that someone would use it to create a map of the sky.
The subhead states "Bacteria treated with compound lose their resistance"
My question is what is treated?
If treated means "immersed in a strong bath of the compound for 2 weeks" then the compound may not be very practical. If treated means "a small dose included with the antibiotic" then the treatment is very practical.
The fact that the article was not very specific suggests its not the latter.
So by using the lignin as a "plastic" we are in fact sequestering the carbon and preventing it from entering the atmosphere. Sounds good.
One slight problem.
The lignin is burned to provide fuel for the pulp making process, if we no longer can burn the lignin for energy we now have to add a new source of energy to the process. Like fossil fuel.
So the net effect is the same as before, from a carbon cycle point of view.
Before:
Oil -> Plastic No net carbon increase
CO2 -> lignin -> Burn lignin -> CO2 No net carbon increase
After:
CO2 -> lignin -> "Plastic" Net carbon decrease
Oil -> Burn to fuel plant -> CO2 Net carbon increase
Depending on the efficiencies of the process there may be a slight increase or decrease in net CO2.
The supposed environmental benefits are NOT a valid justification of the process.
Because the synthetic voice used to read the text is consistent and unvarying then the training process should be very easy. Therefore the accuracy of the transcription should be quite high.
So what we have here is a situation where few individuals manage to manipulate the system and avoid the rules designed to limit this kind of activity and create enormous amount of unearned wealth right out of thin air.
Can we just not use them? I mean, who really cares if the sun is at its highest point a minute after midday on the summer solstice? Maybe in a hundred years or so we can schedule a leap minute, and by then we'll probably have worked out sensible standards for dealing with them.
It been tried.
A gradual error over hundreds of years led to a 10 DAY correction in the 1500's, it caused a lot of problems. In the modern era of tightly coordinated and scheduled computers we should not allow the error to build up more than it needs to.
A lot of 300A's were actually 450's that passed as a 450, but due to demand were relabelled as 300's. So technically there were not being overclocked. They just were not being underclocked anymore.
Actually that is a serial welcome, a parallel welcome (8 core) would be: IIIIIIII,,,,,,,, ffffffffoooooooorrrrrrrr oooooooonnnnnnnneeeeeeee,,,,,,,, etc.
Oliver Wendall Jones: "The following formula shows conclusively how the entire world's energy needs can be fulfilled with only two porcupines, an exercise wheel and six tones of 'Raisin Bran'. Truly... an original notion."
Science Teacher: "...Except that porcupines are allergic to raisins."
It should be noted that these figures have been normalized to compare Windows-based and Linux-based servers running at a full density of sites per shared server. At the time of the study, the Windows-based servers at Hostbasket were running at only 60 percent of full density and the Linux-based servers were running at only 35 percent of full density. Building out these services to achieve full site density may entail more than just a linear extrapolation of labor costs, as more personnel may be needed to support additional site requirements, so the actual cost of running these servers at full density may actually be higher than we have calculated.
So Microsoft is admitting to almost tripling the linux labour costs and increasing windows by 66% in order to "normalize" the results. That will certianly skew the results the way that they want.
By looking at hardware and power costs (not percentages) per site we can calculate that a windows host and a linux host have the same hardware/power costs. Since hardware and power is consumed on a by server basis we can therfore assume that each server hosts the same number of sites regardless of platform. Since a linux box is only at 35% load and the windows box is at 60% load we can conclude you can have approx 70% more sites on a linux box that you can have on a windows box. This disparity is made even worse by the fact that the microsoft hosted sites are all static content and the linux hosted sites are all dynamic content.
Just use rsync to a server in your home every night via dsl or cable. I have done that for the last 4 years and have about 60 gb of offsite storage.
If the work server would die or be stolen I simply drive home, pick up the entire server or just the drive, bring it back to work and set it up. Total down time is a couple of hours.
Total cost was $0 for an old Pentium 100 server, $100 for a 120gb drive and $40/month for the cable internet.
I dont use rsync for the backing up over the local network. I maintain a list of files on the server and compare file modify times using perl. If the file does not exist on the backup server it is simply copied. If there is an existing file then the existing file is renamed before the new file is copied. The unique filename is simply the file renamed with a unix time value (ie seconds since Jan 1/1970) while maintaining the file extention. The actual compression is a cron job that runs over night.
For example:
M1530-2.1.dwg
becomes M1530-2.1.(1086400701).dwg
which them becomes M1530-2.1.(1086400701).dwg.gz
I also rsync to an offsite server at my home 2 times a day, the company pays for my broadband connection. Rsync has been configured to delete any remote files that are no longer on the server but will only delete 50 files per session.
As well I copy all files that have changed during the day to a dated directory I periodically burn them to a cd. I end up with about 1 cd a week going back over 2 years.
All together I have 5 levels of backup. 1) Onsite mirror updated every 15 minutes with incremental versions saved. 2) Daily incremental backups over the last 2 years kept on site. 3) Offsite mirror updated 2 times a day. 4) Old projects are taken off of the server, burned to 2 sets of cds with one set kept off site. 5) Ocasionally I burn a snapshot of the fileserver onto cd's and keep off site.
At my place of work (18 people) I have set up spare low end machine (p233) with a 80gb drive as a backup file server. During the day every 15 minutes everything that has changed is copied to the backup server. The backup fileserver is configured as read only so a user cannot accidently change anything.
If the main fileserver goes down I simply change the configuration to read/write and change filemaping on the users machine and they continue to work. The whole process will take about 10 minutes to reconfigure the server and a couple of minutes per user machine.
As a bonus I dont delete the intermediate versions of changes files as I update the server. Instead I compress them with a unique filenames. So I can recover a fairly complete history of any given file. I have yet to fill up the 80gb drive so I havent needed to delete any backups. When the backup drive is full I will start deleting some of the older version, I should have room for about 6 to 9 months of backups at 15 minute intervals.
Take an 8 1/2 x 11 (A size) double the shortest dimesion and you get 11x17 (B size) do it again and you get 17x22 (C size) and again to get 22x34 (D size) and again to get 24x44 (E size). These are all standard paper sizes.
Historically I believe that it actually worked the other way around, they started with a large standard sheet and kept cutting it in half.
Be sure to order the lightweight bits. After lugging around 40 gb of heavy bits all the time you will be sorry that you didnt order the lighter version. It will cost a little more but it will be worth it.
Slashdot Mirror
Actually slashdot adds nofollow to many, but not all links in comments. I am not sure what the criterion for nofollow vs dofollow but many of the links on this page are in fact dofollow.
Which is good for us/bad for them.
When these kinds of services (meaning flicker et al) open up their api to public use there are always some who cant figure out why.
Well folks, this is the reason why.
I betting when the executives at flicker sat down to decide if they were going top open up the api, they had no idea that someone would use it to create a map of the sky.
The subhead states "Bacteria treated with compound lose their resistance"
My question is what is treated?
If treated means "immersed in a strong bath of the compound for 2 weeks" then the compound may not be very practical. If treated means "a small dose included with the antibiotic" then the treatment is very practical.
The fact that the article was not very specific suggests its not the latter.
So by using the lignin as a "plastic" we are in fact sequestering the carbon and preventing it from entering the atmosphere. Sounds good.
One slight problem.
The lignin is burned to provide fuel for the pulp making process, if we no longer can burn the lignin for energy we now have to add a new source of energy to the process. Like fossil fuel.
So the net effect is the same as before, from a carbon cycle point of view.
Before:
Oil -> Plastic No net carbon increase
CO2 -> lignin -> Burn lignin -> CO2 No net carbon increase
After:
CO2 -> lignin -> "Plastic" Net carbon decrease
Oil -> Burn to fuel plant -> CO2 Net carbon increase
Depending on the efficiencies of the process there may be a slight increase or decrease in net CO2.
The supposed environmental benefits are NOT a valid justification of the process.
That should actually work quite well.
Because the synthetic voice used to read the text is consistent and unvarying then the training process should be very easy. Therefore the accuracy of the transcription should be quite high.
So what we have here is a situation where few individuals manage to manipulate the system and avoid the rules designed to limit this kind of activity and create enormous amount of unearned wealth right out of thin air.
Sounds just like Wall Street.
And after you melt the cow can you cast it into a new cow?
Believe or not that method has a name.
Its called "rubber hose cryptanalysis": http://en.wikipedia.org/wiki/Rubber_hose_cryptanalysis
Can we just not use them? I mean, who really cares if the sun is at its highest point a minute after midday on the summer solstice? Maybe in a hundred years or so we can schedule a leap minute, and by then we'll probably have worked out sensible standards for dealing with them.
It been tried. A gradual error over hundreds of years led to a 10 DAY correction in the 1500's, it caused a lot of problems. In the modern era of tightly coordinated and scheduled computers we should not allow the error to build up more than it needs to.
A lot of 300A's were actually 450's that passed as a 450, but due to demand were relabelled as 300's. So technically there were not being overclocked. They just were not being underclocked anymore.
So we have a story that talks about the economic report, that links to a story talking about the report, but doesn't actually link to the report.
The report that the story is actually about (but doesn't link to) is available here.
fava
The referenced article is at the Proceedings of the National Academy of Sciences website.
fava
Actually that is a serial welcome, a parallel welcome (8 core) would be:
IIIIIIII,,,,,,,, ffffffffoooooooorrrrrrrr oooooooonnnnnnnneeeeeeee,,,,,,,, etc.
fava
No No No.
From Bloom County.
Oliver Wendall Jones:
"The following formula shows conclusively how the entire world's energy needs can be fulfilled with only two porcupines, an exercise wheel and six tones of 'Raisin Bran'. Truly... an original notion."
Science Teacher:
"...Except that porcupines are allergic to raisins."
By looking at hardware and power costs (not percentages) per site we can calculate that a windows host and a linux host have the same hardware/power costs. Since hardware and power is consumed on a by server basis we can therfore assume that each server hosts the same number of sites regardless of platform. Since a linux box is only at 35% load and the windows box is at 60% load we can conclude you can have approx 70% more sites on a linux box that you can have on a windows box. This disparity is made even worse by the fact that the microsoft hosted sites are all static content and the linux hosted sites are all dynamic content.
What about mash (Microsoft Again SHell) for when windows is broken and needs major emergency repair.
Just use rsync to a server in your home every night via dsl or cable. I have done that for the last 4 years and have about 60 gb of offsite storage.
If the work server would die or be stolen I simply drive home, pick up the entire server or just the drive, bring it back to work and set it up. Total down time is a couple of hours.
Total cost was $0 for an old Pentium 100 server, $100 for a 120gb drive and $40/month for the cable internet.
http://ask.slashdot.org/article.pl?sid=03/02/11/10 47231&tid=133
fred@SPAMvanandelFREE.net
I dont use rsync for the backing up over the local network. I maintain a list of files on the server and compare file modify times using perl. If the file does not exist on the backup server it is simply copied. If there is an existing file then the existing file is renamed before the new file is copied. The unique filename is simply the file renamed with a unix time value (ie seconds since Jan 1/1970) while maintaining the file extention. The actual compression is a cron job that runs over night.
For example:
M1530-2.1.dwg
becomes M1530-2.1.(1086400701).dwg
which them becomes M1530-2.1.(1086400701).dwg.gz
I also rsync to an offsite server at my home 2 times a day, the company pays for my broadband connection. Rsync has been configured to delete any remote files that are no longer on the server but will only delete 50 files per session.
As well I copy all files that have changed during the day to a dated directory I periodically burn them to a cd. I end up with about 1 cd a week going back over 2 years.
All together I have 5 levels of backup.
1) Onsite mirror updated every 15 minutes with incremental versions saved.
2) Daily incremental backups over the last 2 years kept on site.
3) Offsite mirror updated 2 times a day.
4) Old projects are taken off of the server, burned to 2 sets of cds with one set kept off site.
5) Ocasionally I burn a snapshot of the fileserver onto cd's and keep off site.
I think I am well covered regarding backups.
At my place of work (18 people) I have set up spare low end machine (p233) with a 80gb drive as a backup file server. During the day every 15 minutes everything that has changed is copied to the backup server. The backup fileserver is configured as read only so a user cannot accidently change anything.
If the main fileserver goes down I simply change the configuration to read/write and change filemaping on the users machine and they continue to work. The whole process will take about 10 minutes to reconfigure the server and a couple of minutes per user machine.
As a bonus I dont delete the intermediate versions of changes files as I update the server. Instead I compress them with a unique filenames. So I can recover a fairly complete history of any given file. I have yet to fill up the 80gb drive so I havent needed to delete any backups. When the backup drive is full I will start deleting some of the older version, I should have room for about 6 to 9 months of backups at 15 minute intervals.
You can take it even further.
Take an 8 1/2 x 11 (A size) double the shortest dimesion and you get 11x17 (B size) do it again and you get 17x22 (C size) and again to get 22x34 (D size) and again to get 24x44 (E size). These are all standard paper sizes.
Historically I believe that it actually worked the other way around, they started with a large standard sheet and kept cutting it in half.
Be sure to order the lightweight bits. After lugging around 40 gb of heavy bits all the time you will be sorry that you didnt order the lighter version. It will cost a little more but it will be worth it.
I wonder how long it will be until someone runs the comparator in it?