Another Ubuntu Question

[Bitmix.in]

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 <myuser>
ls -al /cdrom

[HardcoreSuperstar]

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

[HardcoreSuperstar]

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 

[HardcoreSuperstar]

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

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

[Bitmix.in]

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

[achow101]

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.

[HardcoreSuperstar]

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)

[Bitmix.in]

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

[tspacepilot]

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]

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]

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.

[HardcoreSuperstar]

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]

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]

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]

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]

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]

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]

Code:

$ touch /cdrom/t

I get this:

Code:

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

[Bitmix.in]

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]

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