Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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'm returning to writing code after years of suit-time and now I need to refresh my knowledge and skills in the executable program, and script as program development world. In recent times, it seems that program command lines have become more widely varied that they used to be.
I'm posting these questions while I continue to research these topics. Please reply with information instead of flame because I have not found your favorite reference material ... yet.
Q1. Isn't there some sort of guideline or standard for what is supposed to appear as command line options?
Q2a. X-windows programs have long use single-dash long options [eg, -display] while non-X programs used double-dash long options [eg, --verbose]. What are the conventions for programs intended to run from the graphical desktop?
Q2b. Does each desktop have its own conventions?
Q3. Are their conventions for using or avoiding environment variables?
Q4. Are there conventions for per-program and per application suite configuration files? I see a wide mix of INI-file and XML formatted configuration sets.
Q5. Recommendations for a set of options that benefit every program (a) run from the shell, or (b) run from the desktop, and (c) run both ways.
Q6. Recommendations for a set of options more appropriate to system admin utilities and apps instead of end-user apps.
I will update my posting as I find answers so that others may share the fruit. After all, isn't that why we are reading and posting here in the first place?
Thanks in advance,
Last edited by SaintDanBert; 01-08-2013 at 03:28 PM.
I continue seeking recommendations for a standard set of command-line options for (a) programs run from a shell and used in a terminal window; Are these called "console" apps? and (b) programs used from the desktop that may be launched from the desktop or from a shell.
Thanks in advance,
Last edited by SaintDanBert; 01-09-2013 at 01:32 PM.