Hi Clive,
John's pointed out the underlying cause.
John Palmer wrote:
> johnp@zeno:~$ ls -l /media
> total 4
> drwxr-xr-x 4 root root 4096 2013-01-13 22:23 disc0.ext3
There are two things going on here.
> > /dev/sdb1 /media/CAW1 ext4
> > rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
A block device, /dev/sdb1, can be mounted on a `mount-point', an
existing directory. The existing directory becomes hidden during the
mount. It contents still exist but attempts to traverse into it jump
across to the root directory on the mounted filesystem instead. On
unmounting, the contents re-appear.
Also hidden are the attributes of the mount-point, e.g. user and group.
Instead, those of the / directory in the mounted filesystem are seen.
To create something in a directory is to modify it; it can be thought
of as a list of (filename, inode-number) pairs. So trying to copy
something into /media/CAW1 means /media/CAW1 must give you write
permission. But /media/CAW1 is really / in the mounted filesystem, so
it comes down what did that live distro from which you formatted the
filesystem set /'s attributes to?
Have /media/CAW1 mounted and do
ls -l /media/CAW1
or for a more long-winded view of its status,
stat /media/CAW1
The user, group, and permissions will show who can modify the contents
of its root directory. They might be root:root and only writable by
owner. You can either change them,
sudo chown $USER:$USER /media/CAW1
chmod u=rwx,go=rx /media/CAW1
or leave them alone and create a sub-directory that's yours,
sudo mkdir /media/CAW1/clive
sudo chown $USER:$USER /media/CAW1/clive
Cheers, Ralph.
--
Next meeting: Bournemouth, Tuesday, 2013-04-02 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
New thread on mailing list: mailto:[email protected]
How to Report Bugs Effectively: http://goo.gl/4Xue
