For ls(1), you signal whether to use (or not) a colour palette by setting
the --color option. Often, a distribution will set (through the
/etc/profile script or one of the scripts in /etc/profile.d) an alias for
ls(1) that specifies --color=always. You can disable colourization by
altering or unsetting this alias, or specifying ls with the --color=none
option.
If you prefer ls(1) to colourize it's listing, but don't like the colours
it uses, you can change the colours to your liking. ls(1) determines how
to colourize from the value stored in the LS_COLORS environment variable.
The same /etc/profile script that sets the ls(1) alias often sets the
LS_COLORS envvar by eval(uating) the output of the dircolors(1) command.
You can /alter/ the colours used by ls(1) by changing the information
stored in the LS_COLORS envvar, or (more globally) by altering the
information output by the dircolors(1) command.
dircolors(1) /may/ use an input configuration file, but has a "database"
of colours compiled into it, to use if you do not specify a config file.
/If/ your setup uses dircolors(1) with a config file, you can alter the
contents of that config file to give you a more pleasing palette.
Otherwise, you may be stuck with the colour palette that dircolors(1)
was compiled with. It is worth noting that this colour palette maps
ls item types (directories, files, special files, etc) to specific
escape sequences /by/ terminal type, as each terminal (emulated or real)
may use different escape sequences for colourization. The colour
mappings may not be obvious from the escape sequences: read the doc
on the terminal /you/ use to ensure that you select the correct sequence.
HTH
--
Lew Pitcher
"In Skills We Trust"