|
Down here as well (The Netherlands).
|
|
|
|
No bank is going to go down.
We had a few going down past 10 year (last one was of average size here in the Netherlands, see https://secure.wikimedia.org/wikipedia/en/wiki/DSB_Bank). Nice for those savers to know that they didn't loose their money due to something they didn't have control over. |
|
|
|
Hahaha, 100,000 is but a finite number. We in great USA now have infinite FDIC insurance, literally. No matter how much you can lose, more can be printed.
The finite number is good for 2 things: 1) Our government says, don't bet it on saving accounts with high interest rates. People have to have some sort of responsibility. We had some big problems with people putting a lot of money on Iceave accounts (we all know how that ended). Plus the 100,000 euro insurance is per account (and the hope is then that people split the money and put on different banks). Plus it looks nice towards the tax payers (knowing that there is a limit of tax going into that). 2) Yeah, unlimited printing money is good... no problem with that, right? |
|
|
|
|
We had 2 times, past 2 years that someone told people to get their money from the bank.
It ended in that one bank got bankrupt (there where already financial problems, people getting their money from the bank helped it to get it bankrupt). The other bank (ABN AMRO) ended in the hands of the Dutch government, because if that one would go bankrupt the whole economy would be severely damaged and even more banks would crash. I think banks have to have at least 7% of their money in free available form. In the latter case only a small percentage was withdrawn (government even raised the insured amount of savings in case a bank would go bankrupt (to 100,000 euro if I'm correct)).
|
|
|
|
|
So, how is this supposed to work? (/me does not facebook)
I don't think many people will do anything with this (at least in The Netherlands).
Haven't heard anything about this on the news yet.
|
|
|
|
|
Ah... Chinese people and their prestige projects (they really like them).
IMHO they do a lot of things that have a high "look at us" factor, but poorly executed to be really useful.
Reminds me of a conference in Vienna on radiation induced mutagenesis in plants.
Chinese big boss steps up for a presentation, tells some story about sending seeds into space to
have them irradiated by cosmic rays (all fine so far, from a scientific view, but the real added value might be little).
Then someone in the audience asked how much radiation the seeds received. He couldn't answer and I think they
never measured. Ouch.. epic, expensive fail.
I've got a few more examples of these type of things. Do note that there is also a lot of good research done in China,
but when a lot of money is involved it is often spend on the easy stuff (a.k.a. build a super computer) but the
efficiency to use it can be a lot less.
|
|
|
|
|
I think it is the IRC bot in the bitcoin channel.
|
|
|
|
Bitcoin's law: Every complex discussion about bitcoins will end in a discussion about what exactly is bitcoin. Is it money, currency, commodity, or something else entirely?
Hat tip(metaphorically) to noagendamarket for suggesting the idea on IRC. I merely formulated the law.
I think it should be reformulated, because in this way there could be exceptions. This is the same like Godwins law, but that one is formulated a bit different (If a discussion grows longer the probability of mentioning Nazi's or Hitler goes towards 1). If it were formulated like you do we would have a forum full of topics ending in discussions about how Nazi's would think about what Bitcoin would be.  Now if we have the same penalty in there as is in Godwins law (e.g. mention the question what bitcoin is and you will loose the discussion and have the topic locked). That would be great. |
|
|
|
|
Just see if your system is sane, if it is I'll contact you for the whole strace.
|
|
|
|
|
Wxwidgets isn't needed for bitcoind (the cli daemon).
|
|
|
|
( I can provide the complete strace if needed )
this is true with the 2 last ebuilds, 0.3.13 and 0.3.14
NOTE : the BINARY 32/bitcoind is running well on the same ATOM CPU server
Yes, a complete strace would be more useful. I don't see anything strange in this part. Did you also try ebuilds before 0.3.13, did they give issues? Also give a bit more information about your system (is is x86 or ~x86 for example). |
|
|
|
|
bitcoin-0.3.14.ebuild is on github.
|
|
|
|
|
Do you have setuptools installed? Did you try a reinstall of setuptools? And what version?
It seems version 1.8.1 will be released within 2 weeks that will have binary packages of all dependencies
with it bundled. Might make a few things more easy.
|
|
|
|
|
I see my Makefile.gentoo got reverted to an older version, caused by an update by mizerydearea. That is causing the problem.
I'll see if I can get my version in again.
<edit>Corrected Makefile.gentoo is in github again</edit>
|
|
|
|
I pulled directly from darcs.
I'm normally not a big fan of using development code from a cvs, but anyway. Did you already try to do the following?: Change to /home/kiba/projects/tahoe-lafs/ and run |
|
|
|
File "/home/kiba/projects/tahoe-lafs/support/bin/tahoe", line 6, in <module>
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources I got this error. Help? Google says that setuptools should be installed. Googling doesn't seem to turn up a solution. I try easy_install the .egg but that doesn't exactly work. Perhaps, I'll need to install easy_install too. Strange, easy_install seems to be part of setuptools. Could be different with your distro though. |
|
|
|
File "/home/kiba/projects/tahoe-lafs/support/bin/tahoe", line 6, in <module>
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources I got this error. Help? Google says that setuptools should be installed. |
|
|
|
Well, using a cloud filesystem storage would be great for wallet backup (after encryption, of course).
No need for encryption, tahoe does that for you. That is why tahoe is so great. For debian you need to add a repository to your sources.list, see the install page. |
|
|
|
that's what i did, i just couldn't get it to work.
diskspace wouldn't be a problem at all, got a few hundred gigs left anyway and hdds arent that expensive nowadays,
bandwidth might (or will) be though (sooner or later), but i'll happily donate as much as possible of it.
so far i can't and i guess i'm not the only one.
Well, I had a check on a Windows system today. You have to go through some hoops to get it working (the description is not completely correct in some places and doing some things slightly different might help a lot). Here is how I got it working: No problem here. I've used Python 2.6.6, which is out now. Install it in the default location (C:\Python26). Just install, no problems here. 3. Now install MingW as described in the "What if that doesn't work?" part. Install it in C:\MingW This is not optional as the wiki might suggest. I used file: http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20100909/mingw-get-inst-20100909.exe/download It is important to check the c++ compiler, base system, development system and the build system when you get that option to select it. This is different then what is told on the wiki. 4. Then continue with: I installed this initially in C:\Program Files\Tahoe-LAFS. This does not work. The space in "Program Files" causes problems, so install it in C:\Tahoe-LAFS 5. Open a command prompt and cd to the top of the Tahoe-LAFS tree (e.g. cd \tahoe-lafs).
Run "C:\Python26\python setup.py build". Wait a bit until it stops working. Note that you need a working network connection because it will download various dependencies. Ignore any warnings.
After the cd c:\Tahoe-LAFS there is a directory below that ("allmydata" or something) cd into that dir also, the wiki doesn't say to do that. From this point on you can continue with the normal installation (point 6) with one modification. The wiki says that the tahoe script is in C:\Python26\Scripts, well, it isn't. It is in the bin directory in where you did the setup.py build command C:\Tahoe-LAFS\allmydata-something\bin\ I know this is written down a bit confusing, I hope to provide a more clear "Howto" later, when I have access to a windows system again. |
|
|
|
|
Show Posts
