ls -R --color=auto /dev/ shows device files in yellow on white, when run in an xterm with black on white text. /etc/DIR_COLORS specifies yellow on black. When I chroot(2) to my old (suse 7.3) install, using the same /etc/DIR_COLORS, I see the expected yellow on black. Somehow the 40 for black background is being ignored.
james, a couple of tried to duplicate -- the output is correct in both cases. is this still an issue for you?
sorry, not reproducible, does that only happen in xterm or in all terminals ? also what xfree version and bash version are you using ?
xterm is from xfree-4.3.0-r1, bash is bash-2.05b-r3, /bin/dircolors is from fileutils-4.1.11. Ie ~x86 in general. ~/.Xdefauts includes: xterm*background: LightYellow2 xterm*faceName: Lucida Sans Typewriter-6.5:minspace=true And, yes, it does still fail to work; no cell has its background color changed by dircolors.
strange, except for the .Xdefault lines that's exactly what i have on the box i was testing on. still can't reproduce this. tried it in gnome-terminal or konsole ?
It has the same problem in gnome-terminal. But I just discovered it is a problem with ls(1), not with dircolors(1). ls(1) does do the right thing if the LS_COLORS environmental is set as per the output of dircolors, but ls(1)'s defaults leave out the background color change. In the legacy install ls(1) did the right thing w/o setting LS_COLORS. SuSE must patch ls or something. I'm sure LS_COLORS was not getting set. In any case, my presumption that ls(1) called dircolors(1) to get the color db was invalid.... Next time I'll look at the src first. :( Perhaps, however, there should be a dircolors entry in /etc/env.d?
no i don't think it's something that belongs into env.d or /etc/profile, we have it in /etc/skel/.bashrc so every regular user that is created get's DIR_COLORS but it's not something that should be global, i prefer the root accout as clean as possible.
Agreed, skel is the better place. (I left my /home partition alone when I upgraded to gentoo, so my .bashrc et alia are as they were with the previous install....) I've marked this bug invalid; feel free to change to a better resolution tag if applicable. -JimC
