Friday, September 12, 2014
mpos mining pool
http://coingolem.com/how-to-set-up-your-own-mining-pool-using-mpos-229/
https://github.com/MPOS/php-mpos/wiki/Quick-Start-Guide
https://github.com/MPOS/php-mpos/wiki/Config-Setup
NOMP node open mining portal
https://github.com/zone117x/node-open-mining-portal
Thursday, September 11, 2014
wrong version of dbd ?? easy ./configure --with-incompatible-bdb
recently building a newer dogecoin daemon
a whole new process than :
make -f makefile.unix
instead being :
./autogen.sh
./configure
make
had a problem because it required an earlier version of berkeley db
i believe it was looking for berkeley db 5.1 and i have 5.3.
doesnt matter :)
it seems there are all sorts of switches huzzah
./configure --with-incompatible-bdb
wins the prize
=============================================================
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-miniupnpc enable UPNP (default is yes if libminiupnpc is
found)
--with-comparison-tool path to java comparison tool (requires
--enable-tests)
--with-qrencode enable QR code support (default is yes if qt is
enabled and libqrencode is found)
--with-protoc-bindir=BIN_DIR
specify protoc bin path
--with-incompatible-bdb allow using a bdb version other than 5.1
--with-boost[=ARG] use Boost library from a standard location
(ARG=yes), from the specified location (ARG=),
or disable it (ARG=no) [ARG=yes]
--with-boost-libdir=LIB_DIR
Force given directory for boost libraries. Note that
this will override library path detection, so use
this parameter only if default library detection
fails and you know exactly where your boost
libraries are located.
--with-boost-system[=special-lib]
use the System library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-system=boost_system-gcc-mt
--with-boost-filesystem[=special-lib]
use the Filesystem library from boost - it is
possible to specify a certain library for the linker
e.g. --with-boost-filesystem=boost_filesystem-gcc-mt
--with-boost-program-options[=special-lib]
use the program options library from boost - it is
possible to specify a certain library for the linker
e.g.
--with-boost-program-options=boost_program_options-gc$
--with-boost-thread[=special-lib]
use the Thread library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-thread=boost_thread-gcc-mt
--with-boost-chrono[=special-lib]
use the Chrono library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-chrono=boost_chrono-gcc-mt
--with-boost-unit-test-framework[=special-lib]
use the Unit_Test_Framework library from boost - it
is possible to specify a certain library for the
linker e.g.
--with-boost-unit-test-framework=boost_unit_test_fram$
--with-cli with CLI (default is yes)
--with-daemon with daemon (default is yes)
--with-gui with GUI (no|qt4|qt5|auto. default is auto, qt4
tried first.)
--with-qt-incdir=INC_DIR
specify qt include path (overridden by pkgconfig)
--with-qt-libdir=LIB_DIR
specify qt lib path (overridden by pkgconfig)
--with-qt-plugindir=PLUGIN_DIR
--with-qt-bindir=BIN_DIR
specify qt bin path
--with-qtdbus enable DBus support (default is yes if qt is enabled
and QtDBus is found)
a whole new process than :
make -f makefile.unix
instead being :
./autogen.sh
./configure
make
had a problem because it required an earlier version of berkeley db
i believe it was looking for berkeley db 5.1 and i have 5.3.
doesnt matter :)
it seems there are all sorts of switches huzzah
./configure --with-incompatible-bdb
wins the prize
=============================================================
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-miniupnpc enable UPNP (default is yes if libminiupnpc is
found)
--with-comparison-tool path to java comparison tool (requires
--enable-tests)
--with-qrencode enable QR code support (default is yes if qt is
enabled and libqrencode is found)
--with-protoc-bindir=BIN_DIR
specify protoc bin path
--with-incompatible-bdb allow using a bdb version other than 5.1
--with-boost[=ARG] use Boost library from a standard location
(ARG=yes), from the specified location (ARG=
or disable it (ARG=no) [ARG=yes]
--with-boost-libdir=LIB_DIR
Force given directory for boost libraries. Note that
this will override library path detection, so use
this parameter only if default library detection
fails and you know exactly where your boost
libraries are located.
--with-boost-system[=special-lib]
use the System library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-system=boost_system-gcc-mt
--with-boost-filesystem[=special-lib]
use the Filesystem library from boost - it is
possible to specify a certain library for the linker
e.g. --with-boost-filesystem=boost_filesystem-gcc-mt
--with-boost-program-options[=special-lib]
use the program options library from boost - it is
possible to specify a certain library for the linker
e.g.
--with-boost-program-options=boost_program_options-gc$
--with-boost-thread[=special-lib]
use the Thread library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-thread=boost_thread-gcc-mt
--with-boost-chrono[=special-lib]
use the Chrono library from boost - it is possible
to specify a certain library for the linker e.g.
--with-boost-chrono=boost_chrono-gcc-mt
--with-boost-unit-test-framework[=special-lib]
use the Unit_Test_Framework library from boost - it
is possible to specify a certain library for the
linker e.g.
--with-boost-unit-test-framework=boost_unit_test_fram$
--with-cli with CLI (default is yes)
--with-daemon with daemon (default is yes)
--with-gui with GUI (no|qt4|qt5|auto. default is auto, qt4
tried first.)
--with-qt-incdir=INC_DIR
specify qt include path (overridden by pkgconfig)
--with-qt-libdir=LIB_DIR
specify qt lib path (overridden by pkgconfig)
--with-qt-plugindir=PLUGIN_DIR
--with-qt-bindir=BIN_DIR
specify qt bin path
--with-qtdbus enable DBus support (default is yes if qt is enabled
and QtDBus is found)
Thursday, June 26, 2014
compile zero coins linux daemons
need to make new folders.
cd XCOIN/src
mkdir obj
mkdir obj/zerocoin
need to change permissions.
cd src/leveldb
chmod +x build_detect_platform
make ...
troubles.. should you attempt earlier unsuccesful compile, it can break later compile.
make clean -f makefile.unix
-_-_-_-_-_-_-_
-_-_-_-_-_-_-_
-_-_-_-_-_-_-_
-_-_-_-_-_-_-_
errors that led me...
opening dependency file obj/zerocoin/Accumulator.d: No such file or directory
/leveldb.h:23: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
/////
compiled from random places.
Tuesday, April 22, 2014
Friday, February 7, 2014
CLOUD MINING MAXCOIN
FOR POOL http://max.1gh.com/
compiled from various sources :this worked ubuntu server 13.10 (azure), also debian 7.0 x64 (digital ocean)
once you've create machine and sshhhhed in..
(note to self, azure ssh login was azureuser@MYTHING.cloudapp.net)
-i have not tried this myself, yet, but i assume you can use an exchange based address rather than get the wallet to spit one out...
the wallet being reliant on command line interface. for list of commands see
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list
Create a swap file -
sudo dd if=/dev/zero of=/swapfile bs=64M count=16
sudo mkswap /swapfile
sudo swapon /swapfile
Install dependencies -
sudo apt-get update
sudo apt-get install build-essential libcurl4-openssl-dev git zip
Download the 1GH MaxCoin (SHA-3) minerd (+configure and compile) -
git clone https://github.com/1gh/cpuminer
cd cpuminer
./configure CFLAGS="-O3"
make
strip minerd
Quick test -
./minerd --help
./minerd -a keccak -o stratum+tcp://maxpool.1gh.com:17333 -u maxwalletaddress -p x
to keep it running on restarts, install supervisor, create script - apt-get install supervisorscript contents [program:mining]-a keccak -o stratum+tcp://maxpool.1gh.com:17333 -u maxwalletaddress -p xstdout_logfile=/var/log/supervisor/%(program_name)s.log | |||||||
[start script to auto open your miner in case the server resets -
/etc/init.d/supervisor stop
/etc/init.d/supervisor start
view the status of your miner -
tail -f /var/log/supervisor/mining.log
donate maxcoin to :
mRp5agadH3XCmX5vbabd3gno21LV3JNN4i
hashed together from :
cloud mining guide to maxcoin - using official cpuminer, which at this moment is trash.
https://bitcointalk.org/index.php?topic=450539.0
updated in comment to use pool miner
cloudmining guide to quarkcoin, features autostart script.
Saturday, September 29, 2012
windows bootcamp, print screen !!!
apparently ---
from
http://osxdaily.com/2011/12/19/print-screen-boot-camp/
- Capture Full Screen: FN+Shift+F11
- Capture Front Window: FN+Option+Shift+F11
from
http://osxdaily.com/2011/12/19/print-screen-boot-camp/
Sunday, September 2, 2012
booting from usb flashdrive on virtualbox OSX 10.7
OSX 10..7.4 , VirtualBox 4.1.18
importqnt note.. the reason i wanted to do this was to test the bootability of a usb flashdrive.. however, apparently being able to boot from such a drive in virtualbox doesn't give any true indication of booting a real computerrer.. oh well.
so.
install virtualbox extension pack to give usb2.0. not sure if this is necessary, but it maywell give a useful speed increase la usb2.0 vs 1
basic steps.
create a virtual hdd (usb.vmdk) which matches your usb location using command line tools.
add usb.vmdk as a hard drive in storage settings, make it as primary master.
mmm, i think that was it.
i also added a usb device filter under ports/usb settings, not sure if necessary or not.
again with greater verbosity :)
1. attach flash drive, then in disk utility unmount the partition of flash drive. step 2 will not work when mounted.
2. in terminal the command i used was (creating a virtual disk image in Documents folder) :
VBoxManage internalcommands createrawvmdk -filename /Users/admin/Documents/usbdrive.vmdk -rawdisk /dev/disk1
3. in the virtual machine settings, storage.
add hard disk, then browse to the usbdrive.vmdk just created.
then change the attributes so the usbdrive is IDE primary master.
4. settings/port - add USB filter, browse to your usb drive.. this may only be possible if its' mounted ? which makes me think it an un-necessary step.
mmm, i think that was it.
i did find that OSX kept mounting th partition. if so then the VM wouldn't boot giving an error message about being unable to open image file. this is fixed by once again unmounting in disk utility (NOT ejecting).
------------------
note - the help manual (section 9.8 - Advanced storage configuration) also includes extra variables for connecting to partitions rather than the whole drive.
version for windows
http://agnipulse.com/2009/07/boot-your-usb-drive-in-virtualbox/
also viewed was
https://forums.virtualbox.org/viewtopic.php?p=14648
adding the usb device filter came from here
http://frank.heydlauf.de/jm2c/archive/80/virtualbox-on-os-x-host-howto-mount-an-external-usb-drive
importqnt note.. the reason i wanted to do this was to test the bootability of a usb flashdrive.. however, apparently being able to boot from such a drive in virtualbox doesn't give any true indication of booting a real computerrer.. oh well.
so.
install virtualbox extension pack to give usb2.0. not sure if this is necessary, but it maywell give a useful speed increase la usb2.0 vs 1
basic steps.
create a virtual hdd (usb.vmdk) which matches your usb location using command line tools.
add usb.vmdk as a hard drive in storage settings, make it as primary master.
mmm, i think that was it.
i also added a usb device filter under ports/usb settings, not sure if necessary or not.
again with greater verbosity :)
1. attach flash drive, then in disk utility unmount the partition of flash drive. step 2 will not work when mounted.
2. in terminal the command i used was (creating a virtual disk image in Documents folder) :
VBoxManage internalcommands createrawvmdk -filename /Users/admin/Documents/usbdrive.vmdk -rawdisk /dev/disk1
3. in the virtual machine settings, storage.
add hard disk, then browse to the usbdrive.vmdk just created.
then change the attributes so the usbdrive is IDE primary master.
4. settings/port - add USB filter, browse to your usb drive.. this may only be possible if its' mounted ? which makes me think it an un-necessary step.
mmm, i think that was it.
i did find that OSX kept mounting th partition. if so then the VM wouldn't boot giving an error message about being unable to open image file. this is fixed by once again unmounting in disk utility (NOT ejecting).
------------------
note - the help manual (section 9.8 - Advanced storage configuration) also includes extra variables for connecting to partitions rather than the whole drive.
version for windows
http://agnipulse.com/2009/07/boot-your-usb-drive-in-virtualbox/
also viewed was
https://forums.virtualbox.org/viewtopic.php?p=14648
adding the usb device filter came from here
http://frank.heydlauf.de/jm2c/archive/80/virtualbox-on-os-x-host-howto-mount-an-external-usb-drive
Subscribe to:
Posts (Atom)