Teej: I still get the Operation not permitted message in Jaunty, and I
can test it in Karmic one of these days.
--
misleading error message in terminal when trying to chmod on fat32
https://bugs.launchpad.net/bugs/164507
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: coreutils (Ubuntu)
Importance: Undecided = Low
--
cannot chmod on fat32
https://bugs.launchpad.net/bugs/164507
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have marked this as Low, as I doubt there will be many trying to chmod
a fat32 partition. Even by Windows standards, ntfs is the current one. I
have followed the above test conditions, and can confirm that this
indeed is still a problem in Karmic, coreutils version 7.4-2ubuntu1 - I
believe there
Hi Christoph,
Unfortunately, you didn't specify which version of (x)ubuntu you were using. Do
you know if this is still an issue in a supported version, i.e. Hardy onwards.
Also, are you able to test this in Karmic.
Thank you.
** Changed in: coreutils (Ubuntu)
Status: New = Incomplete
mount -t vfat has a quiet option now. See man(1).
quiet: Turn on the quiet flag. Attempts to chown or chmod files do
not return errors, although they fail. Use with caution!
It isn't enabled by default. However, a lot of things now don't return an
error at all, even without quiet. e.g.
This is one of those parts of Unix that you're probably just going to
have to get used to.
Unfortunately, there are standards (e.g. POSIX.1) that say what possible error
codes a system call is allowed to return, and what they imply for that system
call. run
man 2 chmod
to see the manual for
** Changed in: coreutils (Ubuntu)
Sourcepackagename: xfce4-terminal = coreutils
--
misleading error message in terminal when trying to chmod on fat32
https://bugs.launchpad.net/bugs/164507
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
