0

I'm using the Ubuntu bash on Windows 10(v1804) and am experiencing a problem with the chown command. I'm trying to change the ownership of a file I created on my desktop with the following path:

mnt/c/users/XY/Desktop/filecat.txt

Using sudo -i I switch to the root user and navigate to the mentioned path and run

chown -v user1 filecat.txt

after which I get this message confirming the ownership change:

changed ownership of 'filecat.txt' from amar to user1

However, when I run ls -l filecat.txt it does not show any change in user. It's still the same user which created the file.

Anyone have any idea what might be the problem? I've been searching online but finding nothing similar so here I am asking the question myself.

EDIT:

This is the full output of the command line mentioned in the comments.

$ ls -l filecat.txt; chown user1 filecat.txt; ls -l filecat.txt
-rwxrwxrwx 1 amar amar 2054 Jul  8 20:44 filecat.txt
-rwxrwxrwx 1 amar amar 2054 Jul  8 20:44 filecat.txt

The file system I'm using is NTFS on both of my partitions. Using lsblk results in the following output

lsblk: failed to access sysfs directory: /sys/dev/block: No such file or directory

The answer provided in the linked question suggested editing a certain line in the etc/fstab file. My etc/fstab file contains only the following line 

LABEL=cloudimg-rootfs   /        ext4   defaults        0 0
Oli
  • 299,380
bambooch
  • 1

1 Answers1

1

I had the same issue on my Windows 10 Ubuntu subsystem.

The d drive wouldn't let me change anything from root:root, even though whoami told me I was under my own user.

I then went to my home directory, and from there, everything worked as expected.

Thomas Amar
  • 111
  • 2