Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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)
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:
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