Yet I didn't understand it very well...
Topic: Another Ubuntu Question - page 2. (Read 4283 times)
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
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?
Post result of running as root:
After rebooting, did you run this again?
Code:
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
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:
Code:
mount
id
ls -al /cdrom
id
ls -al /cdrom
This is what I get:
Code:
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
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#
What is working now?
After rebooting, did you run this again?
Post result of running as root:
After rebooting, did you run this again?
Code:
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
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:
Code:
mount
id
ls -al /cdrom
id
ls -al /cdrom
I'd do this:
Then as a regular user run:
If it does not complain about permissions, delete the file: rm /cdrom/permissions.txt and then try starting bitcoin-qt.
Code:
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
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:
Code:
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:
Code:
ubuntu@ubuntu:~$ echo "Testing Permissions" > /cdrom/permissions.txt
bash: /cdrom/permissions.txt: Permission denied
bash: /cdrom/permissions.txt: Permission denied
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.
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.
Make sure that you close everything that could possible have it open (e.g. gparted)
I have only the browser and the terminal opened.
This is what I get running these commands:
I also run "System Monitor" application and it shows that no process is using the device.
Make sure that you close everything that could possible have it open (e.g. gparted) Code:
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
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.
I'd do this:
Code:
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
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:
Code:
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
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.
I'd do this:
Then as a regular user run:
If it does not complain about permissions, delete the file: rm /cdrom/permissions.txt and then try starting bitcoin-qt.
Code:
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
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:
Code:
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.
Code:
mount
Code:
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)
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)
Post result of mount command.
Code:
mount
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
Code:
root@ubuntu:/home/ubuntu# chown 999:999 /cdrom
chown: changing ownership of ‘/cdrom’: Operation not permitted
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:
Code:
~ id
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
or as root:
Code:
# id myuser
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
I get a syntax error with this code.
Code:
id
id myuser
where myuser is your usernameid myuser
I've just tried to change ownership of /cdrom, but I get this:
Code:
root@ubuntu:/home/ubuntu# chown 999:999 /cdrom
chown: changing ownership of ‘/cdrom’: Operation not permitted
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:
Code:
~ id
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
or as root:
Code:
# id myuser
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
I get a syntax error with this code.
Sorry.
~ means running as regular user.
# means running as root
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:
Code:
~ id
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
or as root:
Code:
# id myuser
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
I get a syntax error with this code.
Code:
id
id myuser
where myuser is your username id myuser
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:
Code:
~ id
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
or as root:
Code:
# id myuser
uid=1000(myuser) gid=1000(mygroup) ...
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...
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:
Code:
# 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:
Code:
~ id
uid=1000(myuser) gid=1000(mygroup) ...
uid=1000(myuser) gid=1000(mygroup) ...
or as root:
Code:
# id myuser
uid=1000(myuser) gid=1000(mygroup) ...
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
Jump to: