Bug 449985 - colorize files with capabilities
Summary: colorize files with capabilities
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 449984
TreeView+ depends on / blocked
 
Reported: 2008-06-04 16:05 UTC by Peter Vrabec
Modified: 2008-07-31 13:50 UTC (History)
3 users (show)

Fixed In Version: coreutils-6.12-7.fc10
Clone Of:
Environment:
Last Closed: 2008-07-24 14:02:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Vrabec 2008-06-04 16:05:04 UTC
Description of problem:
'ls' command should colorize the files with capabilities like it does for setuid
programs.

#setcap cap_net_bind_service=ep test.log
#getcap test.log
test.log = cap_net_bind_service+ep
#ls

Comment 1 Ondrej Vasik 2008-07-15 13:37:11 UTC
Patch done by Kamil Dudka, proposed upstream, waiting for reaction. You could
monitor it on the thread
http://lists.gnu.org/archive/html/bug-coreutils/2008-07/msg00099.html

Comment 2 Habig, Alec 2008-07-31 13:35:40 UTC
This bug has caused a regression which renders tcsh unusable.

With the pushing of coreutils-6.10-28.fc9.i386, instances of tcsh now fail early
in their init scripting (before getting to the user ~/.tcshrc file) with the error:

  Unknown colorls variable `ca'.

So at the moment all of my command-line work has been broken badly by this
cosmetic update.

Backing out to coreutils-6.10-27.fc9.i386 fixes the problem.

This does not happen with bash.  Can one of the proponents of this bug please
try firing up tcsh to see what didn't get correspondingly updated somewhere in
the /etc area?  


Comment 3 Kamil Dudka 2008-07-31 13:50:20 UTC
Thanks for your report.

This bug is already reported (including patch) against tcsh as #457342. There 
is also a workaround - clearing LS_COLORS variable should help to start tcsh.

I am sorry for inconveniences.


Note You need to log in before you can comment on or make changes to this bug.