SN-10096 附来源、原文与上下文。
你真的不该继续在 Wine 中运行了，你正在遇到数据库错误（db.log）。你大概是为了应付数据库损坏，才养成了转移到全新安装的这套操作习惯。如果真有什么办法会丢失未确认区块，那只能是数据库错误。你在 Linux 构建中发现的任何问题都可以修复。Berkeley DB 深处的 Wine 兼容性问题则无法修复。
You really don't want to keep running in Wine, you're getting database errors (db.log). You probably developed these rituals of transferring to a fresh install to cope with database corruption. If there is a way to lose unconfirmed blocks, it would have to be the database errors. Any problems you find in the Linux build can be fixed. The Wine incompatibility deep inside Berkeley DB is unfixable.
我想，Linux 构建所用的 GCC 4.3.3 对 SHA-256 代码的优化，比 Windows 上旧的 GCC 3.4.5 更好。当初寻找最佳 SHA-256 代码时，有很多经过手工调整、高度优化的 SHA1 代码可用，但 SHA-256 还不多。我应该看看能否把 MinGW 升级到 4.3.x，让两边处于同一起跑线。
I think GCC 4.3.3 on the Linux build optimized the SHA-256 code better than the old GCC 3.4.5 on Windows. When I was looking for the best SHA-256 code, there was a lot of hand tuned highly optimized SHA1 code available, but not so much for SHA-256 yet. I should see if I can upgrade MinGW to 4.3.x to get them on a level playing field.
引用 New Liberty Standard 的文字New Liberty Standard来源 ↗所有参与制作这个 Linux 构建的人，做得真的很棒！谢谢大家的努力。有些比特币已经开始成熟，所以我暂时会继续运行 Linux 客户端，直到判断出它生成功能至少与运行在 Wine 中的 Windows 版一样好，还是更好。
Everyone that contributed to making this Linux build really did a great job! Thanks for the hard work. It has started maturing some bitcoins, so I'm going to continue to run the Linux client for the time being until I decide whether it's at least as good or better at generating coins than the Windows version running in Wine.
引用 New Liberty Standard 的文字New Liberty Standard来源 ↗另一种我希望同时运行多个实例的情况，是升级 bitcoin。我会取消旧版 bitcoin 的生成币复选框，再使用单独的数据目录，启动新版 bitcoin 并开始生成币，等旧版程序的币成熟后，再把它们发到新版程序，然后关闭旧版。我更喜欢全新安装，而不是保留旧数据升级。
Another instance when I would like to run multiple instances is when I upgrade bitcoin. I will uncheck the generate coin check box in the outdated bitcoin, launch and start generating coins in the new bitcoin using a separate data directory, then when the old application's coins have matured I will send them to the new application and then close the old application. I prefer do do clean installs rather than upgrading while maintaining old data.
引用中本聪此前的文字中本聪来源 ↗谢谢，我看出发生什么了。因为第一个节点很慢，程序最后向其他所有人都请求区块，结果只是把一切都拖慢了。我能修复，只是需要花点时间想想正确的办法。
Thanks for that, I see what happened. Because the first one was slow, it ended up requesting the blocks from everybody else, which only bogged everything down. I can fix this, I just need to think a while about the right way.
有未确认内容时关闭程序没有风险。 当你创建交易或新区块时，程序会立即将它广播到网络。之后不断增加的 #/已确认 数字只是在监测结果。在这段时间里，你的节点不会做任何促进接受的事情。
There's no risk in shutting down while there are unconfirmed. When you make a transaction or new block, it immediately broadcasts it to the network. After that, the increasing #/confirmed number is just monitoring the outcome. There's nothing your node does during that time to promote the acceptance.
