Posts by Studebaker Hawk

1) Message boards : BOINC Manager : Problems with 5.8.15 (Message 9436) Posted 8 Apr 2007 by Studebaker Hawk Post: No need, you might else get confused again LOL Sekerob, You issued the challenge, now you are chickening out? We'll take that as proof you are the confused one. No matter, your improper usage plus your confusion over where you used then/than improperly is apparent to all. Sad, it is a sign of strength to admit one's mistakes and endeavor to do better. Rather than do that you've chosen the tiny man's way out and chosen to deny and lie about it. Hard to break your old habits, huh?
2) Message boards : BOINC client : Official 64 bit clients (Message 9435) Posted 8 Apr 2007 by Studebaker Hawk Post: I'm using Augustine's 5.8.17 on Ubuntu, but the BOINC Manager doesn't work with it. Can you be more specific? About 30 minutes ago I installed Augustine's 5.8.17 on Fedora Core. No problems so far.
3) Message boards : BOINC Manager : Problems with 5.8.15 (Message 9426) Posted 8 Apr 2007 by Studebaker Hawk Post: Propose to make the message in the Tasks tab unambiguous and add 1 word "Ready To Report Result"....could even consider "Ready to Report Result to Scheduler" cheers I agree there is an ambiguity. The ambiguity stems from using the word Report as a verb instead of a noun. Your proposal rearranges the words but still uses Report as a verb. Try "Ready to upload Result Report". Then we need only distinguish between The Result and the The Result Report in posts and docs to avoid ambiguity. Seems simpler to me though I don't know why. (BTW, unrelated to the subject at hand, you repeatedly use "then" when you mean "than" and vice-versa. Your posts would be less confusing if you used then and than correctly.) The entry in the message log speaks again of "Reporting X Tasks".... Is there anything uploaded? Yes, X number of Result Reports are uploaded. The event comes across to me as writing into the database that the files were previously uploaded and to tick them off as done whereupon the scheduler sends an 'acknowledged' back, which regrettably does not generate an entry in the message log. That is pretty much what happens. Where you say "the files were previously uploaded" it might be less ambiguous to say "the result files were previously uploaded". Also, remember that the Result Report contains the host's log of the computation of the WU. The Result Report also tells the server whether or not the computation ended with Success or Computation Error on the host. That tells the server whether or not to replicate another copy of the WU. on the BTW, you might have missed that language barrier part, but I did mean 'than' and not 'then' in my last post ... propose to continue in cafe BOINC, we could converse further in Italian, German, French, Dutch.... and UK English ;P OFF TOPIC QUIBBLING: No, I did not miss that language barrier part. You did not use then/than in Message #9407 which must be the last/previous post you refer to. The last time you used then/than in this thread was in message #9396 where you used it incorrectly. Start a new thread in the cafe and link it here if you have need of further lessons on then/than. Or perhaps you have it sorted now?
4) Message boards : BOINC client : Ubuntu Init Script (Message 9425) Posted 8 Apr 2007 by Studebaker Hawk Post: What is the advantage of getting BOINC from the Ubuntu distro? The official and/or latest BOINC downloads and installs just fine on my machines. The advantage is that BOINC is included in Ubuntu's software repository. That allows crunchers to download and install BOINC and BOINC updates using Linux's software update facility. Not only is the download and installation fairly automated, the updater software checks dependencies which means it checks to see which libraries BOINC requires. If your libraries need to be updated then it updates those too. I think another advantage might be that the people maintaining the repository compile BOINC on the various versions of Ubuntu to ensure that you get updates that will run on whatever Ubuntu version you have installed? If they don't actually compile it then they likely at least check to see if the official compile from Berkeley runs properly on Ubuntu? If the latest official BOINC has a major problem then the repository maintainers can hold back that update and save Ubuntu users some grief. I am not saying all this "automaticness" is the best way. It's only as good as the people who maintain the automation behind the scenes. If they screw up then you get screwed, automatically. There are advantages to doing it all manually if you have the time and expertise. People who don't have time and expertise prefer to have it automated. As more people drop Windows and migrate to Linux I think automated downloads/updates will grow in popularity.
5) Message boards : BOINC Manager : Problems with 5.8.15 (Message 9414) Posted 8 Apr 2007 by Studebaker Hawk Post: Propose to make the message in the Tasks tab unambiguous and add 1 word "Ready To Report Result"....could even consider "Ready to Report Result to Scheduler" cheers I agree there is an ambiguity. The ambiguity stems from using the word Report as a verb instead of a noun. Your proposal rearranges the words but still uses Report as a verb. Try "Ready to upload Result Report". Then we need only distinguish between The Result and the The Result Report in posts and docs to avoid ambiguity. Seems simpler to me though I don't know why. (BTW, unrelated to the subject at hand, you repeatedly use "then" when you mean "than" and vice-versa. Your posts would be less confusing if you used then and than correctly.)
6) Message boards : BOINC Manager : Problems with 5.8.15 (Message 9413) Posted 8 Apr 2007 by Studebaker Hawk Post: It causes a lot more load on the server, I think the switch was disabled from working. The send reports immediately function is intended to help devs debug. It can be turned on but only if a certain other switch is turned on first. I won't tell what that other switch is because it should be kept secret from the masses to prevent unnecessary load on the servers. The only place I have ever seen that other switch documented is.... nah, lips are sealed to spare the servers. Rom Walton wrote a detailed explanation of how reporting single results immediately (as opposed to uploading the result) loads servers. It is clear that reporting 3 or more results at a time is much more efficient. His article is available at Rom World, I think.
7) Message boards : BOINC client : Boinc and Vista (Message 9403) Posted 7 Apr 2007 by Studebaker Hawk Post: Whether the previous instructions are appropriate, the owner/mods of this forum can decide,... Apparently the appropriatness of said thread and appropriatness of BOINC Kopping have been considered and a decision has been rendered.
8) Message boards : BOINC client : Boinc and Vista (Message 9391) Posted 6 Apr 2007 by Studebaker Hawk Post: BOINC 5.8.16 had some Benchmarking issues on Vista. It is less than 1/2. The Core 2 Duo T7200 (2.0G 4M L2) chip used to have a 3.9GFlOPs per core now has a 1.53GFlOPs per core. XP is fine, but Vista is not. The FPU speed is OK. The E6400 (2.13G 2M L2) is 4.07GlOPs per core. Just wanted to bring this to someone's attention. Did they try rerunning benchmarks a bunch of times? There's a bug somewhere where dual cores will drop one of the benchmarks by about half seemingly randomly. On a Pentium D, I ran them maybe 6 or 7 times before I got an accurate one on more than one occasion. Trouble is BOINC runs the benchmarks every 5 days so 5 days later your benchmarks might be out to lunch again. There is no need to let BOINC mess up your benchmarks. First, set the benchmarks yourself then tell BOINC not to mess around with your settings. The steps are: 1. Set all projects to "no new tasks". 2. Drain your WU cache of all WUs except for 1 WU for each project you crunch. To do that, suspend 1 WU from each project and allow the rest to crunch, upload and report. 3. Shutdown BOINC and backup your client_state.xml file. 4. Open client_state.xml file in Notepad. Use Notepad or some other plain text editor, not Wordpad or Word because those editors try to put text formating commands into the file you are editing and you definitely don't want that in your client_state.xml. 5. About 10 lines from the top find lines that start with: <p_fpops> - this is the floating point benchmark <p_iops> - this is the integer benchmark <p_calculated> - this tells BOINC when to re-calculate the benchmarks 6. Alter the numbers following <p_fpops> and <p_iops> to whatever they should be. 7. Alter the number following <p_calculated>. Initially, it will be something like 1171776064.343750 which tells BOINC to re-calculate the benchmarks every 5 days. Increase the 3rd digit from the left by 1 to tell BOINC to re-calculate something like every 30 years. OK, it's not exactly 30 years but it's a very long time and your benchmarks will stay the way you set them until that time. Thus 1171776064.343750 would become 1181776064.343750. 8. Check your typing carefully. When you're satisfied, save the file and exit Notepad. 9. Let the remaining WUs in your cache crunch before you allow more new WUs to download or else BOINC will download too many. Actually, if you blow this part it's not a big deal, you can just abort whatever you know you can't finish in time. It is rumored that in previous versions of BOINC each number you edit must be followed by 6 decimal digits. I don't know if those rumors are true but play it safe and make sure there are exactly 6 digits to the right of the decimal points in the 3 numbers you edit. Post your thank you notes using a sockpuppet unless you want some BOINC Kop like Sekerob following you around from projecty to project accusing you of being a credit cheater.
9) Message boards : BOINC client : Official 64 bit clients (Message 9356) Posted 5 Apr 2007 by Studebaker Hawk Post: Any project devs who don't comply with the standard should be pilloried and have rotten vegetables thrown at them until they comply. Any client that uses a different name wouldn't get work from a project with correct names. Any project with different names wouldn't give work to clients following standard. Of course. But that does not solve the problem, it merely restates the problem. I know, I just gave actual reasons on why the devs should be tortured according to your guidelines :) Also, if a client uses a wrong name and doesn't get work, the user can't really complain to the project... Agreed. Oh well, the projects I want to crunch all do it the right way. I have no desire to crunch SETI or any project like Einstein that lets SETI's goofyness dictate what they do. They can both go pound sand.
10) Message boards : BOINC client : Official 64 bit clients (Message 9353) Posted 4 Apr 2007 by Studebaker Hawk Post: Any project devs who don't comply with the standard should be pilloried and have rotten vegetables thrown at them until they comply. Any client that uses a different name wouldn't get work from a project with correct names. Any project with different names wouldn't give work to clients following standard. Of course. But that does not solve the problem, it merely restates the problem. I can restate it yet another way... If project A uses x86_64-pc-linux-gnu for 64-bit Linux hosts and project B uses x86_64-unknown-linux-gnu for 64-bit Linux hosts then 64-bit Linux clients that identify themselves as x86_64-pc-linux-gnu cannot crunch project A. I believe that is what is happening now, correct me if I am wrong, but I think SETI is using x86_64-unknown-linux-gnu. There, that's the problem. An example of the mayhem and indecision created by that problem is Einstein's position that they do not plan on supporting AMD64 until other projects conform to the standard. At CPDN, in response to requests for sending their 32-bit app to 64-bit systems, Carl is babbling utter nonsense about not having a 64-bit app and not being able to make their source code public which is true but not relevant to what has been requested of him. Apparently Carl wants to sidestep the entire issue of projects not conforming to the naming standard and derail any conversation on the topic by acting like a total idiot and pretending he doesn't understand the question. Can't say I blame him considering how childish and stubborn some project admins are. Then we have others requesting official 64-bit clients to force compliance to the standard when it's obvious that is not going to solve the problem either. Yah, that's mayhem and indecision. At the heart of the problem is 1 or 2 assinine project leaders who refuse to comply with the existing standard. Build all the official 64-bit CCs you want, those assinine project leaders will still be assinine project leaders. Throw them in the pillary and pelt them with rotten veggies and smelly dead aminals until they get a brain. If that doesn't help then just fire their sorry arses out the door.
11) Message boards : BOINC client : Official 64 bit clients (Message 9337) Posted 4 Apr 2007 by Studebaker Hawk Post: We need a standard id string for 64 bit currently as its not official. Some people are using x86_64-pc-linux others support x86_64-unknown-linux. Platform names are already standardized by BOINC. See the platform list. If projects or clients use different names, they're Doing It Wrong :) Agreed. It may not be the best standard. Perhaps there is room for improvement. But it is the standard and should be adhered to otherwise it creates mayhem and indecision. Any project devs who don't comply with the standard should be pilloried and have rotten vegetables thrown at them until they comply.
12) Message boards : BOINC client : Official 64 bit clients (Message 9336) Posted 4 Apr 2007 by Studebaker Hawk Post: I currently use Augustine's client and it works fine but i was after an officially supported 64 bit client and don't really see why people think this is such a terrible idea. It isn't a terrible idea. It's just that the BOINC devs seem to have enough to do with the 32-bit version. If they were to get into the position of officially supporting a 64-bit client too then maybe they would be spread too thin and development would slow down. I suspect the plan at Berkeley is to get a few more features added and get all the bugs worked out (ok, most bugs) and then port it to 64-bit. That will take time. One way to speed it up would be to get Augustine and Crunch3r to join the BOINC dev team and then get Dr. Anderson to appoint them the offical 64-bit developers or porters or whatever title is appropriate. Lately, Augustine and Crunch3r seem to quickly come out with 64-bit compiles of every new 32-bit release. If that's all those 2 did, just port the 32-bit to 64 without adding new features/functions, so the 64-bit is merely a copy of the 32-bit wrt features/functionality, then Berkeley could make that their official 64-bit version and everybody would be happy. Yep! There ya go, problem solved! Somebody tell Augustine, Crunch3r and Anderson what the new plan is ;-)
13) Message boards : BOINC client : Official 64 bit clients (Message 9062) Posted 24 Mar 2007 by Studebaker Hawk Post: Clownius gave us... ... so i would like to move onto a 64bit client and i know many other users would too. Augustine has donated a 64-bit BOINC core for Linux, Crunch3r has donated one for some other operating called Windows. Most projects have a thread called AMD64 in which Augustine has posted download links for both the Linux version and the Windows version. Perhaps try those and let us know if you find anything wrong with them. I've heard they are both simply marvelous.
14) Message boards : BOINC client : Official 64 bit clients (Message 9061) Posted 24 Mar 2007 by Studebaker Hawk Post: There are already plans to make a client that sends multiple platform names, in order of preference (first 64 bit then 32 bit), and server modifications to follow that. Could also be useful for Mac/intel machines, "send mac intel if available, or otherwise mac ppc". Really I don't see what would be so difficult about making a 64-bit client. I mean.. ok.. forgive me if I'm wrong, but don't you just take the same data and just run it through a compiler except with different settings? Isn't that all automated? I mean.. It's not like it takes DAYS OF FRUSTRATING CODING NIGHTMARES to just sleeve the 32-bit version through the compiler and have it come out 64bit right? Am I totally wrong here? Because that's what Intel would have me believe.. The world's biggest and most frequent liar, in the private sector, is Bill Gates. Second, behind Gates, is Intel. In public sector (i.e. government) it's a toss up between George Bush, Kinda Sleezy Rice and Dick Cheney but ... whatever. And you DID say I need, in fact you said it twice. Look and re-read your post, message #8956, see where it says: "I *need* a 64-bit OS to use that much ram.. It seems rational that I would like to see a 64-bit client, since it's the reason I need a 64-bit OS." The bolding of the word "need" is mine, not yours. I put it in bold to help you read your post because your eyes seem to be failing and your spectacles seem to be broken.
15) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 9054) Posted 24 Mar 2007 by Studebaker Hawk Post: Predictor is currently not on Berkeley's list of projects and I hope it stays that way. Predictor gives BOINC and the DC community a bad name by condoning the use of hijacked computers. We need to get Predictor shunned by the entire community. For a start, they should be stricken from the lists of all the stats sites so they aren't advertised via credit brag banners in forum sigs. Are there any other sites that promote Predictor that could be contacted with regarding dropping any and all mention of Predictor. Thats over the top! And not helpful! Why banning a whole project just because their admin is acting "weird"? I believe this project is helpful - ok, Mr. Brauns behaviour isnt - but Mr. Braun IS NOT Predictor, imho. Braun is Predictor's spokesperson and he has informed us of Predictor's policy. Their policy is to use hijacked computers to crunch their WUs. That policy is worse than irresponsible, it is criminal. The entire Predictor team should be charged and put on trial because they are knowing accessories to a crime. It is sad because Predictor is an interesting and worthwhile project but unfortunately it is being run by criminals who are no better than Wate. Scripps Institute should fire the Predictor team and turn the project over to decent people to put the project back on the right track. Now it is on the wrong track and it is a disgrace to the entire BOINC community. Nobody should be promoting Predictor. Anybody who promotes Predictor promotes criminals.
16) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 9036) Posted 23 Mar 2007 by Studebaker Hawk Post: Predictor is currently not on Berkeley's list of projects and I hope it stays that way. Predictor gives BOINC and the DC community a bad name by condoning the use of hijacked computers. We need to get Predictor shunned by the entire community. For a start, they should be stricken from the lists of all the stats sites so they aren't advertised via credit brag banners in forum sigs. Are there any other sites that promote Predictor that could be contacted with regarding dropping any and all mention of Predictor.
17) Message boards : BOINC client : Number of CPUs changing (Message 8762) Posted 15 Mar 2007 by Studebaker Hawk Post: Remember KISS... keep it simple stupid. Put your preferences in a file named global_prefs_override.xml in your BOINC folder and be done with the problem once and for all. If you want to continue having problems then just keep doing it the way you're doing it now. Saving preferences in BOINC's Simple View will also screw up your preferences and cause you nothing but grief and sorrow. That's a contradiction, BOINC's Simple View uses global_prefs_override.xml. Indeed it does use global_prefs_override.xml, just doesn't use it nicely, it appears. Apparently, Simple View allows only a subset of the preferences tags BOINC supports. If you create a global_prefs_override.xml manually with a text editor and include tags Simple View does not support and then use Simple View to modify a preference it will delete any tags it does not recognize when it updates the global_prefs_override.xml. It happened to me a few days ago. Check it out for yourself, I would love to be proven wrong. IIRC the <ram_max_used_busy_pct> tag is one that is not supported and there are other tags too. So the "grief and sorrow" I experienced is that I thought I had turned on Preference X but Simple View deleted it which effectively turned it off for me. Was very confusing for a while until I realised what Simple View was doing. I guess the way around the grief and sorrow is... if you use a global_prefs_override.xml then either use Simple View to edit it or edit it with a text editor but don't mix the 2 methods.
18) Message boards : BOINC client : Number of CPUs changing (Message 8741) Posted 14 Mar 2007 by Studebaker Hawk Post: The reason it's not working and the reason you haven't figured out why it's not working is because you've fallen prey to the "logic" that says you must use every silly bell and whistle every silly programmer trying to be somebody can dream up. Forget about BAM, it will only make life more complicated for you than it needs to be. Remember KISS... keep it simple stupid. Put your preferences in a file named global_prefs_override.xml in your BOINC folder and be done with the problem once and for all. If you want to continue having problems then just keep doing it the way you're doing it now. Saving preferences in BOINC's Simple View will also screw up your preferences and cause you nothing but grief and sorrow.
19) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 8395) Posted 23 Feb 2007 by Studebaker Hawk Post: I'm shure if the police ask the project-leaders they give all infos needet to punish Wate by law... But what is it? They can just say that there is a user called Wateand they could tell the number of his credits. And his emailadress, but if he's clever, and i think so, he used an instand mailaccount like "Temporary Inbox"... You might be right, Wate may be very clever. Or maybe he is not very clever. Remember, the police can be very clever too. We should never assume he cannot be caught. We must first go to the police and let them try. It was not necessary for CPDN or anybody to act so quickly. There was no benefit from acting quickly. They should have taken time to think carefully and find the best solution not just the fast solution. I don't know, but maybe Wate put his BOINC-Trojan to a cracked Softwareversion... So the "damaged" user are given to punishment by law allso! And they are punished by Wate enough... But CPDN can prove that thousands were tricked by Wate so then the police will realise they are innocent. They have nothing to fear.
20) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 8382) Posted 23 Feb 2007 by Studebaker Hawk Post: I am glad Wate was caught and "discredited" but he did not get the punishment he deserves. The police should have been informed before any action was taken by any of the project admins. The police might have been able to trick Wate and lure him out of his hiding place then arrest him and put him in jail where he belongs. Now he has been warned so now he will disappear and escape punishment. When a crime has been committed it is important to always inform the police first before doing anything unless someone is in immediate and grave danger. The police are trained and experienced in criminal matters, we are not. We should report crimes to them first and avoid alerting the criminal. Then it is easier to catch him. If the police decide they cannot investigate then we still have the option to take the matter into our own hands. I hope project admins learn from the mistake they made with Wate. I hope this mistake is not repeated in the future. You can be sure more people will try Wate's method because now they have the impression project admins will not inform the police. Project admins have thus made the problem worse not better.

Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.