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.
now the issue is in my side is the makefile.
the crontab invoked this script which calls the "make App | tee build.log".
But seems it stopped after "make uboot".
If environment is not correct, it cannot build the 1st and 2nd target (update, uboot).
No error msg in the end of build.log, so i don't understand why it stopped there.
Any suggestions pls ?
Originally Posted by haertig
Runs for the command line manual, not from cron - it is always an environment problem.
If you can't set your fully qualified pathnames, other variables, etc., because there are too many of them scattered about, you can run your profile as part of the cron entry.
it's working now, for some reason, "/home/mylogin/.bashrc;" doesn't work...
That's because you need "<DOT> <SPACE> /home/mylogin/.bashrc". That is how you correctly source a file into your environment. Without the leading <DOT> <SPACE>, it doesn't work. It would have been easy to miss that subtlety in my original example (it's there, but I see how you could have overlooked it).
As in :
Glad to hear you got it working in another way though.