外文翻譯--高級bash腳本編程指南一個對腳本編程技術(shù)的深入討論

1、<p><b>　　附 錄</b></p><p>　　外文資料翻譯原文部分</p><p>　　Advanced Bash-Scripting Guide</p><p>　　An in-depth exploration of the art of shell scripting</p><p>　　1.

2、Introduction</p><p>　　The shell is a command interpreter. More than just the insulating layer between the operating system kernel and the user, it's also a fairly powerful programming language. A shell p

3、rogram, called a script, is an easy-to-use tool for building applications by "gluing" together system calls, tools, utilities, and compiled binaries. Virtually the entire repertoire of UNIX commands, utilities,

4、 and tools is available for invocation by a shell script. If that were not enough, internal shell commands, s</p><p>　　2. Why Shell Programming?</p><p>　　A working knowledge of shell scripting i

5、s essential to anyone wishing to become reasonably proficient at system administration, even if they do not anticipate ever having to actually write a script. Consider that as a Linux machine boots up, it executes the sh

6、ell scripts in /etc/rc.d to restore the system configuration and set up services. A detailed understanding of these startup scripts is important for analyzing the behavior of a system, and possibly modifying it.</p>

7、;<p>　　Writing shell scripts is not hard to learn, since the scripts can be built in bite-sized sections and there is only a fairly small set of shell-specific operators and options to learn. The syntax is simple

8、 and straightforward, similar to that of invoking and chaining together utilities at the command line, and there are only a few "rules" to learn. Most short scripts work right the first time, and debugging even

9、 the longer ones is straightforward.</p><p>　　A shell script is a "quick and dirty" method of prototyping a complex application. Getting even a limited subset of the functionality to work in a shel

10、l script is often a useful first stage in project development. This way, the structure of the application can be tested and played with, and the major pitfalls found before proceeding to the final coding in C, C++, Java,

11、 or Perl.</p><p>　　Shell scripting hearkens back to the classic UNIX philosophy of breaking complex projects into simpler subtasks, of chaining together components and utilities. Many consider this a better,

12、 or at least more esthetically pleasing approach to problem solving than using one of the new generation of high powered all-in-one languages, such as Perl, which attempt to be all things to all people, but at the cost o

13、f forcing you to alter your thinking processes to fit the tool.</p><p>　　When not to use shell scripts </p><p>　　Resource-intensive tasks, especially where speed is a factor (sorting, hashing, e

14、tc.)</p><p>　　Procedures involving heavy-duty math operations, especially floating point arithmetic, arbitrary precision calculations, or complex numbers (use C++ or FORTRAN instead)</p><p>　　Cr

15、oss-platform portability required (use C or Java instead)</p><p>　　Complex applications, where structured programming is a necessity (need type-checking of variables, function prototypes, etc.)</p>&l

16、t;p>　　Mission-critical applications upon which you are betting the ranch, or the future of the company</p><p>　　Situations where security is important, where you need to guarantee the integrity of your sy

17、stem and protect against intrusion, cracking, and vandalism</p><p>　　Project consists of subcomponents with interlocking dependencies</p><p>　　Extensive file operations required (Bash is limited

18、 to serial file access, and that only in a particularly clumsy and inefficient line-by-line fashion)</p><p>　　Need native support for multi-dimensional arrays</p><p>　　Need data structures, such

19、 as linked lists or trees</p><p>　　Need to generate or manipulate graphics or GUIs</p><p>　　Need direct access to system hardware</p><p>　　Need port or socket I/O</p><p&g

20、t;　　Need to use libraries or interface with legacy code</p><p>　　Proprietary, closed-source applications (shell scripts put the source code right out in the open for all the world to see)</p><p>

21、;　　If any of the above applies, consider a more powerful scripting language -- perhaps Perl, Tcl, Python, Ruby -- or possibly a high-level compiled language such as C, C++, or Java. Even then, prototyping the application

22、 as a shell script might still be a useful development step.</p><p>　　We will be using Bash, an acronym for "Bourne-Again shell" and a pun on Stephen Bourne's now classic Bourne shell. Bash has

23、 become a de facto standard for shell scripting on all flavors of UNIX. Most of the principles this book covers apply equally well to scripting with other shells, such as the Korn Shell, from which Bash derives some of i

24、ts features, and the C Shell and its variants. (Note that C Shell programming is not recommended due to certain inherent problems, as pointed out in an Octob</p><p>　　What follows is a tutorial on shell scri

25、pting. It relies heavily on examples to illustrate various features of the shell. The example scripts work -- they've been tested, insofar as was possible -- and some of them are even useful in real life. The reader

26、can play with the actual working code of the examples in the source archive (scriptname.sh or scriptname.bash), give them execute permission (chmod u+rx scriptname), then run them to see what happens. Should the source a

27、rchive not be available,</p><p>　　外文資料翻譯譯文部分</p><p>　　高級Bash腳本編程指南</p><p>　　一個對腳本編程技術(shù)的深入討論</p><p><b>　　1：簡介</b></p><p>　　Shell是一個命令解釋器。它是操作系統(tǒng)內(nèi)核

28、和用戶之間的絕緣層，也是一種功能強大的編程語言。一個Shell程序，通常被稱作為腳本，它是由系統(tǒng)調(diào)用，命令工具，軟件包和已編譯的二進(jìn)制包"結(jié)合" 起來的容易使用的工具。事實上，shell腳本可以調(diào)用整個UNIX系統(tǒng)命令，軟件包和工具。如果這還不太夠的話，Shell的內(nèi)部命令，如測試和循環(huán)結(jié)構(gòu)，都使得Shell腳本更強大和更有彈性。Shell腳本在管理系統(tǒng)任務(wù)中表現(xiàn)得非常出色，在對日常反復(fù)性的處理工作中避免使用那些結(jié)構(gòu)

29、復(fù)雜的程序語言。</p><p>　　2：為什么要用Shell編程?</p><p>　　腳本應(yīng)用知識對希望精通系統(tǒng)管理的任何個人說是必需的，他實際上不想寫一個腳本程序。一般說一個Linux機器啟動后，它會執(zhí)行在/etc/rc.d 目錄下的Shell腳本重建系統(tǒng)環(huán)境并且啟動各種服務(wù)。理解這些啟動腳本的細(xì)節(jié)對分析系統(tǒng)運作并修改它是有很大意義的。</p><p>　　編

30、寫shell腳本并不難學(xué)，因為腳本內(nèi)建的功能集（check?）和他們只要學(xué)相當(dāng)少的shell的操作符和選項。語法簡單易懂，像在命令行上調(diào)用和連接軟件包那樣容易，它只有少量的 "規(guī)則" 需要掌握。大多數(shù)短小的腳本第一次就工作的很好，較長的腳本調(diào)試也相當(dāng)?shù)娜菀住?lt;/p><p>　　shell腳本是個復(fù)雜應(yīng)用原型的"quick and dirty" 方法。在項目開發(fā)中用shel

31、l編程實現(xiàn)個有限的功能性子集是有用的開始。用這種方法去測試應(yīng)用程序的結(jié)構(gòu)和模塊組合，可以在實際地用C,C++,Java或者Perl進(jìn)行編程之前發(fā)現(xiàn)主要的設(shè)計缺陷。</p><p>　　Shell編程遵從經(jīng)典UNIX哲學(xué)：把復(fù)雜的問題分成簡單的小問題，然后再把各部分功能組合起來解決復(fù)雜問題。這和用新一代高級的多用途的語言，例如Perl，試圖成為所有人處理所有事情的語言但是所付出的代價是強迫改變你的思維方法來適應(yīng)這種

32、工具，大多數(shù)人認(rèn)為這是一個更好的或者至少感覺上更令人能接受的方法。</p><p>　　什么時候不適合使用Shell編程： </p><p>　　資源緊張的項目，特別是速度是重要因素的地方（排序，散序，等等）</p><p>　　程序要進(jìn)行很復(fù)雜的數(shù)學(xué)計算，特別是浮點計算，任意精度的計算，或者是復(fù)數(shù)計算（應(yīng)該用C＋＋或是FORTRAN代替）</p>&

33、lt;p>　　要求交叉編譯平臺的可移植性（使用C或者是Java代替）</p><p>　　需要結(jié)構(gòu)化編程的復(fù)雜應(yīng)用（需要變量類型檢查和函數(shù)原型等等）</p><p>　　對于影響系統(tǒng)全局性的關(guān)鍵任務(wù)應(yīng)用。</p><p>　　安全非常重要。你必須保證系統(tǒng)完整性和抵抗入侵，攻擊和惡意破壞。</p><p>　　項目由連串的依賴的各個部分組

34、成。</p><p>　　多種文件操作要求（Bash被限制成文件順序存取，并且是以相當(dāng)笨拙，效率低下的逐行的存取方式）</p><p>　　需要良好的多維數(shù)組支持。</p><p>　　需要類似鏈表或樹這樣的數(shù)據(jù)結(jié)構(gòu)。</p><p>　　需要產(chǎn)生或操作圖象或圖形用戶界面。</p><p>　　需要直接存取系統(tǒng)硬件。&

35、lt;/p><p>　　需要端口號或是socket I/O。</p><p>　　需要使用可重用的函數(shù)庫或接口。</p><p>　　所有的私有的不開源的應(yīng)用程序（Shell腳本的源代碼是直接可讀，能被所有人看到的）</p><p>　　如果你需要有上面的任意一種應(yīng)用，請考慮其他的更強大的腳本語言――Perl,Tcl,Python,Ruby，或者

36、可能是其他更高級的編譯型語言，例如C，C＋＋或者是Java。盡管如此，使用Shell腳本來構(gòu)造應(yīng)用原型仍然是一個有用的開發(fā)步驟。</p><p>　　我們將會使用Bash,它是 "Bourne-Again shell" 的首字母縮寫，并且是Setphen Bourne寫的經(jīng)典的Bourne shell的同義詞。Bash已經(jīng)變成了所有令人喜歡的UNIX上shell編程 事實的上的 這本書的大多數(shù)

37、腳本技術(shù)能很好的應(yīng)用到其他的Shell當(dāng)中，比如說Korn Shell，Bash借用了它的一些特性， 還有C Shell和他的不同之處。（注意：C shell編程不是交付一定的內(nèi)在問題，這點已由Tom Christiansen在1993年10月在 Usenet post 被指出了） </p><p>　　接下來是的是一篇腳本的指南。它由許多的例子來引出Shell的許多特性。這些已經(jīng)被測試過的例子不僅能工作，并且可