Yes, currently I have 8 different bash scripts. 2 per miner, 1 per pool. I'm only using 2 pools at the moment. Will probably switch to 3 once I get this figured out, and switching to poclbm might be worth the easy setup of reduncancy. My cards are overclocked in the bios, so I do not mess with scripts and overclocking. Currently I just open 8 different terminals and type ./miner0.sh in one. ./mine1.sh into another etc. This starts one miner per terminal and allows me to see their progress. Yes, kjj, I read that post, but what it fails to mention is the code inside shell_script.sh And when i tried using the first half of the bash script i found by googling, it would only start one miner in a screen session, which was hidden, so I couldn't even see if it was working or idle. Is there a way to remotely connect to the screen sessions? So, basically, I'm not sure if he's using the same script of if it's custom. For most people, the contents of the shell script will just cd into /opt/miners/phoenix or whatever, and run the miner with their args. For you though, you need a shell script that has 8 lines that look like this: lxterminal --command="script_to_start_miner_1.sh" lxterminal --command="script_to_start_miner_2.sh" etc. And yes, you can remotely connect screen sessions. CTRL-A, d will detach a running screen session (if any). CTRL-A, n and CTRL-A, p will cycle through them. If no session is connected, "screen -ls" will list sessions. "screen -r SESSION_NAME" will connect. If the session you want isn't detached, "screen -r SESSION_NAME -d" will detach it, and connect you to it. Also try "man screen". |
|
|
|
No clear answer? Seriously? Yes, it will always have some subjective value as long as humans exists. Its imposible for anything to have objective value. For something to have objective value it needs to have value independently from humans. Its imposible, because by definition value is what we value, its subjective.
How about these answers? |
|
|
|
|
PHYS and PSLV are not ETFs. They are CEFs. Huge, huge difference.
|
|
|
|
|
Open a second cmd window and run "namecoind getinfo". Oh, and make sure your bitcoin.conf for namecoin has set "server=1"
|
|
|
|
Our kids are going to laugh and laugh at us one day if they found out how extremely centralized the begining of the decentralized currency movement was, everybody pretty much uses one exchange, one forum, and we are moving closer and closer to one mining pool. I guess that is just people not wanting to let go of their past ways, living in the past can be so comfortable... there are so many bitcoin forums out there and it can even be fun to be in one that is currently low key that way when more people start showing up you know you were one of the first.
You and I are clearly not reading the same one forum. Because in this one, new pools are springing up nearly every day. |
|
|
|
|
Yup. Someone had suggested doing a minimal connection to avoid having to deal with 4 layer PCBs. It might work, but there are a number of potential problems.
Soldering a BGA, PLCC or QFP and watching it pull itself into perfect alignment is one of the coolest things a guy can do. Totally makes you feel like a wizard, commanding the universe with seemingly nothing but your willpower. On the other hand, when it doesn't work right it'll make you want to murder kittens.
|
|
|
|
|
You may run into thermal issues if you leave a bunch of BGA balls unconnected. The chip designers typically assume that the PCB is going to be sinking most of the heat load.
Then again, with the complexity of SHA256, gate propagation problems will probably force us to run the chips slowly enough that heat won't be the limiting factor.
|
|
|
|
|
Pegs don't work.
There are certain circumstances when a powerful entity can fake it for a bit, but it always breaks down.
Pegging a currency to electrical generation is a particularly bad idea.
|
|
|
|
|
Also, 600 Mhash/sec will probably never find a block. But if you get lucky, it will show up as a generation transaction in the main panel.
|
|
|
|
|
The 4 days is not wasted either way.
|
|
|
|
Ron Paul must love this stuff...in the U.S. anyway, liberty has just about been totally outlawed, and--as has been pointed out--the whole con of modern money, backed by... what's it backed by? Hahaha...bitcoin is just taking it one step further, as the whole statist repression finally comes crashing down...anarchy, but keep the electricity on, and we'll survive  The IRS mostly. No, really. |
|
|
|
|
The real question is, does he want cheezburger?
|
|
|
|
Bitcoin isn't dependent on anyone caring.
That's not an appropriate answer. If you want to criticize me like that, you should have sent me the ftp passwort of that website, so I can correct or delete the links (=care) myself. I think someone (who in your opinion 'does not care') got the password, cause s/he 'runs' (as they say) that website. So, jokes aside, my question was already solved by the first reply. And some interesting information was added by tcatm, thanks to that one. I'd donate some bitcoins if I already had some. I almost sent you the passworts to everything. And then I realized that it said helf. |
|
|
|
1. Enforced limits are not optimal
First, how do you know? Second, the only things enforced by the block chain is block creation speed. The rest are completely client side. You would be better off designing a better client with the same protocol.
Oddly enough, this is probably correct. The enforced limits are very likely to be non-optimal. Also, all other possible values are equally likely to be non-optimal. |
|
|
|
|
I assure you there are no broadcasts involved, TCP is a one to one channel.
The standard fee is included so that people don't make spends that never get accepted by the network, which is largely the default client. As other node software springs up, the rules for both will become far more flexible.
|
|
|
|
|
Run bitcoind on each server, alongside pushpoold.
|
|
|
|
|
There is no progress, just a repeated number of tiny chances.
Each mining client asks a network node for a piece of work to do. That work is unique to the miner, to the node, and across the entire network.
|
|
|
|
|
Show Posts
