[SOLVED] What are the red lines in my terminal?

PJvG · 03-16-2010, 03:54 AM

Hello,

I've cross compiled busybox with buildroot for the mini2440 (configured: arm920t EABI) I compiled it dynamically.
I use Ubuntu 9.10 on my build system.

Doing the "ls -l"-command in the /bin directory I see that busybox is marked red. (This is still on my build system, not on my target system!) The background of the word busybox is marked red. And the word busybox is in default colour instead of yellow, even though all permissions have the executable sign.

I was wondering what this means.
Also whether it's a bad thing?

Also could this mean this is why my mini2440 will not boot correctly after transferring this root file system? (It stops the booting process just after loading the root file system)

Thank you,
PJvG

Sayan Acharjee · 03-16-2010, 04:05 AM

Actually there are different color specifications for different kinds of files in linux, it makes them easier to manage. If the file is one of these files:
.tgz
.arj
.taz
.lzh
.zip
.z
.Z
.gz
.bz2
.bz
.tz
.rpm
.cpio

it will be in red color.

Check this file for more info : /etc/DIR_COLORS

Maligree · 03-16-2010, 04:25 AM

Quote:

The background of the word busybox is marked red. And the word busybox is in default colour instead of yellow, even though all permissions have the executable sign.

To me that's a setuid.

PJvG · 03-16-2010, 04:31 AM

Thank you, but like I said I'm using Ubuntu. Ubuntu has no /etc/DIR_COLORS !

However I have found the data you pointed to by using the "dircolors -p"-command.
Still this tells me nothing about the background color of lines!

(And I just found out I should have said green instead of yellow in my first post. Green is the color of executables. I guess I'm a bit colorblind..)

jamescondron · 03-16-2010, 04:31 AM

Quote:

Originally Posted by Maligree

To me that's a setuid.

Yes that's correct, I think sayan was talking about list items with red text, without realising OP meant the red backgrounded text.

@OP: If you look at what aliases you have, you'll see that 'ls' is set to use 'dircolors'; its set in my .bashrc, for yours it may be the same or elsewhere

Code:

jc@jcmain:~$ grep -n ls .bashrc
77:# enable color support of ls and also add handy aliases
80:    alias ls='ls --color=auto'

Which means when I'm running ls I'm actually running ls --color-auto. If it bothers you, you can get rid of the alias quite easily.

But yes, the different colours wont cause any issue or error.

Sayan Acharjee · 03-16-2010, 04:34 AM

Oops!! My bad.....

PJvG · 03-16-2010, 04:42 AM

Thank you Maligree and jamescondron!

It doesn't bother me, I was just wondering what it is.

jamescondron · 03-16-2010, 05:21 AM

As a caveat, the file command is pretty good when it comes to stuff like this to work out why a file is coloured the way it is, though only if you have two or more coloured the same that you may compare

PJvG · 03-16-2010, 06:26 AM

Ah I see.

When I do file it says:

Code:

.../bin$ file busybox
busybox: setuid ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), stripped

So indeed it's a setuid..
Thank you.