13.07.2015 Views

Java™ Application Development on Linux - Dator

Java™ Application Development on Linux - Dator

Java™ Application Development on Linux - Dator

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4Chapter 1An Embarrassment of Riches: The <strong>Linux</strong> Envir<strong>on</strong>mentto do <strong>on</strong> a <strong>Linux</strong> system, chances are there is already a command (or a sequenceof commands) which will do it.Finally, we will discuss the extent of our remaining ignorance up<strong>on</strong>finishing the chapter.Let us take a moment to explain that last comment. As readers of computerbooks ourselves, we are often frustrated when we discover how lightly a topichas been covered, but particularly so when other parts of the same book arefound to fully explore their topics. When <strong>on</strong>ly some parts of a book are thorough,you often d<strong>on</strong>’t know that you d<strong>on</strong>’t know it all. We will introduce somebasic shell c<strong>on</strong>cepts and commands here, and we may expand <strong>on</strong> some of thesein later chapters, but each of our chapters covers topics that could each fill itsown book. Therefore we need to leave out lots of material. We will also let youknow when we have left things out because they are off-topic, or because wed<strong>on</strong>’t have room. We’ll also try to tell you where to look for the rest of theknowledge. We try to sum this up in a final secti<strong>on</strong> of each chapter entitledWhat You Still D<strong>on</strong>’t Know. But we do have a lot of informati<strong>on</strong> to impart,so let’s get going.1.2THE COMMAND LINE:WHAT’S THE BIG DEAL?One of the revoluti<strong>on</strong>ary things that UNIX (and thus <strong>Linux</strong>) did was to separateoperating system commands from the operating system itself. The commandsto display files, show the c<strong>on</strong>tents of directories, set permissi<strong>on</strong>s, and so<strong>on</strong> were, in the “olden days,” an integral part of an operating system. UNIXremoved all that from the operating system proper, leaving <strong>on</strong>ly a small “kernel”of necessary functi<strong>on</strong>ality in the operating system. The rest became executablesthat lived outside of the operating system and could be changed, enhanced, oreven replaced individually by (advanced) users without modifying the operatingsystem. The most significant of these standal<strong>on</strong>e pieces was the commandprocessor itself, called the shell.The shell is the program that takes command-line input, decides whatprogram(s) you are asking to have run, and then runs those programs. Beforethere were Graphical User Interfaces, the shell was the user interface to UNIX.As more developers began working with UNIX, different shells were developedto provide different features for usability. Now there are several shells tochoose from, though the most popular is bash. Some BSD/UNIX die hards

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!