If I go in /cdrom >>> Properties this is what I get: 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
|
|
|
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 This is what I get: root@ubuntu:/home/ubuntu# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=2010832k,nr_inodes=502708,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404620k,mode=755) /dev/loop0 on /rofs type squashfs (ro,noatime) /cow on / type overlay (rw,relatime,lowerdir=//filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime) cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755) tmpfs on /run/user/999 type tmpfs (rw,nosuid,nodev,relatime,size=404620k,mode=700,uid=999,gid=999) gvfsd-fuse on /run/user/999/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=999,group_id=999) /dev/sdb2 on /media/ubuntu/casper_rw type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2) /dev/loop1 on /media/ubuntu/casper-rw type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2) /dev/sda1 on /media/ubuntu/Riservato per il sistema type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sda2 on /media/ubuntu/AA1EAC811EAC47E1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sdb1 on /cdrom type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) root@ubuntu:/home/ubuntu# id <myuser> bash: syntax error near unexpected token `newline' root@ubuntu:/home/ubuntu# ls -al /cdrom total 4185956 drwxr-xr-x 14 root root 16384 Jan 1 1970 . drwxr-xr-x 1 root root 4096 Oct 5 14:06 .. -rwxr-xr-x 1 root root 134 Apr 22 16:28 autorun.inf drwxr-xr-x 3 root root 16384 Apr 22 16:30 boot drwxr-xr-x 2 root root 16384 Apr 22 16:30 casper -rwxr-xr-x 1 root root 4283432960 Oct 11 10:10 casper-rw drwxr-xr-x 2 root root 16384 Apr 22 16:29 .disk drwxr-xr-x 3 root root 16384 Apr 22 16:29 dists drwxr-xr-x 3 root root 16384 Apr 22 16:30 EFI drwxr-xr-x 2 root root 16384 Apr 22 16:30 install drwxr-xr-x 2 root root 16384 Apr 22 16:30 isolinux -rwxr-xr-x 1 root root 18092 Apr 4 2012 license.txt -rwxr-xr-x 1 root root 21517 Apr 22 16:30 md5sum.txt drwxr-xr-x 2 root root 16384 Apr 22 16:29 pics drwxr-xr-x 4 root root 16384 Apr 22 16:29 pool drwxr-xr-x 2 root root 16384 Apr 22 16:29 preseed -rwxr-xr-x 1 root root 226 Apr 22 16:29 README.diskdefines drwxr-xr-x 2 root root 16384 Oct 5 13:52 System Volume Information -rwxr-xr-x 1 root root 49070 Jan 15 2015 Uni-USB-Installer-Copying.txt -rwxr-xr-x 1 root root 19261 Jun 26 20:58 Uni-USB-Installer-Readme.txt drwxr-xr-x 2 root root 16384 Oct 5 13:52 uui -rwxr-xr-x 1 root root 2573712 Oct 17 2014 wubi.exe root@ubuntu:/home/ubuntu#
|
|
|
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. I restarted the system and now it works, but I still haven't got permissions in /cdrom mount point. I get this: ubuntu@ubuntu:~$ echo "Testing Permissions" > /cdrom/permissions.txt bash: /cdrom/permissions.txt: Permission denied
|
|
|
Make sure that you close everything that could possible have it open (e.g. gparted)
I have only the browser and the terminal opened.
|
|
|
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 This is what I get running these commands: root@ubuntu:/home/ubuntu# umount /dev/sdb1 umount: /cdrom: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).) root@ubuntu:/home/ubuntu# 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 root@ubuntu:/home/ubuntu# mount /dev/sdb1 mount: /dev/sdb1 is already mounted or /cdrom busy /dev/sdb1 is already mounted on /cdrom
I also run "System Monitor" application and it shows that no process is using the device.
|
|
|
The match is over.
Bosnia 2 Wales 0
|
|
|
Post result of mount command. sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=2010832k,nr_inodes=502708,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=404620k,mode=755) /dev/sdb1 on /cdrom type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/loop0 on /rofs type squashfs (ro,noatime) /cow on / type overlay (rw,relatime,lowerdir=//filesystem.squashfs,upperdir=/cow/upper,workdir=/cow/work) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (rw,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime) cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755) tmpfs on /run/user/999 type tmpfs (rw,nosuid,nodev,relatime,size=404620k,mode=700,uid=999,gid=999) gvfsd-fuse on /run/user/999/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=999,group_id=999) /dev/sdb2 on /media/ubuntu/casper_rw type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2) /dev/loop1 on /media/ubuntu/casper-rw type ext2 (rw,nosuid,nodev,relatime,uhelper=udisks2)
|
|
|
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 and I (or other user) will tell you what to modify in order to set user and group for the mountpoint. In options you should add 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 remount (as root: mount /dev/sdb1).
Luckily this will work as expected, if I'm not wrong.
This is etc/fstab content: overlay / overlay rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0
|
|
|
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. the commands are without the ~ or # and the second line is just the output. So really, what you should type into the terminal is this where myuser is your username I've just tried to change ownership of /cdrom, but I get this: root@ubuntu:/home/ubuntu# chown 999:999 /cdrom chown: changing ownership of ‘/cdrom’: Operation not permitted
|
|
|
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.
|
|
|
first shut down bitcoin core.
Then check your permissions. Make sure that you have permission to copy things to /cdrom. Make sure that you have permissions to even move the bin folder.
I don't have permissions to copy things to /cdrom, to move folders or even to create a new folder in /cdrom. I just don't know why...
|
|
|
When you install, if their is an installation wizard, set the installation directory to a folder in sdb1. If it is just binaries you downloaded, just copy them to a folder on sdb1 and run the program from there.
If I try to change the installation directory, I see the following error message: Cannot obtain a lock on data directory /cdrom. Bitcoin Core is probably already running. No such file or directory. For bitcoin core specifically, just copy all of the binaries to a folder in sdb1 and run the program from there.
If I try to copy the binaries to a folder in /cdrom I get the following message: The folder “bin” cannot be copied because you do not have permissions to create it in the destination.
|
|
|
Hi! It's me again Let me explain what is my new question for you Linux experts. I installed Ubuntu 15.04 on an external hard disk, using the free tool called "LiLi" . Then I booted my Linux distro changing the BIOS settings. The main problem with these kinds of installation is persistence. As a standard, FAT32 allows a maximum persistence of 4GB, but it could be easily changed launching the "gparted" application. And this is exactly what I did: I launched gparted and set HD persistence to 1TB. So this is what I get now: Anyway, now I wonder how to install Bitcoin Core ( and any other programs ) on sdb1. How can I do this?
|
|
|
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. Yes, I can install build-essential.
|
|
|
Match ended.
Final score: England 2 Estonia 0
|
|
|
I'm glad to see that you got it working. In the end, you just downloaded the precompiled binaries? If you can't install from source just download the binaries from bitcoin.org. They work out of the box. Just extract the tarball and run.
Ok. I have downloaded it from bitcoin.org and then extracted the tarball. But which application do I need to run the bitcoin-qt file? I am trying with Ubuntu Software Center but I get an error message Open up a terminal in the bin folder and run the following commands chmod +x bitcoin-qt ./bitcoin-qt Every time you want to run bitcoin at, you need to use the second command. Don't close the terminal while the program is running. Thank you very much Abdussamad and knightdk! Now it works I would like to make a donation to both of you to thank you for your patience and help. Please send me a PM or reply under this post writing your addresses. I am gonna make it as soon as possible. Yes, I downloaded the precompiled binaries from bitcoin.org, extracted the tarball and then opened bitcoin-qt by the terminal. The procedure described here didn't work.
|
|
|
Very reliable user! I made a trade with him, sent first and everything went smooth.
|
|
|
If you can't install from source just download the binaries from bitcoin.org. They work out of the box. Just extract the tarball and run.
Ok. I have downloaded it from bitcoin.org and then extracted the tarball. But which application do I need to run the bitcoin-qt file? I am trying with Ubuntu Software Center but I get an error message Open up a terminal in the bin folder and run the following commands chmod +x bitcoin-qt ./bitcoin-qt Every time you want to run bitcoin at, you need to use the second command. Don't close the terminal while the program is running. Thank you very much Abdussamad and knightdk! Now it works I would like to make a donation to both of you to thank you for your patience and help. Please send me a PM or reply under this post writing your addresses. I am gonna make it as soon as possible.
|
|
|
|