* Imagenes de instalación de las versiones estables para Mageia y OpenMandriva.

OpenMandriva: Mageia (Mageia 9) 20/Agosto/2023 - Anuncio, Descargas.

Blogdrake recomienda descargar las imágenes de instalación (iso) vía torrent para evitar corrupción de datos, aprovechar mejor su ancho de banda y mejorar la difusión de las distribuciones.

Mensaje de error : Unknown colorls variable `mh'

Hola, bueno estaba instalando iraf, que es un software de analisis de fotos astronomicas, y de paso quería hacer una guía de instalacion de este programa para usuarios de mandriva. (soy estudiante de astronomía asi que tengo que saber ocuparlo si o si)
el caso es que trabajando en ello y tratando de ejecutar el csh me aparece lo siguiente.

[root@localhost rovmeli]# csh
Unknown colorls variable `mh'.

he encontrado posibles respuestas en dos foros, uno en frances, pero no cacho que onda ya que no hablo ni jota de frances

http://forum.mandriva.com/viewtopic.php?t=117218

y otro en ingles

https://qa.mandriva.com/show_bug.cgi?id=53139

El caso es que como no soy experto en esta cosa, no cacho cuales son las lineas de comando a utilizar.

Segun lo que veo hay que editar unas lineas.

alguien me podría ayudar.

atte
rodrigo
---------------------------------------------------------------------------------------------------------------------
Okey como predomina el imperio, tuve que recurrir a mi ingles de videojuego para tratar de entender que diablos pasa.
La primera solucion que dan en el foro en ingles es eliminar el archivo /etc/profile.d/alias.csh
o volver a la version anterior de coreutils que es la que esta dando problemas.
la version que viene por defecto es la coreutils-7.5-1mdv2010.0.src.rpm y dicen que se soluciona instalando la version
coreutils-7.4-2mdv2010.0.i586.rpm, lo cual no he podido hacer por que el sistema no me deja.
tampoco puedo eliminar el coreutils-7.5, por que si no el mandriva se va al cuerno.

existen otras alternativas donde hay que editar unos ficheros, sin embargo no puedo abrir el kate o el kwrite desde la consola, y simplemente no entiendo como usar el vi.

ahora la ultima solución es una parche que se encuentra en http://cvs.fedoraproject.org/viewvc//devel/tcsh/tcsh-6.17.00-mh-color.patch?view=markup , pero no se como ejecutarlo.

en fin podría alguien orientarme por fa.
atte
rodrigo

PS:este es un bug que no es primera vez que aparece.

Opciones de visualización de comentarios

Seleccione la forma que desee de mostrar los comentarios y haga clic en «Guardar opciones» para activar los cambios.


Gravatar de rodrigo 10

# 93807 ...

Hola a todos, bueno he estado buscando ayuda, por el bug que aparece en la version 2010 de mandriva, usando csh.

las soluciones que te dan son las siguientes
---------------------------------------------------------------------------------------------------------------------------------
Description From Konrad Bernlöhr on 2009-08-24 20:08:40 CEST

Once again a new version of coreutils introduced a new colorls
variable, this time 'mh', resulting in breaking tcsh with
the following error message:

Unknown colorls variable `mh'.

Users with tcsh as their login shell can no longer log in or
use scp to access their data from remote.

We had this problem a number of times before, I think the
last time it was the 'hl' variable.
While the fix may once again have to go into tcsh, I am
reporting this against the coreutils package since the
update of that one broke things.
For the time being, users affected can either
- go back to an older version of coreutils (like
coreutils-7.4-2mdv2010.0.i586.rpm) or
- remove /etc/profile.d/alias.csh

-------- Comment #1 From xuoy@free.fr on 2009-09-21 21:31:16 CEST --------

Hi,

Another workaround can be to comment out the line that contains MULTIHARDLINK
in file /etc/DIR_COLORS or create another /etc/DIR_COLORS_for_tcsh that will
not contain any MULTIHARDLINK definition and will be sourced by
/etc/profile.d/aliases.csh (assuming this file is only used by tcsh users and
not by bash ones).

Note : replacing MULTIHARDLINK by HARDLINK does not solve the problem (HARDLINK
was used in previous versions of /etc/DIR_COLORS).

Regards.

Xuo.

-------- Comment #2 From alexandre on 2009-10-23 13:06:53 CEST --------

thanks for the workaround, it works, but this bug should be fixed before 2010
final.

-------- Comment #3 From Fabrice Boyrie on 2009-10-28 17:13:14 CEST --------

On a fresh installation, I've the bug even if I erase the
MULTIHARDLINK line

In fact,
from bash
strace -f tcsh 2>/tmp/err

grep mh /tmp/err
write(18, "Unknown colorls variable `mh'.\n", 31Unknown colorls variable `mh'.

but grep open /tmp/err| grep -v ENOENT

open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib64/libtermcap.so.2", O_RDONLY) = 3
open("/lib64/libcrypt.so.1", O_RDONLY) = 3
open("/lib64/libc.so.6", O_RDONLY) = 3
open("/usr/share/locale/locale.alias", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_MESSAGES", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_MESSAGES/SYS_LC_MESSAGES", O_RDONLY) = 3
open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_CTYPE", O_RDONLY) = 3
open("/dev/null", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_IDENTIFICATION", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_MEASUREMENT", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_TELEPHONE", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_ADDRESS", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_NAME", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_PAPER", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_MONETARY", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_COLLATE", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_TIME", O_RDONLY) = 3
open("/usr/share/locale/fr_FR.UTF-8/LC_NUMERIC", O_RDONLY) = 3
[pid 12966] open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = 3
[pid 12966] open("/etc/nsswitch.conf", O_RDONLY) = 3
[pid 12966] open("/etc/host.conf", O_RDONLY) = 3
[pid 12966] open("/etc/resolv.conf", O_RDONLY) = 3
[pid 12966] open("/etc/ld.so.cache", O_RDONLY) = 3
[pid 12966] open("/lib64/libnss_mdns4_minimal.so.2", O_RDONLY) = 3
[pid 12966] open("/etc/ld.so.cache", O_RDONLY) = 3
[pid 12966] open("/lib64/libnss_files.so.2", O_RDONLY) = 3
[pid 12966] open("/etc/hosts", O_RDONLY|O_CLOEXEC) = 3
[pid 12966] open("/etc/ld.so.cache", O_RDONLY) = 3
[pid 12966] open("/lib64/libnss_nis.so.2", O_RDONLY) = 3
[pid 12966] open("/lib64/libnsl.so.1", O_RDONLY) = 3
[pid 12966] open("/etc/ld.so.cache", O_RDONLY) = 3
[pid 12966] open("/lib64/libnss_dns.so.2", O_RDONLY) = 3
[pid 12966] open("/lib64/libresolv.so.2", O_RDONLY) = 3

So profiles files are never read

-------- Comment #4 From Konrad Bernlöhr on 2009-10-28 18:40:25 CEST --------

I have a quite different observation. Quite early the /etc/profile.d directory
gets opened and then the individual file names each appear in an lstat64 call.
Later, just picking one random file, I see

...
[pid 14725] execve("/bin/test", ["test", "-r",
"/etc/profile.d/20colorgcc.csh"], [/* 108 vars */]) = -1 ENOENT (No such file
or directory)
[pid 14725] execve("/usr/bin/test", ["test", "-r",
"/etc/profile.d/20colorgcc.csh"], [/* 108 vars */]) = 0
...
[pid 14725] stat64("/etc/profile.d/20colorgcc.csh", {st_mode=S_IFREG|0644,
st_size=106, ...}) = 0
...
[pid 14725] access("/etc/profile.d/20colorgcc.csh", R_OK) = 0
...
open("/etc/profile.d/20colorgcc.csh", O_RDONLY|O_LARGEFILE) = 3
...

So profiles files are indeed read. Otherwise it wouldn't make much sense
to write them in the first place ;)

The fundamental problem with tcsh is that it panics whenever it encounters
these unknown but irrelevant colorls variables.

My current personal solution is the following:

In /etc/profile.d/alias.csh I replaced each occurence of '/etc/DIR_COLORS'
with '/etc/DIR_COLORS_for_tcsh' (in two places).
I copied '/etc/DIR_COLORS' to '/etc/DIR_COLORS_for_tcsh' and commented
one line out in the latter:
diff /etc/DIR_COLORS /etc/DIR_COLORS_for_tcsh
77c77
< MULTIHARDLINK 00 # regular file with more than one link
---
> # MULTIHARDLINK 00 # regular file with more than one link

In order to use this solution with Mandriva, the question arises to
which package the new file '/etc/DIR_COLORS_for_tcsh' should go.
'/etc/profile.d/alias.csh' is part of tcsh, while '/etc/DIR_COLORS'
is part of coreutils. Putting '/etc/DIR_COLORS_for_tcsh' into tcsh
would decouple it from future changes in coreutils - that is when
they add the next colorls variable to '/etc/DIR_COLORS'. Color
schemes for 'ls' in bash and tcsh may eventually go different ways,
but who cares ...
By the way: putting such a '/etc/DIR_COLORS_for_tcsh' into
the tcsh package wouldn't need any change to coreutils.

-------- Comment #5 From Fabrice Boyrie on 2009-10-29 11:16:39 CEST --------

I've found my problem.
I was launching tcsh from bash with the LS_COLORS variable already initialized
at the bad value.

-------- Comment #6 From Eugeni Dodonov private on 2009-11-03 20:07:09 CEST --------

This patch seems to fix it:
http://cvs.fedoraproject.org/viewvc//devel/tcsh/tcsh-6.17.00-mh-color.patch?view=markup

-------------------------------------------------------------------------------------------------------------------------------

la forma de repararlo es editando unos ficheros, cosa que no se hacer y tampoco te especifican en la guía que programa usar para editar el archivo DIR_COLORS u otros que aparecen en las distintas contribuciones.

tambien dice que el problema se soluciona instalando el coreutils version 7.4 (haciendo un downgrade), la cual no esta en los repositorios.
lo que me hace preguntarme es si se puede instalar algun kernel más antiguo que traiga esa version de coreutils
y cual kernel tendría que bajar.

de verdad necesito de su ayuda.
atte
rodrigo

Opciones de visualización de comentarios

Seleccione la forma que desee de mostrar los comentarios y haga clic en «Guardar opciones» para activar los cambios.