Another Ubuntu Question | Bitcointalksearch.org

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: HardcoreSuperstar on October 15, 2015, 04:15:19 AM

Anyway I think I'm gonna switch back to windows. Linux is just too complicated for me!

Sad to hear it. FWIW, I find windows impossible to use. I guess it's what you're used to. As you know Linux is a clone of UNIX, which was envisioned as a multi-user time-sharing operating system from the start (way back in the late 70s). Windows only got multisuer functionality in like windows 95, I think. Anyway, if you have multiple users you need a good system of permissions and ownership. It seems to me that your difficulties are in part from the fact that you're trying to use a FAT32 partition. Why not use ext files system?

Anyway, good luck to you. If you want to keep debugging there are plenty of people here who are willing to try to help.

Best,

TSP

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 15, 2015, 05:29:05 AM

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 15, 2015, 05:20:29 AM

Quote from: HardcoreSuperstar on October 15, 2015, 04:15:19 AM

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.

I think I am going to install some LInux distro on hard disk, when I will buy a second computer. Maybe installing it on an external USB device requires too many steps to work in a proper way...

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 15, 2015, 04:15:19 AM

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.

Quote from: HardcoreSuperstar on October 15, 2015, 04:15:19 AM

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 15, 2015, 03:31:11 AM

Quote from: HardcoreSuperstar on October 15, 2015, 03:15:21 AM

I get this:

Code:

touch: cannot touch ‘/cdrom/t’: Permission denied

You have changed to Linux Mint.
As root:

Code:

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:

Code:

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.

Uid and gid values are the same as before: 999.

Anyway I think I'm gonna switch back to windows. Linux is just too complicated for me!

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

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 15, 2015, 03:15:21 AM

I get this:

Code:

touch: cannot touch ‘/cdrom/t’: Permission denied

You have changed to Linux Mint.
As root:

Code:

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:

Code:

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: tspacepilot on October 14, 2015, 06:17:44 PM

Code:

$ touch /cdrom/t

I get this:

Code:

touch: cannot touch ‘/cdrom/t’: Permission denied

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: HardcoreSuperstar on October 14, 2015, 02:55:04 PM

Yes, /dev/sdb1 is mounted on /cdrom.
Now how can we proceed in order to change ownership?

Above, Bitmix.in says that FAT32 doesn't support per file/directory group and ownership. The idea of that mount command was to mount with uid 999 as owner and group. I assumed this was because the account you want to use is uid 999. Have you tried writing a file to it?

Code:

$ touch /cdrom/t

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: tspacepilot on October 14, 2015, 12:43:45 PM

Quote from: HardcoreSuperstar on October 14, 2015, 12:28:04 PM

Quote from: tspacepilot on October 14, 2015, 11:51:17 AM

Quote from: HardcoreSuperstar on October 14, 2015, 02:47:28 AM

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

No, this command is unsuccessful.

I have to add I recently switched from Ubuntu to Linux Mint 17.2. Anyway I still haven't solved this issue.

I haven't used Linux Mint, but I understand that it's still downstream of debian. In any case, certainly things like mounting drives and reading/writing from them is going to be the same.

On topic, you said the command was unsuccessful, can you cut-n-paste the exact response from the shell?

I get nothing at all.

Code:

mint@mint ~ $ sudo su
mint mint # mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom
mint mint #

That actually means success

You should be about to rerun "mount" without any arguments to see that /dev/sdb1 is mounted on /cdrom rw.

Cheers!

EDIT: for your own education, in general UNIX command return 0 upon success. The return code from the last command is stored in your shell as $?. If you say "echo $?" you can see the return code of the previous command.

Yes, /dev/sdb1 is mounted on /cdrom.
Now how can we proceed in order to change ownership?

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: HardcoreSuperstar on October 14, 2015, 12:28:04 PM

Quote from: tspacepilot on October 14, 2015, 11:51:17 AM

Quote from: HardcoreSuperstar on October 14, 2015, 02:47:28 AM

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

No, this command is unsuccessful.

I have to add I recently switched from Ubuntu to Linux Mint 17.2. Anyway I still haven't solved this issue.

I haven't used Linux Mint, but I understand that it's still downstream of debian. In any case, certainly things like mounting drives and reading/writing from them is going to be the same.

On topic, you said the command was unsuccessful, can you cut-n-paste the exact response from the shell?

I get nothing at all.

Code:

mint@mint ~ $ sudo su
mint mint # mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom
mint mint #

That actually means success

You should be about to rerun "mount" without any arguments to see that /dev/sdb1 is mounted on /cdrom rw.

Cheers!

EDIT: for your own education, in general UNIX command return 0 upon success. The return code from the last command is stored in your shell as $?. If you say "echo $?" you can see the return code of the previous command.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: tspacepilot on October 14, 2015, 11:51:17 AM

Quote from: HardcoreSuperstar on October 14, 2015, 02:47:28 AM

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

No, this command is unsuccessful.

I have to add I recently switched from Ubuntu to Linux Mint 17.2. Anyway I still haven't solved this issue.

I haven't used Linux Mint, but I understand that it's still downstream of debian. In any case, certainly things like mounting drives and reading/writing from them is going to be the same.

On topic, you said the command was unsuccessful, can you cut-n-paste the exact response from the shell?

I get nothing at all.

Code:

mint@mint ~ $ sudo su
mint mint # mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom
mint mint #

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: HardcoreSuperstar on October 14, 2015, 02:47:28 AM

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

No, this command is unsuccessful.

I have to add I recently switched from Ubuntu to Linux Mint 17.2. Anyway I still haven't solved this issue.

I haven't used Linux Mint, but I understand that it's still downstream of debian. In any case, certainly things like mounting drives and reading/writing from them is going to be the same.

On topic, you said the command was unsuccessful, can you cut-n-paste the exact response from the shell?

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

No, this command is unsuccessful.

I have to add I recently switched from Ubuntu to Linux Mint 17.2. Anyway I still haven't solved this issue.

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: Bitmix.in on October 13, 2015, 10:27:35 AM

Quote from: tspacepilot on October 13, 2015, 02:54:53 AM

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.

Right, good point about the filesystem. Also FAT32 isn't going to allow for files larger than 4GB. That shouldn't be a problem for blockchain files, but it's worth keeping in mind.

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: tspacepilot on October 13, 2015, 02:54:53 AM

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.

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: Bitmix.in on October 11, 2015, 04:33:34 PM

Did you try:

Code:

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

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.

Bitmix.in

newbie

Activity: 35

Merit: 0

Did you try:

Code:

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

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 11, 2015, 05:35:32 AM

Post the result of command (run as a regular user): id

This is what I get:

Code:

uid=999(ubuntu) gid=999(ubuntu) groups=999(ubuntu),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),115(lpadmin),131(sambashare)

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Are you sure it isn't just that the /cdrom mount point is only for root? How about changing the mount point to somewhere you know that you have access? Try making a folder in your home directory and mount the partition there.

Bitmix.in

newbie

Activity: 35

Merit: 0

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.

Code:

/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:

Code:

/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:

Code:

mount -o remount,rw,uid=999,gid=999 /dev/sdb1 /cdrom

Post the result of command (run as a regular user): id
When I wrote , I meant replacing 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.

Quote from: HardcoreSuperstar on October 11, 2015, 03:39:27 AM

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 Angry

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

I found this guide: http://www.tuxradar.com/answers/669

Yet I didn't understand it very well... Undecided

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

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 Angry

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 11, 2015, 02:41:14 AM

What is working now?

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

Post result of running as root:

Code:

mount
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#

Bitmix.in

newbie

Activity: 35

Merit: 0

What is working now?

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

Post result of running as root:

Code:

mount
id
ls -al /cdrom

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 10, 2015, 03:28:40 PM

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

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

Bitmix.in

newbie

Activity: 35

Merit: 0

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: achow101 on October 10, 2015, 03:46:02 PM

Make sure that you close everything that could possible have it open (e.g. gparted)

I have only the browser and the terminal opened.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: HardcoreSuperstar on October 10, 2015, 03:40:54 PM

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

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)

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 10, 2015, 03:28:40 PM

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

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

I also run "System Monitor" application and it shows that no process is using the device.

Bitmix.in

newbie

Activity: 35

Merit: 0

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

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 10, 2015, 03:21:21 PM

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)

Bitmix.in

newbie

Activity: 35

Merit: 0

Post result of mount command.

Code:

mount

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 10, 2015, 03:03:35 PM

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

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 10, 2015, 03:00:43 PM

Code:

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: achow101 on October 10, 2015, 02:52:04 PM

Quote from: HardcoreSuperstar on October 10, 2015, 02:43:47 PM

Quote from: Bitmix.in on October 10, 2015, 02:39:36 PM

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) ...

or as root:

Code:

# 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

Code:

id
id myuser

where myuser is your username

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

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 10, 2015, 02:43:47 PM

Quote from: Bitmix.in on October 10, 2015, 02:39:36 PM

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) ...

or as root:

Code:

# 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

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: HardcoreSuperstar on October 10, 2015, 02:43:47 PM

Quote from: Bitmix.in on October 10, 2015, 02:39:36 PM

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) ...

or as root:

Code:

# 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

Code:

id
id myuser

where myuser is your username

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: Bitmix.in on October 10, 2015, 02:39:36 PM

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) ...

or as root:

Code:

# id myuser
uid=1000(myuser) gid=1000(mygroup) ...

I get a syntax error with this code.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: achow101 on October 10, 2015, 11:23:53 AM

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...

Bitmix.in

newbie

Activity: 35

Merit: 0

Quote from: HardcoreSuperstar on October 10, 2015, 11:18:14 AM

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) ...

or as root:

Code:

# 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

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: HardcoreSuperstar on October 10, 2015, 11:18:14 AM

Quote from: achow101 on October 10, 2015, 10:29:48 AM

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.

Quote from: achow101 on October 10, 2015, 10:29:48 AM

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.

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.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Quote from: achow101 on October 10, 2015, 10:29:48 AM

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.

Quote from: achow101 on October 10, 2015, 10:29:48 AM

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.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

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 you are installing with an apt-get command, I don't think it is possible to change the installation directory.

For bitcoin core specifically, just copy all of the binaries to a folder in sdb1 and run the program from there. If you want to also have the data for bitcoin core on sdb1, then use

Code:

-datadir=

to specify the directory. is obviously where you put the path to that directory.

You should also change the PATH environment variable to include the folders where you put the installed programs at so that you can run them from anywhere.

HardcoreSuperstar

full member

Activity: 238

Merit: 100

★YoBit.Net★ 350+ Coins Exchange & Dice

Hi!
It's me again Cheesy

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?

Topic: Another Ubuntu Question (Read 4283 times)