 Show Posts
|
|
Pages: [1] 2 »
|
|
All the mixing process is now responsive.
You can mix from any device. If you find any bug, let me know. Thanks.
A non-critical bug has been fixed.
24 Nov 2015
Updates to the core system:
A new mixing algorithm has been designed and implemented in order to make your orders processed faster.
You now can send Bitcoins from various sources and the system will intelligently wait for all your transfers to be confirmed, no need to wait if you do not want to. Just do not set Gateway waiting time, and you are ready to go.
Your mixes will be now processed faster and more secure, for your convenience, implementing an intelligent algorithm to process your orders. No delays, no waiting.
Update #2:
Change 3 to 2 confirmations required.
With only 2 confirmations, no matter the quantity to mix, your orders will be mixed now more rapidly.
Happy mixing.
|
|
|
|
That tutorial might be outdated. You can find the archive at: https://bitcoin.org/bin/I think you should be using 0.11.1 version in order to get the best performance and features, and also security updates if any. 64 Bits CPU (OS: Linux): wget https://bitcoin.org/bin/bitcoin-core-0.11.1/bitcoin-0.11.1-linux64.tar.gz 32 Bits CPU (OS: Linux): https://bitcoin.org/bin/bitcoin-core-0.11.1/bitcoin-0.11.1-linux32.tar.gz |
|
|
|
|
New Banner design updated and inserted in the main post.
Only 2 confirmations are required to process your requests, rapidly processing them for your convenience.
|
|
|
|
I think I am going to install some LInux distro on hard disk, when I will buy a second computer.
That's a good choice. |
|
|
|
Anyway I think I'm gonna switch back to windows. Linux is just too complicated for me!
I understand you. I'm sure this problem is not too difficult to solve. In an interactive session where I could run commands, it would have been faster. If you have enough time, I would suggest taking some Linux course on your own. Yet I would like to thank you very much, bitmix.in. You have been very kind trying to help me. If you write down your address I will send you a tip, anyway  I'm sending you a PM in 2~5 minutes. |
|
|
|
I get this: touch: cannot touch ‘/cdrom/t’: Permission denied
You have changed to Linux Mint. As root: id mint
# Result: (for example) uid=1000(mint) gid=1000(mint) .... Get the uid=? and gid=? values from the previous command and replace it in the next command. As root, post the results here: mount
mount -o remount,rw,uid=1000,gid=1000 /dev/sdb1 /cdrom
mount
su mint
touch /cdrom/permissions.txt I guess you have rebooted the machine and the external hard disk was not remount correctly before running touch, or maybe, your UID is not 999 now, getting forbidden permissions error. The more things you post details about, the better for me and other users to solve your problem. |
|
|
|
Could also do chmod and chown on the relevant files in /cdrom once it's mounted rw, it looks like there's a potential permissions issue here too unless his user is in a group that allows media access. Also, this isn't important, but it's a little ugly to be mounting /cdrom as rw, doesn't that substring 'rom' stand out a little too loudly? I tend to mount these things in /media/usb or just /mnt, myself. I agree. /cdrom is not a good mount point. About chmod/chown, I think that it's not possible to edit permissions because it's a FAT32 filesystem which does not allow specific file/directory permissions, but it will need to be mount with a specific UID and GID as owner for the filesystem. An EXT4 filesystem will allow this. This step has been already tried previously. I'm waiting for the author of the thread to tell the result, but I did not have an answer since Friday. |
|
|
|
In the end, it seems to me like downloading a precompiled binary might have been a good match for this user's level of experience and pluck.
When downloading a precompiled binary, it's also a good practice to perform checksums. |
|
|
|
Did you try: mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom If that command is successful, post ls -al command result and try to create a file in /cdrom as a regular user: echo testing > /cdrom/permissions-test.txt |
|
|
|
The /cdrom mount point is still mount as root. After the ls -al /cdrom command you can see root being owner of the mountpoint. And after mount, the mount table will show /dev/sdb1 mounted without the specific uid and gid options. /dev/sdb1 on /cdrom type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) This should be: /dev/sdb1 on /cdrom type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,uid=999,gid=999) Run as root: mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom Post the result of command (run as a regular user): idWhen I wrote <myuser>, I meant replacing <myuser> with your username, without <>. I could even help you in a more direct and interactive manner, if you wish, through some remote support application like Teamviewer. PM me in order to start a remote support session.
I search on google how to change permissions and ownership of a mount point, but the usual answer, to use chown command as a root doesn't work  If I'm correct, FAT32 mount points does not support changing permissions to specific files/directories, but instead, rwx (read,write,execute) permissions, and user/group owner needs to be set up at the moment of mounting the file system, through the mount options: (owners) uid, gid; (permissions) umask, fmask and dmask. On the other hand, an EXT4 file system will allow you chowing/chmoding specific files/directories or the whole mount point directly. In EXT4, there is not an option to set up uid and gid options, as this is more specific to other file systems, such as FAT32 and NTFS if I'm not confused. |
|
|
|
What is working now? After rebooting, did you run this again? umount /dev/sdb1
echo "/dev/sdb1 /cdrom vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,uid=999,gid=999 0 0" >> /etc/fstab
mount /dev/sdb1 Post result of running as root: mount
id <myuser>
ls -al /cdrom |
|
|
|
|
Some terminal is in the /cdrom directory?
Post the result of: lsof | grep /cdrom
This will get possible processes which are using that directory.
Do not run the previous echo command more than once, or it will duplicate the lines written in the fstab.
nano /etc/fstab - then remove the lines if duplicated. CTRL+X answer yes, and press enter (will save as fstab the default file).
By the way, I'm curious. That is a bootable live Ubuntu image, right? You will have to repeat the echo >> fstab command after each reboot, as it will not save the changes made to the root filesystem (/).
Just to add something: this is why I prefer using EXT file systems when working in Linux. I can set permissions and owners to specific files/directories instead of the whole mount point.
|
|
|
|
I'd do this: umount /dev/sdb1
echo "/dev/sdb1 /cdrom vfat rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,uid=999,gid=999 0 0" >> /etc/fstab
mount /dev/sdb1 Then as a regular user run: echo "Testing Permissions" > /cdrom/permissions.txt If it does not complain about permissions, delete the file: rm /cdrom/permissions.txt and then try starting bitcoin-qt. |
|
|
|
Post result of mount command. |
|
|
|
root@ubuntu:/home/ubuntu# chown 999:999 /cdrom
chown: changing ownership of ‘/cdrom’: Operation not permitted
I forgot about this. It's not a directory, but instead it is a mount point. Please, post your /etc/fstab file contents in here (as root: cat /etc/fstab) and I (or other user) will tell you what to modify in order to set user and group for the mountpoint. In mount point /cdrom you should add the options uid=999,gid=999 (the user and group id returned by the ID command I posted earlier). Then unmount (as root: umount /dev/sdb1) and re-mount (as root: mount /dev/sdb1). Luckily this will work as expected, if I'm not wrong. |
|
|
|
If you'd like to know what's your user's primary group, normally it will be the same name as your username, but you can check this by running as regular user: ~ id
uid=1000(myuser) gid=1000(mygroup) ... or as root: # id myuser
uid=1000(myuser) gid=1000(mygroup) ... I get a syntax error with this code. Sorry. ~ means running as regular user. # means running as root |
|
|
|
Cannot obtain a lock on data directory /cdrom
That's most likely to be because of permissions as well. I will extend knightdk answer: In order to change permissons run as root, replacing myuser:mygroup to your installation details: # chown myuser:mygroup /cdrom If you'd like to know what's your user's primary group, normally it will be the same name as your username, but you can check this by running as regular user: ~ id
uid=1000(myuser) gid=1000(mygroup) ... or as root: # id myuser
uid=1000(myuser) gid=1000(mygroup) ... ~ means run as user (do not type it into the command) # means run as root (do not type it, it will result in a comment and not returning any value) The lines below are the result of executing the commands |
|
|
|
I wonder if that particular ppa isn't updated very often, if that's why the dependencies couldn't be installed (perhaps because newer versions are already installed on your system or something along those lines). Anyway, I'm glad you got it figured out.
I personally performed a clean Ubuntu 15.04 installation. Then, I replicated the same steps that HardcoreSuperstar did, and I did not have that dependencies problems. The PPA is updated in each bitcoin-qt revision, If I'm not confused. I would like to know if you are able to install any other package: Try doing: apt-get install <some-package> - (for example: apt-get install build-essential) Because this problem might not be PPA or bitcoin-qt-package related, but I misconfiguration in Ubuntu and the package manager itself. Do this if you would like to further continue diagnosing. |
|
|
|
|
By the way, elect22, I'd like to thank you for your help. If you like, post here a BTC address, or PM me in order to not flood this thread, or simply open a support ticket in the web-service, so I can send you a tip for your help.
About the service:
A new mixing system for regular orders (non-gateway) is in the final stage of development. The new system will process orders much faster for your convenience.
|
|
|
|
|
