| PLEX86 | ||
|
Find components of "setup" 5212Find components of "setup" 5213 BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In alt.os.linux.slackware, Vardan Kushnir dared to utter, Not a problem. Most of... Vardan Kushnir Commands and executable files are basicly just two synonymous words. So, you are asking -How to find executable files? Well, they can live anywhere, and be of any sort that the system can interpret, just as they can in windows (though wintendo can not interpret as many in most cases). "Give a command" or "Run an executable" have basicly the same meaning. Allmost all commands are "external" and are not something "built in the kernel" (you gain flexibility by that). Wont to learn how to use them? Well most of them have a manual, try "man command". "man" is short for manual. Want to know what command to use? Try "apropos something" example (piped to grep to sort out things for you) apropos video grep '(1)' Find components of "setup" 5214 Vardan Kushnir There are similar concepts in Linux. In Linux, the command prompt you see comes from a shell (usually 'bash', but it could also be 'tcsh', or 'zsh... From the apropos man page: apropos searches a set of database files containing short descriptions of system commands for keywords and displays the result on the standard output. If you want to look how your system configures itself when it boots up, take a look at the scripts inetc-rc.d (in Slackware..), but do not mess around with those as root until you know what you are doing, and they are not that easy to understand for a newbie (but a lot easier than most of the windows registry). For a newbie i recommend to read: Newbie's Top Ten Commands And when you are ready for more, and how to build your own "commands", i recomend: Advanced Bash-Scripting Guide An in-depth exploration of the art of shell scripting
-- Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works.
|
||||