Added some new html files that failed earlier during change from rst
authoramit@thunder
Fri, 05 Feb 2010 23:42:24 +0530
changeset 1 672eaaab9204
parent 0 8083d21c0020
child 2 52d12eb31c30
Added some new html files that failed earlier during change from rst
web/hgbook/.database.sqlite3
web/hgbook/comments/p_list.py
web/hgbook/comments/p_list.pyc
web/hgbook/comments/views.py
web/hgbook/comments/views.pyc
web/hgbook/comments/views.py~
web/hgbook/run.wsgi
web/hgbook/run.wsgi~
web/html/abc.html~
web/html/abc.py~
web/html/abcd.html~
web/html/ar01.html~
web/html/ch01-intro.html~
web/html/ch01-introduction.html~
web/html/ch02-basic_intro.html~
web/html/ch02-oop.html~
web/html/ch03-session4.html~
web/html/ch04-handout.html~
web/html/ch04-latex.html~
web/html/ch1Introduction.html
web/html/ch1Introduction.html~
web/html/ch2intro.html
web/html/ch2intro.html~
web/html/ch4strings_dicts.html
web/html/ch4strings_dicts.html~
web/html/ch5func.html
web/html/ch5func.html~
web/html/ch6oop.html
web/html/ch6oop.html~
web/html/ch7interim_assessment.html
web/html/ch7interim_assessment.html~
web/html/ch8ult_module_plan.html
web/html/ch9Using_Linux_Tools.html
web/html/chap_intro.py~
web/html/chn10session4.html
web/html/chn11Section_5.html
web/html/func.html~
web/html/paragraphlist.py~
web/html/test.html~
Binary file web/hgbook/.database.sqlite3 has changed
--- a/web/hgbook/comments/p_list.py	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/hgbook/comments/p_list.py	Fri Feb 05 23:42:24 2010 +0530
@@ -1,1 +1,1 @@
-p_list= {'ch6oop': ['ch6oop_1', 'ch6oop_2', 'ch6oop_3', 'ch6oop_4', 'ch6oop_5', 'ch6oop_6'], 'ch1Introduction': ['ch1Introduction_1', 'ch1Introduction_2', 'ch1Introduction_3', 'ch1Introduction_4', 'ch1Introduction_5', 'ch1Introduction_6', 'ch1Introduction_7', 'ch1Introduction_8', 'ch1Introduction_9', 'ch1Introduction_a', 'ch1Introduction_b', 'ch1Introduction_c', 'ch1Introduction_d'], 'ch5func': ['ch5func_1', 'ch5func_2', 'ch5func_3', 'ch5func_4', 'ch5func_5', 'ch5func_6', 'ch5func_7', 'ch5func_8', 'ch5func_9', 'ch5func_a', 'ch5func_b', 'ch5func_c', 'ch5func_d', 'ch5func_e', 'ch5func_f', 'ch5func_10', 'ch5func_11', 'ch5func_12', 'ch5func_13', 'ch5func_14', 'ch5func_15', 'ch5func_16', 'ch5func_17', 'ch5func_18', 'ch5func_19', 'ch5func_1a', 'ch5func_1b', 'ch5func_1c', 'ch5func_1d', 'ch5func_1e', 'ch5func_1f'], 'ch3list_tuples': ['ch3list_tuples_1', 'ch3list_tuples_2', 'ch3list_tuples_3', 'ch3list_tuples_4', 'ch3list_tuples_5', 'ch3list_tuples_6', 'ch3list_tuples_7', 'ch3list_tuples_8', 'ch3list_tuples_9', 'ch3list_tuples_a', 'ch3list_tuples_b', 'ch3list_tuples_c', 'ch3list_tuples_d', 'ch3list_tuples_e', 'ch3list_tuples_f', 'ch3list_tuples_10', 'ch3list_tuples_11', 'ch3list_tuples_12', 'ch3list_tuples_13', 'ch3list_tuples_14', 'ch3list_tuples_15', 'ch3list_tuples_16', 'ch3list_tuples_17', 'ch3list_tuples_18', 'ch3list_tuples_19', 'ch3list_tuples_1a', 'ch3list_tuples_1b', 'ch3list_tuples_1c', 'ch3list_tuples_1d', 'ch3list_tuples_1e', 'ch3list_tuples_1f', 'ch3list_tuples_20', 'ch3list_tuples_21', 'ch3list_tuples_22', 'ch3list_tuples_23', 'ch3list_tuples_24', 'ch3list_tuples_25', 'ch3list_tuples_26', 'ch3list_tuples_27', 'ch3list_tuples_28', 'ch3list_tuples_29', 'ch3list_tuples_2a', 'ch3list_tuples_2b', 'ch3list_tuples_2c', 'ch3list_tuples_2d', 'ch3list_tuples_2e', 'ch3list_tuples_2f', 'ch3list_tuples_30', 'ch3list_tuples_31', 'ch3list_tuples_32', 'ch3list_tuples_33', 'ch3list_tuples_34', 'ch3list_tuples_35', 'ch3list_tuples_36', 'ch3list_tuples_37'], 'ch2intro': ['ch2intro_1', 'ch2intro_2', 'ch2intro_3', 'ch2intro_4', 'ch2intro_5', 'ch2intro_6', 'ch2intro_7', 'ch2intro_8', 'ch2intro_9', 'ch2intro_a', 'ch2intro_b', 'ch2intro_c', 'ch2intro_d', 'ch2intro_e', 'ch2intro_f', 'ch2intro_10', 'ch2intro_11', 'ch2intro_12', 'ch2intro_13', 'ch2intro_14', 'ch2intro_15', 'ch2intro_16', 'ch2intro_17', 'ch2intro_18', 'ch2intro_19', 'ch2intro_1a', 'ch2intro_1b', 'ch2intro_1c', 'ch2intro_1d', 'ch2intro_1e', 'ch2intro_1f', 'ch2intro_20', 'ch2intro_21', 'ch2intro_22', 'ch2intro_23', 'ch2intro_24', 'ch2intro_25', 'ch2intro_26', 'ch2intro_27', 'ch2intro_28', 'ch2intro_29', 'ch2intro_2a', 'ch2intro_2b', 'ch2intro_2c', 'ch2intro_2d', 'ch2intro_2e', 'ch2intro_2f', 'ch2intro_30', 'ch2intro_31', 'ch2intro_32', 'ch2intro_33', 'ch2intro_34', 'ch2intro_35', 'ch2intro_36', 'ch2intro_37', 'ch2intro_38', 'ch2intro_39', 'ch2intro_3a', 'ch2intro_3b', 'ch2intro_3c', 'ch2intro_3d', 'ch2intro_3e', 'ch2intro_3f', 'ch2intro_40', 'ch2intro_41', 'ch2intro_42', 'ch2intro_43', 'ch2intro_44', 'ch2intro_45', 'ch2intro_46', 'ch2intro_47', 'ch2intro_48', 'ch2intro_49', 'ch2intro_4a', 'ch2intro_4b', 'ch2intro_4c', 'ch2intro_4d', 'ch2intro_4e', 'ch2intro_4f', 'ch2intro_50', 'ch2intro_51', 'ch2intro_52', 'ch2intro_53', 'ch2intro_54', 'ch2intro_55', 'ch2intro_56', 'ch2intro_57', 'ch2intro_58', 'ch2intro_59', 'ch2intro_5a', 'ch2intro_5b', 'ch2intro_5c', 'ch2intro_5d', 'ch2intro_5e', 'ch2intro_5f', 'ch2intro_60', 'ch2intro_61', 'ch2intro_62', 'ch2intro_63', 'ch2intro_64', 'ch2intro_65', 'ch2intro_66', 'ch2intro_67'], 'ch4strings_dicts': ['ch4strings_dicts_1', 'ch4strings_dicts_2', 'ch4strings_dicts_3', 'ch4strings_dicts_4', 'ch4strings_dicts_5', 'ch4strings_dicts_6', 'ch4strings_dicts_7', 'ch4strings_dicts_8', 'ch4strings_dicts_9', 'ch4strings_dicts_a', 'ch4strings_dicts_b', 'ch4strings_dicts_c', 'ch4strings_dicts_d', 'ch4strings_dicts_e', 'ch4strings_dicts_f', 'ch4strings_dicts_10', 'ch4strings_dicts_11', 'ch4strings_dicts_12', 'ch4strings_dicts_13', 'ch4strings_dicts_14', 'ch4strings_dicts_15', 'ch4strings_dicts_16', 'ch4strings_dicts_17', 'ch4strings_dicts_18', 'ch4strings_dicts_19', 'ch4strings_dicts_1a', 'ch4strings_dicts_1b', 'ch4strings_dicts_1c', 'ch4strings_dicts_1d', 'ch4strings_dicts_1e', 'ch4strings_dicts_1f', 'ch4strings_dicts_20', 'ch4strings_dicts_21', 'ch4strings_dicts_22', 'ch4strings_dicts_23', 'ch4strings_dicts_24', 'ch4strings_dicts_25', 'ch4strings_dicts_26', 'ch4strings_dicts_27', 'ch4strings_dicts_28', 'ch4strings_dicts_29', 'ch4strings_dicts_2a', 'ch4strings_dicts_2b', 'ch4strings_dicts_2c', 'ch4strings_dicts_2d', 'ch4strings_dicts_2e', 'ch4strings_dicts_2f', 'ch4strings_dicts_30'], 'ch11Section_5': ['ch11Section_5_1', 'ch11Section_5_2', 'ch11Section_5_3', 'ch11Section_5_4', 'ch11Section_5_5', 'ch11Section_5_6', 'ch11Section_5_7', 'ch11Section_5_8', 'ch11Section_5_9', 'ch11Section_5_a', 'ch11Section_5_b', 'ch11Section_5_c', 'ch11Section_5_d', 'ch11Section_5_e', 'ch11Section_5_f', 'ch11Section_5_10', 'ch11Section_5_11', 'ch11Section_5_12', 'ch11Section_5_13', 'ch11Section_5_14', 'ch11Section_5_15', 'ch11Section_5_16', 'ch11Section_5_17', 'ch11Section_5_18', 'ch11Section_5_19', 'ch11Section_5_1a', 'ch11Section_5_1b', 'ch11Section_5_1c', 'ch11Section_5_1d', 'ch11Section_5_1e', 'ch11Section_5_1f', 'ch11Section_5_20', 'ch11Section_5_21', 'ch11Section_5_22', 'ch11Section_5_23', 'ch11Section_5_24', 'ch11Section_5_25', 'ch11Section_5_26', 'ch11Section_5_27', 'ch11Section_5_28', 'ch11Section_5_29', 'ch11Section_5_2a', 'ch11Section_5_2b', 'ch11Section_5_2c', 'ch11Section_5_2d', 'ch11Section_5_2e', 'ch11Section_5_2f', 'ch11Section_5_30', 'ch11Section_5_31', 'ch11Section_5_32', 'ch11Section_5_33', 'ch11Section_5_34', 'ch11Section_5_35', 'ch11Section_5_36', 'ch11Section_5_37', 'ch11Section_5_38', 'ch11Section_5_39', 'ch11Section_5_3a', 'ch11Section_5_3b', 'ch11Section_5_3c', 'ch11Section_5_3d', 'ch11Section_5_3e', 'ch11Section_5_3f', 'ch11Section_5_40', 'ch11Section_5_41', 'ch11Section_5_42', 'ch11Section_5_43', 'ch11Section_5_44', 'ch11Section_5_45', 'ch11Section_5_46', 'ch11Section_5_47', 'ch11Section_5_48', 'ch11Section_5_49', 'ch11Section_5_4a', 'ch11Section_5_4b', 'ch11Section_5_4c', 'ch11Section_5_4d', 'ch11Section_5_4e', 'ch11Section_5_4f', 'ch11Section_5_50', 'ch11Section_5_51', 'ch11Section_5_52', 'ch11Section_5_53', 'ch11Section_5_54', 'ch11Section_5_55', 'ch11Section_5_56', 'ch11Section_5_57', 'ch11Section_5_58', 'ch11Section_5_59', 'ch11Section_5_5a', 'ch11Section_5_5b', 'ch11Section_5_5c', 'ch11Section_5_5d', 'ch11Section_5_5e', 'ch11Section_5_5f', 'ch11Section_5_60', 'ch11Section_5_61', 'ch11Section_5_62', 'ch11Section_5_63', 'ch11Section_5_64', 'ch11Section_5_65', 'ch11Section_5_66', 'ch11Section_5_67', 'ch11Section_5_68', 'ch11Section_5_69', 'ch11Section_5_6a', 'ch11Section_5_6b', 'ch11Section_5_6c', 'ch11Section_5_6d', 'ch11Section_5_6e'], 'ch7interim_assessment': [], 'ch8ult_module_plan': ['ch8ult_module_plan_1', 'ch8ult_module_plan_2', 'ch8ult_module_plan_3', 'ch8ult_module_plan_4', 'ch8ult_module_plan_5', 'ch8ult_module_plan_6', 'ch8ult_module_plan_7', 'ch8ult_module_plan_8', 'ch8ult_module_plan_9', 'ch8ult_module_plan_a', 'ch8ult_module_plan_b', 'ch8ult_module_plan_c', 'ch8ult_module_plan_d', 'ch8ult_module_plan_e', 'ch8ult_module_plan_f', 'ch8ult_module_plan_10', 'ch8ult_module_plan_11', 'ch8ult_module_plan_12', 'ch8ult_module_plan_13', 'ch8ult_module_plan_14', 'ch8ult_module_plan_15', 'ch8ult_module_plan_16', 'ch8ult_module_plan_17', 'ch8ult_module_plan_18', 'ch8ult_module_plan_19', 'ch8ult_module_plan_1a', 'ch8ult_module_plan_1b', 'ch8ult_module_plan_1c', 'ch8ult_module_plan_1d', 'ch8ult_module_plan_1e', 'ch8ult_module_plan_1f', 'ch8ult_module_plan_20', 'ch8ult_module_plan_21', 'ch8ult_module_plan_22', 'ch8ult_module_plan_23', 'ch8ult_module_plan_24', 'ch8ult_module_plan_25', 'ch8ult_module_plan_26', 'ch8ult_module_plan_27', 'ch8ult_module_plan_28', 'ch8ult_module_plan_29', 'ch8ult_module_plan_2a', 'ch8ult_module_plan_2b', 'ch8ult_module_plan_2c', 'ch8ult_module_plan_2d', 'ch8ult_module_plan_2e', 'ch8ult_module_plan_2f', 'ch8ult_module_plan_30', 'ch8ult_module_plan_31', 'ch8ult_module_plan_32', 'ch8ult_module_plan_33', 'ch8ult_module_plan_34', 'ch8ult_module_plan_35', 'ch8ult_module_plan_36', 'ch8ult_module_plan_37', 'ch8ult_module_plan_38', 'ch8ult_module_plan_39', 'ch8ult_module_plan_3a', 'ch8ult_module_plan_3b', 'ch8ult_module_plan_3c', 'ch8ult_module_plan_3d', 'ch8ult_module_plan_3e', 'ch8ult_module_plan_3f', 'ch8ult_module_plan_40', 'ch8ult_module_plan_41', 'ch8ult_module_plan_42', 'ch8ult_module_plan_43', 'ch8ult_module_plan_44'], 'ch10session4': ['ch10session4_1', 'ch10session4_2', 'ch10session4_3', 'ch10session4_4', 'ch10session4_5', 'ch10session4_6', 'ch10session4_7', 'ch10session4_8', 'ch10session4_9', 'ch10session4_a', 'ch10session4_b', 'ch10session4_c', 'ch10session4_d', 'ch10session4_e', 'ch10session4_f', 'ch10session4_10', 'ch10session4_11', 'ch10session4_12', 'ch10session4_13', 'ch10session4_14', 'ch10session4_15', 'ch10session4_16', 'ch10session4_17', 'ch10session4_18', 'ch10session4_19', 'ch10session4_1a', 'ch10session4_1b', 'ch10session4_1c', 'ch10session4_1d', 'ch10session4_1e', 'ch10session4_1f', 'ch10session4_20', 'ch10session4_21', 'ch10session4_22', 'ch10session4_23', 'ch10session4_24', 'ch10session4_25', 'ch10session4_26', 'ch10session4_27', 'ch10session4_28', 'ch10session4_29', 'ch10session4_2a', 'ch10session4_2b', 'ch10session4_2c', 'ch10session4_2d', 'ch10session4_2e', 'ch10session4_2f', 'ch10session4_30', 'ch10session4_31', 'ch10session4_32', 'ch10session4_33', 'ch10session4_34', 'ch10session4_35', 'ch10session4_36', 'ch10session4_37', 'ch10session4_38', 'ch10session4_39', 'ch10session4_3a', 'ch10session4_3b', 'ch10session4_3c', 'ch10session4_3d', 'ch10session4_3e', 'ch10session4_3f', 'ch10session4_40', 'ch10session4_41', 'ch10session4_42', 'ch10session4_43', 'ch10session4_44', 'ch10session4_45', 'ch10session4_46', 'ch10session4_47', 'ch10session4_48', 'ch10session4_49', 'ch10session4_4a', 'ch10session4_4b', 'ch10session4_4c', 'ch10session4_4d', 'ch10session4_4e', 'ch10session4_4f', 'ch10session4_50', 'ch10session4_51', 'ch10session4_52', 'ch10session4_53', 'ch10session4_54', 'ch10session4_55', 'ch10session4_56', 'ch10session4_57', 'ch10session4_58', 'ch10session4_59', 'ch10session4_5a', 'ch10session4_5b', 'ch10session4_5c', 'ch10session4_5d', 'ch10session4_5e', 'ch10session4_5f', 'ch10session4_60', 'ch10session4_61', 'ch10session4_62', 'ch10session4_63', 'ch10session4_64', 'ch10session4_65', 'ch10session4_66', 'ch10session4_67', 'ch10session4_68', 'ch10session4_69', 'ch10session4_6a', 'ch10session4_6b', 'ch10session4_6c', 'ch10session4_6d', 'ch10session4_6e', 'ch10session4_6f', 'ch10session4_70', 'ch10session4_71', 'ch10session4_72', 'ch10session4_73', 'ch10session4_74', 'ch10session4_75', 'ch10session4_76', 'ch10session4_77', 'ch10session4_78', 'ch10session4_79', 'ch10session4_7a', 'ch10session4_7b', 'ch10session4_7c', 'ch10session4_7d', 'ch10session4_7e', 'ch10session4_7f', 'ch10session4_80', 'ch10session4_81', 'ch10session4_82', 'ch10session4_83', 'ch10session4_84', 'ch10session4_85', 'ch10session4_86', 'ch10session4_87', 'ch10session4_88', 'ch10session4_89', 'ch10session4_8a', 'ch10session4_8b', 'ch10session4_8c', 'ch10session4_8d', 'ch10session4_8e', 'ch10session4_8f', 'ch10session4_90', 'ch10session4_91', 'ch10session4_92', 'ch10session4_93', 'ch10session4_94', 'ch10session4_95', 'ch10session4_96', 'ch10session4_97', 'ch10session4_98', 'ch10session4_99', 'ch10session4_9a', 'ch10session4_9b', 'ch10session4_9c', 'ch10session4_9d', 'ch10session4_9e', 'ch10session4_9f', 'ch10session4_a0', 'ch10session4_a1', 'ch10session4_a2', 'ch10session4_a3', 'ch10session4_a4', 'ch10session4_a5', 'ch10session4_a6', 'ch10session4_a7', 'ch10session4_a8', 'ch10session4_a9', 'ch10session4_aa', 'ch10session4_ab', 'ch10session4_ac', 'ch10session4_ad', 'ch10session4_ae', 'ch10session4_af', 'ch10session4_b0', 'ch10session4_b1', 'ch10session4_b2', 'ch10session4_b3', 'ch10session4_b4', 'ch10session4_b5', 'ch10session4_b6']}
\ No newline at end of file
+p_list= {'ch6oop': ['ch6oop_1', 'ch6oop_2', 'ch6oop_3', 'ch6oop_4', 'ch6oop_5', 'ch6oop_6', 'ch6oop_7', 'ch6oop_8', 'ch6oop_9', 'ch6oop_a', 'ch6oop_b', 'ch6oop_c', 'ch6oop_d', 'ch6oop_e', 'ch6oop_f', 'ch6oop_10', 'ch6oop_11', 'ch6oop_12', 'ch6oop_13', 'ch6oop_14', 'ch6oop_15', 'ch6oop_16', 'ch6oop_17', 'ch6oop_18', 'ch6oop_19', 'ch6oop_1a', 'ch6oop_1b', 'ch6oop_1c', 'ch6oop_1d', 'ch6oop_1e', 'ch6oop_1f', 'ch6oop_20', 'ch6oop_21', 'ch6oop_22', 'ch6oop_23', 'ch6oop_24', 'ch6oop_25', 'ch6oop_26', 'ch6oop_27', 'ch6oop_28', 'ch6oop_29', 'ch6oop_2a', 'ch6oop_2b', 'ch6oop_2c', 'ch6oop_2d', 'ch6oop_2e', 'ch6oop_2f', 'ch6oop_30', 'ch6oop_31', 'ch6oop_32', 'ch6oop_33', 'ch6oop_34', 'ch6oop_35', 'ch6oop_36', 'ch6oop_37', 'ch6oop_38', 'ch6oop_39', 'ch6oop_3a', 'ch6oop_3b', 'ch6oop_3c', 'ch6oop_3d', 'ch6oop_3e', 'ch6oop_3f', 'ch6oop_40', 'ch6oop_41', 'ch6oop_42', 'ch6oop_43', 'ch6oop_44', 'ch6oop_45', 'ch6oop_46', 'ch6oop_47', 'ch6oop_48', 'ch6oop_49', 'ch6oop_4a', 'ch6oop_4b', 'ch6oop_4c', 'ch6oop_4d', 'ch6oop_4e', 'ch6oop_4f', 'ch6oop_50', 'ch6oop_51', 'ch6oop_52', 'ch6oop_53', 'ch6oop_54', 'ch6oop_55', 'ch6oop_56', 'ch6oop_57', 'ch6oop_58', 'ch6oop_59', 'ch6oop_5a', 'ch6oop_5b', 'ch6oop_5c', 'ch6oop_5d', 'ch6oop_5e', 'ch6oop_5f', 'ch6oop_60', 'ch6oop_61', 'ch6oop_62', 'ch6oop_63', 'ch6oop_64', 'ch6oop_65', 'ch6oop_66', 'ch6oop_67', 'ch6oop_68', 'ch6oop_69', 'ch6oop_6a', 'ch6oop_6b', 'ch6oop_6c', 'ch6oop_6d', 'ch6oop_6e', 'ch6oop_6f', 'ch6oop_70', 'ch6oop_71', 'ch6oop_72', 'ch6oop_73', 'ch6oop_74', 'ch6oop_75', 'ch6oop_76', 'ch6oop_77', 'ch6oop_78', 'ch6oop_79', 'ch6oop_7a', 'ch6oop_7b', 'ch6oop_7c', 'ch6oop_7d', 'ch6oop_7e', 'ch6oop_7f', 'ch6oop_80', 'ch6oop_81', 'ch6oop_82', 'ch6oop_83', 'ch6oop_84', 'ch6oop_85', 'ch6oop_86', 'ch6oop_87', 'ch6oop_88', 'ch6oop_89', 'ch6oop_8a', 'ch6oop_8b', 'ch6oop_8c', 'ch6oop_8d', 'ch6oop_8e', 'ch6oop_8f', 'ch6oop_90', 'ch6oop_91', 'ch6oop_92', 'ch6oop_93', 'ch6oop_94', 'ch6oop_95', 'ch6oop_96', 'ch6oop_97', 'ch6oop_98', 'ch6oop_99', 'ch6oop_9a', 'ch6oop_9b', 'ch6oop_9c', 'ch6oop_9d', 'ch6oop_9e', 'ch6oop_9f', 'ch6oop_a0', 'ch6oop_a1', 'ch6oop_a2', 'ch6oop_a3', 'ch6oop_a4', 'ch6oop_a5', 'ch6oop_a6', 'ch6oop_a7', 'ch6oop_a8', 'ch6oop_a9', 'ch6oop_aa', 'ch6oop_ab', 'ch6oop_ac', 'ch6oop_ad', 'ch6oop_ae', 'ch6oop_af', 'ch6oop_b0', 'ch6oop_b1', 'ch6oop_b2', 'ch6oop_b3', 'ch6oop_b4', 'ch6oop_b5', 'ch6oop_b6', 'ch6oop_b7', 'ch6oop_b8', 'ch6oop_b9', 'ch6oop_ba', 'ch6oop_bb', 'ch6oop_bc', 'ch6oop_bd', 'ch6oop_be', 'ch6oop_bf', 'ch6oop_c0', 'ch6oop_c1', 'ch6oop_c2', 'ch6oop_c3', 'ch6oop_c4', 'ch6oop_c5', 'ch6oop_c6', 'ch6oop_c7', 'ch6oop_c8', 'ch6oop_c9', 'ch6oop_ca', 'ch6oop_cb', 'ch6oop_cc', 'ch6oop_cd', 'ch6oop_ce', 'ch6oop_cf', 'ch6oop_d0', 'ch6oop_d1', 'ch6oop_d2', 'ch6oop_d3', 'ch6oop_d4', 'ch6oop_d5', 'ch6oop_d6', 'ch6oop_d7', 'ch6oop_d8', 'ch6oop_d9', 'ch6oop_da', 'ch6oop_db', 'ch6oop_dc', 'ch6oop_dd', 'ch6oop_de', 'ch6oop_df', 'ch6oop_e0', 'ch6oop_e1', 'ch6oop_e2', 'ch6oop_e3', 'ch6oop_e4', 'ch6oop_e5', 'ch6oop_e6', 'ch6oop_e7', 'ch6oop_e8', 'ch6oop_e9', 'ch6oop_ea', 'ch6oop_eb', 'ch6oop_ec', 'ch6oop_ed', 'ch6oop_ee', 'ch6oop_ef', 'ch6oop_f0', 'ch6oop_f1', 'ch6oop_f2', 'ch6oop_f3', 'ch6oop_f4', 'ch6oop_f5', 'ch6oop_f6', 'ch6oop_f7', 'ch6oop_f8', 'ch6oop_f9', 'ch6oop_fa', 'ch6oop_fb', 'ch6oop_fc', 'ch6oop_fd', 'ch6oop_fe', 'ch6oop_ff', 'ch6oop_100', 'ch6oop_101', 'ch6oop_102', 'ch6oop_103', 'ch6oop_104', 'ch6oop_105', 'ch6oop_106', 'ch6oop_107', 'ch6oop_108', 'ch6oop_109', 'ch6oop_10a', 'ch6oop_10b', 'ch6oop_10c', 'ch6oop_10d', 'ch6oop_10e', 'ch6oop_10f', 'ch6oop_110', 'ch6oop_111', 'ch6oop_112', 'ch6oop_113', 'ch6oop_114', 'ch6oop_115', 'ch6oop_116', 'ch6oop_117', 'ch6oop_118', 'ch6oop_119', 'ch6oop_11a', 'ch6oop_11b', 'ch6oop_11c', 'ch6oop_11d', 'ch6oop_11e', 'ch6oop_11f', 'ch6oop_120', 'ch6oop_121', 'ch6oop_122', 'ch6oop_123', 'ch6oop_124', 'ch6oop_125', 'ch6oop_126', 'ch6oop_127', 'ch6oop_128', 'ch6oop_129', 'ch6oop_12a', 'ch6oop_12b', 'ch6oop_12c', 'ch6oop_12d', 'ch6oop_12e', 'ch6oop_12f', 'ch6oop_130', 'ch6oop_131', 'ch6oop_132', 'ch6oop_133', 'ch6oop_134', 'ch6oop_135', 'ch6oop_136', 'ch6oop_137', 'ch6oop_138', 'ch6oop_139', 'ch6oop_13a', 'ch6oop_13b', 'ch6oop_13c', 'ch6oop_13d', 'ch6oop_13e', 'ch6oop_13f', 'ch6oop_140', 'ch6oop_141', 'ch6oop_142', 'ch6oop_143', 'ch6oop_144', 'ch6oop_145', 'ch6oop_146', 'ch6oop_147', 'ch6oop_148', 'ch6oop_149', 'ch6oop_14a', 'ch6oop_14b', 'ch6oop_14c', 'ch6oop_14d', 'ch6oop_14e', 'ch6oop_14f', 'ch6oop_150', 'ch6oop_151', 'ch6oop_152', 'ch6oop_153', 'ch6oop_154', 'ch6oop_155', 'ch6oop_156', 'ch6oop_157', 'ch6oop_158', 'ch6oop_159', 'ch6oop_15a', 'ch6oop_15b', 'ch6oop_15c', 'ch6oop_15d', 'ch6oop_15e', 'ch6oop_15f', 'ch6oop_160', 'ch6oop_161', 'ch6oop_162', 'ch6oop_163', 'ch6oop_164', 'ch6oop_165', 'ch6oop_166', 'ch6oop_167', 'ch6oop_168', 'ch6oop_169', 'ch6oop_16a', 'ch6oop_16b', 'ch6oop_16c', 'ch6oop_16d', 'ch6oop_16e', 'ch6oop_16f', 'ch6oop_170', 'ch6oop_171', 'ch6oop_172', 'ch6oop_173', 'ch6oop_174', 'ch6oop_175', 'ch6oop_176', 'ch6oop_177', 'ch6oop_178', 'ch6oop_179', 'ch6oop_17a', 'ch6oop_17b', 'ch6oop_17c', 'ch6oop_17d', 'ch6oop_17e', 'ch6oop_17f', 'ch6oop_180', 'ch6oop_181', 'ch6oop_182', 'ch6oop_183', 'ch6oop_184', 'ch6oop_185', 'ch6oop_186', 'ch6oop_187', 'ch6oop_188', 'ch6oop_189', 'ch6oop_18a', 'ch6oop_18b', 'ch6oop_18c', 'ch6oop_18d', 'ch6oop_18e', 'ch6oop_18f', 'ch6oop_190', 'ch6oop_191', 'ch6oop_192', 'ch6oop_193', 'ch6oop_194', 'ch6oop_195', 'ch6oop_196', 'ch6oop_197', 'ch6oop_198', 'ch6oop_199', 'ch6oop_19a', 'ch6oop_19b', 'ch6oop_19c', 'ch6oop_19d', 'ch6oop_19e', 'ch6oop_19f', 'ch6oop_1a0', 'ch6oop_1a1', 'ch6oop_1a2', 'ch6oop_1a3', 'ch6oop_1a4', 'ch6oop_1a5', 'ch6oop_1a6', 'ch6oop_1a7', 'ch6oop_1a8', 'ch6oop_1a9', 'ch6oop_1aa', 'ch6oop_1ab', 'ch6oop_1ac', 'ch6oop_1ad', 'ch6oop_1ae', 'ch6oop_1af', 'ch6oop_1b0', 'ch6oop_1b1', 'ch6oop_1b2', 'ch6oop_1b3', 'ch6oop_1b4', 'ch6oop_1b5', 'ch6oop_1b6', 'ch6oop_1b7', 'ch6oop_1b8', 'ch6oop_1b9', 'ch6oop_1ba', 'ch6oop_1bb', 'ch6oop_1bc', 'ch6oop_1bd', 'ch6oop_1be', 'ch6oop_1bf', 'ch6oop_1c0', 'ch6oop_1c1', 'ch6oop_1c2', 'ch6oop_1c3', 'ch6oop_1c4', 'ch6oop_1c5', 'ch6oop_1c6', 'ch6oop_1c7', 'ch6oop_1c8', 'ch6oop_1c9', 'ch6oop_1ca', 'ch6oop_1cb', 'ch6oop_1cc', 'ch6oop_1cd', 'ch6oop_1ce', 'ch6oop_1cf', 'ch6oop_1d0', 'ch6oop_1d1', 'ch6oop_1d2', 'ch6oop_1d3', 'ch6oop_1d4', 'ch6oop_1d5', 'ch6oop_1d6', 'ch6oop_1d7', 'ch6oop_1d8', 'ch6oop_1d9', 'ch6oop_1da', 'ch6oop_1db', 'ch6oop_1dc', 'ch6oop_1dd', 'ch6oop_1de', 'ch6oop_1df', 'ch6oop_1e0', 'ch6oop_1e1'], 'ch9Using_Linux_Tools': ['ch9Using_Linux_Tools_1', 'ch9Using_Linux_Tools_2', 'ch9Using_Linux_Tools_3', 'ch9Using_Linux_Tools_4', 'ch9Using_Linux_Tools_5', 'ch9Using_Linux_Tools_6', 'ch9Using_Linux_Tools_7', 'ch9Using_Linux_Tools_8', 'ch9Using_Linux_Tools_9', 'ch9Using_Linux_Tools_a', 'ch9Using_Linux_Tools_b', 'ch9Using_Linux_Tools_c', 'ch9Using_Linux_Tools_d', 'ch9Using_Linux_Tools_e', 'ch9Using_Linux_Tools_f', 'ch9Using_Linux_Tools_10', 'ch9Using_Linux_Tools_11', 'ch9Using_Linux_Tools_12', 'ch9Using_Linux_Tools_13', 'ch9Using_Linux_Tools_14', 'ch9Using_Linux_Tools_15', 'ch9Using_Linux_Tools_16', 'ch9Using_Linux_Tools_17', 'ch9Using_Linux_Tools_18', 'ch9Using_Linux_Tools_19', 'ch9Using_Linux_Tools_1a', 'ch9Using_Linux_Tools_1b', 'ch9Using_Linux_Tools_1c', 'ch9Using_Linux_Tools_1d', 'ch9Using_Linux_Tools_1e', 'ch9Using_Linux_Tools_1f', 'ch9Using_Linux_Tools_20', 'ch9Using_Linux_Tools_21', 'ch9Using_Linux_Tools_22', 'ch9Using_Linux_Tools_23', 'ch9Using_Linux_Tools_24', 'ch9Using_Linux_Tools_25', 'ch9Using_Linux_Tools_26', 'ch9Using_Linux_Tools_27', 'ch9Using_Linux_Tools_28', 'ch9Using_Linux_Tools_29', 'ch9Using_Linux_Tools_2a', 'ch9Using_Linux_Tools_2b', 'ch9Using_Linux_Tools_2c', 'ch9Using_Linux_Tools_2d', 'ch9Using_Linux_Tools_2e', 'ch9Using_Linux_Tools_2f', 'ch9Using_Linux_Tools_30', 'ch9Using_Linux_Tools_31', 'ch9Using_Linux_Tools_32', 'ch9Using_Linux_Tools_33', 'ch9Using_Linux_Tools_34', 'ch9Using_Linux_Tools_35', 'ch9Using_Linux_Tools_36', 'ch9Using_Linux_Tools_37', 'ch9Using_Linux_Tools_38', 'ch9Using_Linux_Tools_39', 'ch9Using_Linux_Tools_3a', 'ch9Using_Linux_Tools_3b', 'ch9Using_Linux_Tools_3c', 'ch9Using_Linux_Tools_3d', 'ch9Using_Linux_Tools_3e', 'ch9Using_Linux_Tools_3f', 'ch9Using_Linux_Tools_40', 'ch9Using_Linux_Tools_41', 'ch9Using_Linux_Tools_42', 'ch9Using_Linux_Tools_43', 'ch9Using_Linux_Tools_44', 'ch9Using_Linux_Tools_45', 'ch9Using_Linux_Tools_46', 'ch9Using_Linux_Tools_47', 'ch9Using_Linux_Tools_48', 'ch9Using_Linux_Tools_49', 'ch9Using_Linux_Tools_4a', 'ch9Using_Linux_Tools_4b', 'ch9Using_Linux_Tools_4c', 'ch9Using_Linux_Tools_4d', 'ch9Using_Linux_Tools_4e', 'ch9Using_Linux_Tools_4f', 'ch9Using_Linux_Tools_50', 'ch9Using_Linux_Tools_51', 'ch9Using_Linux_Tools_52', 'ch9Using_Linux_Tools_53', 'ch9Using_Linux_Tools_54', 'ch9Using_Linux_Tools_55', 'ch9Using_Linux_Tools_56', 'ch9Using_Linux_Tools_57', 'ch9Using_Linux_Tools_58', 'ch9Using_Linux_Tools_59', 'ch9Using_Linux_Tools_5a', 'ch9Using_Linux_Tools_5b', 'ch9Using_Linux_Tools_5c', 'ch9Using_Linux_Tools_5d', 'ch9Using_Linux_Tools_5e', 'ch9Using_Linux_Tools_5f', 'ch9Using_Linux_Tools_60', 'ch9Using_Linux_Tools_61', 'ch9Using_Linux_Tools_62', 'ch9Using_Linux_Tools_63', 'ch9Using_Linux_Tools_64', 'ch9Using_Linux_Tools_65', 'ch9Using_Linux_Tools_66', 'ch9Using_Linux_Tools_67', 'ch9Using_Linux_Tools_68', 'ch9Using_Linux_Tools_69', 'ch9Using_Linux_Tools_6a', 'ch9Using_Linux_Tools_6b', 'ch9Using_Linux_Tools_6c', 'ch9Using_Linux_Tools_6d', 'ch9Using_Linux_Tools_6e', 'ch9Using_Linux_Tools_6f', 'ch9Using_Linux_Tools_70', 'ch9Using_Linux_Tools_71', 'ch9Using_Linux_Tools_72', 'ch9Using_Linux_Tools_73', 'ch9Using_Linux_Tools_74', 'ch9Using_Linux_Tools_75', 'ch9Using_Linux_Tools_76', 'ch9Using_Linux_Tools_77', 'ch9Using_Linux_Tools_78', 'ch9Using_Linux_Tools_79', 'ch9Using_Linux_Tools_7a', 'ch9Using_Linux_Tools_7b', 'ch9Using_Linux_Tools_7c', 'ch9Using_Linux_Tools_7d', 'ch9Using_Linux_Tools_7e', 'ch9Using_Linux_Tools_7f', 'ch9Using_Linux_Tools_80', 'ch9Using_Linux_Tools_81', 'ch9Using_Linux_Tools_82', 'ch9Using_Linux_Tools_83', 'ch9Using_Linux_Tools_84', 'ch9Using_Linux_Tools_85', 'ch9Using_Linux_Tools_86', 'ch9Using_Linux_Tools_87', 'ch9Using_Linux_Tools_88', 'ch9Using_Linux_Tools_89', 'ch9Using_Linux_Tools_8a', 'ch9Using_Linux_Tools_8b', 'ch9Using_Linux_Tools_8c', 'ch9Using_Linux_Tools_8d', 'ch9Using_Linux_Tools_8e', 'ch9Using_Linux_Tools_8f', 'ch9Using_Linux_Tools_90', 'ch9Using_Linux_Tools_91', 'ch9Using_Linux_Tools_92', 'ch9Using_Linux_Tools_93', 'ch9Using_Linux_Tools_94', 'ch9Using_Linux_Tools_95', 'ch9Using_Linux_Tools_96', 'ch9Using_Linux_Tools_97', 'ch9Using_Linux_Tools_98', 'ch9Using_Linux_Tools_99', 'ch9Using_Linux_Tools_9a', 'ch9Using_Linux_Tools_9b', 'ch9Using_Linux_Tools_9c', 'ch9Using_Linux_Tools_9d', 'ch9Using_Linux_Tools_9e', 'ch9Using_Linux_Tools_9f', 'ch9Using_Linux_Tools_a0', 'ch9Using_Linux_Tools_a1', 'ch9Using_Linux_Tools_a2', 'ch9Using_Linux_Tools_a3', 'ch9Using_Linux_Tools_a4', 'ch9Using_Linux_Tools_a5', 'ch9Using_Linux_Tools_a6', 'ch9Using_Linux_Tools_a7', 'ch9Using_Linux_Tools_a8', 'ch9Using_Linux_Tools_a9', 'ch9Using_Linux_Tools_aa', 'ch9Using_Linux_Tools_ab', 'ch9Using_Linux_Tools_ac', 'ch9Using_Linux_Tools_ad', 'ch9Using_Linux_Tools_ae', 'ch9Using_Linux_Tools_af', 'ch9Using_Linux_Tools_b0', 'ch9Using_Linux_Tools_b1', 'ch9Using_Linux_Tools_b2', 'ch9Using_Linux_Tools_b3', 'ch9Using_Linux_Tools_b4', 'ch9Using_Linux_Tools_b5', 'ch9Using_Linux_Tools_b6', 'ch9Using_Linux_Tools_b7', 'ch9Using_Linux_Tools_b8', 'ch9Using_Linux_Tools_b9', 'ch9Using_Linux_Tools_ba', 'ch9Using_Linux_Tools_bb', 'ch9Using_Linux_Tools_bc', 'ch9Using_Linux_Tools_bd', 'ch9Using_Linux_Tools_be', 'ch9Using_Linux_Tools_bf', 'ch9Using_Linux_Tools_c0', 'ch9Using_Linux_Tools_c1', 'ch9Using_Linux_Tools_c2', 'ch9Using_Linux_Tools_c3', 'ch9Using_Linux_Tools_c4', 'ch9Using_Linux_Tools_c5', 'ch9Using_Linux_Tools_c6', 'ch9Using_Linux_Tools_c7', 'ch9Using_Linux_Tools_c8', 'ch9Using_Linux_Tools_c9', 'ch9Using_Linux_Tools_ca', 'ch9Using_Linux_Tools_cb', 'ch9Using_Linux_Tools_cc', 'ch9Using_Linux_Tools_cd', 'ch9Using_Linux_Tools_ce', 'ch9Using_Linux_Tools_cf', 'ch9Using_Linux_Tools_d0', 'ch9Using_Linux_Tools_d1', 'ch9Using_Linux_Tools_d2', 'ch9Using_Linux_Tools_d3', 'ch9Using_Linux_Tools_d4', 'ch9Using_Linux_Tools_d5', 'ch9Using_Linux_Tools_d6', 'ch9Using_Linux_Tools_d7', 'ch9Using_Linux_Tools_d8', 'ch9Using_Linux_Tools_d9', 'ch9Using_Linux_Tools_da', 'ch9Using_Linux_Tools_db', 'ch9Using_Linux_Tools_dc', 'ch9Using_Linux_Tools_dd', 'ch9Using_Linux_Tools_de', 'ch9Using_Linux_Tools_df', 'ch9Using_Linux_Tools_e0', 'ch9Using_Linux_Tools_e1', 'ch9Using_Linux_Tools_e2', 'ch9Using_Linux_Tools_e3', 'ch9Using_Linux_Tools_e4', 'ch9Using_Linux_Tools_e5', 'ch9Using_Linux_Tools_e6', 'ch9Using_Linux_Tools_e7', 'ch9Using_Linux_Tools_e8', 'ch9Using_Linux_Tools_e9', 'ch9Using_Linux_Tools_ea', 'ch9Using_Linux_Tools_eb', 'ch9Using_Linux_Tools_ec', 'ch9Using_Linux_Tools_ed', 'ch9Using_Linux_Tools_ee', 'ch9Using_Linux_Tools_ef', 'ch9Using_Linux_Tools_f0', 'ch9Using_Linux_Tools_f1', 'ch9Using_Linux_Tools_f2', 'ch9Using_Linux_Tools_f3', 'ch9Using_Linux_Tools_f4', 'ch9Using_Linux_Tools_f5', 'ch9Using_Linux_Tools_f6', 'ch9Using_Linux_Tools_f7', 'ch9Using_Linux_Tools_f8', 'ch9Using_Linux_Tools_f9', 'ch9Using_Linux_Tools_fa', 'ch9Using_Linux_Tools_fb', 'ch9Using_Linux_Tools_fc', 'ch9Using_Linux_Tools_fd', 'ch9Using_Linux_Tools_fe', 'ch9Using_Linux_Tools_ff', 'ch9Using_Linux_Tools_100', 'ch9Using_Linux_Tools_101', 'ch9Using_Linux_Tools_102', 'ch9Using_Linux_Tools_103', 'ch9Using_Linux_Tools_104', 'ch9Using_Linux_Tools_105', 'ch9Using_Linux_Tools_106', 'ch9Using_Linux_Tools_107', 'ch9Using_Linux_Tools_108', 'ch9Using_Linux_Tools_109', 'ch9Using_Linux_Tools_10a', 'ch9Using_Linux_Tools_10b', 'ch9Using_Linux_Tools_10c', 'ch9Using_Linux_Tools_10d', 'ch9Using_Linux_Tools_10e', 'ch9Using_Linux_Tools_10f', 'ch9Using_Linux_Tools_110', 'ch9Using_Linux_Tools_111', 'ch9Using_Linux_Tools_112', 'ch9Using_Linux_Tools_113', 'ch9Using_Linux_Tools_114', 'ch9Using_Linux_Tools_115', 'ch9Using_Linux_Tools_116', 'ch9Using_Linux_Tools_117', 'ch9Using_Linux_Tools_118', 'ch9Using_Linux_Tools_119', 'ch9Using_Linux_Tools_11a', 'ch9Using_Linux_Tools_11b', 'ch9Using_Linux_Tools_11c', 'ch9Using_Linux_Tools_11d', 'ch9Using_Linux_Tools_11e', 'ch9Using_Linux_Tools_11f', 'ch9Using_Linux_Tools_120', 'ch9Using_Linux_Tools_121', 'ch9Using_Linux_Tools_122', 'ch9Using_Linux_Tools_123', 'ch9Using_Linux_Tools_124', 'ch9Using_Linux_Tools_125', 'ch9Using_Linux_Tools_126', 'ch9Using_Linux_Tools_127', 'ch9Using_Linux_Tools_128', 'ch9Using_Linux_Tools_129', 'ch9Using_Linux_Tools_12a', 'ch9Using_Linux_Tools_12b', 'ch9Using_Linux_Tools_12c', 'ch9Using_Linux_Tools_12d', 'ch9Using_Linux_Tools_12e', 'ch9Using_Linux_Tools_12f', 'ch9Using_Linux_Tools_130', 'ch9Using_Linux_Tools_131', 'ch9Using_Linux_Tools_132', 'ch9Using_Linux_Tools_133', 'ch9Using_Linux_Tools_134', 'ch9Using_Linux_Tools_135', 'ch9Using_Linux_Tools_136', 'ch9Using_Linux_Tools_137', 'ch9Using_Linux_Tools_138', 'ch9Using_Linux_Tools_139', 'ch9Using_Linux_Tools_13a', 'ch9Using_Linux_Tools_13b', 'ch9Using_Linux_Tools_13c', 'ch9Using_Linux_Tools_13d', 'ch9Using_Linux_Tools_13e', 'ch9Using_Linux_Tools_13f', 'ch9Using_Linux_Tools_140', 'ch9Using_Linux_Tools_141', 'ch9Using_Linux_Tools_142', 'ch9Using_Linux_Tools_143', 'ch9Using_Linux_Tools_144', 'ch9Using_Linux_Tools_145', 'ch9Using_Linux_Tools_146', 'ch9Using_Linux_Tools_147', 'ch9Using_Linux_Tools_148', 'ch9Using_Linux_Tools_149', 'ch9Using_Linux_Tools_14a', 'ch9Using_Linux_Tools_14b', 'ch9Using_Linux_Tools_14c', 'ch9Using_Linux_Tools_14d', 'ch9Using_Linux_Tools_14e', 'ch9Using_Linux_Tools_14f', 'ch9Using_Linux_Tools_150', 'ch9Using_Linux_Tools_151', 'ch9Using_Linux_Tools_152', 'ch9Using_Linux_Tools_153', 'ch9Using_Linux_Tools_154', 'ch9Using_Linux_Tools_155', 'ch9Using_Linux_Tools_156', 'ch9Using_Linux_Tools_157', 'ch9Using_Linux_Tools_158', 'ch9Using_Linux_Tools_159', 'ch9Using_Linux_Tools_15a', 'ch9Using_Linux_Tools_15b', 'ch9Using_Linux_Tools_15c', 'ch9Using_Linux_Tools_15d', 'ch9Using_Linux_Tools_15e', 'ch9Using_Linux_Tools_15f', 'ch9Using_Linux_Tools_160', 'ch9Using_Linux_Tools_161', 'ch9Using_Linux_Tools_162', 'ch9Using_Linux_Tools_163', 'ch9Using_Linux_Tools_164', 'ch9Using_Linux_Tools_165', 'ch9Using_Linux_Tools_166', 'ch9Using_Linux_Tools_167', 'ch9Using_Linux_Tools_168', 'ch9Using_Linux_Tools_169', 'ch9Using_Linux_Tools_16a', 'ch9Using_Linux_Tools_16b', 'ch9Using_Linux_Tools_16c', 'ch9Using_Linux_Tools_16d', 'ch9Using_Linux_Tools_16e', 'ch9Using_Linux_Tools_16f', 'ch9Using_Linux_Tools_170', 'ch9Using_Linux_Tools_171', 'ch9Using_Linux_Tools_172', 'ch9Using_Linux_Tools_173', 'ch9Using_Linux_Tools_174', 'ch9Using_Linux_Tools_175', 'ch9Using_Linux_Tools_176', 'ch9Using_Linux_Tools_177', 'ch9Using_Linux_Tools_178', 'ch9Using_Linux_Tools_179', 'ch9Using_Linux_Tools_17a', 'ch9Using_Linux_Tools_17b', 'ch9Using_Linux_Tools_17c', 'ch9Using_Linux_Tools_17d', 'ch9Using_Linux_Tools_17e', 'ch9Using_Linux_Tools_17f', 'ch9Using_Linux_Tools_180', 'ch9Using_Linux_Tools_181', 'ch9Using_Linux_Tools_182', 'ch9Using_Linux_Tools_183', 'ch9Using_Linux_Tools_184', 'ch9Using_Linux_Tools_185', 'ch9Using_Linux_Tools_186', 'ch9Using_Linux_Tools_187', 'ch9Using_Linux_Tools_188', 'ch9Using_Linux_Tools_189', 'ch9Using_Linux_Tools_18a', 'ch9Using_Linux_Tools_18b', 'ch9Using_Linux_Tools_18c', 'ch9Using_Linux_Tools_18d', 'ch9Using_Linux_Tools_18e', 'ch9Using_Linux_Tools_18f', 'ch9Using_Linux_Tools_190', 'ch9Using_Linux_Tools_191', 'ch9Using_Linux_Tools_192', 'ch9Using_Linux_Tools_193', 'ch9Using_Linux_Tools_194', 'ch9Using_Linux_Tools_195', 'ch9Using_Linux_Tools_196', 'ch9Using_Linux_Tools_197', 'ch9Using_Linux_Tools_198', 'ch9Using_Linux_Tools_199', 'ch9Using_Linux_Tools_19a', 'ch9Using_Linux_Tools_19b', 'ch9Using_Linux_Tools_19c', 'ch9Using_Linux_Tools_19d', 'ch9Using_Linux_Tools_19e', 'ch9Using_Linux_Tools_19f', 'ch9Using_Linux_Tools_1a0', 'ch9Using_Linux_Tools_1a1', 'ch9Using_Linux_Tools_1a2', 'ch9Using_Linux_Tools_1a3', 'ch9Using_Linux_Tools_1a4', 'ch9Using_Linux_Tools_1a5', 'ch9Using_Linux_Tools_1a6', 'ch9Using_Linux_Tools_1a7', 'ch9Using_Linux_Tools_1a8', 'ch9Using_Linux_Tools_1a9', 'ch9Using_Linux_Tools_1aa', 'ch9Using_Linux_Tools_1ab', 'ch9Using_Linux_Tools_1ac', 'ch9Using_Linux_Tools_1ad', 'ch9Using_Linux_Tools_1ae', 'ch9Using_Linux_Tools_1af', 'ch9Using_Linux_Tools_1b0', 'ch9Using_Linux_Tools_1b1', 'ch9Using_Linux_Tools_1b2', 'ch9Using_Linux_Tools_1b3', 'ch9Using_Linux_Tools_1b4', 'ch9Using_Linux_Tools_1b5', 'ch9Using_Linux_Tools_1b6', 'ch9Using_Linux_Tools_1b7', 'ch9Using_Linux_Tools_1b8', 'ch9Using_Linux_Tools_1b9', 'ch9Using_Linux_Tools_1ba', 'ch9Using_Linux_Tools_1bb', 'ch9Using_Linux_Tools_1bc', 'ch9Using_Linux_Tools_1bd', 'ch9Using_Linux_Tools_1be', 'ch9Using_Linux_Tools_1bf', 'ch9Using_Linux_Tools_1c0', 'ch9Using_Linux_Tools_1c1', 'ch9Using_Linux_Tools_1c2', 'ch9Using_Linux_Tools_1c3', 'ch9Using_Linux_Tools_1c4', 'ch9Using_Linux_Tools_1c5', 'ch9Using_Linux_Tools_1c6', 'ch9Using_Linux_Tools_1c7', 'ch9Using_Linux_Tools_1c8', 'ch9Using_Linux_Tools_1c9', 'ch9Using_Linux_Tools_1ca', 'ch9Using_Linux_Tools_1cb', 'ch9Using_Linux_Tools_1cc', 'ch9Using_Linux_Tools_1cd', 'ch9Using_Linux_Tools_1ce', 'ch9Using_Linux_Tools_1cf', 'ch9Using_Linux_Tools_1d0', 'ch9Using_Linux_Tools_1d1', 'ch9Using_Linux_Tools_1d2', 'ch9Using_Linux_Tools_1d3', 'ch9Using_Linux_Tools_1d4', 'ch9Using_Linux_Tools_1d5', 'ch9Using_Linux_Tools_1d6', 'ch9Using_Linux_Tools_1d7', 'ch9Using_Linux_Tools_1d8', 'ch9Using_Linux_Tools_1d9', 'ch9Using_Linux_Tools_1da', 'ch9Using_Linux_Tools_1db', 'ch9Using_Linux_Tools_1dc', 'ch9Using_Linux_Tools_1dd', 'ch9Using_Linux_Tools_1de', 'ch9Using_Linux_Tools_1df', 'ch9Using_Linux_Tools_1e0', 'ch9Using_Linux_Tools_1e1'], 'ch1Introduction': ['ch1Introduction_1', 'ch1Introduction_2', 'ch1Introduction_3', 'ch1Introduction_4', 'ch1Introduction_5', 'ch1Introduction_6', 'ch1Introduction_7', 'ch1Introduction_8', 'ch1Introduction_9', 'ch1Introduction_a', 'ch1Introduction_b', 'ch1Introduction_c', 'ch1Introduction_d', 'ch1Introduction_e', 'ch1Introduction_f', 'ch1Introduction_10', 'ch1Introduction_11', 'ch1Introduction_12', 'ch1Introduction_13', 'ch1Introduction_14', 'ch1Introduction_15', 'ch1Introduction_16', 'ch1Introduction_17', 'ch1Introduction_18', 'ch1Introduction_19', 'ch1Introduction_1a', 'ch1Introduction_1b', 'ch1Introduction_1c', 'ch1Introduction_1d', 'ch1Introduction_1e', 'ch1Introduction_1f', 'ch1Introduction_20', 'ch1Introduction_21', 'ch1Introduction_22', 'ch1Introduction_23', 'ch1Introduction_24', 'ch1Introduction_25', 'ch1Introduction_26', 'ch1Introduction_27', 'ch1Introduction_28', 'ch1Introduction_29', 'ch1Introduction_2a', 'ch1Introduction_2b', 'ch1Introduction_2c', 'ch1Introduction_2d', 'ch1Introduction_2e', 'ch1Introduction_2f', 'ch1Introduction_30', 'ch1Introduction_31', 'ch1Introduction_32', 'ch1Introduction_33', 'ch1Introduction_34', 'ch1Introduction_35', 'ch1Introduction_36', 'ch1Introduction_37', 'ch1Introduction_38', 'ch1Introduction_39', 'ch1Introduction_3a', 'ch1Introduction_3b', 'ch1Introduction_3c', 'ch1Introduction_3d', 'ch1Introduction_3e', 'ch1Introduction_3f', 'ch1Introduction_40', 'ch1Introduction_41', 'ch1Introduction_42', 'ch1Introduction_43', 'ch1Introduction_44', 'ch1Introduction_45', 'ch1Introduction_46', 'ch1Introduction_47', 'ch1Introduction_48', 'ch1Introduction_49', 'ch1Introduction_4a', 'ch1Introduction_4b', 'ch1Introduction_4c', 'ch1Introduction_4d', 'ch1Introduction_4e', 'ch1Introduction_4f', 'ch1Introduction_50', 'ch1Introduction_51', 'ch1Introduction_52', 'ch1Introduction_53', 'ch1Introduction_54', 'ch1Introduction_55', 'ch1Introduction_56', 'ch1Introduction_57', 'ch1Introduction_58', 'ch1Introduction_59', 'ch1Introduction_5a', 'ch1Introduction_5b', 'ch1Introduction_5c', 'ch1Introduction_5d', 'ch1Introduction_5e', 'ch1Introduction_5f', 'ch1Introduction_60', 'ch1Introduction_61', 'ch1Introduction_62', 'ch1Introduction_63', 'ch1Introduction_64', 'ch1Introduction_65', 'ch1Introduction_66', 'ch1Introduction_67', 'ch1Introduction_68', 'ch1Introduction_69', 'ch1Introduction_6a', 'ch1Introduction_6b', 'ch1Introduction_6c', 'ch1Introduction_6d', 'ch1Introduction_6e', 'ch1Introduction_6f', 'ch1Introduction_70', 'ch1Introduction_71', 'ch1Introduction_72', 'ch1Introduction_73', 'ch1Introduction_74', 'ch1Introduction_75', 'ch1Introduction_76', 'ch1Introduction_77', 'ch1Introduction_78', 'ch1Introduction_79', 'ch1Introduction_7a', 'ch1Introduction_7b', 'ch1Introduction_7c', 'ch1Introduction_7d', 'ch1Introduction_7e', 'ch1Introduction_7f', 'ch1Introduction_80', 'ch1Introduction_81', 'ch1Introduction_82', 'ch1Introduction_83', 'ch1Introduction_84', 'ch1Introduction_85', 'ch1Introduction_86', 'ch1Introduction_87', 'ch1Introduction_88', 'ch1Introduction_89', 'ch1Introduction_8a', 'ch1Introduction_8b', 'ch1Introduction_8c', 'ch1Introduction_8d', 'ch1Introduction_8e', 'ch1Introduction_8f', 'ch1Introduction_90', 'ch1Introduction_91', 'ch1Introduction_92', 'ch1Introduction_93', 'ch1Introduction_94', 'ch1Introduction_95', 'ch1Introduction_96', 'ch1Introduction_97', 'ch1Introduction_98', 'ch1Introduction_99', 'ch1Introduction_9a', 'ch1Introduction_9b', 'ch1Introduction_9c', 'ch1Introduction_9d', 'ch1Introduction_9e', 'ch1Introduction_9f', 'ch1Introduction_a0', 'ch1Introduction_a1', 'ch1Introduction_a2', 'ch1Introduction_a3', 'ch1Introduction_a4', 'ch1Introduction_a5', 'ch1Introduction_a6', 'ch1Introduction_a7', 'ch1Introduction_a8', 'ch1Introduction_a9', 'ch1Introduction_aa', 'ch1Introduction_ab', 'ch1Introduction_ac', 'ch1Introduction_ad', 'ch1Introduction_ae', 'ch1Introduction_af', 'ch1Introduction_b0', 'ch1Introduction_b1', 'ch1Introduction_b2', 'ch1Introduction_b3', 'ch1Introduction_b4', 'ch1Introduction_b5', 'ch1Introduction_b6', 'ch1Introduction_b7', 'ch1Introduction_b8', 'ch1Introduction_b9', 'ch1Introduction_ba', 'ch1Introduction_bb', 'ch1Introduction_bc', 'ch1Introduction_bd', 'ch1Introduction_be', 'ch1Introduction_bf', 'ch1Introduction_c0', 'ch1Introduction_c1', 'ch1Introduction_c2', 'ch1Introduction_c3', 'ch1Introduction_c4', 'ch1Introduction_c5', 'ch1Introduction_c6', 'ch1Introduction_c7', 'ch1Introduction_c8', 'ch1Introduction_c9', 'ch1Introduction_ca', 'ch1Introduction_cb', 'ch1Introduction_cc', 'ch1Introduction_cd', 'ch1Introduction_ce', 'ch1Introduction_cf', 'ch1Introduction_d0', 'ch1Introduction_d1', 'ch1Introduction_d2', 'ch1Introduction_d3', 'ch1Introduction_d4', 'ch1Introduction_d5', 'ch1Introduction_d6', 'ch1Introduction_d7', 'ch1Introduction_d8', 'ch1Introduction_d9', 'ch1Introduction_da', 'ch1Introduction_db', 'ch1Introduction_dc', 'ch1Introduction_dd', 'ch1Introduction_de', 'ch1Introduction_df', 'ch1Introduction_e0', 'ch1Introduction_e1', 'ch1Introduction_e2', 'ch1Introduction_e3', 'ch1Introduction_e4', 'ch1Introduction_e5', 'ch1Introduction_e6', 'ch1Introduction_e7', 'ch1Introduction_e8', 'ch1Introduction_e9', 'ch1Introduction_ea', 'ch1Introduction_eb', 'ch1Introduction_ec', 'ch1Introduction_ed', 'ch1Introduction_ee', 'ch1Introduction_ef', 'ch1Introduction_f0', 'ch1Introduction_f1', 'ch1Introduction_f2', 'ch1Introduction_f3', 'ch1Introduction_f4', 'ch1Introduction_f5', 'ch1Introduction_f6', 'ch1Introduction_f7', 'ch1Introduction_f8', 'ch1Introduction_f9', 'ch1Introduction_fa', 'ch1Introduction_fb', 'ch1Introduction_fc', 'ch1Introduction_fd', 'ch1Introduction_fe', 'ch1Introduction_ff', 'ch1Introduction_100', 'ch1Introduction_101', 'ch1Introduction_102', 'ch1Introduction_103', 'ch1Introduction_104', 'ch1Introduction_105', 'ch1Introduction_106', 'ch1Introduction_107', 'ch1Introduction_108', 'ch1Introduction_109', 'ch1Introduction_10a', 'ch1Introduction_10b', 'ch1Introduction_10c', 'ch1Introduction_10d', 'ch1Introduction_10e', 'ch1Introduction_10f', 'ch1Introduction_110', 'ch1Introduction_111', 'ch1Introduction_112', 'ch1Introduction_113', 'ch1Introduction_114', 'ch1Introduction_115', 'ch1Introduction_116', 'ch1Introduction_117', 'ch1Introduction_118', 'ch1Introduction_119', 'ch1Introduction_11a', 'ch1Introduction_11b', 'ch1Introduction_11c', 'ch1Introduction_11d', 'ch1Introduction_11e', 'ch1Introduction_11f', 'ch1Introduction_120', 'ch1Introduction_121', 'ch1Introduction_122', 'ch1Introduction_123', 'ch1Introduction_124', 'ch1Introduction_125', 'ch1Introduction_126', 'ch1Introduction_127', 'ch1Introduction_128', 'ch1Introduction_129', 'ch1Introduction_12a', 'ch1Introduction_12b', 'ch1Introduction_12c', 'ch1Introduction_12d', 'ch1Introduction_12e', 'ch1Introduction_12f', 'ch1Introduction_130', 'ch1Introduction_131', 'ch1Introduction_132', 'ch1Introduction_133', 'ch1Introduction_134', 'ch1Introduction_135', 'ch1Introduction_136', 'ch1Introduction_137', 'ch1Introduction_138', 'ch1Introduction_139', 'ch1Introduction_13a', 'ch1Introduction_13b', 'ch1Introduction_13c', 'ch1Introduction_13d', 'ch1Introduction_13e', 'ch1Introduction_13f', 'ch1Introduction_140', 'ch1Introduction_141', 'ch1Introduction_142', 'ch1Introduction_143', 'ch1Introduction_144', 'ch1Introduction_145', 'ch1Introduction_146', 'ch1Introduction_147', 'ch1Introduction_148', 'ch1Introduction_149', 'ch1Introduction_14a', 'ch1Introduction_14b', 'ch1Introduction_14c', 'ch1Introduction_14d', 'ch1Introduction_14e', 'ch1Introduction_14f', 'ch1Introduction_150', 'ch1Introduction_151', 'ch1Introduction_152', 'ch1Introduction_153', 'ch1Introduction_154', 'ch1Introduction_155', 'ch1Introduction_156', 'ch1Introduction_157', 'ch1Introduction_158', 'ch1Introduction_159', 'ch1Introduction_15a', 'ch1Introduction_15b', 'ch1Introduction_15c', 'ch1Introduction_15d', 'ch1Introduction_15e', 'ch1Introduction_15f', 'ch1Introduction_160', 'ch1Introduction_161', 'ch1Introduction_162', 'ch1Introduction_163', 'ch1Introduction_164', 'ch1Introduction_165', 'ch1Introduction_166', 'ch1Introduction_167', 'ch1Introduction_168', 'ch1Introduction_169', 'ch1Introduction_16a', 'ch1Introduction_16b', 'ch1Introduction_16c', 'ch1Introduction_16d', 'ch1Introduction_16e', 'ch1Introduction_16f', 'ch1Introduction_170', 'ch1Introduction_171', 'ch1Introduction_172', 'ch1Introduction_173', 'ch1Introduction_174', 'ch1Introduction_175', 'ch1Introduction_176', 'ch1Introduction_177', 'ch1Introduction_178', 'ch1Introduction_179', 'ch1Introduction_17a', 'ch1Introduction_17b', 'ch1Introduction_17c', 'ch1Introduction_17d', 'ch1Introduction_17e', 'ch1Introduction_17f', 'ch1Introduction_180', 'ch1Introduction_181', 'ch1Introduction_182', 'ch1Introduction_183', 'ch1Introduction_184', 'ch1Introduction_185', 'ch1Introduction_186', 'ch1Introduction_187', 'ch1Introduction_188', 'ch1Introduction_189', 'ch1Introduction_18a', 'ch1Introduction_18b', 'ch1Introduction_18c', 'ch1Introduction_18d', 'ch1Introduction_18e', 'ch1Introduction_18f', 'ch1Introduction_190', 'ch1Introduction_191', 'ch1Introduction_192', 'ch1Introduction_193', 'ch1Introduction_194', 'ch1Introduction_195', 'ch1Introduction_196', 'ch1Introduction_197', 'ch1Introduction_198', 'ch1Introduction_199', 'ch1Introduction_19a', 'ch1Introduction_19b', 'ch1Introduction_19c', 'ch1Introduction_19d', 'ch1Introduction_19e', 'ch1Introduction_19f', 'ch1Introduction_1a0', 'ch1Introduction_1a1', 'ch1Introduction_1a2', 'ch1Introduction_1a3', 'ch1Introduction_1a4', 'ch1Introduction_1a5', 'ch1Introduction_1a6', 'ch1Introduction_1a7', 'ch1Introduction_1a8', 'ch1Introduction_1a9', 'ch1Introduction_1aa', 'ch1Introduction_1ab', 'ch1Introduction_1ac', 'ch1Introduction_1ad', 'ch1Introduction_1ae', 'ch1Introduction_1af', 'ch1Introduction_1b0', 'ch1Introduction_1b1', 'ch1Introduction_1b2', 'ch1Introduction_1b3', 'ch1Introduction_1b4', 'ch1Introduction_1b5', 'ch1Introduction_1b6', 'ch1Introduction_1b7', 'ch1Introduction_1b8', 'ch1Introduction_1b9', 'ch1Introduction_1ba', 'ch1Introduction_1bb', 'ch1Introduction_1bc', 'ch1Introduction_1bd', 'ch1Introduction_1be', 'ch1Introduction_1bf', 'ch1Introduction_1c0', 'ch1Introduction_1c1', 'ch1Introduction_1c2', 'ch1Introduction_1c3', 'ch1Introduction_1c4', 'ch1Introduction_1c5', 'ch1Introduction_1c6', 'ch1Introduction_1c7', 'ch1Introduction_1c8', 'ch1Introduction_1c9', 'ch1Introduction_1ca', 'ch1Introduction_1cb', 'ch1Introduction_1cc', 'ch1Introduction_1cd', 'ch1Introduction_1ce', 'ch1Introduction_1cf', 'ch1Introduction_1d0', 'ch1Introduction_1d1', 'ch1Introduction_1d2', 'ch1Introduction_1d3', 'ch1Introduction_1d4', 'ch1Introduction_1d5', 'ch1Introduction_1d6', 'ch1Introduction_1d7', 'ch1Introduction_1d8', 'ch1Introduction_1d9', 'ch1Introduction_1da', 'ch1Introduction_1db', 'ch1Introduction_1dc', 'ch1Introduction_1dd', 'ch1Introduction_1de', 'ch1Introduction_1df', 'ch1Introduction_1e0', 'ch1Introduction_1e1'], 'ch5func': ['ch5func_1', 'ch5func_2', 'ch5func_3', 'ch5func_4', 'ch5func_5', 'ch5func_6', 'ch5func_7', 'ch5func_8', 'ch5func_9', 'ch5func_a', 'ch5func_b', 'ch5func_c', 'ch5func_d', 'ch5func_e', 'ch5func_f', 'ch5func_10', 'ch5func_11', 'ch5func_12', 'ch5func_13', 'ch5func_14', 'ch5func_15', 'ch5func_16', 'ch5func_17', 'ch5func_18', 'ch5func_19', 'ch5func_1a', 'ch5func_1b', 'ch5func_1c', 'ch5func_1d', 'ch5func_1e', 'ch5func_1f', 'ch5func_20', 'ch5func_21', 'ch5func_22', 'ch5func_23', 'ch5func_24', 'ch5func_25', 'ch5func_26', 'ch5func_27', 'ch5func_28', 'ch5func_29', 'ch5func_2a', 'ch5func_2b', 'ch5func_2c', 'ch5func_2d', 'ch5func_2e', 'ch5func_2f', 'ch5func_30', 'ch5func_31', 'ch5func_32', 'ch5func_33', 'ch5func_34', 'ch5func_35', 'ch5func_36', 'ch5func_37', 'ch5func_38', 'ch5func_39', 'ch5func_3a', 'ch5func_3b', 'ch5func_3c', 'ch5func_3d', 'ch5func_3e', 'ch5func_3f', 'ch5func_40', 'ch5func_41', 'ch5func_42', 'ch5func_43', 'ch5func_44', 'ch5func_45', 'ch5func_46', 'ch5func_47', 'ch5func_48', 'ch5func_49', 'ch5func_4a', 'ch5func_4b', 'ch5func_4c', 'ch5func_4d', 'ch5func_4e', 'ch5func_4f', 'ch5func_50', 'ch5func_51', 'ch5func_52', 'ch5func_53', 'ch5func_54', 'ch5func_55', 'ch5func_56', 'ch5func_57', 'ch5func_58', 'ch5func_59', 'ch5func_5a', 'ch5func_5b', 'ch5func_5c', 'ch5func_5d', 'ch5func_5e', 'ch5func_5f', 'ch5func_60', 'ch5func_61', 'ch5func_62', 'ch5func_63', 'ch5func_64', 'ch5func_65', 'ch5func_66', 'ch5func_67', 'ch5func_68', 'ch5func_69', 'ch5func_6a', 'ch5func_6b', 'ch5func_6c', 'ch5func_6d', 'ch5func_6e', 'ch5func_6f', 'ch5func_70', 'ch5func_71', 'ch5func_72', 'ch5func_73', 'ch5func_74', 'ch5func_75', 'ch5func_76', 'ch5func_77', 'ch5func_78', 'ch5func_79', 'ch5func_7a', 'ch5func_7b', 'ch5func_7c', 'ch5func_7d', 'ch5func_7e', 'ch5func_7f', 'ch5func_80', 'ch5func_81', 'ch5func_82', 'ch5func_83', 'ch5func_84', 'ch5func_85', 'ch5func_86', 'ch5func_87', 'ch5func_88', 'ch5func_89', 'ch5func_8a', 'ch5func_8b', 'ch5func_8c', 'ch5func_8d', 'ch5func_8e', 'ch5func_8f', 'ch5func_90', 'ch5func_91', 'ch5func_92', 'ch5func_93', 'ch5func_94', 'ch5func_95', 'ch5func_96', 'ch5func_97', 'ch5func_98', 'ch5func_99', 'ch5func_9a', 'ch5func_9b', 'ch5func_9c', 'ch5func_9d', 'ch5func_9e', 'ch5func_9f', 'ch5func_a0', 'ch5func_a1', 'ch5func_a2', 'ch5func_a3', 'ch5func_a4', 'ch5func_a5', 'ch5func_a6', 'ch5func_a7', 'ch5func_a8', 'ch5func_a9', 'ch5func_aa', 'ch5func_ab', 'ch5func_ac', 'ch5func_ad', 'ch5func_ae', 'ch5func_af', 'ch5func_b0', 'ch5func_b1', 'ch5func_b2', 'ch5func_b3', 'ch5func_b4', 'ch5func_b5', 'ch5func_b6', 'ch5func_b7', 'ch5func_b8', 'ch5func_b9', 'ch5func_ba', 'ch5func_bb', 'ch5func_bc', 'ch5func_bd', 'ch5func_be', 'ch5func_bf', 'ch5func_c0', 'ch5func_c1', 'ch5func_c2', 'ch5func_c3', 'ch5func_c4', 'ch5func_c5', 'ch5func_c6', 'ch5func_c7', 'ch5func_c8', 'ch5func_c9', 'ch5func_ca', 'ch5func_cb', 'ch5func_cc', 'ch5func_cd', 'ch5func_ce', 'ch5func_cf', 'ch5func_d0', 'ch5func_d1', 'ch5func_d2', 'ch5func_d3', 'ch5func_d4', 'ch5func_d5', 'ch5func_d6', 'ch5func_d7', 'ch5func_d8', 'ch5func_d9', 'ch5func_da', 'ch5func_db', 'ch5func_dc', 'ch5func_dd', 'ch5func_de', 'ch5func_df', 'ch5func_e0', 'ch5func_e1', 'ch5func_e2', 'ch5func_e3', 'ch5func_e4', 'ch5func_e5', 'ch5func_e6', 'ch5func_e7', 'ch5func_e8', 'ch5func_e9', 'ch5func_ea', 'ch5func_eb', 'ch5func_ec', 'ch5func_ed', 'ch5func_ee', 'ch5func_ef', 'ch5func_f0', 'ch5func_f1', 'ch5func_f2', 'ch5func_f3', 'ch5func_f4', 'ch5func_f5', 'ch5func_f6', 'ch5func_f7', 'ch5func_f8', 'ch5func_f9', 'ch5func_fa', 'ch5func_fb', 'ch5func_fc', 'ch5func_fd', 'ch5func_fe', 'ch5func_ff', 'ch5func_100', 'ch5func_101', 'ch5func_102', 'ch5func_103', 'ch5func_104', 'ch5func_105', 'ch5func_106', 'ch5func_107', 'ch5func_108', 'ch5func_109', 'ch5func_10a', 'ch5func_10b', 'ch5func_10c', 'ch5func_10d', 'ch5func_10e', 'ch5func_10f', 'ch5func_110', 'ch5func_111', 'ch5func_112', 'ch5func_113', 'ch5func_114', 'ch5func_115', 'ch5func_116', 'ch5func_117', 'ch5func_118', 'ch5func_119', 'ch5func_11a', 'ch5func_11b', 'ch5func_11c', 'ch5func_11d', 'ch5func_11e', 'ch5func_11f', 'ch5func_120', 'ch5func_121', 'ch5func_122', 'ch5func_123', 'ch5func_124', 'ch5func_125', 'ch5func_126', 'ch5func_127', 'ch5func_128', 'ch5func_129', 'ch5func_12a', 'ch5func_12b', 'ch5func_12c', 'ch5func_12d', 'ch5func_12e', 'ch5func_12f', 'ch5func_130', 'ch5func_131', 'ch5func_132', 'ch5func_133', 'ch5func_134', 'ch5func_135', 'ch5func_136', 'ch5func_137', 'ch5func_138', 'ch5func_139', 'ch5func_13a', 'ch5func_13b', 'ch5func_13c', 'ch5func_13d', 'ch5func_13e', 'ch5func_13f', 'ch5func_140', 'ch5func_141', 'ch5func_142', 'ch5func_143', 'ch5func_144', 'ch5func_145', 'ch5func_146', 'ch5func_147', 'ch5func_148', 'ch5func_149', 'ch5func_14a', 'ch5func_14b', 'ch5func_14c', 'ch5func_14d', 'ch5func_14e', 'ch5func_14f', 'ch5func_150', 'ch5func_151', 'ch5func_152', 'ch5func_153', 'ch5func_154', 'ch5func_155', 'ch5func_156', 'ch5func_157', 'ch5func_158', 'ch5func_159', 'ch5func_15a', 'ch5func_15b', 'ch5func_15c', 'ch5func_15d', 'ch5func_15e', 'ch5func_15f', 'ch5func_160', 'ch5func_161', 'ch5func_162', 'ch5func_163', 'ch5func_164', 'ch5func_165', 'ch5func_166', 'ch5func_167', 'ch5func_168', 'ch5func_169', 'ch5func_16a', 'ch5func_16b', 'ch5func_16c', 'ch5func_16d', 'ch5func_16e', 'ch5func_16f', 'ch5func_170', 'ch5func_171', 'ch5func_172', 'ch5func_173', 'ch5func_174', 'ch5func_175', 'ch5func_176', 'ch5func_177', 'ch5func_178', 'ch5func_179', 'ch5func_17a', 'ch5func_17b', 'ch5func_17c', 'ch5func_17d', 'ch5func_17e', 'ch5func_17f', 'ch5func_180', 'ch5func_181', 'ch5func_182', 'ch5func_183', 'ch5func_184', 'ch5func_185', 'ch5func_186', 'ch5func_187', 'ch5func_188', 'ch5func_189', 'ch5func_18a', 'ch5func_18b', 'ch5func_18c', 'ch5func_18d', 'ch5func_18e', 'ch5func_18f', 'ch5func_190', 'ch5func_191', 'ch5func_192', 'ch5func_193', 'ch5func_194', 'ch5func_195', 'ch5func_196', 'ch5func_197', 'ch5func_198', 'ch5func_199', 'ch5func_19a', 'ch5func_19b', 'ch5func_19c', 'ch5func_19d', 'ch5func_19e', 'ch5func_19f', 'ch5func_1a0', 'ch5func_1a1', 'ch5func_1a2', 'ch5func_1a3', 'ch5func_1a4', 'ch5func_1a5', 'ch5func_1a6', 'ch5func_1a7', 'ch5func_1a8', 'ch5func_1a9', 'ch5func_1aa', 'ch5func_1ab', 'ch5func_1ac', 'ch5func_1ad', 'ch5func_1ae', 'ch5func_1af', 'ch5func_1b0', 'ch5func_1b1', 'ch5func_1b2', 'ch5func_1b3', 'ch5func_1b4', 'ch5func_1b5', 'ch5func_1b6', 'ch5func_1b7', 'ch5func_1b8', 'ch5func_1b9', 'ch5func_1ba', 'ch5func_1bb', 'ch5func_1bc', 'ch5func_1bd', 'ch5func_1be', 'ch5func_1bf', 'ch5func_1c0', 'ch5func_1c1', 'ch5func_1c2', 'ch5func_1c3', 'ch5func_1c4', 'ch5func_1c5', 'ch5func_1c6', 'ch5func_1c7', 'ch5func_1c8', 'ch5func_1c9', 'ch5func_1ca', 'ch5func_1cb', 'ch5func_1cc', 'ch5func_1cd', 'ch5func_1ce', 'ch5func_1cf', 'ch5func_1d0', 'ch5func_1d1', 'ch5func_1d2', 'ch5func_1d3', 'ch5func_1d4', 'ch5func_1d5', 'ch5func_1d6', 'ch5func_1d7', 'ch5func_1d8', 'ch5func_1d9', 'ch5func_1da', 'ch5func_1db', 'ch5func_1dc', 'ch5func_1dd', 'ch5func_1de', 'ch5func_1df', 'ch5func_1e0', 'ch5func_1e1'], 'ch3list_tuples': ['ch3list_tuples_1', 'ch3list_tuples_2', 'ch3list_tuples_3', 'ch3list_tuples_4', 'ch3list_tuples_5', 'ch3list_tuples_6', 'ch3list_tuples_7', 'ch3list_tuples_8', 'ch3list_tuples_9', 'ch3list_tuples_a', 'ch3list_tuples_b', 'ch3list_tuples_c', 'ch3list_tuples_d', 'ch3list_tuples_e', 'ch3list_tuples_f', 'ch3list_tuples_10', 'ch3list_tuples_11', 'ch3list_tuples_12', 'ch3list_tuples_13', 'ch3list_tuples_14', 'ch3list_tuples_15', 'ch3list_tuples_16', 'ch3list_tuples_17', 'ch3list_tuples_18', 'ch3list_tuples_19', 'ch3list_tuples_1a', 'ch3list_tuples_1b', 'ch3list_tuples_1c', 'ch3list_tuples_1d', 'ch3list_tuples_1e', 'ch3list_tuples_1f', 'ch3list_tuples_20', 'ch3list_tuples_21', 'ch3list_tuples_22', 'ch3list_tuples_23', 'ch3list_tuples_24', 'ch3list_tuples_25', 'ch3list_tuples_26', 'ch3list_tuples_27', 'ch3list_tuples_28', 'ch3list_tuples_29', 'ch3list_tuples_2a', 'ch3list_tuples_2b', 'ch3list_tuples_2c', 'ch3list_tuples_2d', 'ch3list_tuples_2e', 'ch3list_tuples_2f', 'ch3list_tuples_30', 'ch3list_tuples_31', 'ch3list_tuples_32', 'ch3list_tuples_33', 'ch3list_tuples_34', 'ch3list_tuples_35', 'ch3list_tuples_36', 'ch3list_tuples_37', 'ch3list_tuples_38', 'ch3list_tuples_39', 'ch3list_tuples_3a', 'ch3list_tuples_3b', 'ch3list_tuples_3c', 'ch3list_tuples_3d', 'ch3list_tuples_3e', 'ch3list_tuples_3f', 'ch3list_tuples_40', 'ch3list_tuples_41', 'ch3list_tuples_42', 'ch3list_tuples_43', 'ch3list_tuples_44', 'ch3list_tuples_45', 'ch3list_tuples_46', 'ch3list_tuples_47', 'ch3list_tuples_48', 'ch3list_tuples_49', 'ch3list_tuples_4a', 'ch3list_tuples_4b', 'ch3list_tuples_4c', 'ch3list_tuples_4d', 'ch3list_tuples_4e', 'ch3list_tuples_4f', 'ch3list_tuples_50', 'ch3list_tuples_51', 'ch3list_tuples_52', 'ch3list_tuples_53', 'ch3list_tuples_54', 'ch3list_tuples_55', 'ch3list_tuples_56', 'ch3list_tuples_57', 'ch3list_tuples_58', 'ch3list_tuples_59', 'ch3list_tuples_5a', 'ch3list_tuples_5b', 'ch3list_tuples_5c', 'ch3list_tuples_5d', 'ch3list_tuples_5e', 'ch3list_tuples_5f', 'ch3list_tuples_60', 'ch3list_tuples_61', 'ch3list_tuples_62', 'ch3list_tuples_63', 'ch3list_tuples_64', 'ch3list_tuples_65', 'ch3list_tuples_66', 'ch3list_tuples_67', 'ch3list_tuples_68', 'ch3list_tuples_69', 'ch3list_tuples_6a', 'ch3list_tuples_6b', 'ch3list_tuples_6c', 'ch3list_tuples_6d', 'ch3list_tuples_6e', 'ch3list_tuples_6f', 'ch3list_tuples_70', 'ch3list_tuples_71', 'ch3list_tuples_72', 'ch3list_tuples_73', 'ch3list_tuples_74', 'ch3list_tuples_75', 'ch3list_tuples_76', 'ch3list_tuples_77', 'ch3list_tuples_78', 'ch3list_tuples_79', 'ch3list_tuples_7a', 'ch3list_tuples_7b', 'ch3list_tuples_7c', 'ch3list_tuples_7d', 'ch3list_tuples_7e', 'ch3list_tuples_7f', 'ch3list_tuples_80', 'ch3list_tuples_81', 'ch3list_tuples_82', 'ch3list_tuples_83', 'ch3list_tuples_84', 'ch3list_tuples_85', 'ch3list_tuples_86', 'ch3list_tuples_87', 'ch3list_tuples_88', 'ch3list_tuples_89', 'ch3list_tuples_8a', 'ch3list_tuples_8b', 'ch3list_tuples_8c', 'ch3list_tuples_8d', 'ch3list_tuples_8e', 'ch3list_tuples_8f', 'ch3list_tuples_90', 'ch3list_tuples_91', 'ch3list_tuples_92', 'ch3list_tuples_93', 'ch3list_tuples_94', 'ch3list_tuples_95', 'ch3list_tuples_96', 'ch3list_tuples_97', 'ch3list_tuples_98', 'ch3list_tuples_99', 'ch3list_tuples_9a', 'ch3list_tuples_9b', 'ch3list_tuples_9c', 'ch3list_tuples_9d', 'ch3list_tuples_9e', 'ch3list_tuples_9f', 'ch3list_tuples_a0', 'ch3list_tuples_a1', 'ch3list_tuples_a2', 'ch3list_tuples_a3', 'ch3list_tuples_a4', 'ch3list_tuples_a5', 'ch3list_tuples_a6', 'ch3list_tuples_a7', 'ch3list_tuples_a8', 'ch3list_tuples_a9', 'ch3list_tuples_aa', 'ch3list_tuples_ab', 'ch3list_tuples_ac', 'ch3list_tuples_ad', 'ch3list_tuples_ae', 'ch3list_tuples_af', 'ch3list_tuples_b0', 'ch3list_tuples_b1', 'ch3list_tuples_b2', 'ch3list_tuples_b3', 'ch3list_tuples_b4', 'ch3list_tuples_b5', 'ch3list_tuples_b6', 'ch3list_tuples_b7', 'ch3list_tuples_b8', 'ch3list_tuples_b9', 'ch3list_tuples_ba', 'ch3list_tuples_bb', 'ch3list_tuples_bc', 'ch3list_tuples_bd', 'ch3list_tuples_be', 'ch3list_tuples_bf', 'ch3list_tuples_c0', 'ch3list_tuples_c1', 'ch3list_tuples_c2', 'ch3list_tuples_c3', 'ch3list_tuples_c4', 'ch3list_tuples_c5', 'ch3list_tuples_c6', 'ch3list_tuples_c7', 'ch3list_tuples_c8', 'ch3list_tuples_c9', 'ch3list_tuples_ca', 'ch3list_tuples_cb', 'ch3list_tuples_cc', 'ch3list_tuples_cd', 'ch3list_tuples_ce', 'ch3list_tuples_cf', 'ch3list_tuples_d0', 'ch3list_tuples_d1', 'ch3list_tuples_d2', 'ch3list_tuples_d3', 'ch3list_tuples_d4', 'ch3list_tuples_d5', 'ch3list_tuples_d6', 'ch3list_tuples_d7', 'ch3list_tuples_d8', 'ch3list_tuples_d9', 'ch3list_tuples_da', 'ch3list_tuples_db', 'ch3list_tuples_dc', 'ch3list_tuples_dd', 'ch3list_tuples_de', 'ch3list_tuples_df', 'ch3list_tuples_e0', 'ch3list_tuples_e1', 'ch3list_tuples_e2', 'ch3list_tuples_e3', 'ch3list_tuples_e4', 'ch3list_tuples_e5', 'ch3list_tuples_e6', 'ch3list_tuples_e7', 'ch3list_tuples_e8', 'ch3list_tuples_e9', 'ch3list_tuples_ea', 'ch3list_tuples_eb', 'ch3list_tuples_ec', 'ch3list_tuples_ed', 'ch3list_tuples_ee', 'ch3list_tuples_ef', 'ch3list_tuples_f0', 'ch3list_tuples_f1', 'ch3list_tuples_f2', 'ch3list_tuples_f3', 'ch3list_tuples_f4', 'ch3list_tuples_f5', 'ch3list_tuples_f6', 'ch3list_tuples_f7', 'ch3list_tuples_f8', 'ch3list_tuples_f9', 'ch3list_tuples_fa', 'ch3list_tuples_fb', 'ch3list_tuples_fc', 'ch3list_tuples_fd', 'ch3list_tuples_fe', 'ch3list_tuples_ff', 'ch3list_tuples_100', 'ch3list_tuples_101', 'ch3list_tuples_102', 'ch3list_tuples_103', 'ch3list_tuples_104', 'ch3list_tuples_105', 'ch3list_tuples_106', 'ch3list_tuples_107', 'ch3list_tuples_108', 'ch3list_tuples_109', 'ch3list_tuples_10a', 'ch3list_tuples_10b', 'ch3list_tuples_10c', 'ch3list_tuples_10d', 'ch3list_tuples_10e', 'ch3list_tuples_10f', 'ch3list_tuples_110', 'ch3list_tuples_111', 'ch3list_tuples_112', 'ch3list_tuples_113', 'ch3list_tuples_114', 'ch3list_tuples_115', 'ch3list_tuples_116', 'ch3list_tuples_117', 'ch3list_tuples_118', 'ch3list_tuples_119', 'ch3list_tuples_11a', 'ch3list_tuples_11b', 'ch3list_tuples_11c', 'ch3list_tuples_11d', 'ch3list_tuples_11e', 'ch3list_tuples_11f', 'ch3list_tuples_120', 'ch3list_tuples_121', 'ch3list_tuples_122', 'ch3list_tuples_123', 'ch3list_tuples_124', 'ch3list_tuples_125', 'ch3list_tuples_126', 'ch3list_tuples_127', 'ch3list_tuples_128', 'ch3list_tuples_129', 'ch3list_tuples_12a', 'ch3list_tuples_12b', 'ch3list_tuples_12c', 'ch3list_tuples_12d', 'ch3list_tuples_12e', 'ch3list_tuples_12f', 'ch3list_tuples_130', 'ch3list_tuples_131', 'ch3list_tuples_132', 'ch3list_tuples_133', 'ch3list_tuples_134', 'ch3list_tuples_135', 'ch3list_tuples_136', 'ch3list_tuples_137', 'ch3list_tuples_138', 'ch3list_tuples_139', 'ch3list_tuples_13a', 'ch3list_tuples_13b', 'ch3list_tuples_13c', 'ch3list_tuples_13d', 'ch3list_tuples_13e', 'ch3list_tuples_13f', 'ch3list_tuples_140', 'ch3list_tuples_141', 'ch3list_tuples_142', 'ch3list_tuples_143', 'ch3list_tuples_144', 'ch3list_tuples_145', 'ch3list_tuples_146', 'ch3list_tuples_147', 'ch3list_tuples_148', 'ch3list_tuples_149', 'ch3list_tuples_14a', 'ch3list_tuples_14b', 'ch3list_tuples_14c', 'ch3list_tuples_14d', 'ch3list_tuples_14e', 'ch3list_tuples_14f', 'ch3list_tuples_150', 'ch3list_tuples_151', 'ch3list_tuples_152', 'ch3list_tuples_153', 'ch3list_tuples_154', 'ch3list_tuples_155', 'ch3list_tuples_156', 'ch3list_tuples_157', 'ch3list_tuples_158', 'ch3list_tuples_159', 'ch3list_tuples_15a', 'ch3list_tuples_15b', 'ch3list_tuples_15c', 'ch3list_tuples_15d', 'ch3list_tuples_15e', 'ch3list_tuples_15f', 'ch3list_tuples_160', 'ch3list_tuples_161', 'ch3list_tuples_162', 'ch3list_tuples_163', 'ch3list_tuples_164', 'ch3list_tuples_165', 'ch3list_tuples_166', 'ch3list_tuples_167', 'ch3list_tuples_168', 'ch3list_tuples_169', 'ch3list_tuples_16a', 'ch3list_tuples_16b', 'ch3list_tuples_16c', 'ch3list_tuples_16d', 'ch3list_tuples_16e', 'ch3list_tuples_16f', 'ch3list_tuples_170', 'ch3list_tuples_171', 'ch3list_tuples_172', 'ch3list_tuples_173', 'ch3list_tuples_174', 'ch3list_tuples_175', 'ch3list_tuples_176', 'ch3list_tuples_177', 'ch3list_tuples_178', 'ch3list_tuples_179', 'ch3list_tuples_17a', 'ch3list_tuples_17b', 'ch3list_tuples_17c', 'ch3list_tuples_17d', 'ch3list_tuples_17e', 'ch3list_tuples_17f', 'ch3list_tuples_180', 'ch3list_tuples_181', 'ch3list_tuples_182', 'ch3list_tuples_183', 'ch3list_tuples_184', 'ch3list_tuples_185', 'ch3list_tuples_186', 'ch3list_tuples_187', 'ch3list_tuples_188', 'ch3list_tuples_189', 'ch3list_tuples_18a', 'ch3list_tuples_18b', 'ch3list_tuples_18c', 'ch3list_tuples_18d', 'ch3list_tuples_18e', 'ch3list_tuples_18f', 'ch3list_tuples_190', 'ch3list_tuples_191', 'ch3list_tuples_192', 'ch3list_tuples_193', 'ch3list_tuples_194', 'ch3list_tuples_195', 'ch3list_tuples_196', 'ch3list_tuples_197', 'ch3list_tuples_198', 'ch3list_tuples_199', 'ch3list_tuples_19a', 'ch3list_tuples_19b', 'ch3list_tuples_19c', 'ch3list_tuples_19d', 'ch3list_tuples_19e', 'ch3list_tuples_19f', 'ch3list_tuples_1a0', 'ch3list_tuples_1a1', 'ch3list_tuples_1a2', 'ch3list_tuples_1a3', 'ch3list_tuples_1a4', 'ch3list_tuples_1a5', 'ch3list_tuples_1a6', 'ch3list_tuples_1a7', 'ch3list_tuples_1a8', 'ch3list_tuples_1a9', 'ch3list_tuples_1aa', 'ch3list_tuples_1ab', 'ch3list_tuples_1ac', 'ch3list_tuples_1ad', 'ch3list_tuples_1ae', 'ch3list_tuples_1af', 'ch3list_tuples_1b0', 'ch3list_tuples_1b1', 'ch3list_tuples_1b2', 'ch3list_tuples_1b3', 'ch3list_tuples_1b4', 'ch3list_tuples_1b5', 'ch3list_tuples_1b6', 'ch3list_tuples_1b7', 'ch3list_tuples_1b8', 'ch3list_tuples_1b9', 'ch3list_tuples_1ba', 'ch3list_tuples_1bb', 'ch3list_tuples_1bc', 'ch3list_tuples_1bd', 'ch3list_tuples_1be', 'ch3list_tuples_1bf', 'ch3list_tuples_1c0', 'ch3list_tuples_1c1', 'ch3list_tuples_1c2', 'ch3list_tuples_1c3', 'ch3list_tuples_1c4', 'ch3list_tuples_1c5', 'ch3list_tuples_1c6', 'ch3list_tuples_1c7', 'ch3list_tuples_1c8', 'ch3list_tuples_1c9', 'ch3list_tuples_1ca', 'ch3list_tuples_1cb', 'ch3list_tuples_1cc', 'ch3list_tuples_1cd', 'ch3list_tuples_1ce', 'ch3list_tuples_1cf', 'ch3list_tuples_1d0', 'ch3list_tuples_1d1', 'ch3list_tuples_1d2', 'ch3list_tuples_1d3', 'ch3list_tuples_1d4', 'ch3list_tuples_1d5', 'ch3list_tuples_1d6', 'ch3list_tuples_1d7', 'ch3list_tuples_1d8', 'ch3list_tuples_1d9', 'ch3list_tuples_1da', 'ch3list_tuples_1db', 'ch3list_tuples_1dc', 'ch3list_tuples_1dd', 'ch3list_tuples_1de', 'ch3list_tuples_1df', 'ch3list_tuples_1e0', 'ch3list_tuples_1e1'], 'ch2intro': ['ch2intro_1', 'ch2intro_2', 'ch2intro_3', 'ch2intro_4', 'ch2intro_5', 'ch2intro_6', 'ch2intro_7', 'ch2intro_8', 'ch2intro_9', 'ch2intro_a', 'ch2intro_b', 'ch2intro_c', 'ch2intro_d', 'ch2intro_e', 'ch2intro_f', 'ch2intro_10', 'ch2intro_11', 'ch2intro_12', 'ch2intro_13', 'ch2intro_14', 'ch2intro_15', 'ch2intro_16', 'ch2intro_17', 'ch2intro_18', 'ch2intro_19', 'ch2intro_1a', 'ch2intro_1b', 'ch2intro_1c', 'ch2intro_1d', 'ch2intro_1e', 'ch2intro_1f', 'ch2intro_20', 'ch2intro_21', 'ch2intro_22', 'ch2intro_23', 'ch2intro_24', 'ch2intro_25', 'ch2intro_26', 'ch2intro_27', 'ch2intro_28', 'ch2intro_29', 'ch2intro_2a', 'ch2intro_2b', 'ch2intro_2c', 'ch2intro_2d', 'ch2intro_2e', 'ch2intro_2f', 'ch2intro_30', 'ch2intro_31', 'ch2intro_32', 'ch2intro_33', 'ch2intro_34', 'ch2intro_35', 'ch2intro_36', 'ch2intro_37', 'ch2intro_38', 'ch2intro_39', 'ch2intro_3a', 'ch2intro_3b', 'ch2intro_3c', 'ch2intro_3d', 'ch2intro_3e', 'ch2intro_3f', 'ch2intro_40', 'ch2intro_41', 'ch2intro_42', 'ch2intro_43', 'ch2intro_44', 'ch2intro_45', 'ch2intro_46', 'ch2intro_47', 'ch2intro_48', 'ch2intro_49', 'ch2intro_4a', 'ch2intro_4b', 'ch2intro_4c', 'ch2intro_4d', 'ch2intro_4e', 'ch2intro_4f', 'ch2intro_50', 'ch2intro_51', 'ch2intro_52', 'ch2intro_53', 'ch2intro_54', 'ch2intro_55', 'ch2intro_56', 'ch2intro_57', 'ch2intro_58', 'ch2intro_59', 'ch2intro_5a', 'ch2intro_5b', 'ch2intro_5c', 'ch2intro_5d', 'ch2intro_5e', 'ch2intro_5f', 'ch2intro_60', 'ch2intro_61', 'ch2intro_62', 'ch2intro_63', 'ch2intro_64', 'ch2intro_65', 'ch2intro_66', 'ch2intro_67', 'ch2intro_68', 'ch2intro_69', 'ch2intro_6a', 'ch2intro_6b', 'ch2intro_6c', 'ch2intro_6d', 'ch2intro_6e', 'ch2intro_6f', 'ch2intro_70', 'ch2intro_71', 'ch2intro_72', 'ch2intro_73', 'ch2intro_74', 'ch2intro_75', 'ch2intro_76', 'ch2intro_77', 'ch2intro_78', 'ch2intro_79', 'ch2intro_7a', 'ch2intro_7b', 'ch2intro_7c', 'ch2intro_7d', 'ch2intro_7e', 'ch2intro_7f', 'ch2intro_80', 'ch2intro_81', 'ch2intro_82', 'ch2intro_83', 'ch2intro_84', 'ch2intro_85', 'ch2intro_86', 'ch2intro_87', 'ch2intro_88', 'ch2intro_89', 'ch2intro_8a', 'ch2intro_8b', 'ch2intro_8c', 'ch2intro_8d', 'ch2intro_8e', 'ch2intro_8f', 'ch2intro_90', 'ch2intro_91', 'ch2intro_92', 'ch2intro_93', 'ch2intro_94', 'ch2intro_95', 'ch2intro_96', 'ch2intro_97', 'ch2intro_98', 'ch2intro_99', 'ch2intro_9a', 'ch2intro_9b', 'ch2intro_9c', 'ch2intro_9d', 'ch2intro_9e', 'ch2intro_9f', 'ch2intro_a0', 'ch2intro_a1', 'ch2intro_a2', 'ch2intro_a3', 'ch2intro_a4', 'ch2intro_a5', 'ch2intro_a6', 'ch2intro_a7', 'ch2intro_a8', 'ch2intro_a9', 'ch2intro_aa', 'ch2intro_ab', 'ch2intro_ac', 'ch2intro_ad', 'ch2intro_ae', 'ch2intro_af', 'ch2intro_b0', 'ch2intro_b1', 'ch2intro_b2', 'ch2intro_b3', 'ch2intro_b4', 'ch2intro_b5', 'ch2intro_b6', 'ch2intro_b7', 'ch2intro_b8', 'ch2intro_b9', 'ch2intro_ba', 'ch2intro_bb', 'ch2intro_bc', 'ch2intro_bd', 'ch2intro_be', 'ch2intro_bf', 'ch2intro_c0', 'ch2intro_c1', 'ch2intro_c2', 'ch2intro_c3', 'ch2intro_c4', 'ch2intro_c5', 'ch2intro_c6', 'ch2intro_c7', 'ch2intro_c8', 'ch2intro_c9', 'ch2intro_ca', 'ch2intro_cb', 'ch2intro_cc', 'ch2intro_cd', 'ch2intro_ce', 'ch2intro_cf', 'ch2intro_d0', 'ch2intro_d1', 'ch2intro_d2', 'ch2intro_d3', 'ch2intro_d4', 'ch2intro_d5', 'ch2intro_d6', 'ch2intro_d7', 'ch2intro_d8', 'ch2intro_d9', 'ch2intro_da', 'ch2intro_db', 'ch2intro_dc', 'ch2intro_dd', 'ch2intro_de', 'ch2intro_df', 'ch2intro_e0', 'ch2intro_e1', 'ch2intro_e2', 'ch2intro_e3', 'ch2intro_e4', 'ch2intro_e5', 'ch2intro_e6', 'ch2intro_e7', 'ch2intro_e8', 'ch2intro_e9', 'ch2intro_ea', 'ch2intro_eb', 'ch2intro_ec', 'ch2intro_ed', 'ch2intro_ee', 'ch2intro_ef', 'ch2intro_f0', 'ch2intro_f1', 'ch2intro_f2', 'ch2intro_f3', 'ch2intro_f4', 'ch2intro_f5', 'ch2intro_f6', 'ch2intro_f7', 'ch2intro_f8', 'ch2intro_f9', 'ch2intro_fa', 'ch2intro_fb', 'ch2intro_fc', 'ch2intro_fd', 'ch2intro_fe', 'ch2intro_ff', 'ch2intro_100', 'ch2intro_101', 'ch2intro_102', 'ch2intro_103', 'ch2intro_104', 'ch2intro_105', 'ch2intro_106', 'ch2intro_107', 'ch2intro_108', 'ch2intro_109', 'ch2intro_10a', 'ch2intro_10b', 'ch2intro_10c', 'ch2intro_10d', 'ch2intro_10e', 'ch2intro_10f', 'ch2intro_110', 'ch2intro_111', 'ch2intro_112', 'ch2intro_113', 'ch2intro_114', 'ch2intro_115', 'ch2intro_116', 'ch2intro_117', 'ch2intro_118', 'ch2intro_119', 'ch2intro_11a', 'ch2intro_11b', 'ch2intro_11c', 'ch2intro_11d', 'ch2intro_11e', 'ch2intro_11f', 'ch2intro_120', 'ch2intro_121', 'ch2intro_122', 'ch2intro_123', 'ch2intro_124', 'ch2intro_125', 'ch2intro_126', 'ch2intro_127', 'ch2intro_128', 'ch2intro_129', 'ch2intro_12a', 'ch2intro_12b', 'ch2intro_12c', 'ch2intro_12d', 'ch2intro_12e', 'ch2intro_12f', 'ch2intro_130', 'ch2intro_131', 'ch2intro_132', 'ch2intro_133', 'ch2intro_134', 'ch2intro_135', 'ch2intro_136', 'ch2intro_137', 'ch2intro_138', 'ch2intro_139', 'ch2intro_13a', 'ch2intro_13b', 'ch2intro_13c', 'ch2intro_13d', 'ch2intro_13e', 'ch2intro_13f', 'ch2intro_140', 'ch2intro_141', 'ch2intro_142', 'ch2intro_143', 'ch2intro_144', 'ch2intro_145', 'ch2intro_146', 'ch2intro_147', 'ch2intro_148', 'ch2intro_149', 'ch2intro_14a', 'ch2intro_14b', 'ch2intro_14c', 'ch2intro_14d', 'ch2intro_14e', 'ch2intro_14f', 'ch2intro_150', 'ch2intro_151', 'ch2intro_152', 'ch2intro_153', 'ch2intro_154', 'ch2intro_155', 'ch2intro_156', 'ch2intro_157', 'ch2intro_158', 'ch2intro_159', 'ch2intro_15a', 'ch2intro_15b', 'ch2intro_15c', 'ch2intro_15d', 'ch2intro_15e', 'ch2intro_15f', 'ch2intro_160', 'ch2intro_161', 'ch2intro_162', 'ch2intro_163', 'ch2intro_164', 'ch2intro_165', 'ch2intro_166', 'ch2intro_167', 'ch2intro_168', 'ch2intro_169', 'ch2intro_16a', 'ch2intro_16b', 'ch2intro_16c', 'ch2intro_16d', 'ch2intro_16e', 'ch2intro_16f', 'ch2intro_170', 'ch2intro_171', 'ch2intro_172', 'ch2intro_173', 'ch2intro_174', 'ch2intro_175', 'ch2intro_176', 'ch2intro_177', 'ch2intro_178', 'ch2intro_179', 'ch2intro_17a', 'ch2intro_17b', 'ch2intro_17c', 'ch2intro_17d', 'ch2intro_17e', 'ch2intro_17f', 'ch2intro_180', 'ch2intro_181', 'ch2intro_182', 'ch2intro_183', 'ch2intro_184', 'ch2intro_185', 'ch2intro_186', 'ch2intro_187', 'ch2intro_188', 'ch2intro_189', 'ch2intro_18a', 'ch2intro_18b', 'ch2intro_18c', 'ch2intro_18d', 'ch2intro_18e', 'ch2intro_18f', 'ch2intro_190', 'ch2intro_191', 'ch2intro_192', 'ch2intro_193', 'ch2intro_194', 'ch2intro_195', 'ch2intro_196', 'ch2intro_197', 'ch2intro_198', 'ch2intro_199', 'ch2intro_19a', 'ch2intro_19b', 'ch2intro_19c', 'ch2intro_19d', 'ch2intro_19e', 'ch2intro_19f', 'ch2intro_1a0', 'ch2intro_1a1', 'ch2intro_1a2', 'ch2intro_1a3', 'ch2intro_1a4', 'ch2intro_1a5', 'ch2intro_1a6', 'ch2intro_1a7', 'ch2intro_1a8', 'ch2intro_1a9', 'ch2intro_1aa', 'ch2intro_1ab', 'ch2intro_1ac', 'ch2intro_1ad', 'ch2intro_1ae', 'ch2intro_1af', 'ch2intro_1b0', 'ch2intro_1b1', 'ch2intro_1b2', 'ch2intro_1b3', 'ch2intro_1b4', 'ch2intro_1b5', 'ch2intro_1b6', 'ch2intro_1b7', 'ch2intro_1b8', 'ch2intro_1b9', 'ch2intro_1ba', 'ch2intro_1bb', 'ch2intro_1bc', 'ch2intro_1bd', 'ch2intro_1be', 'ch2intro_1bf', 'ch2intro_1c0', 'ch2intro_1c1', 'ch2intro_1c2', 'ch2intro_1c3', 'ch2intro_1c4', 'ch2intro_1c5', 'ch2intro_1c6', 'ch2intro_1c7', 'ch2intro_1c8', 'ch2intro_1c9', 'ch2intro_1ca', 'ch2intro_1cb', 'ch2intro_1cc', 'ch2intro_1cd', 'ch2intro_1ce', 'ch2intro_1cf', 'ch2intro_1d0', 'ch2intro_1d1', 'ch2intro_1d2', 'ch2intro_1d3', 'ch2intro_1d4', 'ch2intro_1d5', 'ch2intro_1d6', 'ch2intro_1d7', 'ch2intro_1d8', 'ch2intro_1d9', 'ch2intro_1da', 'ch2intro_1db', 'ch2intro_1dc', 'ch2intro_1dd', 'ch2intro_1de', 'ch2intro_1df', 'ch2intro_1e0', 'ch2intro_1e1'], 'ch4strings_dicts': ['ch4strings_dicts_1', 'ch4strings_dicts_2', 'ch4strings_dicts_3', 'ch4strings_dicts_4', 'ch4strings_dicts_5', 'ch4strings_dicts_6', 'ch4strings_dicts_7', 'ch4strings_dicts_8', 'ch4strings_dicts_9', 'ch4strings_dicts_a', 'ch4strings_dicts_b', 'ch4strings_dicts_c', 'ch4strings_dicts_d', 'ch4strings_dicts_e', 'ch4strings_dicts_f', 'ch4strings_dicts_10', 'ch4strings_dicts_11', 'ch4strings_dicts_12', 'ch4strings_dicts_13', 'ch4strings_dicts_14', 'ch4strings_dicts_15', 'ch4strings_dicts_16', 'ch4strings_dicts_17', 'ch4strings_dicts_18', 'ch4strings_dicts_19', 'ch4strings_dicts_1a', 'ch4strings_dicts_1b', 'ch4strings_dicts_1c', 'ch4strings_dicts_1d', 'ch4strings_dicts_1e', 'ch4strings_dicts_1f', 'ch4strings_dicts_20', 'ch4strings_dicts_21', 'ch4strings_dicts_22', 'ch4strings_dicts_23', 'ch4strings_dicts_24', 'ch4strings_dicts_25', 'ch4strings_dicts_26', 'ch4strings_dicts_27', 'ch4strings_dicts_28', 'ch4strings_dicts_29', 'ch4strings_dicts_2a', 'ch4strings_dicts_2b', 'ch4strings_dicts_2c', 'ch4strings_dicts_2d', 'ch4strings_dicts_2e', 'ch4strings_dicts_2f', 'ch4strings_dicts_30', 'ch4strings_dicts_31', 'ch4strings_dicts_32', 'ch4strings_dicts_33', 'ch4strings_dicts_34', 'ch4strings_dicts_35', 'ch4strings_dicts_36', 'ch4strings_dicts_37', 'ch4strings_dicts_38', 'ch4strings_dicts_39', 'ch4strings_dicts_3a', 'ch4strings_dicts_3b', 'ch4strings_dicts_3c', 'ch4strings_dicts_3d', 'ch4strings_dicts_3e', 'ch4strings_dicts_3f', 'ch4strings_dicts_40', 'ch4strings_dicts_41', 'ch4strings_dicts_42', 'ch4strings_dicts_43', 'ch4strings_dicts_44', 'ch4strings_dicts_45', 'ch4strings_dicts_46', 'ch4strings_dicts_47', 'ch4strings_dicts_48', 'ch4strings_dicts_49', 'ch4strings_dicts_4a', 'ch4strings_dicts_4b', 'ch4strings_dicts_4c', 'ch4strings_dicts_4d', 'ch4strings_dicts_4e', 'ch4strings_dicts_4f', 'ch4strings_dicts_50', 'ch4strings_dicts_51', 'ch4strings_dicts_52', 'ch4strings_dicts_53', 'ch4strings_dicts_54', 'ch4strings_dicts_55', 'ch4strings_dicts_56', 'ch4strings_dicts_57', 'ch4strings_dicts_58', 'ch4strings_dicts_59', 'ch4strings_dicts_5a', 'ch4strings_dicts_5b', 'ch4strings_dicts_5c', 'ch4strings_dicts_5d', 'ch4strings_dicts_5e', 'ch4strings_dicts_5f', 'ch4strings_dicts_60', 'ch4strings_dicts_61', 'ch4strings_dicts_62', 'ch4strings_dicts_63', 'ch4strings_dicts_64', 'ch4strings_dicts_65', 'ch4strings_dicts_66', 'ch4strings_dicts_67', 'ch4strings_dicts_68', 'ch4strings_dicts_69', 'ch4strings_dicts_6a', 'ch4strings_dicts_6b', 'ch4strings_dicts_6c', 'ch4strings_dicts_6d', 'ch4strings_dicts_6e', 'ch4strings_dicts_6f', 'ch4strings_dicts_70', 'ch4strings_dicts_71', 'ch4strings_dicts_72', 'ch4strings_dicts_73', 'ch4strings_dicts_74', 'ch4strings_dicts_75', 'ch4strings_dicts_76', 'ch4strings_dicts_77', 'ch4strings_dicts_78', 'ch4strings_dicts_79', 'ch4strings_dicts_7a', 'ch4strings_dicts_7b', 'ch4strings_dicts_7c', 'ch4strings_dicts_7d', 'ch4strings_dicts_7e', 'ch4strings_dicts_7f', 'ch4strings_dicts_80', 'ch4strings_dicts_81', 'ch4strings_dicts_82', 'ch4strings_dicts_83', 'ch4strings_dicts_84', 'ch4strings_dicts_85', 'ch4strings_dicts_86', 'ch4strings_dicts_87', 'ch4strings_dicts_88', 'ch4strings_dicts_89', 'ch4strings_dicts_8a', 'ch4strings_dicts_8b', 'ch4strings_dicts_8c', 'ch4strings_dicts_8d', 'ch4strings_dicts_8e', 'ch4strings_dicts_8f', 'ch4strings_dicts_90', 'ch4strings_dicts_91', 'ch4strings_dicts_92', 'ch4strings_dicts_93', 'ch4strings_dicts_94', 'ch4strings_dicts_95', 'ch4strings_dicts_96', 'ch4strings_dicts_97', 'ch4strings_dicts_98', 'ch4strings_dicts_99', 'ch4strings_dicts_9a', 'ch4strings_dicts_9b', 'ch4strings_dicts_9c', 'ch4strings_dicts_9d', 'ch4strings_dicts_9e', 'ch4strings_dicts_9f', 'ch4strings_dicts_a0', 'ch4strings_dicts_a1', 'ch4strings_dicts_a2', 'ch4strings_dicts_a3', 'ch4strings_dicts_a4', 'ch4strings_dicts_a5', 'ch4strings_dicts_a6', 'ch4strings_dicts_a7', 'ch4strings_dicts_a8', 'ch4strings_dicts_a9', 'ch4strings_dicts_aa', 'ch4strings_dicts_ab', 'ch4strings_dicts_ac', 'ch4strings_dicts_ad', 'ch4strings_dicts_ae', 'ch4strings_dicts_af', 'ch4strings_dicts_b0', 'ch4strings_dicts_b1', 'ch4strings_dicts_b2', 'ch4strings_dicts_b3', 'ch4strings_dicts_b4', 'ch4strings_dicts_b5', 'ch4strings_dicts_b6', 'ch4strings_dicts_b7', 'ch4strings_dicts_b8', 'ch4strings_dicts_b9', 'ch4strings_dicts_ba', 'ch4strings_dicts_bb', 'ch4strings_dicts_bc', 'ch4strings_dicts_bd', 'ch4strings_dicts_be', 'ch4strings_dicts_bf', 'ch4strings_dicts_c0', 'ch4strings_dicts_c1', 'ch4strings_dicts_c2', 'ch4strings_dicts_c3', 'ch4strings_dicts_c4', 'ch4strings_dicts_c5', 'ch4strings_dicts_c6', 'ch4strings_dicts_c7', 'ch4strings_dicts_c8', 'ch4strings_dicts_c9', 'ch4strings_dicts_ca', 'ch4strings_dicts_cb', 'ch4strings_dicts_cc', 'ch4strings_dicts_cd', 'ch4strings_dicts_ce', 'ch4strings_dicts_cf', 'ch4strings_dicts_d0', 'ch4strings_dicts_d1', 'ch4strings_dicts_d2', 'ch4strings_dicts_d3', 'ch4strings_dicts_d4', 'ch4strings_dicts_d5', 'ch4strings_dicts_d6', 'ch4strings_dicts_d7', 'ch4strings_dicts_d8', 'ch4strings_dicts_d9', 'ch4strings_dicts_da', 'ch4strings_dicts_db', 'ch4strings_dicts_dc', 'ch4strings_dicts_dd', 'ch4strings_dicts_de', 'ch4strings_dicts_df', 'ch4strings_dicts_e0', 'ch4strings_dicts_e1', 'ch4strings_dicts_e2', 'ch4strings_dicts_e3', 'ch4strings_dicts_e4', 'ch4strings_dicts_e5', 'ch4strings_dicts_e6', 'ch4strings_dicts_e7', 'ch4strings_dicts_e8', 'ch4strings_dicts_e9', 'ch4strings_dicts_ea', 'ch4strings_dicts_eb', 'ch4strings_dicts_ec', 'ch4strings_dicts_ed', 'ch4strings_dicts_ee', 'ch4strings_dicts_ef', 'ch4strings_dicts_f0', 'ch4strings_dicts_f1', 'ch4strings_dicts_f2', 'ch4strings_dicts_f3', 'ch4strings_dicts_f4', 'ch4strings_dicts_f5', 'ch4strings_dicts_f6', 'ch4strings_dicts_f7', 'ch4strings_dicts_f8', 'ch4strings_dicts_f9', 'ch4strings_dicts_fa', 'ch4strings_dicts_fb', 'ch4strings_dicts_fc', 'ch4strings_dicts_fd', 'ch4strings_dicts_fe', 'ch4strings_dicts_ff', 'ch4strings_dicts_100', 'ch4strings_dicts_101', 'ch4strings_dicts_102', 'ch4strings_dicts_103', 'ch4strings_dicts_104', 'ch4strings_dicts_105', 'ch4strings_dicts_106', 'ch4strings_dicts_107', 'ch4strings_dicts_108', 'ch4strings_dicts_109', 'ch4strings_dicts_10a', 'ch4strings_dicts_10b', 'ch4strings_dicts_10c', 'ch4strings_dicts_10d', 'ch4strings_dicts_10e', 'ch4strings_dicts_10f', 'ch4strings_dicts_110', 'ch4strings_dicts_111', 'ch4strings_dicts_112', 'ch4strings_dicts_113', 'ch4strings_dicts_114', 'ch4strings_dicts_115', 'ch4strings_dicts_116', 'ch4strings_dicts_117', 'ch4strings_dicts_118', 'ch4strings_dicts_119', 'ch4strings_dicts_11a', 'ch4strings_dicts_11b', 'ch4strings_dicts_11c', 'ch4strings_dicts_11d', 'ch4strings_dicts_11e', 'ch4strings_dicts_11f', 'ch4strings_dicts_120', 'ch4strings_dicts_121', 'ch4strings_dicts_122', 'ch4strings_dicts_123', 'ch4strings_dicts_124', 'ch4strings_dicts_125', 'ch4strings_dicts_126', 'ch4strings_dicts_127', 'ch4strings_dicts_128', 'ch4strings_dicts_129', 'ch4strings_dicts_12a', 'ch4strings_dicts_12b', 'ch4strings_dicts_12c', 'ch4strings_dicts_12d', 'ch4strings_dicts_12e', 'ch4strings_dicts_12f', 'ch4strings_dicts_130', 'ch4strings_dicts_131', 'ch4strings_dicts_132', 'ch4strings_dicts_133', 'ch4strings_dicts_134', 'ch4strings_dicts_135', 'ch4strings_dicts_136', 'ch4strings_dicts_137', 'ch4strings_dicts_138', 'ch4strings_dicts_139', 'ch4strings_dicts_13a', 'ch4strings_dicts_13b', 'ch4strings_dicts_13c', 'ch4strings_dicts_13d', 'ch4strings_dicts_13e', 'ch4strings_dicts_13f', 'ch4strings_dicts_140', 'ch4strings_dicts_141', 'ch4strings_dicts_142', 'ch4strings_dicts_143', 'ch4strings_dicts_144', 'ch4strings_dicts_145', 'ch4strings_dicts_146', 'ch4strings_dicts_147', 'ch4strings_dicts_148', 'ch4strings_dicts_149', 'ch4strings_dicts_14a', 'ch4strings_dicts_14b', 'ch4strings_dicts_14c', 'ch4strings_dicts_14d', 'ch4strings_dicts_14e', 'ch4strings_dicts_14f', 'ch4strings_dicts_150', 'ch4strings_dicts_151', 'ch4strings_dicts_152', 'ch4strings_dicts_153', 'ch4strings_dicts_154', 'ch4strings_dicts_155', 'ch4strings_dicts_156', 'ch4strings_dicts_157', 'ch4strings_dicts_158', 'ch4strings_dicts_159', 'ch4strings_dicts_15a', 'ch4strings_dicts_15b', 'ch4strings_dicts_15c', 'ch4strings_dicts_15d', 'ch4strings_dicts_15e', 'ch4strings_dicts_15f', 'ch4strings_dicts_160', 'ch4strings_dicts_161', 'ch4strings_dicts_162', 'ch4strings_dicts_163', 'ch4strings_dicts_164', 'ch4strings_dicts_165', 'ch4strings_dicts_166', 'ch4strings_dicts_167', 'ch4strings_dicts_168', 'ch4strings_dicts_169', 'ch4strings_dicts_16a', 'ch4strings_dicts_16b', 'ch4strings_dicts_16c', 'ch4strings_dicts_16d', 'ch4strings_dicts_16e', 'ch4strings_dicts_16f', 'ch4strings_dicts_170', 'ch4strings_dicts_171', 'ch4strings_dicts_172', 'ch4strings_dicts_173', 'ch4strings_dicts_174', 'ch4strings_dicts_175', 'ch4strings_dicts_176', 'ch4strings_dicts_177', 'ch4strings_dicts_178', 'ch4strings_dicts_179', 'ch4strings_dicts_17a', 'ch4strings_dicts_17b', 'ch4strings_dicts_17c', 'ch4strings_dicts_17d', 'ch4strings_dicts_17e', 'ch4strings_dicts_17f', 'ch4strings_dicts_180', 'ch4strings_dicts_181', 'ch4strings_dicts_182', 'ch4strings_dicts_183', 'ch4strings_dicts_184', 'ch4strings_dicts_185', 'ch4strings_dicts_186', 'ch4strings_dicts_187', 'ch4strings_dicts_188', 'ch4strings_dicts_189', 'ch4strings_dicts_18a', 'ch4strings_dicts_18b', 'ch4strings_dicts_18c', 'ch4strings_dicts_18d', 'ch4strings_dicts_18e', 'ch4strings_dicts_18f', 'ch4strings_dicts_190', 'ch4strings_dicts_191', 'ch4strings_dicts_192', 'ch4strings_dicts_193', 'ch4strings_dicts_194', 'ch4strings_dicts_195', 'ch4strings_dicts_196', 'ch4strings_dicts_197', 'ch4strings_dicts_198', 'ch4strings_dicts_199', 'ch4strings_dicts_19a', 'ch4strings_dicts_19b', 'ch4strings_dicts_19c', 'ch4strings_dicts_19d', 'ch4strings_dicts_19e', 'ch4strings_dicts_19f', 'ch4strings_dicts_1a0', 'ch4strings_dicts_1a1', 'ch4strings_dicts_1a2', 'ch4strings_dicts_1a3', 'ch4strings_dicts_1a4', 'ch4strings_dicts_1a5', 'ch4strings_dicts_1a6', 'ch4strings_dicts_1a7', 'ch4strings_dicts_1a8', 'ch4strings_dicts_1a9', 'ch4strings_dicts_1aa', 'ch4strings_dicts_1ab', 'ch4strings_dicts_1ac', 'ch4strings_dicts_1ad', 'ch4strings_dicts_1ae', 'ch4strings_dicts_1af', 'ch4strings_dicts_1b0', 'ch4strings_dicts_1b1', 'ch4strings_dicts_1b2', 'ch4strings_dicts_1b3', 'ch4strings_dicts_1b4', 'ch4strings_dicts_1b5', 'ch4strings_dicts_1b6', 'ch4strings_dicts_1b7', 'ch4strings_dicts_1b8', 'ch4strings_dicts_1b9', 'ch4strings_dicts_1ba', 'ch4strings_dicts_1bb', 'ch4strings_dicts_1bc', 'ch4strings_dicts_1bd', 'ch4strings_dicts_1be', 'ch4strings_dicts_1bf', 'ch4strings_dicts_1c0', 'ch4strings_dicts_1c1', 'ch4strings_dicts_1c2', 'ch4strings_dicts_1c3', 'ch4strings_dicts_1c4', 'ch4strings_dicts_1c5', 'ch4strings_dicts_1c6', 'ch4strings_dicts_1c7', 'ch4strings_dicts_1c8', 'ch4strings_dicts_1c9', 'ch4strings_dicts_1ca', 'ch4strings_dicts_1cb', 'ch4strings_dicts_1cc', 'ch4strings_dicts_1cd', 'ch4strings_dicts_1ce', 'ch4strings_dicts_1cf', 'ch4strings_dicts_1d0', 'ch4strings_dicts_1d1', 'ch4strings_dicts_1d2', 'ch4strings_dicts_1d3', 'ch4strings_dicts_1d4', 'ch4strings_dicts_1d5', 'ch4strings_dicts_1d6', 'ch4strings_dicts_1d7', 'ch4strings_dicts_1d8', 'ch4strings_dicts_1d9', 'ch4strings_dicts_1da', 'ch4strings_dicts_1db', 'ch4strings_dicts_1dc', 'ch4strings_dicts_1dd', 'ch4strings_dicts_1de', 'ch4strings_dicts_1df', 'ch4strings_dicts_1e0', 'ch4strings_dicts_1e1'], 'ch11Section_5': ['ch11Section_5_1', 'ch11Section_5_2', 'ch11Section_5_3', 'ch11Section_5_4', 'ch11Section_5_5', 'ch11Section_5_6', 'ch11Section_5_7', 'ch11Section_5_8', 'ch11Section_5_9', 'ch11Section_5_a', 'ch11Section_5_b', 'ch11Section_5_c', 'ch11Section_5_d', 'ch11Section_5_e', 'ch11Section_5_f', 'ch11Section_5_10', 'ch11Section_5_11', 'ch11Section_5_12', 'ch11Section_5_13', 'ch11Section_5_14', 'ch11Section_5_15', 'ch11Section_5_16', 'ch11Section_5_17', 'ch11Section_5_18', 'ch11Section_5_19', 'ch11Section_5_1a', 'ch11Section_5_1b', 'ch11Section_5_1c', 'ch11Section_5_1d', 'ch11Section_5_1e', 'ch11Section_5_1f', 'ch11Section_5_20', 'ch11Section_5_21', 'ch11Section_5_22', 'ch11Section_5_23', 'ch11Section_5_24', 'ch11Section_5_25', 'ch11Section_5_26', 'ch11Section_5_27', 'ch11Section_5_28', 'ch11Section_5_29', 'ch11Section_5_2a', 'ch11Section_5_2b', 'ch11Section_5_2c', 'ch11Section_5_2d', 'ch11Section_5_2e', 'ch11Section_5_2f', 'ch11Section_5_30', 'ch11Section_5_31', 'ch11Section_5_32', 'ch11Section_5_33', 'ch11Section_5_34', 'ch11Section_5_35', 'ch11Section_5_36', 'ch11Section_5_37', 'ch11Section_5_38', 'ch11Section_5_39', 'ch11Section_5_3a', 'ch11Section_5_3b', 'ch11Section_5_3c', 'ch11Section_5_3d', 'ch11Section_5_3e', 'ch11Section_5_3f', 'ch11Section_5_40', 'ch11Section_5_41', 'ch11Section_5_42', 'ch11Section_5_43', 'ch11Section_5_44', 'ch11Section_5_45', 'ch11Section_5_46', 'ch11Section_5_47', 'ch11Section_5_48', 'ch11Section_5_49', 'ch11Section_5_4a', 'ch11Section_5_4b', 'ch11Section_5_4c', 'ch11Section_5_4d', 'ch11Section_5_4e', 'ch11Section_5_4f', 'ch11Section_5_50', 'ch11Section_5_51', 'ch11Section_5_52', 'ch11Section_5_53', 'ch11Section_5_54', 'ch11Section_5_55', 'ch11Section_5_56', 'ch11Section_5_57', 'ch11Section_5_58', 'ch11Section_5_59', 'ch11Section_5_5a', 'ch11Section_5_5b', 'ch11Section_5_5c', 'ch11Section_5_5d', 'ch11Section_5_5e', 'ch11Section_5_5f', 'ch11Section_5_60', 'ch11Section_5_61', 'ch11Section_5_62', 'ch11Section_5_63', 'ch11Section_5_64', 'ch11Section_5_65', 'ch11Section_5_66', 'ch11Section_5_67', 'ch11Section_5_68', 'ch11Section_5_69', 'ch11Section_5_6a', 'ch11Section_5_6b', 'ch11Section_5_6c', 'ch11Section_5_6d', 'ch11Section_5_6e', 'ch11Section_5_6f', 'ch11Section_5_70', 'ch11Section_5_71', 'ch11Section_5_72', 'ch11Section_5_73', 'ch11Section_5_74', 'ch11Section_5_75', 'ch11Section_5_76', 'ch11Section_5_77', 'ch11Section_5_78', 'ch11Section_5_79', 'ch11Section_5_7a', 'ch11Section_5_7b', 'ch11Section_5_7c', 'ch11Section_5_7d', 'ch11Section_5_7e', 'ch11Section_5_7f', 'ch11Section_5_80', 'ch11Section_5_81', 'ch11Section_5_82', 'ch11Section_5_83', 'ch11Section_5_84', 'ch11Section_5_85', 'ch11Section_5_86', 'ch11Section_5_87', 'ch11Section_5_88', 'ch11Section_5_89', 'ch11Section_5_8a', 'ch11Section_5_8b', 'ch11Section_5_8c', 'ch11Section_5_8d', 'ch11Section_5_8e', 'ch11Section_5_8f', 'ch11Section_5_90', 'ch11Section_5_91', 'ch11Section_5_92', 'ch11Section_5_93', 'ch11Section_5_94', 'ch11Section_5_95', 'ch11Section_5_96', 'ch11Section_5_97', 'ch11Section_5_98', 'ch11Section_5_99', 'ch11Section_5_9a', 'ch11Section_5_9b', 'ch11Section_5_9c', 'ch11Section_5_9d', 'ch11Section_5_9e', 'ch11Section_5_9f', 'ch11Section_5_a0', 'ch11Section_5_a1', 'ch11Section_5_a2', 'ch11Section_5_a3', 'ch11Section_5_a4', 'ch11Section_5_a5', 'ch11Section_5_a6', 'ch11Section_5_a7', 'ch11Section_5_a8', 'ch11Section_5_a9', 'ch11Section_5_aa', 'ch11Section_5_ab', 'ch11Section_5_ac', 'ch11Section_5_ad', 'ch11Section_5_ae', 'ch11Section_5_af', 'ch11Section_5_b0', 'ch11Section_5_b1', 'ch11Section_5_b2', 'ch11Section_5_b3', 'ch11Section_5_b4', 'ch11Section_5_b5', 'ch11Section_5_b6', 'ch11Section_5_b7', 'ch11Section_5_b8', 'ch11Section_5_b9', 'ch11Section_5_ba', 'ch11Section_5_bb', 'ch11Section_5_bc', 'ch11Section_5_bd', 'ch11Section_5_be', 'ch11Section_5_bf', 'ch11Section_5_c0', 'ch11Section_5_c1', 'ch11Section_5_c2', 'ch11Section_5_c3', 'ch11Section_5_c4', 'ch11Section_5_c5', 'ch11Section_5_c6', 'ch11Section_5_c7', 'ch11Section_5_c8', 'ch11Section_5_c9', 'ch11Section_5_ca', 'ch11Section_5_cb', 'ch11Section_5_cc', 'ch11Section_5_cd', 'ch11Section_5_ce', 'ch11Section_5_cf', 'ch11Section_5_d0', 'ch11Section_5_d1', 'ch11Section_5_d2', 'ch11Section_5_d3', 'ch11Section_5_d4', 'ch11Section_5_d5', 'ch11Section_5_d6', 'ch11Section_5_d7', 'ch11Section_5_d8', 'ch11Section_5_d9', 'ch11Section_5_da', 'ch11Section_5_db', 'ch11Section_5_dc', 'ch11Section_5_dd', 'ch11Section_5_de', 'ch11Section_5_df', 'ch11Section_5_e0', 'ch11Section_5_e1', 'ch11Section_5_e2', 'ch11Section_5_e3', 'ch11Section_5_e4', 'ch11Section_5_e5', 'ch11Section_5_e6', 'ch11Section_5_e7', 'ch11Section_5_e8', 'ch11Section_5_e9', 'ch11Section_5_ea', 'ch11Section_5_eb', 'ch11Section_5_ec', 'ch11Section_5_ed', 'ch11Section_5_ee', 'ch11Section_5_ef', 'ch11Section_5_f0', 'ch11Section_5_f1', 'ch11Section_5_f2', 'ch11Section_5_f3', 'ch11Section_5_f4', 'ch11Section_5_f5', 'ch11Section_5_f6', 'ch11Section_5_f7', 'ch11Section_5_f8', 'ch11Section_5_f9', 'ch11Section_5_fa', 'ch11Section_5_fb', 'ch11Section_5_fc', 'ch11Section_5_fd', 'ch11Section_5_fe', 'ch11Section_5_ff', 'ch11Section_5_100', 'ch11Section_5_101', 'ch11Section_5_102', 'ch11Section_5_103', 'ch11Section_5_104', 'ch11Section_5_105', 'ch11Section_5_106', 'ch11Section_5_107', 'ch11Section_5_108', 'ch11Section_5_109', 'ch11Section_5_10a', 'ch11Section_5_10b', 'ch11Section_5_10c', 'ch11Section_5_10d', 'ch11Section_5_10e', 'ch11Section_5_10f', 'ch11Section_5_110', 'ch11Section_5_111', 'ch11Section_5_112', 'ch11Section_5_113', 'ch11Section_5_114', 'ch11Section_5_115', 'ch11Section_5_116', 'ch11Section_5_117', 'ch11Section_5_118', 'ch11Section_5_119', 'ch11Section_5_11a', 'ch11Section_5_11b', 'ch11Section_5_11c', 'ch11Section_5_11d', 'ch11Section_5_11e', 'ch11Section_5_11f', 'ch11Section_5_120', 'ch11Section_5_121', 'ch11Section_5_122', 'ch11Section_5_123', 'ch11Section_5_124', 'ch11Section_5_125', 'ch11Section_5_126', 'ch11Section_5_127', 'ch11Section_5_128', 'ch11Section_5_129', 'ch11Section_5_12a', 'ch11Section_5_12b', 'ch11Section_5_12c', 'ch11Section_5_12d', 'ch11Section_5_12e', 'ch11Section_5_12f', 'ch11Section_5_130', 'ch11Section_5_131', 'ch11Section_5_132', 'ch11Section_5_133', 'ch11Section_5_134', 'ch11Section_5_135', 'ch11Section_5_136', 'ch11Section_5_137', 'ch11Section_5_138', 'ch11Section_5_139', 'ch11Section_5_13a', 'ch11Section_5_13b', 'ch11Section_5_13c', 'ch11Section_5_13d', 'ch11Section_5_13e', 'ch11Section_5_13f', 'ch11Section_5_140', 'ch11Section_5_141', 'ch11Section_5_142', 'ch11Section_5_143', 'ch11Section_5_144', 'ch11Section_5_145', 'ch11Section_5_146', 'ch11Section_5_147', 'ch11Section_5_148', 'ch11Section_5_149', 'ch11Section_5_14a', 'ch11Section_5_14b', 'ch11Section_5_14c', 'ch11Section_5_14d', 'ch11Section_5_14e', 'ch11Section_5_14f', 'ch11Section_5_150', 'ch11Section_5_151', 'ch11Section_5_152', 'ch11Section_5_153', 'ch11Section_5_154', 'ch11Section_5_155', 'ch11Section_5_156', 'ch11Section_5_157', 'ch11Section_5_158', 'ch11Section_5_159', 'ch11Section_5_15a', 'ch11Section_5_15b', 'ch11Section_5_15c', 'ch11Section_5_15d', 'ch11Section_5_15e', 'ch11Section_5_15f', 'ch11Section_5_160', 'ch11Section_5_161', 'ch11Section_5_162', 'ch11Section_5_163', 'ch11Section_5_164', 'ch11Section_5_165', 'ch11Section_5_166', 'ch11Section_5_167', 'ch11Section_5_168', 'ch11Section_5_169', 'ch11Section_5_16a', 'ch11Section_5_16b', 'ch11Section_5_16c', 'ch11Section_5_16d', 'ch11Section_5_16e', 'ch11Section_5_16f', 'ch11Section_5_170', 'ch11Section_5_171', 'ch11Section_5_172', 'ch11Section_5_173', 'ch11Section_5_174', 'ch11Section_5_175', 'ch11Section_5_176', 'ch11Section_5_177', 'ch11Section_5_178', 'ch11Section_5_179', 'ch11Section_5_17a', 'ch11Section_5_17b', 'ch11Section_5_17c', 'ch11Section_5_17d', 'ch11Section_5_17e', 'ch11Section_5_17f', 'ch11Section_5_180', 'ch11Section_5_181', 'ch11Section_5_182', 'ch11Section_5_183', 'ch11Section_5_184', 'ch11Section_5_185', 'ch11Section_5_186', 'ch11Section_5_187', 'ch11Section_5_188', 'ch11Section_5_189', 'ch11Section_5_18a', 'ch11Section_5_18b', 'ch11Section_5_18c', 'ch11Section_5_18d', 'ch11Section_5_18e', 'ch11Section_5_18f', 'ch11Section_5_190', 'ch11Section_5_191', 'ch11Section_5_192', 'ch11Section_5_193', 'ch11Section_5_194', 'ch11Section_5_195', 'ch11Section_5_196', 'ch11Section_5_197', 'ch11Section_5_198', 'ch11Section_5_199', 'ch11Section_5_19a', 'ch11Section_5_19b', 'ch11Section_5_19c', 'ch11Section_5_19d', 'ch11Section_5_19e', 'ch11Section_5_19f', 'ch11Section_5_1a0', 'ch11Section_5_1a1', 'ch11Section_5_1a2', 'ch11Section_5_1a3', 'ch11Section_5_1a4', 'ch11Section_5_1a5', 'ch11Section_5_1a6', 'ch11Section_5_1a7', 'ch11Section_5_1a8', 'ch11Section_5_1a9', 'ch11Section_5_1aa', 'ch11Section_5_1ab', 'ch11Section_5_1ac', 'ch11Section_5_1ad', 'ch11Section_5_1ae', 'ch11Section_5_1af', 'ch11Section_5_1b0', 'ch11Section_5_1b1', 'ch11Section_5_1b2', 'ch11Section_5_1b3', 'ch11Section_5_1b4', 'ch11Section_5_1b5', 'ch11Section_5_1b6', 'ch11Section_5_1b7', 'ch11Section_5_1b8', 'ch11Section_5_1b9', 'ch11Section_5_1ba', 'ch11Section_5_1bb', 'ch11Section_5_1bc', 'ch11Section_5_1bd', 'ch11Section_5_1be', 'ch11Section_5_1bf', 'ch11Section_5_1c0', 'ch11Section_5_1c1', 'ch11Section_5_1c2', 'ch11Section_5_1c3', 'ch11Section_5_1c4', 'ch11Section_5_1c5', 'ch11Section_5_1c6', 'ch11Section_5_1c7', 'ch11Section_5_1c8', 'ch11Section_5_1c9', 'ch11Section_5_1ca', 'ch11Section_5_1cb', 'ch11Section_5_1cc', 'ch11Section_5_1cd', 'ch11Section_5_1ce', 'ch11Section_5_1cf', 'ch11Section_5_1d0', 'ch11Section_5_1d1', 'ch11Section_5_1d2', 'ch11Section_5_1d3', 'ch11Section_5_1d4', 'ch11Section_5_1d5', 'ch11Section_5_1d6', 'ch11Section_5_1d7', 'ch11Section_5_1d8', 'ch11Section_5_1d9', 'ch11Section_5_1da', 'ch11Section_5_1db', 'ch11Section_5_1dc', 'ch11Section_5_1dd', 'ch11Section_5_1de', 'ch11Section_5_1df', 'ch11Section_5_1e0', 'ch11Section_5_1e1'], 'ch7interim_assessment': ['ch7interim_assessment_1', 'ch7interim_assessment_2', 'ch7interim_assessment_3', 'ch7interim_assessment_4', 'ch7interim_assessment_5', 'ch7interim_assessment_6', 'ch7interim_assessment_7', 'ch7interim_assessment_8', 'ch7interim_assessment_9', 'ch7interim_assessment_a', 'ch7interim_assessment_b', 'ch7interim_assessment_c', 'ch7interim_assessment_d', 'ch7interim_assessment_e', 'ch7interim_assessment_f', 'ch7interim_assessment_10', 'ch7interim_assessment_11', 'ch7interim_assessment_12', 'ch7interim_assessment_13', 'ch7interim_assessment_14', 'ch7interim_assessment_15', 'ch7interim_assessment_16', 'ch7interim_assessment_17', 'ch7interim_assessment_18', 'ch7interim_assessment_19', 'ch7interim_assessment_1a', 'ch7interim_assessment_1b', 'ch7interim_assessment_1c', 'ch7interim_assessment_1d', 'ch7interim_assessment_1e', 'ch7interim_assessment_1f', 'ch7interim_assessment_20', 'ch7interim_assessment_21', 'ch7interim_assessment_22', 'ch7interim_assessment_23', 'ch7interim_assessment_24', 'ch7interim_assessment_25', 'ch7interim_assessment_26', 'ch7interim_assessment_27', 'ch7interim_assessment_28', 'ch7interim_assessment_29', 'ch7interim_assessment_2a', 'ch7interim_assessment_2b', 'ch7interim_assessment_2c', 'ch7interim_assessment_2d', 'ch7interim_assessment_2e', 'ch7interim_assessment_2f', 'ch7interim_assessment_30', 'ch7interim_assessment_31', 'ch7interim_assessment_32', 'ch7interim_assessment_33', 'ch7interim_assessment_34', 'ch7interim_assessment_35', 'ch7interim_assessment_36', 'ch7interim_assessment_37', 'ch7interim_assessment_38', 'ch7interim_assessment_39', 'ch7interim_assessment_3a', 'ch7interim_assessment_3b', 'ch7interim_assessment_3c', 'ch7interim_assessment_3d', 'ch7interim_assessment_3e', 'ch7interim_assessment_3f', 'ch7interim_assessment_40', 'ch7interim_assessment_41', 'ch7interim_assessment_42', 'ch7interim_assessment_43', 'ch7interim_assessment_44', 'ch7interim_assessment_45', 'ch7interim_assessment_46', 'ch7interim_assessment_47', 'ch7interim_assessment_48', 'ch7interim_assessment_49', 'ch7interim_assessment_4a', 'ch7interim_assessment_4b', 'ch7interim_assessment_4c', 'ch7interim_assessment_4d', 'ch7interim_assessment_4e', 'ch7interim_assessment_4f', 'ch7interim_assessment_50', 'ch7interim_assessment_51', 'ch7interim_assessment_52', 'ch7interim_assessment_53', 'ch7interim_assessment_54', 'ch7interim_assessment_55', 'ch7interim_assessment_56', 'ch7interim_assessment_57', 'ch7interim_assessment_58', 'ch7interim_assessment_59', 'ch7interim_assessment_5a', 'ch7interim_assessment_5b', 'ch7interim_assessment_5c', 'ch7interim_assessment_5d', 'ch7interim_assessment_5e', 'ch7interim_assessment_5f', 'ch7interim_assessment_60', 'ch7interim_assessment_61', 'ch7interim_assessment_62', 'ch7interim_assessment_63', 'ch7interim_assessment_64', 'ch7interim_assessment_65', 'ch7interim_assessment_66', 'ch7interim_assessment_67', 'ch7interim_assessment_68', 'ch7interim_assessment_69', 'ch7interim_assessment_6a', 'ch7interim_assessment_6b', 'ch7interim_assessment_6c', 'ch7interim_assessment_6d', 'ch7interim_assessment_6e', 'ch7interim_assessment_6f', 'ch7interim_assessment_70', 'ch7interim_assessment_71', 'ch7interim_assessment_72', 'ch7interim_assessment_73', 'ch7interim_assessment_74', 'ch7interim_assessment_75', 'ch7interim_assessment_76', 'ch7interim_assessment_77', 'ch7interim_assessment_78', 'ch7interim_assessment_79', 'ch7interim_assessment_7a', 'ch7interim_assessment_7b', 'ch7interim_assessment_7c', 'ch7interim_assessment_7d', 'ch7interim_assessment_7e', 'ch7interim_assessment_7f', 'ch7interim_assessment_80', 'ch7interim_assessment_81', 'ch7interim_assessment_82', 'ch7interim_assessment_83', 'ch7interim_assessment_84', 'ch7interim_assessment_85', 'ch7interim_assessment_86', 'ch7interim_assessment_87', 'ch7interim_assessment_88', 'ch7interim_assessment_89', 'ch7interim_assessment_8a', 'ch7interim_assessment_8b', 'ch7interim_assessment_8c', 'ch7interim_assessment_8d', 'ch7interim_assessment_8e', 'ch7interim_assessment_8f', 'ch7interim_assessment_90', 'ch7interim_assessment_91', 'ch7interim_assessment_92', 'ch7interim_assessment_93', 'ch7interim_assessment_94', 'ch7interim_assessment_95', 'ch7interim_assessment_96', 'ch7interim_assessment_97', 'ch7interim_assessment_98', 'ch7interim_assessment_99', 'ch7interim_assessment_9a', 'ch7interim_assessment_9b', 'ch7interim_assessment_9c', 'ch7interim_assessment_9d', 'ch7interim_assessment_9e', 'ch7interim_assessment_9f', 'ch7interim_assessment_a0', 'ch7interim_assessment_a1', 'ch7interim_assessment_a2', 'ch7interim_assessment_a3', 'ch7interim_assessment_a4', 'ch7interim_assessment_a5', 'ch7interim_assessment_a6', 'ch7interim_assessment_a7', 'ch7interim_assessment_a8', 'ch7interim_assessment_a9', 'ch7interim_assessment_aa', 'ch7interim_assessment_ab', 'ch7interim_assessment_ac', 'ch7interim_assessment_ad', 'ch7interim_assessment_ae', 'ch7interim_assessment_af', 'ch7interim_assessment_b0', 'ch7interim_assessment_b1', 'ch7interim_assessment_b2', 'ch7interim_assessment_b3', 'ch7interim_assessment_b4', 'ch7interim_assessment_b5', 'ch7interim_assessment_b6', 'ch7interim_assessment_b7', 'ch7interim_assessment_b8', 'ch7interim_assessment_b9', 'ch7interim_assessment_ba', 'ch7interim_assessment_bb', 'ch7interim_assessment_bc', 'ch7interim_assessment_bd', 'ch7interim_assessment_be', 'ch7interim_assessment_bf', 'ch7interim_assessment_c0', 'ch7interim_assessment_c1', 'ch7interim_assessment_c2', 'ch7interim_assessment_c3', 'ch7interim_assessment_c4', 'ch7interim_assessment_c5', 'ch7interim_assessment_c6', 'ch7interim_assessment_c7', 'ch7interim_assessment_c8', 'ch7interim_assessment_c9', 'ch7interim_assessment_ca', 'ch7interim_assessment_cb', 'ch7interim_assessment_cc', 'ch7interim_assessment_cd', 'ch7interim_assessment_ce', 'ch7interim_assessment_cf', 'ch7interim_assessment_d0', 'ch7interim_assessment_d1', 'ch7interim_assessment_d2', 'ch7interim_assessment_d3', 'ch7interim_assessment_d4', 'ch7interim_assessment_d5', 'ch7interim_assessment_d6', 'ch7interim_assessment_d7', 'ch7interim_assessment_d8', 'ch7interim_assessment_d9', 'ch7interim_assessment_da', 'ch7interim_assessment_db', 'ch7interim_assessment_dc', 'ch7interim_assessment_dd', 'ch7interim_assessment_de', 'ch7interim_assessment_df', 'ch7interim_assessment_e0', 'ch7interim_assessment_e1', 'ch7interim_assessment_e2', 'ch7interim_assessment_e3', 'ch7interim_assessment_e4', 'ch7interim_assessment_e5', 'ch7interim_assessment_e6', 'ch7interim_assessment_e7', 'ch7interim_assessment_e8', 'ch7interim_assessment_e9', 'ch7interim_assessment_ea', 'ch7interim_assessment_eb', 'ch7interim_assessment_ec', 'ch7interim_assessment_ed', 'ch7interim_assessment_ee', 'ch7interim_assessment_ef', 'ch7interim_assessment_f0', 'ch7interim_assessment_f1', 'ch7interim_assessment_f2', 'ch7interim_assessment_f3', 'ch7interim_assessment_f4', 'ch7interim_assessment_f5', 'ch7interim_assessment_f6', 'ch7interim_assessment_f7', 'ch7interim_assessment_f8', 'ch7interim_assessment_f9', 'ch7interim_assessment_fa', 'ch7interim_assessment_fb', 'ch7interim_assessment_fc', 'ch7interim_assessment_fd', 'ch7interim_assessment_fe', 'ch7interim_assessment_ff', 'ch7interim_assessment_100', 'ch7interim_assessment_101', 'ch7interim_assessment_102', 'ch7interim_assessment_103', 'ch7interim_assessment_104', 'ch7interim_assessment_105', 'ch7interim_assessment_106', 'ch7interim_assessment_107', 'ch7interim_assessment_108', 'ch7interim_assessment_109', 'ch7interim_assessment_10a', 'ch7interim_assessment_10b', 'ch7interim_assessment_10c', 'ch7interim_assessment_10d', 'ch7interim_assessment_10e', 'ch7interim_assessment_10f', 'ch7interim_assessment_110', 'ch7interim_assessment_111', 'ch7interim_assessment_112', 'ch7interim_assessment_113', 'ch7interim_assessment_114', 'ch7interim_assessment_115', 'ch7interim_assessment_116', 'ch7interim_assessment_117', 'ch7interim_assessment_118', 'ch7interim_assessment_119', 'ch7interim_assessment_11a', 'ch7interim_assessment_11b', 'ch7interim_assessment_11c', 'ch7interim_assessment_11d', 'ch7interim_assessment_11e', 'ch7interim_assessment_11f', 'ch7interim_assessment_120', 'ch7interim_assessment_121', 'ch7interim_assessment_122', 'ch7interim_assessment_123', 'ch7interim_assessment_124', 'ch7interim_assessment_125', 'ch7interim_assessment_126', 'ch7interim_assessment_127', 'ch7interim_assessment_128', 'ch7interim_assessment_129', 'ch7interim_assessment_12a', 'ch7interim_assessment_12b', 'ch7interim_assessment_12c', 'ch7interim_assessment_12d', 'ch7interim_assessment_12e', 'ch7interim_assessment_12f', 'ch7interim_assessment_130', 'ch7interim_assessment_131', 'ch7interim_assessment_132', 'ch7interim_assessment_133', 'ch7interim_assessment_134', 'ch7interim_assessment_135', 'ch7interim_assessment_136', 'ch7interim_assessment_137', 'ch7interim_assessment_138', 'ch7interim_assessment_139', 'ch7interim_assessment_13a', 'ch7interim_assessment_13b', 'ch7interim_assessment_13c', 'ch7interim_assessment_13d', 'ch7interim_assessment_13e', 'ch7interim_assessment_13f', 'ch7interim_assessment_140', 'ch7interim_assessment_141', 'ch7interim_assessment_142', 'ch7interim_assessment_143', 'ch7interim_assessment_144', 'ch7interim_assessment_145', 'ch7interim_assessment_146', 'ch7interim_assessment_147', 'ch7interim_assessment_148', 'ch7interim_assessment_149', 'ch7interim_assessment_14a', 'ch7interim_assessment_14b', 'ch7interim_assessment_14c', 'ch7interim_assessment_14d', 'ch7interim_assessment_14e', 'ch7interim_assessment_14f', 'ch7interim_assessment_150', 'ch7interim_assessment_151', 'ch7interim_assessment_152', 'ch7interim_assessment_153', 'ch7interim_assessment_154', 'ch7interim_assessment_155', 'ch7interim_assessment_156', 'ch7interim_assessment_157', 'ch7interim_assessment_158', 'ch7interim_assessment_159', 'ch7interim_assessment_15a', 'ch7interim_assessment_15b', 'ch7interim_assessment_15c', 'ch7interim_assessment_15d', 'ch7interim_assessment_15e', 'ch7interim_assessment_15f', 'ch7interim_assessment_160', 'ch7interim_assessment_161', 'ch7interim_assessment_162', 'ch7interim_assessment_163', 'ch7interim_assessment_164', 'ch7interim_assessment_165', 'ch7interim_assessment_166', 'ch7interim_assessment_167', 'ch7interim_assessment_168', 'ch7interim_assessment_169', 'ch7interim_assessment_16a', 'ch7interim_assessment_16b', 'ch7interim_assessment_16c', 'ch7interim_assessment_16d', 'ch7interim_assessment_16e', 'ch7interim_assessment_16f', 'ch7interim_assessment_170', 'ch7interim_assessment_171', 'ch7interim_assessment_172', 'ch7interim_assessment_173', 'ch7interim_assessment_174', 'ch7interim_assessment_175', 'ch7interim_assessment_176', 'ch7interim_assessment_177', 'ch7interim_assessment_178', 'ch7interim_assessment_179', 'ch7interim_assessment_17a', 'ch7interim_assessment_17b', 'ch7interim_assessment_17c', 'ch7interim_assessment_17d', 'ch7interim_assessment_17e', 'ch7interim_assessment_17f', 'ch7interim_assessment_180', 'ch7interim_assessment_181', 'ch7interim_assessment_182', 'ch7interim_assessment_183', 'ch7interim_assessment_184', 'ch7interim_assessment_185', 'ch7interim_assessment_186', 'ch7interim_assessment_187', 'ch7interim_assessment_188', 'ch7interim_assessment_189', 'ch7interim_assessment_18a', 'ch7interim_assessment_18b', 'ch7interim_assessment_18c', 'ch7interim_assessment_18d', 'ch7interim_assessment_18e', 'ch7interim_assessment_18f', 'ch7interim_assessment_190', 'ch7interim_assessment_191', 'ch7interim_assessment_192', 'ch7interim_assessment_193', 'ch7interim_assessment_194', 'ch7interim_assessment_195', 'ch7interim_assessment_196', 'ch7interim_assessment_197', 'ch7interim_assessment_198', 'ch7interim_assessment_199', 'ch7interim_assessment_19a', 'ch7interim_assessment_19b', 'ch7interim_assessment_19c', 'ch7interim_assessment_19d', 'ch7interim_assessment_19e', 'ch7interim_assessment_19f', 'ch7interim_assessment_1a0', 'ch7interim_assessment_1a1', 'ch7interim_assessment_1a2', 'ch7interim_assessment_1a3', 'ch7interim_assessment_1a4', 'ch7interim_assessment_1a5', 'ch7interim_assessment_1a6', 'ch7interim_assessment_1a7', 'ch7interim_assessment_1a8', 'ch7interim_assessment_1a9', 'ch7interim_assessment_1aa', 'ch7interim_assessment_1ab', 'ch7interim_assessment_1ac', 'ch7interim_assessment_1ad', 'ch7interim_assessment_1ae', 'ch7interim_assessment_1af', 'ch7interim_assessment_1b0', 'ch7interim_assessment_1b1', 'ch7interim_assessment_1b2', 'ch7interim_assessment_1b3', 'ch7interim_assessment_1b4', 'ch7interim_assessment_1b5', 'ch7interim_assessment_1b6', 'ch7interim_assessment_1b7', 'ch7interim_assessment_1b8', 'ch7interim_assessment_1b9', 'ch7interim_assessment_1ba', 'ch7interim_assessment_1bb', 'ch7interim_assessment_1bc', 'ch7interim_assessment_1bd', 'ch7interim_assessment_1be', 'ch7interim_assessment_1bf', 'ch7interim_assessment_1c0', 'ch7interim_assessment_1c1', 'ch7interim_assessment_1c2', 'ch7interim_assessment_1c3', 'ch7interim_assessment_1c4', 'ch7interim_assessment_1c5', 'ch7interim_assessment_1c6', 'ch7interim_assessment_1c7', 'ch7interim_assessment_1c8', 'ch7interim_assessment_1c9', 'ch7interim_assessment_1ca', 'ch7interim_assessment_1cb', 'ch7interim_assessment_1cc', 'ch7interim_assessment_1cd', 'ch7interim_assessment_1ce', 'ch7interim_assessment_1cf', 'ch7interim_assessment_1d0', 'ch7interim_assessment_1d1', 'ch7interim_assessment_1d2', 'ch7interim_assessment_1d3', 'ch7interim_assessment_1d4', 'ch7interim_assessment_1d5', 'ch7interim_assessment_1d6', 'ch7interim_assessment_1d7', 'ch7interim_assessment_1d8', 'ch7interim_assessment_1d9', 'ch7interim_assessment_1da', 'ch7interim_assessment_1db', 'ch7interim_assessment_1dc', 'ch7interim_assessment_1dd', 'ch7interim_assessment_1de', 'ch7interim_assessment_1df', 'ch7interim_assessment_1e0', 'ch7interim_assessment_1e1'], 'ch8ult_module_plan': ['ch8ult_module_plan_1', 'ch8ult_module_plan_2', 'ch8ult_module_plan_3', 'ch8ult_module_plan_4', 'ch8ult_module_plan_5', 'ch8ult_module_plan_6', 'ch8ult_module_plan_7', 'ch8ult_module_plan_8', 'ch8ult_module_plan_9', 'ch8ult_module_plan_a', 'ch8ult_module_plan_b', 'ch8ult_module_plan_c', 'ch8ult_module_plan_d', 'ch8ult_module_plan_e', 'ch8ult_module_plan_f', 'ch8ult_module_plan_10', 'ch8ult_module_plan_11', 'ch8ult_module_plan_12', 'ch8ult_module_plan_13', 'ch8ult_module_plan_14', 'ch8ult_module_plan_15', 'ch8ult_module_plan_16', 'ch8ult_module_plan_17', 'ch8ult_module_plan_18', 'ch8ult_module_plan_19', 'ch8ult_module_plan_1a', 'ch8ult_module_plan_1b', 'ch8ult_module_plan_1c', 'ch8ult_module_plan_1d', 'ch8ult_module_plan_1e', 'ch8ult_module_plan_1f', 'ch8ult_module_plan_20', 'ch8ult_module_plan_21', 'ch8ult_module_plan_22', 'ch8ult_module_plan_23', 'ch8ult_module_plan_24', 'ch8ult_module_plan_25', 'ch8ult_module_plan_26', 'ch8ult_module_plan_27', 'ch8ult_module_plan_28', 'ch8ult_module_plan_29', 'ch8ult_module_plan_2a', 'ch8ult_module_plan_2b', 'ch8ult_module_plan_2c', 'ch8ult_module_plan_2d', 'ch8ult_module_plan_2e', 'ch8ult_module_plan_2f', 'ch8ult_module_plan_30', 'ch8ult_module_plan_31', 'ch8ult_module_plan_32', 'ch8ult_module_plan_33', 'ch8ult_module_plan_34', 'ch8ult_module_plan_35', 'ch8ult_module_plan_36', 'ch8ult_module_plan_37', 'ch8ult_module_plan_38', 'ch8ult_module_plan_39', 'ch8ult_module_plan_3a', 'ch8ult_module_plan_3b', 'ch8ult_module_plan_3c', 'ch8ult_module_plan_3d', 'ch8ult_module_plan_3e', 'ch8ult_module_plan_3f', 'ch8ult_module_plan_40', 'ch8ult_module_plan_41', 'ch8ult_module_plan_42', 'ch8ult_module_plan_43', 'ch8ult_module_plan_44', 'ch8ult_module_plan_45', 'ch8ult_module_plan_46', 'ch8ult_module_plan_47', 'ch8ult_module_plan_48', 'ch8ult_module_plan_49', 'ch8ult_module_plan_4a', 'ch8ult_module_plan_4b', 'ch8ult_module_plan_4c', 'ch8ult_module_plan_4d', 'ch8ult_module_plan_4e', 'ch8ult_module_plan_4f', 'ch8ult_module_plan_50', 'ch8ult_module_plan_51', 'ch8ult_module_plan_52', 'ch8ult_module_plan_53', 'ch8ult_module_plan_54', 'ch8ult_module_plan_55', 'ch8ult_module_plan_56', 'ch8ult_module_plan_57', 'ch8ult_module_plan_58', 'ch8ult_module_plan_59', 'ch8ult_module_plan_5a', 'ch8ult_module_plan_5b', 'ch8ult_module_plan_5c', 'ch8ult_module_plan_5d', 'ch8ult_module_plan_5e', 'ch8ult_module_plan_5f', 'ch8ult_module_plan_60', 'ch8ult_module_plan_61', 'ch8ult_module_plan_62', 'ch8ult_module_plan_63', 'ch8ult_module_plan_64', 'ch8ult_module_plan_65', 'ch8ult_module_plan_66', 'ch8ult_module_plan_67', 'ch8ult_module_plan_68', 'ch8ult_module_plan_69', 'ch8ult_module_plan_6a', 'ch8ult_module_plan_6b', 'ch8ult_module_plan_6c', 'ch8ult_module_plan_6d', 'ch8ult_module_plan_6e', 'ch8ult_module_plan_6f', 'ch8ult_module_plan_70', 'ch8ult_module_plan_71', 'ch8ult_module_plan_72', 'ch8ult_module_plan_73', 'ch8ult_module_plan_74', 'ch8ult_module_plan_75', 'ch8ult_module_plan_76', 'ch8ult_module_plan_77', 'ch8ult_module_plan_78', 'ch8ult_module_plan_79', 'ch8ult_module_plan_7a', 'ch8ult_module_plan_7b', 'ch8ult_module_plan_7c', 'ch8ult_module_plan_7d', 'ch8ult_module_plan_7e', 'ch8ult_module_plan_7f', 'ch8ult_module_plan_80', 'ch8ult_module_plan_81', 'ch8ult_module_plan_82', 'ch8ult_module_plan_83', 'ch8ult_module_plan_84', 'ch8ult_module_plan_85', 'ch8ult_module_plan_86', 'ch8ult_module_plan_87', 'ch8ult_module_plan_88', 'ch8ult_module_plan_89', 'ch8ult_module_plan_8a', 'ch8ult_module_plan_8b', 'ch8ult_module_plan_8c', 'ch8ult_module_plan_8d', 'ch8ult_module_plan_8e', 'ch8ult_module_plan_8f', 'ch8ult_module_plan_90', 'ch8ult_module_plan_91', 'ch8ult_module_plan_92', 'ch8ult_module_plan_93', 'ch8ult_module_plan_94', 'ch8ult_module_plan_95', 'ch8ult_module_plan_96', 'ch8ult_module_plan_97', 'ch8ult_module_plan_98', 'ch8ult_module_plan_99', 'ch8ult_module_plan_9a', 'ch8ult_module_plan_9b', 'ch8ult_module_plan_9c', 'ch8ult_module_plan_9d', 'ch8ult_module_plan_9e', 'ch8ult_module_plan_9f', 'ch8ult_module_plan_a0', 'ch8ult_module_plan_a1', 'ch8ult_module_plan_a2', 'ch8ult_module_plan_a3', 'ch8ult_module_plan_a4', 'ch8ult_module_plan_a5', 'ch8ult_module_plan_a6', 'ch8ult_module_plan_a7', 'ch8ult_module_plan_a8', 'ch8ult_module_plan_a9', 'ch8ult_module_plan_aa', 'ch8ult_module_plan_ab', 'ch8ult_module_plan_ac', 'ch8ult_module_plan_ad', 'ch8ult_module_plan_ae', 'ch8ult_module_plan_af', 'ch8ult_module_plan_b0', 'ch8ult_module_plan_b1', 'ch8ult_module_plan_b2', 'ch8ult_module_plan_b3', 'ch8ult_module_plan_b4', 'ch8ult_module_plan_b5', 'ch8ult_module_plan_b6', 'ch8ult_module_plan_b7', 'ch8ult_module_plan_b8', 'ch8ult_module_plan_b9', 'ch8ult_module_plan_ba', 'ch8ult_module_plan_bb', 'ch8ult_module_plan_bc', 'ch8ult_module_plan_bd', 'ch8ult_module_plan_be', 'ch8ult_module_plan_bf', 'ch8ult_module_plan_c0', 'ch8ult_module_plan_c1', 'ch8ult_module_plan_c2', 'ch8ult_module_plan_c3', 'ch8ult_module_plan_c4', 'ch8ult_module_plan_c5', 'ch8ult_module_plan_c6', 'ch8ult_module_plan_c7', 'ch8ult_module_plan_c8', 'ch8ult_module_plan_c9', 'ch8ult_module_plan_ca', 'ch8ult_module_plan_cb', 'ch8ult_module_plan_cc', 'ch8ult_module_plan_cd', 'ch8ult_module_plan_ce', 'ch8ult_module_plan_cf', 'ch8ult_module_plan_d0', 'ch8ult_module_plan_d1', 'ch8ult_module_plan_d2', 'ch8ult_module_plan_d3', 'ch8ult_module_plan_d4', 'ch8ult_module_plan_d5', 'ch8ult_module_plan_d6', 'ch8ult_module_plan_d7', 'ch8ult_module_plan_d8', 'ch8ult_module_plan_d9', 'ch8ult_module_plan_da', 'ch8ult_module_plan_db', 'ch8ult_module_plan_dc', 'ch8ult_module_plan_dd', 'ch8ult_module_plan_de', 'ch8ult_module_plan_df', 'ch8ult_module_plan_e0', 'ch8ult_module_plan_e1', 'ch8ult_module_plan_e2', 'ch8ult_module_plan_e3', 'ch8ult_module_plan_e4', 'ch8ult_module_plan_e5', 'ch8ult_module_plan_e6', 'ch8ult_module_plan_e7', 'ch8ult_module_plan_e8', 'ch8ult_module_plan_e9', 'ch8ult_module_plan_ea', 'ch8ult_module_plan_eb', 'ch8ult_module_plan_ec', 'ch8ult_module_plan_ed', 'ch8ult_module_plan_ee', 'ch8ult_module_plan_ef', 'ch8ult_module_plan_f0', 'ch8ult_module_plan_f1', 'ch8ult_module_plan_f2', 'ch8ult_module_plan_f3', 'ch8ult_module_plan_f4', 'ch8ult_module_plan_f5', 'ch8ult_module_plan_f6', 'ch8ult_module_plan_f7', 'ch8ult_module_plan_f8', 'ch8ult_module_plan_f9', 'ch8ult_module_plan_fa', 'ch8ult_module_plan_fb', 'ch8ult_module_plan_fc', 'ch8ult_module_plan_fd', 'ch8ult_module_plan_fe', 'ch8ult_module_plan_ff', 'ch8ult_module_plan_100', 'ch8ult_module_plan_101', 'ch8ult_module_plan_102', 'ch8ult_module_plan_103', 'ch8ult_module_plan_104', 'ch8ult_module_plan_105', 'ch8ult_module_plan_106', 'ch8ult_module_plan_107', 'ch8ult_module_plan_108', 'ch8ult_module_plan_109', 'ch8ult_module_plan_10a', 'ch8ult_module_plan_10b', 'ch8ult_module_plan_10c', 'ch8ult_module_plan_10d', 'ch8ult_module_plan_10e', 'ch8ult_module_plan_10f', 'ch8ult_module_plan_110', 'ch8ult_module_plan_111', 'ch8ult_module_plan_112', 'ch8ult_module_plan_113', 'ch8ult_module_plan_114', 'ch8ult_module_plan_115', 'ch8ult_module_plan_116', 'ch8ult_module_plan_117', 'ch8ult_module_plan_118', 'ch8ult_module_plan_119', 'ch8ult_module_plan_11a', 'ch8ult_module_plan_11b', 'ch8ult_module_plan_11c', 'ch8ult_module_plan_11d', 'ch8ult_module_plan_11e', 'ch8ult_module_plan_11f', 'ch8ult_module_plan_120', 'ch8ult_module_plan_121', 'ch8ult_module_plan_122', 'ch8ult_module_plan_123', 'ch8ult_module_plan_124', 'ch8ult_module_plan_125', 'ch8ult_module_plan_126', 'ch8ult_module_plan_127', 'ch8ult_module_plan_128', 'ch8ult_module_plan_129', 'ch8ult_module_plan_12a', 'ch8ult_module_plan_12b', 'ch8ult_module_plan_12c', 'ch8ult_module_plan_12d', 'ch8ult_module_plan_12e', 'ch8ult_module_plan_12f', 'ch8ult_module_plan_130', 'ch8ult_module_plan_131', 'ch8ult_module_plan_132', 'ch8ult_module_plan_133', 'ch8ult_module_plan_134', 'ch8ult_module_plan_135', 'ch8ult_module_plan_136', 'ch8ult_module_plan_137', 'ch8ult_module_plan_138', 'ch8ult_module_plan_139', 'ch8ult_module_plan_13a', 'ch8ult_module_plan_13b', 'ch8ult_module_plan_13c', 'ch8ult_module_plan_13d', 'ch8ult_module_plan_13e', 'ch8ult_module_plan_13f', 'ch8ult_module_plan_140', 'ch8ult_module_plan_141', 'ch8ult_module_plan_142', 'ch8ult_module_plan_143', 'ch8ult_module_plan_144', 'ch8ult_module_plan_145', 'ch8ult_module_plan_146', 'ch8ult_module_plan_147', 'ch8ult_module_plan_148', 'ch8ult_module_plan_149', 'ch8ult_module_plan_14a', 'ch8ult_module_plan_14b', 'ch8ult_module_plan_14c', 'ch8ult_module_plan_14d', 'ch8ult_module_plan_14e', 'ch8ult_module_plan_14f', 'ch8ult_module_plan_150', 'ch8ult_module_plan_151', 'ch8ult_module_plan_152', 'ch8ult_module_plan_153', 'ch8ult_module_plan_154', 'ch8ult_module_plan_155', 'ch8ult_module_plan_156', 'ch8ult_module_plan_157', 'ch8ult_module_plan_158', 'ch8ult_module_plan_159', 'ch8ult_module_plan_15a', 'ch8ult_module_plan_15b', 'ch8ult_module_plan_15c', 'ch8ult_module_plan_15d', 'ch8ult_module_plan_15e', 'ch8ult_module_plan_15f', 'ch8ult_module_plan_160', 'ch8ult_module_plan_161', 'ch8ult_module_plan_162', 'ch8ult_module_plan_163', 'ch8ult_module_plan_164', 'ch8ult_module_plan_165', 'ch8ult_module_plan_166', 'ch8ult_module_plan_167', 'ch8ult_module_plan_168', 'ch8ult_module_plan_169', 'ch8ult_module_plan_16a', 'ch8ult_module_plan_16b', 'ch8ult_module_plan_16c', 'ch8ult_module_plan_16d', 'ch8ult_module_plan_16e', 'ch8ult_module_plan_16f', 'ch8ult_module_plan_170', 'ch8ult_module_plan_171', 'ch8ult_module_plan_172', 'ch8ult_module_plan_173', 'ch8ult_module_plan_174', 'ch8ult_module_plan_175', 'ch8ult_module_plan_176', 'ch8ult_module_plan_177', 'ch8ult_module_plan_178', 'ch8ult_module_plan_179', 'ch8ult_module_plan_17a', 'ch8ult_module_plan_17b', 'ch8ult_module_plan_17c', 'ch8ult_module_plan_17d', 'ch8ult_module_plan_17e', 'ch8ult_module_plan_17f', 'ch8ult_module_plan_180', 'ch8ult_module_plan_181', 'ch8ult_module_plan_182', 'ch8ult_module_plan_183', 'ch8ult_module_plan_184', 'ch8ult_module_plan_185', 'ch8ult_module_plan_186', 'ch8ult_module_plan_187', 'ch8ult_module_plan_188', 'ch8ult_module_plan_189', 'ch8ult_module_plan_18a', 'ch8ult_module_plan_18b', 'ch8ult_module_plan_18c', 'ch8ult_module_plan_18d', 'ch8ult_module_plan_18e', 'ch8ult_module_plan_18f', 'ch8ult_module_plan_190', 'ch8ult_module_plan_191', 'ch8ult_module_plan_192', 'ch8ult_module_plan_193', 'ch8ult_module_plan_194', 'ch8ult_module_plan_195', 'ch8ult_module_plan_196', 'ch8ult_module_plan_197', 'ch8ult_module_plan_198', 'ch8ult_module_plan_199', 'ch8ult_module_plan_19a', 'ch8ult_module_plan_19b', 'ch8ult_module_plan_19c', 'ch8ult_module_plan_19d', 'ch8ult_module_plan_19e', 'ch8ult_module_plan_19f', 'ch8ult_module_plan_1a0', 'ch8ult_module_plan_1a1', 'ch8ult_module_plan_1a2', 'ch8ult_module_plan_1a3', 'ch8ult_module_plan_1a4', 'ch8ult_module_plan_1a5', 'ch8ult_module_plan_1a6', 'ch8ult_module_plan_1a7', 'ch8ult_module_plan_1a8', 'ch8ult_module_plan_1a9', 'ch8ult_module_plan_1aa', 'ch8ult_module_plan_1ab', 'ch8ult_module_plan_1ac', 'ch8ult_module_plan_1ad', 'ch8ult_module_plan_1ae', 'ch8ult_module_plan_1af', 'ch8ult_module_plan_1b0', 'ch8ult_module_plan_1b1', 'ch8ult_module_plan_1b2', 'ch8ult_module_plan_1b3', 'ch8ult_module_plan_1b4', 'ch8ult_module_plan_1b5', 'ch8ult_module_plan_1b6', 'ch8ult_module_plan_1b7', 'ch8ult_module_plan_1b8', 'ch8ult_module_plan_1b9', 'ch8ult_module_plan_1ba', 'ch8ult_module_plan_1bb', 'ch8ult_module_plan_1bc', 'ch8ult_module_plan_1bd', 'ch8ult_module_plan_1be', 'ch8ult_module_plan_1bf', 'ch8ult_module_plan_1c0', 'ch8ult_module_plan_1c1', 'ch8ult_module_plan_1c2', 'ch8ult_module_plan_1c3', 'ch8ult_module_plan_1c4', 'ch8ult_module_plan_1c5', 'ch8ult_module_plan_1c6', 'ch8ult_module_plan_1c7', 'ch8ult_module_plan_1c8', 'ch8ult_module_plan_1c9', 'ch8ult_module_plan_1ca', 'ch8ult_module_plan_1cb', 'ch8ult_module_plan_1cc', 'ch8ult_module_plan_1cd', 'ch8ult_module_plan_1ce', 'ch8ult_module_plan_1cf', 'ch8ult_module_plan_1d0', 'ch8ult_module_plan_1d1', 'ch8ult_module_plan_1d2', 'ch8ult_module_plan_1d3', 'ch8ult_module_plan_1d4', 'ch8ult_module_plan_1d5', 'ch8ult_module_plan_1d6', 'ch8ult_module_plan_1d7', 'ch8ult_module_plan_1d8', 'ch8ult_module_plan_1d9', 'ch8ult_module_plan_1da', 'ch8ult_module_plan_1db', 'ch8ult_module_plan_1dc', 'ch8ult_module_plan_1dd', 'ch8ult_module_plan_1de', 'ch8ult_module_plan_1df', 'ch8ult_module_plan_1e0', 'ch8ult_module_plan_1e1'], 'ch10session4': ['ch10session4_1', 'ch10session4_2', 'ch10session4_3', 'ch10session4_4', 'ch10session4_5', 'ch10session4_6', 'ch10session4_7', 'ch10session4_8', 'ch10session4_9', 'ch10session4_a', 'ch10session4_b', 'ch10session4_c', 'ch10session4_d', 'ch10session4_e', 'ch10session4_f', 'ch10session4_10', 'ch10session4_11', 'ch10session4_12', 'ch10session4_13', 'ch10session4_14', 'ch10session4_15', 'ch10session4_16', 'ch10session4_17', 'ch10session4_18', 'ch10session4_19', 'ch10session4_1a', 'ch10session4_1b', 'ch10session4_1c', 'ch10session4_1d', 'ch10session4_1e', 'ch10session4_1f', 'ch10session4_20', 'ch10session4_21', 'ch10session4_22', 'ch10session4_23', 'ch10session4_24', 'ch10session4_25', 'ch10session4_26', 'ch10session4_27', 'ch10session4_28', 'ch10session4_29', 'ch10session4_2a', 'ch10session4_2b', 'ch10session4_2c', 'ch10session4_2d', 'ch10session4_2e', 'ch10session4_2f', 'ch10session4_30', 'ch10session4_31', 'ch10session4_32', 'ch10session4_33', 'ch10session4_34', 'ch10session4_35', 'ch10session4_36', 'ch10session4_37', 'ch10session4_38', 'ch10session4_39', 'ch10session4_3a', 'ch10session4_3b', 'ch10session4_3c', 'ch10session4_3d', 'ch10session4_3e', 'ch10session4_3f', 'ch10session4_40', 'ch10session4_41', 'ch10session4_42', 'ch10session4_43', 'ch10session4_44', 'ch10session4_45', 'ch10session4_46', 'ch10session4_47', 'ch10session4_48', 'ch10session4_49', 'ch10session4_4a', 'ch10session4_4b', 'ch10session4_4c', 'ch10session4_4d', 'ch10session4_4e', 'ch10session4_4f', 'ch10session4_50', 'ch10session4_51', 'ch10session4_52', 'ch10session4_53', 'ch10session4_54', 'ch10session4_55', 'ch10session4_56', 'ch10session4_57', 'ch10session4_58', 'ch10session4_59', 'ch10session4_5a', 'ch10session4_5b', 'ch10session4_5c', 'ch10session4_5d', 'ch10session4_5e', 'ch10session4_5f', 'ch10session4_60', 'ch10session4_61', 'ch10session4_62', 'ch10session4_63', 'ch10session4_64', 'ch10session4_65', 'ch10session4_66', 'ch10session4_67', 'ch10session4_68', 'ch10session4_69', 'ch10session4_6a', 'ch10session4_6b', 'ch10session4_6c', 'ch10session4_6d', 'ch10session4_6e', 'ch10session4_6f', 'ch10session4_70', 'ch10session4_71', 'ch10session4_72', 'ch10session4_73', 'ch10session4_74', 'ch10session4_75', 'ch10session4_76', 'ch10session4_77', 'ch10session4_78', 'ch10session4_79', 'ch10session4_7a', 'ch10session4_7b', 'ch10session4_7c', 'ch10session4_7d', 'ch10session4_7e', 'ch10session4_7f', 'ch10session4_80', 'ch10session4_81', 'ch10session4_82', 'ch10session4_83', 'ch10session4_84', 'ch10session4_85', 'ch10session4_86', 'ch10session4_87', 'ch10session4_88', 'ch10session4_89', 'ch10session4_8a', 'ch10session4_8b', 'ch10session4_8c', 'ch10session4_8d', 'ch10session4_8e', 'ch10session4_8f', 'ch10session4_90', 'ch10session4_91', 'ch10session4_92', 'ch10session4_93', 'ch10session4_94', 'ch10session4_95', 'ch10session4_96', 'ch10session4_97', 'ch10session4_98', 'ch10session4_99', 'ch10session4_9a', 'ch10session4_9b', 'ch10session4_9c', 'ch10session4_9d', 'ch10session4_9e', 'ch10session4_9f', 'ch10session4_a0', 'ch10session4_a1', 'ch10session4_a2', 'ch10session4_a3', 'ch10session4_a4', 'ch10session4_a5', 'ch10session4_a6', 'ch10session4_a7', 'ch10session4_a8', 'ch10session4_a9', 'ch10session4_aa', 'ch10session4_ab', 'ch10session4_ac', 'ch10session4_ad', 'ch10session4_ae', 'ch10session4_af', 'ch10session4_b0', 'ch10session4_b1', 'ch10session4_b2', 'ch10session4_b3', 'ch10session4_b4', 'ch10session4_b5', 'ch10session4_b6', 'ch10session4_b7', 'ch10session4_b8', 'ch10session4_b9', 'ch10session4_ba', 'ch10session4_bb', 'ch10session4_bc', 'ch10session4_bd', 'ch10session4_be', 'ch10session4_bf', 'ch10session4_c0', 'ch10session4_c1', 'ch10session4_c2', 'ch10session4_c3', 'ch10session4_c4', 'ch10session4_c5', 'ch10session4_c6', 'ch10session4_c7', 'ch10session4_c8', 'ch10session4_c9', 'ch10session4_ca', 'ch10session4_cb', 'ch10session4_cc', 'ch10session4_cd', 'ch10session4_ce', 'ch10session4_cf', 'ch10session4_d0', 'ch10session4_d1', 'ch10session4_d2', 'ch10session4_d3', 'ch10session4_d4', 'ch10session4_d5', 'ch10session4_d6', 'ch10session4_d7', 'ch10session4_d8', 'ch10session4_d9', 'ch10session4_da', 'ch10session4_db', 'ch10session4_dc', 'ch10session4_dd', 'ch10session4_de', 'ch10session4_df', 'ch10session4_e0', 'ch10session4_e1', 'ch10session4_e2', 'ch10session4_e3', 'ch10session4_e4', 'ch10session4_e5', 'ch10session4_e6', 'ch10session4_e7', 'ch10session4_e8', 'ch10session4_e9', 'ch10session4_ea', 'ch10session4_eb', 'ch10session4_ec', 'ch10session4_ed', 'ch10session4_ee', 'ch10session4_ef', 'ch10session4_f0', 'ch10session4_f1', 'ch10session4_f2', 'ch10session4_f3', 'ch10session4_f4', 'ch10session4_f5', 'ch10session4_f6', 'ch10session4_f7', 'ch10session4_f8', 'ch10session4_f9', 'ch10session4_fa', 'ch10session4_fb', 'ch10session4_fc', 'ch10session4_fd', 'ch10session4_fe', 'ch10session4_ff', 'ch10session4_100', 'ch10session4_101', 'ch10session4_102', 'ch10session4_103', 'ch10session4_104', 'ch10session4_105', 'ch10session4_106', 'ch10session4_107', 'ch10session4_108', 'ch10session4_109', 'ch10session4_10a', 'ch10session4_10b', 'ch10session4_10c', 'ch10session4_10d', 'ch10session4_10e', 'ch10session4_10f', 'ch10session4_110', 'ch10session4_111', 'ch10session4_112', 'ch10session4_113', 'ch10session4_114', 'ch10session4_115', 'ch10session4_116', 'ch10session4_117', 'ch10session4_118', 'ch10session4_119', 'ch10session4_11a', 'ch10session4_11b', 'ch10session4_11c', 'ch10session4_11d', 'ch10session4_11e', 'ch10session4_11f', 'ch10session4_120', 'ch10session4_121', 'ch10session4_122', 'ch10session4_123', 'ch10session4_124', 'ch10session4_125', 'ch10session4_126', 'ch10session4_127', 'ch10session4_128', 'ch10session4_129', 'ch10session4_12a', 'ch10session4_12b', 'ch10session4_12c', 'ch10session4_12d', 'ch10session4_12e', 'ch10session4_12f', 'ch10session4_130', 'ch10session4_131', 'ch10session4_132', 'ch10session4_133', 'ch10session4_134', 'ch10session4_135', 'ch10session4_136', 'ch10session4_137', 'ch10session4_138', 'ch10session4_139', 'ch10session4_13a', 'ch10session4_13b', 'ch10session4_13c', 'ch10session4_13d', 'ch10session4_13e', 'ch10session4_13f', 'ch10session4_140', 'ch10session4_141', 'ch10session4_142', 'ch10session4_143', 'ch10session4_144', 'ch10session4_145', 'ch10session4_146', 'ch10session4_147', 'ch10session4_148', 'ch10session4_149', 'ch10session4_14a', 'ch10session4_14b', 'ch10session4_14c', 'ch10session4_14d', 'ch10session4_14e', 'ch10session4_14f', 'ch10session4_150', 'ch10session4_151', 'ch10session4_152', 'ch10session4_153', 'ch10session4_154', 'ch10session4_155', 'ch10session4_156', 'ch10session4_157', 'ch10session4_158', 'ch10session4_159', 'ch10session4_15a', 'ch10session4_15b', 'ch10session4_15c', 'ch10session4_15d', 'ch10session4_15e', 'ch10session4_15f', 'ch10session4_160', 'ch10session4_161', 'ch10session4_162', 'ch10session4_163', 'ch10session4_164', 'ch10session4_165', 'ch10session4_166', 'ch10session4_167', 'ch10session4_168', 'ch10session4_169', 'ch10session4_16a', 'ch10session4_16b', 'ch10session4_16c', 'ch10session4_16d', 'ch10session4_16e', 'ch10session4_16f', 'ch10session4_170', 'ch10session4_171', 'ch10session4_172', 'ch10session4_173', 'ch10session4_174', 'ch10session4_175', 'ch10session4_176', 'ch10session4_177', 'ch10session4_178', 'ch10session4_179', 'ch10session4_17a', 'ch10session4_17b', 'ch10session4_17c', 'ch10session4_17d', 'ch10session4_17e', 'ch10session4_17f', 'ch10session4_180', 'ch10session4_181', 'ch10session4_182', 'ch10session4_183', 'ch10session4_184', 'ch10session4_185', 'ch10session4_186', 'ch10session4_187', 'ch10session4_188', 'ch10session4_189', 'ch10session4_18a', 'ch10session4_18b', 'ch10session4_18c', 'ch10session4_18d', 'ch10session4_18e', 'ch10session4_18f', 'ch10session4_190', 'ch10session4_191', 'ch10session4_192', 'ch10session4_193', 'ch10session4_194', 'ch10session4_195', 'ch10session4_196', 'ch10session4_197', 'ch10session4_198', 'ch10session4_199', 'ch10session4_19a', 'ch10session4_19b', 'ch10session4_19c', 'ch10session4_19d', 'ch10session4_19e', 'ch10session4_19f', 'ch10session4_1a0', 'ch10session4_1a1', 'ch10session4_1a2', 'ch10session4_1a3', 'ch10session4_1a4', 'ch10session4_1a5', 'ch10session4_1a6', 'ch10session4_1a7', 'ch10session4_1a8', 'ch10session4_1a9', 'ch10session4_1aa', 'ch10session4_1ab', 'ch10session4_1ac', 'ch10session4_1ad', 'ch10session4_1ae', 'ch10session4_1af', 'ch10session4_1b0', 'ch10session4_1b1', 'ch10session4_1b2', 'ch10session4_1b3', 'ch10session4_1b4', 'ch10session4_1b5', 'ch10session4_1b6', 'ch10session4_1b7', 'ch10session4_1b8', 'ch10session4_1b9', 'ch10session4_1ba', 'ch10session4_1bb', 'ch10session4_1bc', 'ch10session4_1bd', 'ch10session4_1be', 'ch10session4_1bf', 'ch10session4_1c0', 'ch10session4_1c1', 'ch10session4_1c2', 'ch10session4_1c3', 'ch10session4_1c4', 'ch10session4_1c5', 'ch10session4_1c6', 'ch10session4_1c7', 'ch10session4_1c8', 'ch10session4_1c9', 'ch10session4_1ca', 'ch10session4_1cb', 'ch10session4_1cc', 'ch10session4_1cd', 'ch10session4_1ce', 'ch10session4_1cf', 'ch10session4_1d0', 'ch10session4_1d1', 'ch10session4_1d2', 'ch10session4_1d3', 'ch10session4_1d4', 'ch10session4_1d5', 'ch10session4_1d6', 'ch10session4_1d7', 'ch10session4_1d8', 'ch10session4_1d9', 'ch10session4_1da', 'ch10session4_1db', 'ch10session4_1dc', 'ch10session4_1dd', 'ch10session4_1de', 'ch10session4_1df', 'ch10session4_1e0', 'ch10session4_1e1']}
\ No newline at end of file
Binary file web/hgbook/comments/p_list.pyc has changed
--- a/web/hgbook/comments/views.py	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/hgbook/comments/views.py	Fri Feb 05 23:42:24 2010 +0530
@@ -10,7 +10,7 @@
 from p_list import *
 from BeautifulSoup import BeautifulSoup
 import glob
-html_folder='/home/amit/hgbook-alqua/web/html/'
+html_folder='/home/amit/SEES-hacks/web/html/'
 
 def sort_dict(dict):
 	new_dict = {}
@@ -49,7 +49,9 @@
 
 def index(request):
 	html_files = glob.glob(html_folder+'ch*.html')
-#	print >> sys.stderr , html_files	
+	print >> sys.stderr ,html_files	
+	print >> sys.stderr ,"just checking whether i got here"	
+	print >> sys.stderr , html_files	
 	html_files.sort()
 	link_list=['/review/html/'+a.split('/')[-1] for a in html_files]
 #	print >> sys.stderr , html_files        
@@ -63,7 +65,7 @@
 		title_list.append(title_str)
 	
 	resp_dict=zip(link_list,title_list)
-	
+	print >>sys.stderr ,resp_dict
 	return render_to_response('index.html', {'resp_dict': resp_dict })
 
 
Binary file web/hgbook/comments/views.pyc has changed
--- a/web/hgbook/comments/views.py~	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/hgbook/comments/views.py~	Fri Feb 05 23:42:24 2010 +0530
@@ -10,7 +10,7 @@
 from p_list import *
 from BeautifulSoup import BeautifulSoup
 import glob
-html_folder='/home/amit/hgbook-alqua/web/html/'
+html_folder='/home/amit/SEES-hacks/web/html'
 
 def sort_dict(dict):
 	new_dict = {}
@@ -49,9 +49,11 @@
 
 def index(request):
 	html_files = glob.glob(html_folder+'ch*.html')
-#	print >> sys.stderr , html_files	
+	print >> sys.stderr ,html_files	
+	print >> sys.stderr ,"just checking whether i got here"	
+	print >> sys.stderr , html_files	
 	html_files.sort()
-	link_list=['/review/html/'+a.split('/')[-1] for a in html_file]
+	link_list=['/review/html/'+a.split('/')[-1] for a in html_files]
 #	print >> sys.stderr , html_files        
 	title_list=[]
 	for html_file in html_files:
@@ -63,7 +65,7 @@
 		title_list.append(title_str)
 	
 	resp_dict=zip(link_list,title_list)
-	
+	print >>sys.stderr ,resp_dict
 	return render_to_response('index.html', {'resp_dict': resp_dict })
 
 
--- a/web/hgbook/run.wsgi	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/hgbook/run.wsgi	Fri Feb 05 23:42:24 2010 +0530
@@ -1,8 +1,8 @@
 import os
 import sys
 import django
-sys.path.append('/home/amit/hgbook-alqua/web')
-sys.path.append('/home/amit/hgbook-alqua/web/hgbook/comments')
+sys.path.append('/home/amit/SEES-hacks/web')
+sys.path.append('/home/amit/SEES-hacks/web/hgbook/comments')
 os.environ['DJANGO_SETTINGS_MODULE'] = 'hgbook.settings'
 import django.core.handlers.wsgi
 application = django.core.handlers.wsgi.WSGIHandler()
--- a/web/hgbook/run.wsgi~	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/hgbook/run.wsgi~	Fri Feb 05 23:42:24 2010 +0530
@@ -4,6 +4,7 @@
 sys.path.append('/home/amit/hgbook-alqua/web')
 sys.path.append('/home/amit/hgbook-alqua/web/hgbook/comments')
 os.environ['DJANGO_SETTINGS_MODULE'] = 'hgbook.settings'
+import django.core.handlers.wsgi
 application = django.core.handlers.wsgi.WSGIHandler()
 
 
--- a/web/html/abc.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,530 +0,0 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Chapter 9. Finding and fixing mistakes</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3"><link rel="home" href="index.html" title="Mercurial: The Definitive Guide">
-<link rel="up" href="index.html" title="Mercurial: The Definitive Guide">
-<link rel="prev" href="managing-releases-and-branchy-development.html" title="Chapter 8. Managing releases and branchy development">
-<link rel="next" href="handling-repository-events-with-hooks.html" title="Chapter 10. Handling repository events with hooks"><link rel="alternate" type="application/atom+xml" title="Comments" href="/feeds/comments/">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script></head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="navheader">
-<table width="100%" summary="Navigation header">
-<tr><th colspan="3" align="center">Chapter 14. Adding functionality with extensions</th></tr>
-<tr>
-<td width="20%" align="left">
-<a accesskey="p" href="advanced-uses-of-mercurial-queues.html">Prev</a> </td>
-<th width="60%" align="center"> </th>
-<td width="20%" align="right"> <a accesskey="n" href="migrating-to-mercurial.html">Next</a>
-</td>
-</tr>
-</table>
-<hr>
-</div>
-<div class="chapter" title="Chapter 14. Adding functionality with extensions">
-<div class="titlepage"><div><div><h2 class="title">
-<a name="chap:hgext"></a>Chapter 14. Adding functionality with extensions</h2></div></div></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="sect1"><a href="adding-functionality-with-extensions.html#sec:hgext:inotify">14.1. Improve performance with the <code class="literal">inotify</code> extension</a></span></dt>
-<dt><span class="sect1"><a href="adding-functionality-with-extensions.html#sec:hgext:extdiff">14.2. Flexible diff support with the <code class="literal">extdiff</code> extension</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="adding-functionality-with-extensions.html#id3071699">14.2.1. Defining command aliases</a></span></dt></dl></dd>
-<dt><span class="sect1"><a href="adding-functionality-with-extensions.html#sec:hgext:transplant">14.3. Cherrypicking changes with the <code class="literal">transplant</code> extension</a></span></dt>
-<dt><span class="sect1"><a href="adding-functionality-with-extensions.html#sec:hgext:patchbomb">14.4. Send changes via email with the <code class="literal">patchbomb</code> extension</a></span></dt>
-<dd><dl><dt><span class="sect2"><a href="adding-functionality-with-extensions.html#id3072184">14.4.1. Changing the behavior of patchbombs</a></span></dt></dl></dd>
-</dl>
-</div>
-<p><a name="x_4fe"></a>While the core of Mercurial is quite complete from a
-    functionality standpoint, it's deliberately shorn of fancy
-    features.  This approach of preserving simplicity keeps the
-    software easy to deal with for both maintainers and users.</p>
-<p><a name="x_4ff"></a>However, Mercurial doesn't box you in with an inflexible
-    command set: you can add features to it as
-    <span class="emphasis"><em>extensions</em></span> (sometimes known as
-    <span class="emphasis"><em>plugins</em></span>).  We've already discussed a few of
-    these extensions in earlier chapters.</p>
-<p id="x_546"><a name="x_546"></a>When you provide a directory name, Mercurial will interpret
-      this as “<span class="quote">operate on every file in this directory and its
-	subdirectories</span>”. Mercurial traverses the files and
-      subdirectories in a directory in alphabetical order.  When it
-      encounters a subdirectory, it will traverse that subdirectory
-      before continuing with the current directory.</p>
-
-
-
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem"><p><a name="x_500"></a><a class="xref" href="a-tour-of-mercurial-merging-work.html#sec:tour-merge:fetch" title="3.3. Simplifying the pull-merge-commit sequence">Section 3.3, “Simplifying the pull-merge-commit sequence”</a>
-	covers the <code class="literal">fetch</code> extension;
-	this combines pulling new changes and merging them with local
-	changes into a single command, <span class="command"><strong>fetch</strong></span>.</p></li>
-<li class="listitem"><p><a name="x_501"></a>In <a class="xref" href="handling-repository-events-with-hooks.html" title="Chapter 10. Handling repository events with hooks">Chapter 10, <i>Handling repository events with hooks</i></a>, we covered
-	several extensions that are useful for hook-related
-	functionality: <code class="literal">acl</code> adds
-	access control lists; <code class="literal">bugzilla</code> adds integration with the
-	Bugzilla bug tracking system; and <code class="literal">notify</code> sends notification emails on
-	new changes.</p></li>
-<li class="listitem"><p><a name="x_502"></a>The Mercurial Queues patch management extension is
-	so invaluable that it merits two chapters and an appendix all
-	to itself. <a class="xref" href="managing-change-with-mercurial-queues.html" title="Chapter 12. Managing change with Mercurial Queues">Chapter 12, <i>Managing change with Mercurial Queues</i></a> covers the
-	basics; <a class="xref" href="advanced-uses-of-mercurial-queues.html" title="Chapter 13. Advanced uses of Mercurial Queues">Chapter 13, <i>Advanced uses of Mercurial Queues</i></a> discusses advanced topics;
-	and <a class="xref" href="mercurial-queues-reference.html" title="Appendix B. Mercurial Queues reference">Appendix B, <i>Mercurial Queues reference</i></a> goes into detail on
-	each
-	command.</p></li>
-</ul></div>
-<p><a name="x_503"></a>In this chapter, we'll cover some of the other extensions that
-    are available for Mercurial, and briefly touch on some of the
-    machinery you'll need to know about if you want to write an
-    extension of your own.</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a name="x_504"></a>In <a class="xref" href="adding-functionality-with-extensions.html#sec:hgext:inotify" title="14.1. Improve performance with the inotify extension">Section 14.1, “Improve performance with the <code class="literal">inotify</code> extension”</a>,
-	we'll discuss the possibility of <span class="emphasis"><em>huge</em></span>
-	performance improvements using the <code class="literal">inotify</code> extension.</p></li></ul></div>
-<div class="sect1" title="14.1. Improve performance with the inotify extension">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="sec:hgext:inotify"></a>14.1. Improve performance with the <code class="literal">inotify</code> extension</h2></div></div></div>
-<p><a name="x_505"></a>Are you interested in having some of the most common
-      Mercurial operations run as much as a hundred times faster?
-      Read on!</p>
-<p><a name="x_506"></a>Mercurial has great performance under normal circumstances.
-      For example, when you run the <span class="command"><strong>hg
-	status</strong></span> command, Mercurial has to scan almost every
-      directory and file in your repository so that it can display
-      file status.  Many other Mercurial commands need to do the same
-      work behind the scenes; for example, the <span class="command"><strong>hg diff</strong></span> command uses the status
-      machinery to avoid doing an expensive comparison operation on
-      files that obviously haven't changed.</p>
-<p><a name="x_507"></a>Because obtaining file status is crucial to good
-      performance, the authors of Mercurial have optimised this code
-      to within an inch of its life.  However, there's no avoiding the
-      fact that when you run <span class="command"><strong>hg
-	status</strong></span>, Mercurial is going to have to perform at
-      least one expensive system call for each managed file to
-      determine whether it's changed since the last time Mercurial
-      checked.  For a sufficiently large repository, this can take a
-      long time.</p>
-<p><a name="x_508"></a>To put a number on the magnitude of this effect, I created a
-      repository containing 150,000 managed files.  I timed <span class="command"><strong>hg status</strong></span> as taking ten seconds to
-      run, even when <span class="emphasis"><em>none</em></span> of those files had been
-      modified.</p>
-<p><a name="x_509"></a>Many modern operating systems contain a file notification
-      facility. If a program signs up to an appropriate service, the
-      operating system will notify it every time a file of interest is
-      created, modified, or deleted.  On Linux systems, the kernel
-      component that does this is called
-      <code class="literal">inotify</code>.</p>
-<p><a name="x_50a"></a>Mercurial's <code class="literal">inotify</code>
-      extension talks to the kernel's <code class="literal">inotify</code>
-      component to optimise <span class="command"><strong>hg status</strong></span>
-      commands.  The extension has two components.  A daemon sits in
-      the background and receives notifications from the
-      <code class="literal">inotify</code> subsystem.  It also listens for
-      connections from a regular Mercurial command.  The extension
-      modifies Mercurial's behavior so that instead of scanning the
-      filesystem, it queries the daemon.  Since the daemon has perfect
-      information about the state of the repository, it can respond
-      with a result instantaneously, avoiding the need to scan every
-      directory and file in the repository.</p>
-<p><a name="x_50b"></a>Recall the ten seconds that I measured plain Mercurial as
-      taking to run <span class="command"><strong>hg status</strong></span> on a
-      150,000 file repository.  With the <code class="literal">inotify</code> extension enabled, the time
-      dropped to 0.1 seconds, a factor of <span class="emphasis"><em>one
-	hundred</em></span> faster.</p>
-<p><a name="x_50c"></a>Before we continue, please pay attention to some
-      caveats.</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem"><p><a name="x_50d"></a>The <code class="literal">inotify</code>
-	  extension is Linux-specific.  Because it interfaces directly
-	  to the Linux kernel's <code class="literal">inotify</code> subsystem,
-	  it does not work on other operating systems.</p></li>
-<li class="listitem"><p><a name="x_50e"></a>It should work on any Linux distribution that
-	  was released after early 2005.  Older distributions are
-	  likely to have a kernel that lacks
-	  <code class="literal">inotify</code>, or a version of
-	  <code class="literal">glibc</code> that does not have the necessary
-	  interfacing support.</p></li>
-<li class="listitem"><p><a name="x_50f"></a>Not all filesystems are suitable for use with
-	  the <code class="literal">inotify</code> extension.
-	  Network filesystems such as NFS are a non-starter, for
-	  example, particularly if you're running Mercurial on several
-	  systems, all mounting the same network filesystem.  The
-	  kernel's <code class="literal">inotify</code> system has no way of
-	  knowing about changes made on another system.  Most local
-	  filesystems (e.g. ext3, XFS, ReiserFS) should work
-	  fine.</p></li>
-</ul></div>
-<p><a name="x_510"></a>The <code class="literal">inotify</code> extension is
-      not yet shipped with Mercurial as of May 2007, so it's a little
-      more involved to set up than other extensions.  But the
-      performance improvement is worth it!</p>
-<p><a name="x_511"></a>The extension currently comes in two parts: a set of patches
-      to the Mercurial source code, and a library of Python bindings
-      to the <code class="literal">inotify</code> subsystem.</p>
-<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
-<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="figs/note.png"></td>
-<th align="left">Note</th>
-</tr>
-<tr><td align="left" valign="top"><p><a name="x_512"></a>  There are <span class="emphasis"><em>two</em></span> Python
-	<code class="literal">inotify</code> binding libraries.  One of them is
-	called <code class="literal">pyinotify</code>, and is packaged by some
-	Linux distributions as <code class="literal">python-inotify</code>.
-	This is <span class="emphasis"><em>not</em></span> the one you'll need, as it is
-	too buggy and inefficient to be practical.</p></td></tr>
-</table></div>
-<p><a name="x_513"></a>To get going, it's best to already have a functioning copy
-      of Mercurial installed.</p>
-<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note">
-<tr>
-<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="figs/note.png"></td>
-<th align="left">Note</th>
-</tr>
-<tr><td align="left" valign="top"><p><a name="x_514"></a>  If you follow the instructions below, you'll be
-	<span class="emphasis"><em>replacing</em></span> and overwriting any existing
-	installation of Mercurial that you might already have, using
-	the latest <span class="quote">“<span class="quote">bleeding edge</span>”</span> Mercurial code. Don't
-	say you weren't warned!</p></td></tr>
-</table></div>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem">
-<p><a name="x_515"></a>Clone the Python <code class="literal">inotify</code>
-	  binding repository.  Build and install it.</p>
-<pre class="programlisting">hg clone http://hg.kublai.com/python/inotify
-cd inotify
-python setup.py build --force
-sudo python setup.py install --skip-build</pre>
-</li>
-<li class="listitem">
-<p><a name="x_516"></a>Clone the <code class="filename">crew</code> Mercurial repository.
-	  Clone the <code class="literal">inotify</code> patch
-	  repository so that Mercurial Queues will be able to apply
-	  patches to your cope of the <code class="filename">crew</code> repository.</p>
-<pre class="programlisting">hg clone http://hg.intevation.org/mercurial/crew
-hg clone crew inotify
-hg clone http://hg.kublai.com/mercurial/patches/inotify inotify/.hg/patches</pre>
-</li>
-<li class="listitem"><p><a name="x_517"></a>Make sure that you have the Mercurial Queues
-	  extension, <code class="literal">mq</code>, enabled.  If
-	  you've never used MQ, read <a class="xref" href="managing-change-with-mercurial-queues.html#sec:mq:start" title="12.5. Getting started with Mercurial Queues">Section 12.5, “Getting started with Mercurial Queues”</a> to get started
-	  quickly.</p></li>
-<li class="listitem">
-<p><a name="x_518"></a>Go into the <code class="filename">inotify</code> repo, and apply all
-	  of the <code class="literal">inotify</code> patches
-	  using the <code class="option">hg
-	    -a</code> option to the <span class="command"><strong>qpush</strong></span> command.</p>
-<pre class="programlisting">cd inotify
-hg qpush -a</pre>
-</li>
-<li class="listitem"><p><a name="x_519"></a>  If you get an error message from <span class="command"><strong>qpush</strong></span>, you should not continue.
-	  Instead, ask for help.</p></li>
-<li class="listitem">
-<p><a name="x_51a"></a>Build and install the patched version of
-	  Mercurial.</p>
-<pre class="programlisting">python setup.py build --force
-sudo python setup.py install --skip-build</pre>
-</li>
-</ol></div>
-<p><a name="x_51b"></a>Once you've build a suitably patched version of Mercurial,
-      all you need to do to enable the <code class="literal">inotify</code> extension is add an entry to
-      your <code class="filename">~/.hgrc</code>.</p>
-<pre class="programlisting">[extensions] inotify =</pre>
-<p><a name="x_51c"></a>When the <code class="literal">inotify</code> extension
-      is enabled, Mercurial will automatically and transparently start
-      the status daemon the first time you run a command that needs
-      status in a repository.  It runs one status daemon per
-      repository.</p>
-<p><a name="x_51d"></a>The status daemon is started silently, and runs in the
-      background.  If you look at a list of running processes after
-      you've enabled the <code class="literal">inotify</code>
-      extension and run a few commands in different repositories,
-      you'll thus see a few <code class="literal">hg</code> processes sitting
-      around, waiting for updates from the kernel and queries from
-      Mercurial.</p>
-<p><a name="x_51e"></a>The first time you run a Mercurial command in a repository
-      when you have the <code class="literal">inotify</code>
-      extension enabled, it will run with about the same performance
-      as a normal Mercurial command.  This is because the status
-      daemon needs to perform a normal status scan so that it has a
-      baseline against which to apply later updates from the kernel.
-      However, <span class="emphasis"><em>every</em></span> subsequent command that does
-      any kind of status check should be noticeably faster on
-      repositories of even fairly modest size.  Better yet, the bigger
-      your repository is, the greater a performance advantage you'll
-      see.  The <code class="literal">inotify</code> daemon makes
-      status operations almost instantaneous on repositories of all
-      sizes!</p>
-<p><a name="x_51f"></a>If you like, you can manually start a status daemon using
-      the <span class="command"><strong>inserve</strong></span> command.
-      This gives you slightly finer control over how the daemon ought
-      to run.  This command will of course only be available when the
-      <code class="literal">inotify</code> extension is
-      enabled.</p>
-<p><a name="x_520"></a>When you're using the <code class="literal">inotify</code> extension, you should notice
-      <span class="emphasis"><em>no difference at all</em></span> in Mercurial's
-      behavior, with the sole exception of status-related commands
-      running a whole lot faster than they used to.  You should
-      specifically expect that commands will not print different
-      output; neither should they give different results. If either of
-      these situations occurs, please report a bug.</p>
-</div>
-<div class="sect1" title="14.2. Flexible diff support with the extdiff extension">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="sec:hgext:extdiff"></a>14.2. Flexible diff support with the <code class="literal">extdiff</code> extension</h2></div></div></div>
-<p><a name="x_521"></a>Mercurial's built-in <span class="command"><strong>hg
-	diff</strong></span> command outputs plaintext unified diffs.</p>
-<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>hg diff</code></strong>
-diff -r 80997726a0ea myfile
---- a/myfile	Wed Jan 06 06:50:18 2010 +0000
-+++ b/myfile	Wed Jan 06 06:50:18 2010 +0000
-@@ -1,1 +1,2 @@
- The first line.
-+The second line.
-</pre>
-<p><a name="x_522"></a>If you would like to use an external tool to display
-      modifications, you'll want to use the <code class="literal">extdiff</code> extension.  This will let you
-      use, for example, a graphical diff tool.</p>
-<p><a name="x_523"></a>The <code class="literal">extdiff</code> extension is
-      bundled with Mercurial, so it's easy to set up.  In the <code class="literal">extensions</code> section of your
-      <code class="filename">~/.hgrc</code>, simply add a
-      one-line entry to enable the extension.</p>
-<pre class="programlisting">[extensions]
-extdiff =</pre>
-<p><a name="x_524"></a>This introduces a command named <span class="command"><strong>extdiff</strong></span>, which by default uses
-      your system's <span class="command"><strong>diff</strong></span> command to generate a
-      unified diff in the same form as the built-in <span class="command"><strong>hg diff</strong></span> command.</p>
-<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>hg extdiff</code></strong>
---- a.80997726a0ea/myfile	2010-01-06 06:50:18.613674526 +0000
-+++ /tmp/extdiffNErQlu/a/myfile	2010-01-06 06:50:18.437687076 +0000
-@@ -1 +1,2 @@
- The first line.
-+The second line.
-</pre>
-<p><a name="x_525"></a>The result won't be exactly the same as with the built-in
-      <span class="command"><strong>hg diff</strong></span> variations, because the
-      output of <span class="command"><strong>diff</strong></span> varies from one system to
-      another, even when passed the same options.</p>
-<p><a name="x_526"></a>As the <span class="quote">“<span class="quote"><code class="literal">making snapshot</code></span>”</span>
-      lines of output above imply, the <span class="command"><strong>extdiff</strong></span> command works by
-      creating two snapshots of your source tree.  The first snapshot
-      is of the source revision; the second, of the target revision or
-      working directory.  The <span class="command"><strong>extdiff</strong></span> command generates
-      these snapshots in a temporary directory, passes the name of
-      each directory to an external diff viewer, then deletes the
-      temporary directory.  For efficiency, it only snapshots the
-      directories and files that have changed between the two
-      revisions.</p>
-<p><a name="x_527"></a>Snapshot directory names have the same base name as your
-      repository. If your repository path is <code class="filename">/quux/bar/foo</code>, then <code class="filename">foo</code> will be the name of each
-      snapshot directory.  Each snapshot directory name has its
-      changeset ID appended, if appropriate.  If a snapshot is of
-      revision <code class="literal">a631aca1083f</code>, the directory will be
-      named <code class="filename">foo.a631aca1083f</code>.
-      A snapshot of the working directory won't have a changeset ID
-      appended, so it would just be <code class="filename">foo</code> in this example.  To see what
-      this looks like in practice, look again at the <span class="command"><strong>extdiff</strong></span> example above.  Notice
-      that the diff has the snapshot directory names embedded in its
-      header.</p>
-<p><a name="x_528"></a>The <span class="command"><strong>extdiff</strong></span> command
-      accepts two important options. The <code class="option">hg -p</code> option
-      lets you choose a program to view differences with, instead of
-      <span class="command"><strong>diff</strong></span>.  With the <code class="option">hg -o</code> option,
-      you can change the options that <span class="command"><strong>extdiff</strong></span> passes to the program
-      (by default, these options are
-      <span class="quote">“<span class="quote"><code class="literal">-Npru</code></span>”</span>, which only make sense
-      if you're running <span class="command"><strong>diff</strong></span>).  In other respects,
-      the <span class="command"><strong>extdiff</strong></span> command
-      acts similarly to the built-in <span class="command"><strong>hg
-	diff</strong></span> command: you use the same option names, syntax,
-      and arguments to specify the revisions you want, the files you
-      want, and so on.</p>
-<p><a name="x_529"></a>As an example, here's how to run the normal system
-      <span class="command"><strong>diff</strong></span> command, getting it to generate context
-      diffs (using the <code class="option">-c</code> option)
-      instead of unified diffs, and five lines of context instead of
-      the default three (passing <code class="literal">5</code> as the argument
-      to the <code class="option">-C</code> option).</p>
-<pre class="screen"><code class="prompt">$</code> <strong class="userinput"><code>hg extdiff -o -NprcC5</code></strong>
-*** a.80997726a0ea/myfile	Wed Jan  6 06:50:18 2010
---- /tmp/extdiffNErQlu/a/myfile	Wed Jan  6 06:50:18 2010
-***************
-*** 1 ****
---- 1,2 ----
-  The first line.
-+ The second line.
-</pre>
-<p><a name="x_52a"></a>Launching a visual diff tool is just as easy.  Here's how to
-      launch the <span class="command"><strong>kdiff3</strong></span> viewer.</p>
-<pre class="programlisting">hg extdiff -p kdiff3 -o</pre>
-<p><a name="x_52b"></a>If your diff viewing command can't deal with directories,
-      you can easily work around this with a little scripting.  For an
-      example of such scripting in action with the <code class="literal">mq</code> extension and the
-      <span class="command"><strong>interdiff</strong></span> command, see <a class="xref" href="advanced-uses-of-mercurial-queues.html#mq-collab:tips:interdiff" title="13.9.2. Viewing the history of a patch">Section 13.9.2, “Viewing the history of a patch”</a>.</p>
-<div class="sect2" title="14.2.1. Defining command aliases">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3071699"></a>14.2.1. Defining command aliases</h3></div></div></div>
-<p><a name="x_52c"></a>It can be cumbersome to remember the options to both the
-	<span class="command"><strong>extdiff</strong></span> command and
-	the diff viewer you want to use, so the <code class="literal">extdiff</code> extension lets you define
-	<span class="emphasis"><em>new</em></span> commands that will invoke your diff
-	viewer with exactly the right options.</p>
-<p><a name="x_52d"></a>All you need to do is edit your <code class="filename">~/.hgrc</code>, and add a section named
-	<code class="literal">extdiff</code>.  Inside this
-	section, you can define multiple commands.  Here's how to add
-	a <code class="literal">kdiff3</code> command.  Once you've defined
-	this, you can type <span class="quote">“<span class="quote"><code class="literal">hg kdiff3</code></span>”</span>
-	and the <code class="literal">extdiff</code> extension
-	will run <span class="command"><strong>kdiff3</strong></span> for you.</p>
-<pre class="programlisting">[extdiff]
-cmd.kdiff3 =</pre>
-<p><a name="x_52e"></a>If you leave the right hand side of the definition empty,
-	as above, the <code class="literal">extdiff</code>
-	extension uses the name of the command you defined as the name
-	of the external program to run.  But these names don't have to
-	be the same.  Here, we define a command named
-	<span class="quote">“<span class="quote"><code class="literal">hg wibble</code></span>”</span>, which runs
-	<span class="command"><strong>kdiff3</strong></span>.</p>
-<pre class="programlisting">[extdiff]
- cmd.wibble = kdiff3</pre>
-<p><a name="x_52f"></a>You can also specify the default options that you want to
-	invoke your diff viewing program with.  The prefix to use is
-	<span class="quote">“<span class="quote"><code class="literal">opts.</code></span>”</span>, followed by the name
-	of the command to which the options apply.  This example
-	defines a <span class="quote">“<span class="quote"><code class="literal">hg vimdiff</code></span>”</span> command
-	that runs the <span class="command"><strong>vim</strong></span> editor's
-	<code class="literal">DirDiff</code> extension.</p>
-<pre class="programlisting">[extdiff]
- cmd.vimdiff = vim
-opts.vimdiff = -f '+next' '+execute "DirDiff" argv(0) argv(1)'</pre>
-</div>
-</div>
-<div class="sect1" title="14.3. Cherrypicking changes with the transplant extension">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="sec:hgext:transplant"></a>14.3. Cherrypicking changes with the <code class="literal">transplant</code> extension</h2></div></div></div>
-<p><a name="x_530"></a>Need to have a long chat with Brendan about this.</p>
-</div>
-<div class="sect1" title="14.4. Send changes via email with the patchbomb extension">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="sec:hgext:patchbomb"></a>14.4. Send changes via email with the <code class="literal">patchbomb</code> extension</h2></div></div></div>
-<p><a name="x_531"></a>Many projects have a culture of <span class="quote">“<span class="quote">change
-	review</span>”</span>, in which people send their modifications to a
-      mailing list for others to read and comment on before they
-      commit the final version to a shared repository.  Some projects
-      have people who act as gatekeepers; they apply changes from
-      other people to a repository to which those others don't have
-      access.</p>
-<p><a name="x_532"></a>Mercurial makes it easy to send changes over email for
-      review or application, via its <code class="literal">patchbomb</code> extension.  The extension is
-      so named because changes are formatted as patches, and it's usual
-      to send one changeset per email message.  Sending a long series
-      of changes by email is thus much like <span class="quote">“<span class="quote">bombing</span>”</span> the
-      recipient's inbox, hence <span class="quote">“<span class="quote">patchbomb</span>”</span>.</p>
-<p><a name="x_533"></a>As usual, the basic configuration of the <code class="literal">patchbomb</code> extension takes just one or
-      two lines in your <code class="filename">
-	/.hgrc</code>.</p>
-<pre class="programlisting">[extensions]
-patchbomb =</pre>
-<p><a name="x_534"></a>Once you've enabled the extension, you will have a new
-      command available, named <span class="command"><strong>email</strong></span>.</p>
-<p><a name="x_535"></a>The safest and best way to invoke the <span class="command"><strong>email</strong></span> command is to
-      <span class="emphasis"><em>always</em></span> run it first with the <code class="option">hg -n</code> option.
-      This will show you what the command <span class="emphasis"><em>would</em></span>
-      send, without actually sending anything.  Once you've had a
-      quick glance over the changes and verified that you are sending
-      the right ones, you can rerun the same command, with the <code class="option">hg -n</code> option
-      removed.</p>
-<p><a name="x_536"></a>The <span class="command"><strong>email</strong></span> command
-      accepts the same kind of revision syntax as every other
-      Mercurial command.  For example, this command will send every
-      revision between 7 and <code class="literal">tip</code>, inclusive.</p>
-<pre class="programlisting">hg email -n 7:tip</pre>
-<p><a name="x_537"></a>You can also specify a <span class="emphasis"><em>repository</em></span> to
-      compare with.  If you provide a repository but no revisions, the
-      <span class="command"><strong>email</strong></span> command will
-      send all revisions in the local repository that are not present
-      in the remote repository.  If you additionally specify revisions
-      or a branch name (the latter using the <code class="option">hg -b</code> option),
-      this will constrain the revisions sent.</p>
-<p><a name="x_538"></a>It's perfectly safe to run the <span class="command"><strong>email</strong></span> command without the
-      names of the people you want to send to: if you do this, it will
-      just prompt you for those values interactively.  (If you're
-      using a Linux or Unix-like system, you should have enhanced
-      <code class="literal">readline</code>-style editing capabilities when
-      entering those headers, too, which is useful.)</p>
-<p><a name="x_539"></a>When you are sending just one revision, the <span class="command"><strong>email</strong></span> command will by
-      default use the first line of the changeset description as the
-      subject of the single email message it sends.</p>
-<p><a name="x_53a"></a>If you send multiple revisions, the <span class="command"><strong>email</strong></span> command will usually
-      send one message per changeset.  It will preface the series with
-      an introductory message, in which you should describe the
-      purpose of the series of changes you're sending.</p>
-<div class="sect2" title="14.4.1. Changing the behavior of patchbombs">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3072184"></a>14.4.1. Changing the behavior of patchbombs</h3></div></div></div>
-<p><a name="x_53b"></a>Not every project has exactly the same conventions for
-	sending changes in email; the <code class="literal">patchbomb</code> extension tries to
-	accommodate a number of variations through command line
-	options.</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="disc">
-<li class="listitem"><p><a name="x_53c"></a>You can write a subject for the introductory
-	    message on the command line using the <code class="option">hg -s</code>
-	    option.  This takes one argument, the text of the subject
-	    to use.</p></li>
-<li class="listitem"><p><a name="x_53d"></a>To change the email address from which the
-	    messages originate, use the <code class="option">hg -f</code>
-	    option.  This takes one argument, the email address to
-	    use.</p></li>
-<li class="listitem"><p><a name="x_53e"></a>The default behavior is to send unified diffs
-	    (see <a class="xref" href="managing-change-with-mercurial-queues.html#sec:mq:patch" title="12.4. Understanding patches">Section 12.4, “Understanding patches”</a> for a
-	    description of the
-	    format), one per message.  You can send a binary bundle
-	    instead with the <code class="option">hg -b</code>
-	    option.</p></li>
-<li class="listitem"><p><a name="x_53f"></a>Unified diffs are normally prefaced with a
-	    metadata header.  You can omit this, and send unadorned
-	    diffs, with the <code class="option">hg
-	      --plain</code> option.</p></li>
-<li class="listitem"><p><a name="x_540"></a>Diffs are normally sent <span class="quote">“<span class="quote">inline</span>”</span>,
-	    in the same body part as the description of a patch.  This
-	    makes it easiest for the largest number of readers to
-	    quote and respond to parts of a diff, as some mail clients
-	    will only quote the first MIME body part in a message. If
-	    you'd prefer to send the description and the diff in
-	    separate body parts, use the <code class="option">hg -a</code>
-	    option.</p></li>
-<li class="listitem"><p><a name="x_541"></a>Instead of sending mail messages, you can
-	    write them to an <code class="literal">mbox</code>-format mail
-	    folder using the <code class="option">hg -m</code>
-	    option.  That option takes one argument, the name of the
-	    file to write to.</p></li>
-<li class="listitem"><p><a name="x_542"></a>If you would like to add a
-	    <span class="command"><strong>diffstat</strong></span>-format summary to each patch,
-	    and one to the introductory message, use the <code class="option">hg -d</code>
-	    option.  The <span class="command"><strong>diffstat</strong></span> command displays
-	    a table containing the name of each file patched, the
-	    number of lines affected, and a histogram showing how much
-	    each file is modified.  This gives readers a qualitative
-	    glance at how complex a patch is.</p></li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="navfooter">
-<hr>
-<table width="100%" summary="Navigation footer">
-<tr>
-<td width="40%" align="left">
-<a accesskey="p" href="advanced-uses-of-mercurial-queues.html">Prev</a> </td>
-<td width="20%" align="center"> </td>
-<td width="40%" align="right"> <a accesskey="n" href="migrating-to-mercurial.html">Next</a>
-</td>
-</tr>
-<tr>
-<td width="40%" align="left" valign="top">Chapter 13. Advanced uses of Mercurial Queues </td>
-<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
-<td width="40%" align="right" valign="top"> Appendix A. Migrating to Mercurial</td>
-</tr>
-</table>
-</div>
-</body>
-</html>
--- a/web/html/ar01.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,387 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Functional Approach</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta id="generator" content="DocBook XSL Stylesheets V1.74.3"><link rel="home" href="index.html" title="Mercurial: The Definitive Guide">
-<link rel="up" href="index.html" title="Mercurial: The Definitive Guide">
-<link rel="prev" href="managing-releases-and-branchy-development.html" title="Chapter 8. Managing releases and branchy development">
-<link rel="next" href="handling-repository-events-with-hooks.html" title="Chapter 10. Handling repository events with hooks"><link rel="alternate" type="application/atom+xml" title="Comments" href="/feeds/comments/">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script></head>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="navheader">
-<table width="100%" summary="Navigation header">
-<tr><th colspan="3" align="center">Functional Approach</th></tr>
-<tr>
-<td width="20%" align="left">
-<a accesskey="p" href="index.html">Prev</a> </td>
-<th width="60%" align="center"> </th>
-<td width="20%" align="right"> </td>
-</tr>
-</table>
-<hr>
-</div>
-<div class="article" title="Functional Approach">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2496165"></a>Functional Approach</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="ar01.html#default-arguments">1. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="ar01.html#keyword-arguments">2. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="ar01.html#parameter-packing-and-unpacking">3. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="ar01.html#nested-functions-and-scopes">4. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="ar01.html#map-reduce-and-filter-functions">5. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="ar01.html#list-comprehensions">5.1. List Comprehensions</a></span></dt></dl></dd>
-</dl>
-</div>
-<p id="x_74b"><a name="x_74b"></a>
-    <span class="emphasis"><em>Functions</em></span> allow us to enclose a set of statements and call the function again and again instead of repeating the group of statements everytime. Functions also allow us to isolate a piece of code from all the other code and provides the convenience of not polluting the global variables.
-  </p>
-<p id="x_74c"><a name="x_74c"></a>
-    <span class="emphasis"><em>Function</em></span> in python is defined with the keyword 
-    <span class="strong"><strong>def</strong></span> followed by the name of the function, in turn followed by a pair of parenthesis which encloses the list of parameters to the function. The definition line ends with a ':'. The definition line is followed by the body of the function intended by one block. The 
-    <span class="emphasis"><em>Function</em></span> must return a value:
-  </p>
-<pre class="programlisting">def factorial(n):
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact
-
-</pre>
-<p><a name="x_74d"></a>The code snippet above defines a function with the name factorial, takes the number for which the factorial must be computed, computes the factorial and returns the value.</p>
-<p><a name="x_74e"></a>A 
-    <span class="emphasis"><em>Function</em></span> once defined can be used or called anywhere else in the program. We call a fucntion with its name followed by a pair of parenthesis which encloses the arguments to the function.
-  </p>
-<p><a name="x_74f"></a>The value that function returns can be assigned to a variable. Let's call the above function and store the factorial in a variable:</p>
-<pre class="programlisting">fact5 = factorial(5)
-
-</pre>
-<p><a name="x_750"></a>The value of fact5 will now be 120, which is the factorial of 5. Note that we passed 5 as the argument to the function.</p>
-<p><a name="x_751"></a>It may be necessary to document what the function does, for each of the function to help the person who reads our code to understand it better. In order to do this Python allows the first line of the function body to be a string. This string is called as 
-    <span class="emphasis"><em>Documentation String</em></span> or 
-    <span class="emphasis"><em>docstring</em></span>. 
-    <span class="emphasis"><em>docstrings</em></span> prove to be very handy since there are number of tools which can pull out all the docstrings from Python functions and generate the documentation automatically from it. 
-    <span class="emphasis"><em>docstrings</em></span> for functions can be written as follows:
-  </p>
-<pre class="programlisting">def factorial(n):
-  'Returns the factorial for the number n.'
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact
-
-</pre>
-<p><a name="x_752"></a>An important point to note at this point is that, a function can return any Python value or a Python object, which also includes a 
-    <span class="emphasis"><em>Tuple</em></span>. A 
-    <span class="emphasis"><em>Tuple</em></span> is just a collection of values and those values themselves can be of any other valid Python datatypes, including 
-    <span class="emphasis"><em>Lists</em></span>, 
-    <span class="emphasis"><em>Tuples</em></span>, 
-    <span class="emphasis"><em>Dictionaries</em></span> among other things. So effectively, if a function can return a tuple, it can return any number of values through a tuple
-  </p>
-<p><a name="x_753"></a>Let us write a small function to swap two values:</p>
-<pre class="programlisting">def swap(a, b):
-  return b, a
-
-c, d = swap(a, b)
-
-</pre>
-<p><a name="x_754"></a>Function scope --------------- The variables used inside the function are confined to the function's scope and doesn't pollute the variables of the same name outside the scope of the function. Also the arguments passed to the function are passed by-value if it is of basic Python data type:</p>
-<pre class="programlisting">def cant_change(n):
-  n = 10
-
-n = 5
-cant_change(n)
-
-</pre>
-<p><a name="x_755"></a>Upon running this code, what do you think would have happened to value of n which was assigned 5 before the function call? If you have already tried out that snippet on the interpreter you already know that the value of n is not changed. This is true of any immutable types of Python like 
-    <span class="emphasis"><em>Numbers</em></span>, 
-    <span class="emphasis"><em>Strings</em></span> and 
-    <span class="emphasis"><em>Tuples</em></span>. But when you pass mutable objects like 
-    <span class="emphasis"><em>Lists</em></span> and 
-    <span class="emphasis"><em>Dictionaries</em></span> the values are manipulated even outside the function:
-  </p>
-<pre class="programlisting">&gt;&gt;&gt; def can_change(n):
-...   n[1] = James
-...
-
-&gt;&gt;&gt; name = ['Mr.', 'Steve', 'Gosling']
-&gt;&gt;&gt; can_change(name)
-&gt;&gt;&gt; name
-['Mr.', 'James', 'Gosling']
-
-</pre>
-<p><a name="x_756"></a>If nothing is returned by the function explicitly, Python takes care to return None when the funnction is called.</p>
-<div class="section" title="1. Default Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="default-arguments"></a>1. Default Arguments</h2></div></div></div>
-<p><a name="x_757"></a>There may be situations where we need to allow the functions to take the arguments optionally. Python allows us to define function this way by providing a facility called 
-      <span class="emphasis"><em>Default Arguments</em></span>. For example, we need to write a function that returns a list of fibonacci numbers. Since our function cannot generate an infinite list of fibonacci numbers, we need to specify the number of elements that the fibonacci sequence must contain. Suppose, additionally, we want to the function to return 10 numbers in the sequence if no option is specified we can define the function as follows:
-    </p>
-<pre class="programlisting">def fib(n=10):
-  fib_list = [0, 1]
-  for i in range(n - 2):
-    next = fib_list[-2] + fib_list[-1]
-    fib_list.append(next)
-  return fib_list
-
-</pre>
-<p><a name="x_758"></a>When we call this function, we can optionally specify the value for the parameter n, during the call as an argument. Calling with no argument and argument with n=5 returns the following fibonacci sequences:</p>
-<pre class="programlisting">fib()
-[0, 1, 1, 2, 3, 5, 8, 13, 21, 34]
-fib(5)
-[0, 1, 1, 2, 3]
-
-</pre>
-</div>
-<div class="section" title="2. Keyword Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="keyword-arguments"></a>2. Keyword Arguments</h2></div></div></div>
-<p><a name="x_759"></a>When a function takes a large number of arguments, it may be difficult to remember the order of the parameters in the function definition or it may be necessary to pass values to only certain parameters since others take the default value. In either of these cases, Python provides the facility of passing arguments by specifying the name of the parameter as defined in the function definition. This is known as 
-      <span class="emphasis"><em>Keyword Arguments</em></span>.
-    </p>
-<p><a name="x_75a"></a>In a function call, 
-      <span class="emphasis"><em>Keyword arguments</em></span> can be used for each argument, in the following fashion:
-    </p>
-<pre class="programlisting">argument_name=argument_value
-Also denoted as: keyword=argument
-
-def wish(name='World', greetings='Hello'):
-  print "%s, %s!" % (greetings, name)
-
-</pre>
-<p><a name="x_75b"></a>This function can be called in one of the following ways. It is important to note that no restriction is imposed in the order in which 
-      <span class="emphasis"><em>Keyword arguments</em></span> can be specified. Also note, that we have combined 
-      <span class="emphasis"><em>Keyword arguments</em></span> with 
-      <span class="emphasis"><em>Default arguments</em></span> in this example, however it is not necessary:
-    </p>
-<pre class="programlisting">wish(name='Guido', greetings='Hey')
-wish(greetings='Hey', name='Guido')
-
-</pre>
-<p><a name="x_75c"></a>Calling functions by specifying arguments in the order of parameters specified in the function definition is called as 
-      <span class="emphasis"><em>Positional arguments</em></span>, as opposed to 
-      <span class="emphasis"><em>Keyword arguments</em></span>. It is possible to use both 
-      <span class="emphasis"><em>Positional arguments</em></span> and 
-      <span class="emphasis"><em>Keyword arguments</em></span> in a single function call. But Python doesn't allow us to bungle up both of them. The arguments to the function, in the call, must always start with 
-      <span class="emphasis"><em>Positional arguments</em></span> which is in turn followed by 
-      <span class="emphasis"><em>Keyword arguments</em></span>:
-    </p>
-<pre class="programlisting">def my_func(x, y, z, u, v, w):
-  # initialize variables.
-  ...
-  # do some stuff 
-  ...
-  # return the value
-
-</pre>
-<p><a name="x_75d"></a>It is valid to call the above functions in the following ways:</p>
-<pre class="programlisting">my_func(10, 20, 30, u=1.0, v=2.0, w=3.0)
-my_func(10, 20, 30, 1.0, 2.0, w=3.0)
-my_func(10, 20, z=30, u=1.0, v=2.0, w=3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, w=3.0)
-
-</pre>
-<p><a name="x_75e"></a>Following lists some of the invalid calls:</p>
-<pre class="programlisting">my_func(10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, 3.0)
-
-</pre>
-</div>
-<div class="section" title="3. Parameter Packing and Unpacking">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="parameter-packing-and-unpacking"></a>3. Parameter Packing and Unpacking</h2></div></div></div>
-<p><a name="x_75f"></a>The positional arguments passed to a function can be collected in a tuple parameter and keyword arguments can be collected in a dictionary. Since keyword arguments must always be the last set of arguments passed to a function, the keyword dictionary parameter must be the last parameter. The function definition must include a list explicit parameters, followed by tuple paramter collecting parameter, whose name is preceded by a *****, for collecting positional parameters, in turn followed by the dictionary collecting parameter, whose name is preceded by a ****** :</p>
-<pre class="programlisting">def print_report(title, *args, **name):
-  """Structure of *args*
-  (age, email-id)
-  Structure of *name*
-  {
-      'first': First Name
-      'middle': Middle Name
-      'last': Last Name
-  }
-  """
-
-  print "Title: %s" % (title)
-  print "Full name: %(first)s %(middle)s %(last)s" % name
-  print "Age: %d\nEmail-ID: %s" % args
-
-</pre>
-<p><a name="x_760"></a>The above function can be called as. Note, the order of keyword parameters can be interchanged:</p>
-<pre class="programlisting">&gt;&gt;&gt; print_report('Employee Report', 29, 'johny@example.com', first='Johny',
-                 last='Charles', middle='Douglas')
-Title: Employee Report
-Full name: Johny Douglas Charles
-Age: 29
-Email-ID: johny@example.com
-
-</pre>
-<p><a name="x_761"></a>The reverse of this can also be achieved by using a very identical syntax while calling the function. A tuple or a dictionary can be passed as arguments in place of a list of *Positional arguments* or *Keyword arguments* respectively using ***** or ****** :</p>
-<pre class="programlisting">def print_report(title, age, email, first, middle, last):
-  print "Title: %s" % (title)
-  print "Full name: %s %s %s" % (first, middle, last)
-  print "Age: %d\nEmail-ID: %s" % (age, email)
-
-&gt;&gt;&gt; args = (29, 'johny@example.com')
-&gt;&gt;&gt; name = {
-        'first': 'Johny',
-        'middle': 'Charles',
-        'last': 'Douglas'
-        }
-&gt;&gt;&gt; print_report('Employee Report', *args, **name)
-Title: Employee Report
-Full name: Johny Charles Douglas
-Age: 29
-Email-ID: johny@example.com
-
-</pre>
-</div>
-<div class="section" title="4. Nested Functions and Scopes">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="nested-functions-and-scopes"></a>4. Nested Functions and Scopes</h2></div></div></div>
-<p><a name="x_762"></a>Python allows nesting one function inside another. This style of programming turns out to be extremely flexible and powerful features when we use 
-      <span class="emphasis"><em>Python decorators</em></span>. We will not talk about decorators is beyond the scope of this course. If you are interested in knowing more about 
-      <span class="emphasis"><em>decorator programming</em></span> in Python you are suggested to read:
-    </p>
-<div class="literallayout"><p><br>
-      <a class="ulink" href="http://avinashv.net/2008/04/python-decorators-syntactic-sugar" target="_top">http://avinashv.net/2008/04/python-decorators-syntactic-sugar</a>/<br>
-      <a class="ulink" href="http://personalpages.tds.net" target="_top">http://personalpages.tds.net</a>/~kent37/kk/00001.html<br>
-    </p></div>
-<p><a name="x_763"></a>However, the following is an example for nested functions in Python:</p>
-<pre class="programlisting">def outer():
-  print "Outer..."
-  def inner():
-    print "Inner..."
-  print "Outer..."
-  inner()
-
-&gt;&gt;&gt; outer()
-
-</pre>
-</div>
-<div class="section" title="5. map, reduce and filter functions">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="map-reduce-and-filter-functions"></a>5. map, reduce and filter functions</h2></div></div></div>
-<p><a name="x_764"></a>Python provides several built-in functions for convenience. The 
-      <span class="strong"><strong>map()</strong></span>, 
-      <span class="strong"><strong>reduce()</strong></span> and 
-      <span class="strong"><strong>filter()</strong></span> functions prove to be very useful with sequences like 
-      <span class="emphasis"><em>Lists</em></span>.
-    </p>
-<p><a name="x_765"></a>The 
-      <span class="strong"><strong>map</strong></span> (
-      <span class="emphasis"><em>function</em></span>, 
-      <span class="emphasis"><em>sequence</em></span>) function takes two arguments: 
-      <span class="emphasis"><em>function</em></span> and a 
-      <span class="emphasis"><em>sequence</em></span> argument. The 
-      <span class="emphasis"><em>function</em></span> argument must be the name of the function which in turn takes a single argument, the individual element of the 
-      <span class="emphasis"><em>sequence</em></span>. The 
-      <span class="strong"><strong>map</strong></span> function calls 
-      <span class="emphasis"><em>function(item)</em></span>, for each item in the sequence and returns a list of values, where each value is the value returned by each call to 
-      <span class="emphasis"><em>function(item)</em></span>. 
-      <span class="strong"><strong>map()</strong></span> function allows to pass more than one sequence. In this case, the first argument, 
-      <span class="emphasis"><em>function</em></span> must take as many arguments as the number of sequences passed. This function is called with each corresponding element in the each of the sequences, or 
-      <span class="strong"><strong>None</strong></span> if one of the sequence is exhausted:
-    </p>
-<pre class="programlisting">def square(x):
-  return x*x
-
-&gt;&gt;&gt; map(square, [1, 2, 3, 4])
-[1, 4, 9, 16]
-
-def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; map(mul, [1, 2, 3, 4], [6, 7, 8, 9])
-
-</pre>
-<p><a name="x_766"></a>The 
-      <span class="strong"><strong>filter</strong></span> (
-      <span class="emphasis"><em>function</em></span>, 
-      <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to the 
-      <span class="strong"><strong>map()</strong></span> function. The 
-      <span class="strong"><strong>filter</strong></span> function calls 
-      <span class="emphasis"><em>function(item)</em></span>, for each item in the sequence and returns all the elements in the sequence for which 
-      <span class="emphasis"><em>function(item)</em></span> returned True:
-    </p>
-<pre class="programlisting">def even(x):
-  if x % 2:
-    return True
-  else:
-    return False
-
-&gt;&gt;&gt; filter(even, range(1, 10))
-[1, 3, 5, 7, 9]
-
-</pre>
-<p><a name="x_767"></a>The 
-      <span class="strong"><strong>reduce</strong></span> (
-      <span class="emphasis"><em>function</em></span>, 
-      <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to 
-      <span class="strong"><strong>map</strong></span> function, however multiple sequences are not allowed. The 
-      <span class="strong"><strong>reduce</strong></span> function calls 
-      <span class="emphasis"><em>function</em></span> with first two consecutive elements in the sequence, obtains the result, calls 
-      <span class="emphasis"><em>function</em></span> with the result and the subsequent element in the sequence and so on until the end of the list and returns the final result:
-    </p>
-<pre class="programlisting">def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; reduce(mul, [1, 2, 3, 4])
-24
-
-</pre>
-<div class="section" title="5.1. List Comprehensions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="list-comprehensions"></a>5.1. List Comprehensions</h3></div></div></div>
-<p><a name="x_768"></a>List Comprehension is a convenvience utility provided by Python. It is a syntatic sugar to create 
-        <span class="emphasis"><em>Lists</em></span>. Using 
-        <span class="emphasis"><em>List Comprehensions</em></span> one can create 
-        <span class="emphasis"><em>Lists</em></span> from other type of sequential data structures or other 
-        <span class="emphasis"><em>Lists</em></span> itself. The syntax of 
-        <span class="emphasis"><em>List Comprehensions</em></span> consists of a square brackets to indicate the result is a 
-        <span class="emphasis"><em>List</em></span> within which we include at least one 
-        <span class="strong"><strong>for</strong></span> clause and multiple 
-        <span class="strong"><strong>if</strong></span> clauses. It will be more clear with an example:
-      </p>
-<pre class="programlisting">&gt;&gt;&gt; num = [1, 2, 3]
-&gt;&gt;&gt; sq = [x*x for x in num]
-&gt;&gt;&gt; sq
-[1, 4, 9]
-&gt;&gt;&gt; all_num = [1, 2, 3, 4, 5, 6, 7, 8, 9]
-&gt;&gt;&gt; even = [x for x in all_num if x%2 == 0]
-
-</pre>
-<p><a name="x_769"></a>The syntax used here is very clear from the way it is written. It can be translated into english as, "for each element x in the list all_num, if remainder of x divided by 2 is 0, add x to the list."</p>
-</div>
-</div>
-</div>
-<div class="navfooter">
-<hr>
-<table width="100%" summary="Navigation footer">
-<tr>
-<td width="40%" align="left">
-<a accesskey="p" href="index.html">Prev</a> </td>
-<td width="20%" align="center"> </td>
-<td width="40%" align="right"> </td>
-</tr>
-<tr>
-<td width="40%" align="left" valign="top">Chapter 1.  </td>
-<td width="20%" align="center"> </td>
-<td width="40%" align="right" valign="top"> </td>
-</tr>
-</table>
-</div>
-</body>
-</html>
--- a/web/html/ch01-intro.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,692 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Basic Python</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<!--<div class="navheader">
-<table width="100%" summary="Navigation header">
-<tr><th colspan="3" align="center">Basic Python</th></tr>
-<tr>
-<td width="20%" align="left">
-
-<th width="60%" align="center"> </th>
-<td width="20%" align="right"> </td>
-</tr>
-</table>
-<hr>
-</div>  -->
-<div>
-	<form style="margin-left: 800" method="POST" action="/review/hello">
-		<input id="id_q" type="text" name="q"/>
-		<input type="submit" value="Go"/>
-	</form>
-</div>
-
-<div class="chapter" lang="en" id="chap_intro">
-<div class="article" title="Basic Python">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2988867"></a>Basic Python</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#introduction">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#the-python-interpreter">2. The Python Interpreter</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#the-interactive-interpreter">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#ipython-an-enhanced-interactive-python-interpreter">2.2. 
-        <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter
-      </a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#editing-and-running-a-python-file">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#basic-datatypes-and-operators-in-python">4. Basic Datatypes and operators in Python</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#numbers">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#variables">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#strings">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#boolean">4.4. Boolean</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#the-while-loop">5. The 
-      <span class="strong"><strong>while</strong></span> loop
-    </a></span></dt>
-<dt><span class="section"><a href="#the-if-conditional">6. The 
-      <span class="strong"><strong>if</strong></span> conditional
-    </a></span></dt>
-<dt><span class="section"><a href="#raw_input">7.       <span class="strong"><strong>raw_input()</strong></span>
-    </a></span></dt>
-<dt><span class="section"><a href="#int-method">8. 
-      <span class="strong"><strong>int()</strong></span> method
-    </a></span></dt>
-</dl>
-</div>
-<p id="x_38"></a>This document is intended to be handed out at the end of the workshop. It has been designed for Engineering students who are Python beginners and have basic programming skills. The focus is on basic numerics and plotting using Python.</p>
-<p id="x_39"></a>The system requirements:</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_3a"></a>Python - version 2.5.x or newer.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_3b"></a>IPython</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_3c"></a>Text editor - scite, vim, emacs or whatever you are comfortable with.</p></li>
-</ul></div>
-<div class="section" title="1. Introduction">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="introduction"></a>1. Introduction</h2></div></div></div>
-<p id="x_3d"></a>The Python programming language was created by a dutch named Guido van Rossum. The idea of Python was conceived in December 1989. The name Python has nothing to do with the reptilian, but its been named after the 70s comedy series "Monty Python's Flying Circus", since it happens to be Guido's favourite TV series.</p>
-<p id="x_3e"></a>Current stable version of Python is 2.6.x, although Python 3.0 is also the stable version, it is not backwards compatible with the previous versions and is hence not entirely popular at the moment. This material will focus on the 2.6.x series.</p>
-<p id="x_3f"></a>Python is licensed under the Python Software Foundation License (PSF License) which is GPL compatible Free Software license (excepting license version 1.6 and 2.0) It is a no strings attached license, which means the source code is free to modify and redistribute.</p>
-<p id="x_40"></a>The Python docs define Python as "Python is an interpreted, object-oriented, high-level programming language with dynamic semantics." A more detailed summary can be found at 
-      <a class="ulink" href="http://www.python.org/doc/essays/blurb.html" target="_top">http://www.python.org/doc/essays/blurb.html</a>. Python is a language that has been designed to help the programmer concentrate on solving the problem at hand and not worry about the programming language idiosyncrasies.
-    </p>
-<p id="x_41"></a>Python is a highly cross platform compatible language on account of it being an interpreted language. It is highly scalable and hence has been adapted to run on the Nokia 60 series phones. Python has been designed to be readable and easy to use</p>
-<p id="x_42"></a>
-      <span class="strong"><strong>Resources available for reference</strong></span>
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_43"></a>Web: 
-          <a class="ulink" href="http://www.python.org" target="_top">http://www.python.org</a>
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_44"></a>Doc: 
-          <a class="ulink" href="http://www.python.org/doc" target="_top">http://www.python.org/doc</a>
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_45"></a>Free Tutorials: 
-          <span class="emphasis"><em> Official Python Tutorial: 
-            <a class="ulink" href="http://docs.python.org/tut/tut.html" target="_top">http://docs.python.org/tut/tut.html</a> 
-          </em></span> Byte of Python: 
-          <a class="ulink" href="http://www.byteofpython.info" target="_top">http://www.byteofpython.info</a>/ * Dive into Python: 
-          <a class="ulink" href="http://diveintopython.org" target="_top">http://diveintopython.org</a>/
-        </p></li>
-</ul></div>
-<p id="x_46"></a>
-      <span class="strong"><strong>Advantages of Python - Why Python??</strong></span>
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_47"></a>Python has been designed for readability and ease of use. Its been designed in  such a fashion that it imposes readability on the programmer. Python does away with the braces and the semicolons and instead implements code blocks based on indentation, thus enhancing readability.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_48"></a>Python is a high level, interpreted, modular and object oriented language. Python performs memory management on its own, thus the programmer need not bother about allocating and deallocating memory to variables. Python provides extensibility by providing modules which can be easily imported similar to headers in C and packages in Java. Python is object oriented and hence provides all the object oriented characteristics such as inheritance, encapsulation and polymorphism.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_49"></a>Python offers a highly powerful interactive programming interface in the form of the 'Interactive Interpreter' which will be discussed in more detail in the following sections.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_4a"></a>Python provides a rich standard library and an extensive set of modules. The  power of Python modules can be seen in this slightly exaggerated cartoon 
-          <a class="ulink" href="http://xkcd.com/353" target="_top">http://xkcd.com/353</a>/
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_4b"></a>Python interfaces well with most other programming languages such as C, C++  and FORTRAN.</p></li>
-</ul></div>
-<p id="x_4c"></a>Although, Python has one setback. Python is not fast as some of the compiled languages like C or C++. Yet, the amount of flexibility and power more than make up for this setback.</p>
-</div>
-<div class="section" title="2. The Python Interpreter">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-python-interpreter"></a>2. The Python Interpreter</h2></div></div></div>
-<div class="section" title="2.1. The Interactive Interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="the-interactive-interpreter"></a>2.1. The Interactive Interpreter</h3></div></div></div>
-<p id="x_4d"></a>Typing 
-        <span class="emphasis"><em>python</em></span> at the shell prompt on any standard Unix/Gnu-Linux system and hitting the enter key fires up the Python 'Interactive Interpreter'. The Python interpreter is one of the most integral features of Python. The prompt obtained when the interactive interpreter is similar to what is shown below. The exact appearance might differ based on the version of Python being used. The 
-        <code class="literal">&gt;&gt;&gt;</code> thing shown is the python prompt. When something is typed at the prompt and the enter key is hit, the python interpreter interprets the command entered and performs the appropriate action. All the examples presented in this document are to be tried hands on, on the interactive interpreter.
-      </p>
-<pre class="programlisting">Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
-[GCC 4.3.2] on linux2
-Type "help", "copyright", "credits" or "license" for more information.
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_4e"></a>Lets try with an example, type 
-        <code class="literal">print 'Hello, World!'</code> at the prompt and hit the enter key.
-      </p>
-<pre class="programlisting">&gt;&gt;&gt; print 'Hello, World!'
-Hello, World!
-
-</pre>
-<p id="x_4f"></a>This example was quite straight forward, and thus we have written our first line of Python code. Now let us try typing something arbitrary at the prompt. For example:</p>
-<pre class="programlisting">&gt;&gt;&gt; arbit word
-  File "&lt;stdin&gt;", line 1
-    arbit word
-            ^
-SyntaxError: invalid syntax
-&gt;&gt;&gt;
-
-</pre>
-<p id="x_50"></a>The interpreter gave an error message saying that 'arbit word' was invalid syntax which is valid. The interpreter is an amazing tool when learning to program in Python. The interpreter provides a help function that provides the necessary documentation regarding all Python syntax, constructs, modules and objects. Typing 
-        <span class="emphasis"><em>help()</em></span> at the prompt gives the following output:
-      </p>
-<pre class="programlisting">&gt;&gt;&gt; help()
-
-Welcome to Python 2.5!  This is the online help utility.
-
-If this is your first time using Python, you should definitely check out
-the tutorial on the Internet at http://www.python.org/doc/tut/.
-
-Enter the name of any module, keyword, or topic to get help on writing
-Python programs and using Python modules.  To quit this help utility and
-return to the interpreter, just type "quit".
-
-To get a list of available modules, keywords, or topics, type "modules",
-"keywords", or "topics".  Each module also comes with a one-line summary
-of what it does; to list the modules whose summaries contain a given word
-such as "spam", type "modules spam".
-
-help&gt; 
-
-
-</pre>
-<p id="x_51"></a>As mentioned in the output, entering the name of any module, keyword or topic will provide the documentation and help regarding the same through the online help utility. Pressing 
-        <span class="emphasis"><em>Ctrl+d</em></span> exits the help prompt and returns to the python prompt.
-      </p>
-<p id="x_52"></a>Let us now try a few examples at the python interpreter.</p>
-<p id="x_53"></a>Eg 1:</p>
-<pre class="programlisting">&gt;&gt;&gt; print 'Hello, python!'
-Hello, python!
-&gt;&gt;&gt;
-
-</pre>
-<p id="x_54"></a>Eg 2:</p>
-<pre class="programlisting">&gt;&gt;&gt; print 4321*567890
-2453852690
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_55"></a>Eg 3:</p>
-<pre class="programlisting">&gt;&gt;&gt; 4321*567890
-2453852690L
-&gt;&gt;&gt;
-
-</pre>
-<pre class="programlisting">Note: Notice the 'L' at the end of the output. The 'L' signifies that the
-output of the operation is of type *long*. It was absent in the previous
-example because we used the print statement. This is because *print* formats
-the output before displaying.
-
-</pre>
-<p id="x_56"></a>Eg 4:</p>
-<pre class="programlisting">&gt;&gt;&gt; big = 12345678901234567890 ** 3
-&gt;&gt;&gt; print big
-1881676372353657772490265749424677022198701224860897069000
-&gt;&gt;&gt; 
-
-</pre>
-<pre class="programlisting">This example is to show that unlike in C or C++ there is no limit on the
-value of an integer.
-
-</pre>
-<p id="x_57"></a>Try this on the interactive interpreter: 
-        <code class="literal">import this</code>
-      </p>
-<p id="x_58"></a>
-        <span class="emphasis"><em>Hint: The output gives an idea of Power of Python</em></span>
-      </p>
-</div>
-<div class="section" title="2.2.  ipython - An enhanced interactive Python interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="ipython-an-enhanced-interactive-python-interpreter"></a>2.2. 
-        <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter
-      </h3></div></div></div>
-<p id="x_59"></a>The power and the importance of the interactive interpreter was the highlight of the previous section. This section provides insight into the enhanced interpreter with more advanced set of features called 
-        <span class="strong"><strong>ipython</strong></span>. Entering 
-        <span class="emphasis"><em>ipython</em></span> at the shell prompt fires up the interactive interpreter.
-      </p>
-<pre class="programlisting">$ ipython
-Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
-Type "copyright", "credits" or "license" for more information.
-
-IPython 0.8.4 -- An enhanced Interactive Python.
-?         -&gt; Introduction and overview of IPython's features.
-%quickref -&gt; Quick reference.
-help      -&gt; Python's own help system.
-object?   -&gt; Details about 'object'. ?object also works, ?? prints more.
-
-In [1]: 
-
-</pre>
-<p id="x_5a"></a>This is the output obtained upon firing ipython. The exact appearance may change based on the Python version installed. The following are some of the various features provided by 
-        <span class="strong"><strong>ipython</strong></span>:
-      </p>
-<div class="variablelist"><dl>
-<dt><span class="term"></span></dt>
-<dd>
-<p></p>
-<p id="x_5b"></a>Suggestions - ipython provides suggestions of the possible methods and operations available for the given python object.</p>
-</dd>
-</dl></div>
-<p id="x_5c"></a>Eg 5:</p>
-<pre class="programlisting">In [4]: a = 6
-
-In [5]: a.
-a.__abs__           a.__divmod__        a.__index__         a.__neg__          a.__rand__          a.__rmod__          a.__rxor__
-a.__add__           a.__doc__           a.__init__          a.__new__          a.__rdiv__          a.__rmul__          a.__setattr__
-a.__and__           a.__float__         a.__int__           a.__nonzero__      a.__rdivmod__       a.__ror__           a.__str__
-a.__class__         a.__floordiv__      a.__invert__        a.__oct__          a.__reduce__        a.__rpow__          a.__sub__
-a.__cmp__           a.__getattribute__  a.__long__          a.__or__           a.__reduce_ex__     a.__rrshift__       a.__truediv__
-a.__coerce__        a.__getnewargs__    a.__lshift__        a.__pos__          a.__repr__          a.__rshift__        a.__xor__
-a.__delattr__       a.__hash__          a.__mod__           a.__pow__          a.__rfloordiv__     a.__rsub__          
-a.__div__           a.__hex__           a.__mul__           a.__radd__         a.__rlshift__       a.__rtruediv__      
-
-</pre>
-<p id="x_5d"></a>In this example, we initialized 'a' (a variable - a concept that will be discussed in the subsequent sections.) to 6. In the next line when the 
-        <span class="emphasis"><em>tab</em></span> key is pressed after typing '
-        <span class="emphasis"><em>a.</em></span>' ipython displays the set of all possible methods that are applicable on the object 'a' (an integer in this context). Ipython provides many such datatype specific features which will be presented in the further sections as and when the datatypes are introduced.
-      </p>
-</div>
-</div>
-<div class="section" title="3. Editing and running a python file">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="editing-and-running-a-python-file"></a>3. Editing and running a python file</h2></div></div></div>
-<p id="x_5e"></a>The previous sections focused on the use of the interpreter to run python code. While the interpeter is an excellent tool to test simple solutions and experiment with small code snippets, its main disadvantage is that everything written in the interpreter is lost once its quit. Most of the times a program is used by people other than the author. So the programs have to be available in some form suitable for distribution, and hence they are written in files. This section will focus on editing and running python files. Start by opening a text editor ( it is recommended you choose one from the list at the top of this page ). In the editor type down python code and save the file with an extension 
-      <span class="strong"><strong>.py</strong></span> (python files have an extension of .py). Once done with the editing, save the file and exit the editor.
-    </p>
-<p id="x_5f"></a>Let us look at a simple example of calculating the gcd of 2 numbers using Python:</p>
-<p id="x_60"></a>
-      <span class="strong"><strong>Creating the first python script(file)</strong></span> :
-    </p>
-<pre class="programlisting">$ emacs gcd.py
-  def gcd(x,y):
-    if x % y == 0:
-      return y
-    return gcd(y, x%y)
-
-  print gcd(72, 92)
-
-</pre>
-<p id="x_61"></a>To run the script, open the shell prompt, navigate to the directory that contains the python file and run 
-      <code class="literal">python &lt;filename.py&gt;</code> at the prompt ( in this case filename is gcd.py )
-    </p>
-<p id="x_62"></a>
-      <span class="strong"><strong>Running the python script</strong></span> :
-    </p>
-<pre class="programlisting">$ python gcd.py
-4
-$ 
-
-</pre>
-<p id="x_63"></a>Another method to run a python script would be to include the line</p>
-<p id="x_64"></a>
-      <code class="literal">#! /usr/bin/python</code>
-    </p>
-<p id="x_65"></a>at the beginning of the python file and then make the file executable by</p>
-<p id="x_66"></a>$ chmod a+x 
-      <span class="emphasis"><em>filename.py</em></span>
-    </p>
-<p id="x_67"></a>Once this is done, the script can be run as a standalone program as follows:</p>
-<p id="x_68"></a>$ ./
-      <span class="emphasis"><em>filename.py</em></span>
-    </p>
-</div>
-<div class="section" title="4. Basic Datatypes and operators in Python">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="basic-datatypes-and-operators-in-python"></a>4. Basic Datatypes and operators in Python</h2></div></div></div>
-<p id="x_69"></a>Python provides the following set of basic datatypes.</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_6a"></a>Numbers: int, float, long, complex</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_6b"></a>Strings</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_6c"></a>Boolean</p></li>
-</ul></div></blockquote></div>
-<div class="section" title="4.1. Numbers">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="numbers"></a>4.1. Numbers</h3></div></div></div>
-<p id="x_6d"></a>Numbers were introduced in the examples presented in the interactive interpreter section. Numbers include types as mentioned earlier viz., int (integers), float (floating point numbers), long (large integers), complex (complex numbers with real and imaginary parts). Python is not a strongly typed language, which means the type of a variable need not mentioned during its initialization. Let us look at a few examples.</p>
-<p id="x_6e"></a>Eg 6:</p>
-<pre class="programlisting">&gt;&gt;&gt; a = 1 #here a is an integer variable
-
-</pre>
-<p id="x_6f"></a>Eg 7:</p>
-<pre class="programlisting">&gt;&gt;&gt; lng = 122333444455555666666777777788888888999999999 #here lng is a variable of type long
-&gt;&gt;&gt; lng
-122333444455555666666777777788888888999999999L #notice the trailing 'L'
-&gt;&gt;&gt; print lng
-122333444455555666666777777788888888999999999 #notice the absence of the trailing 'L'
-&gt;&gt;&gt; lng+1
-122333444455555666666777777788888889000000000L
-
-
-</pre>
-<p id="x_70"></a>Long numbers are the same as integers in almost all aspects. They can be used in operations just like integers and along with integers without any distinction. The only distinction comes during type checking (which is not a healthy practice). Long numbers are tucked with a trailing 'L' just to signify that they are long. Notice that in the example just lng at the prompt displays the value of the variable with the 'L' whereas 
-        <code class="literal">print lng</code> displays without the 'L'. This is because print formats the output before printing. Also in the example, notice that adding an integer to a long does not give any errors and the result is as expected. So for all practical purposes longs can be treated as ints.
-      </p>
-<p id="x_71"></a>Eg 8:</p>
-<pre class="programlisting">&gt;&gt;&gt; fl = 3.14159 #fl is a float variable
-&gt;&gt;&gt; e = 1.234e-4 #e is also a float variable, specified in the exponential form
-&gt;&gt;&gt; a = 1
-&gt;&gt;&gt; b = 2
-&gt;&gt;&gt; a/b #integer division
-0
-&gt;&gt;&gt; a/fl #floating point division
-0.31831015504887655
-&gt;&gt;&gt; e/fl
-3.9279473133031364e-05
-
-
-</pre>
-<p id="x_72"></a>Floating point numbers, simply called floats are real numbers with a decimal point. The example above shows the initialization of a float variable. Shown also in this example is the difference between integer division and floating point division. 'a' and 'b' here are integer variables and hence the division gives 0 as the quotient. When either of the operands is a float, the operation is a floating point division, and the result is also a float as illustrated.</p>
-<p id="x_73"></a>Eg 9:</p>
-<pre class="programlisting">&gt;&gt;&gt; cplx = 3 + 4j #cplx is a complex variable
-&gt;&gt;&gt; cplx
-(3+4j)
-&gt;&gt;&gt; print cplx.real #prints the real part of the complex number
-3.0
-&gt;&gt;&gt; print cplx.imag #prints the imaginary part of the complex number
-4.0
-&gt;&gt;&gt; print cplx*fl  #multiplies the real and imag parts of the complex number with the multiplier
-(9.42477+12.56636j)
-&gt;&gt;&gt; abs(cplx) #returns the absolute value of the complex number
-5.0
-
-</pre>
-<p id="x_74"></a>Python provides a datatype for complex numbers. Complex numbers are initialized as shown in the example above. The 
-        <span class="emphasis"><em>real</em></span> and 
-        <span class="emphasis"><em>imag</em></span> operators return the real and imaginary parts of the complex number as shown. The 
-        <span class="emphasis"><em>abs()</em></span> returns the absolute value of the complex number.
-      </p>
-</div>
-<div class="section" title="4.2. Variables">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="variables"></a>4.2. Variables</h3></div></div></div>
-<p id="x_75"></a>Variables are just names that represent a value. Variables have already been introduced in the various examples from the previous sections. Certain rules about using variables:</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_76"></a>Variables have to be initialized or assigned a value before being used.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_77"></a>Variable names can consist of letters, digits and 
-              <a class="link" href="">underscores</a> .
-            </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_78"></a>Variable names cannot begin with digits, but can contain digits in them.</p></li>
-</ul></div></blockquote></div>
-<p id="x_79"></a>In reference to the previous section examples, 'a', 'b', 'lng', 'fl', 'e' and 'cplx' are all variables of various datatypes.</p>
-<pre class="programlisting">Note: Python is not a strongly typed language and hence an integer variable can at a
-later stage be used as a float variable as well.
-
-</pre>
-</div>
-<div class="section" title="4.3. Strings">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="strings"></a>4.3. Strings</h3></div></div></div>
-<p id="x_7a"></a>Strings are one of the essential data structures of any programming language. The 
-        <code class="literal">print "Hello, World!"</code> program was introduced in the earlier section, and the 
-        <span class="emphasis"><em>"Hello, World!"</em></span> in the print statement is a string. A string is basically a set of characters. Strings can be represented in various ways shown below:
-      </p>
-<pre class="programlisting">s = 'this is a string'              # a string variable can be represented using single quotes
-s = 'This one has "quotes" inside!' # The string can have quotes inside it as shown
-s = "I have 'single-quotes' inside!"
-l = "A string spanning many lines\
-one more line\
-yet another"                        # a string can span more than a single line.
-t = """A triple quoted string does  # another way of representing multiline strings.
-not need to be escaped at the end and
-"can have nested quotes" etc."""
-
-</pre>
-<p id="x_7b"></a>Try the following on the interpreter: 
-        <code class="literal">s = 'this is a string with 'quotes' of similar kind'</code>
-      </p>
-<p id="x_7c"></a>
-        <span class="strong"><strong>Exercise: How to use single quotes within single quotes in a string as shown in the above example without getting an error?</strong></span>
-      </p>
-<div class="section" title="4.3.1. String operations">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="string-operations"></a>4.3.1. String operations</h4></div></div></div>
-<p id="x_7d"></a>A few basic string operations are presented here.</p>
-<p id="x_7e"></a>
-          <span class="strong"><strong>String concatenation</strong></span> String concatenation is done by simple addition of two strings.
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = 'Hello'
-&gt;&gt;&gt; y = ' Python'
-&gt;&gt;&gt; print x+y
-Hello Python
-
-</pre>
-<p id="x_7f"></a>          <span class="emphasis"><em>Try this yourself:</em></span>
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; somenum = 13
-&gt;&gt;&gt; print x+somenum
-
-</pre>
-<p id="x_80"></a>The problem with the above example is that here a string variable and an integer variable are trying to be concantenated. To obtain the desired result from the above example the str(), repr() and the `` can be used.</p>
-<p id="x_81"></a>
-          <span class="strong"><strong>str()</strong></span> simply converts a value to a string in a reasonable form. 
-          <span class="strong"><strong>repr()</strong></span> creates a string that is a representation of the value.
-        </p>
-<p id="x_82"></a>The difference can be seen in the example shown below:</p>
-<pre class="programlisting">&gt;&gt;&gt; str(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000'
-&gt;&gt;&gt; repr(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000L'
-
-</pre>
-<p id="x_83"></a>It can be observed that the 'L' in the long value shown was omitted by str(), whereas repr() converted that into a string too. An alternative way of using repr(value) is `
-          <code class="literal">value</code>`.
-        </p>
-<p id="x_84"></a>A few more examples:</p>
-<pre class="programlisting">&gt;&gt;&gt; x = "Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go 
-to Pycon
-
-</pre>
-<p id="x_85"></a>In the above example, notice that the '\n'(newline) character is formatted and the string is printed on two lines. The strings discussed until now were normal strings. Other than these there are two other types of strings namely, raw strings and unicode strings.</p>
-<p id="x_86"></a>
-          <span class="strong"><strong>Raw strings</strong></span> are strings which are unformatted, that is the backslashes(\) are not parsed and are left as it is in the string. Raw strings are represented with an 'r' at the start of a string. Let us look at an example
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = r"Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go \nto Pycon
-
-</pre>
-<p id="x_87"></a>Note: The '\n' is not being parsed into a new line and is left as it is.</p>
-<p id="x_88"></a>
-          <span class="emphasis"><em>Try this yourself:</em></span>
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = r"Let's go to Pycon\"
-
-</pre>
-<p id="x_89"></a>          <span class="strong"><strong>Unicode strings</strong></span> are strings where the characters are Unicode characters as opposed to ASCII characters. Unicode strings are represented with a 'u' at the start of the string. Let us look at an example:
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = u"Let's go to Pycon!"
-&gt;&gt;&gt; print x
-Let's go to Pycon!
-
-</pre>
-</div>
-</div>
-<div class="section" title="4.4. Boolean">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="boolean"></a>4.4. Boolean</h3></div></div></div>
-<p id="x_8a"></a>Python also provides special Boolean datatype. A boolean variable can assume a value of either 
-        <span class="emphasis"><em>True</em></span> or 
-        <span class="emphasis"><em>False</em></span> (Note the capitalizations).
-      </p>
-<p id="x_8b"></a>Let us look at examples:</p>
-<pre class="programlisting">&gt;&gt;&gt; t = True
-&gt;&gt;&gt; f = not t
-&gt;&gt;&gt; print f
-False
-&gt;&gt;&gt; f or t
-True
-&gt;&gt;&gt; f and t
-False
-
-</pre>
-</div>
-</div>
-<div class="section" title="5. The while loop">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-while-loop"></a>5. The 
-      <span class="strong"><strong>while</strong></span> loop
-    </h2></div></div></div>
-<p id="x_8c"></a>The Python 
-      <span class="strong"><strong>while</strong></span> loop is similar to the C/C++ while loop. The syntax is as follows:
-    </p>
-<pre class="programlisting">statement 0
-while condition:
-  statement 1 #while block
-  statement 2 #while block
-statement 3 #outside the while block.
-
-</pre>
-<p id="x_8d"></a>Let us look at an example:</p>
-<pre class="programlisting">&gt;&gt;&gt; x = 1  
-&gt;&gt;&gt; while x &lt;= 5:
-...   print x
-...   x += 1
-... 
-1
-2
-3
-4
-5
-
-</pre>
-</div>
-<div class="section" title="6. The if conditional">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-if-conditional"></a>6. The 
-      <span class="strong"><strong>if</strong></span> conditional
-    </h2></div></div></div>
-<p id="x_8e"></a>The Python 
-      <span class="strong"><strong>if</strong></span> block provides the conditional execution of statements. If the condition evaluates as true the block of statements defined under the if block are executed.
-    </p>
-<p id="x_8f"></a>If the first block is not executed on account of the condition not being satisfied, the set of statements in the 
-      <span class="strong"><strong>else</strong></span> block are executed.
-    </p>
-<p id="x_90"></a>The 
-      <span class="strong"><strong>elif</strong></span> block provides the functionality of evaluation of multiple conditions as shown in the example.
-    </p>
-<p id="x_91"></a>The syntax is as follows:</p>
-<pre class="programlisting">if condition :
-    statement_1
-    statement_2
-
-elif condition:
-    statement_3
-    statement_4
-else:
-    statement_5
-    statement_6
-
-</pre>
-<p id="x_92"></a>Let us look at an example:</p>
-<pre class="programlisting">&gt;&gt;&gt; n = raw_input("Input a number:")
-&gt;&gt;&gt; if n &lt; 0:
-      print n," is negative"
-      elif n &gt; 0:
-      print n," is positive"
-      else:
-      print n, " is 0"
-
-</pre>
-</div>
-<div class="section" title="7.  raw_input()">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="raw_input"></a>7.       <span class="strong"><strong>raw_input()</strong></span>
-    </h2></div></div></div>
-<p id="x_93"></a>In the previous example we saw the call to the raw_input() subroutine. The 
-      <span class="strong"><strong>raw_input()</strong></span> method is used to take user inputs through the console. Unlike 
-      <span class="strong"><strong>input()</strong></span> which assumes the data entered by the user as a standard python expression, 
-      <span class="strong"><strong>raw_input()</strong></span> treats all the input data as raw data and converts everything into a string. To illustrate this let us look at an example.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-121
-
-&gt;&gt;&gt; input("Enter your name:")
-Enter your name:PythonFreak
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-  File "&lt;string&gt;", line 1, in &lt;module&gt;
-NameError: name 'PythonFreak' is not defined
-
-</pre>
-<p id="x_94"></a>As shown above the 
-      <span class="strong"><strong>input()</strong></span> assumes that the data entered is a valid Python expression. In the first call it prompts for an integer input and when entered it accepts the integer as an integer, whereas in the second call, when the string is entered without the quotes, 
-      <span class="strong"><strong>input()</strong></span> assumes that the entered data is a valid Python expression and hence it raises and exception saying PythonFreak is not defined.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; input("Enter your name:")
-Enter your name:'PythonFreak'
-'PythonFreak'
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_95"></a>Here the name is accepted because its entered as a string (within quotes). But its unreasonable to go on using quotes each time a string is entered. Hence the alternative is to use 
-      <span class="strong"><strong>raw_input()</strong></span>.
-    </p>
-<p id="x_96"></a>Let us now look at how 
-      <span class="strong"><strong>raw_input()</strong></span> operates with an example.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; raw_input("Enter your name:")
-Enter your name:PythonFreak
-'PythonFreak'
-
-</pre>
-<p id="x_97"></a>Observe that the 
-      <span class="strong"><strong>raw_input()</strong></span> is converting it into a string all by itself.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-'121'
-
-</pre>
-<p id="x_98"></a>Observe that 
-      <span class="strong"><strong>raw_input()</strong></span> is converting the integer 121 also to a string as '121'. Let us look at another example:
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-&gt;&gt;&gt; pal + 2
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: cannot concatenate 'str' and 'int' objects
-&gt;&gt;&gt; pal
-'121'
-
-</pre>
-<p id="x_99"></a>Observe here that the variable 
-      <span class="emphasis"><em>pal</em></span> is a string and hence integer operations cannot be performed on it. Hence the exception is raised.
-    </p>
-</div>
-<div class="section" title="8.  int() method">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="int-method"></a>8. 
-      <span class="strong"><strong>int()</strong></span> method
-    </h2></div></div></div>
-<p id="x_9a"></a>Generally for computing purposes, the data used is not strings or raw data but on integers, floats and similar mathematical data structures. The data obtained from 
-      <span class="strong"><strong>raw_input()</strong></span> is raw data in the form of strings. In order to obtain integers from strings we use the method 
-      <span class="strong"><strong>int()</strong></span>.
-    </p>
-<p id="x_9b"></a>Let us look at an example.</p>
-<pre class="programlisting">&gt;&gt;&gt; intpal = int(pal)
-&gt;&gt;&gt; intpal
-121
-
-</pre>
-<p id="x_9c"></a>In the previous example it was observed that 
-      <span class="emphasis"><em>pal</em></span> was a string variable. Here using the 
-      <span class="strong"><strong>int()</strong></span> method the string 
-      <span class="emphasis"><em>pal</em></span> was converted to an integer variable.
-    </p>
-<p id="x_9d"></a>
-      <span class="emphasis"><em>Try This Yourself:</em></span>
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; stringvar = raw_input("Enter a name:")
-Enter a name:Guido Van Rossum
-&gt;&gt;&gt; stringvar
-'Guido Van Rossum'
-&gt;&gt;&gt; numvar = int(stringvar)
-
-</pre>
-</div>
-</div>
-<div class="navfooter">
-<hr>
-<table width="100%" summary="Navigation footer">
-<tr>
-<td width="40%" align="left">
-<a accesskey="p" href="index.html">Prev</a> </td>
-<td width="20%" align="center"> </td>
-<td width="40%" align="right"> </td>
-</tr>
-<tr>
-<td width="40%" align="left" valign="top">Chapter 1. Introduction </td>
-<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
-<td width="40%" align="right" valign="top"> </td>
-</tr>
-</table>
-</div>
-</body>
-</html>
--- a/web/html/ch01-introduction.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,44 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. </title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 1. ">
-<div class="chapter" lang="en" id="chap_intro">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2560661">Introduction to the Course</a></span></dt></dl>
-</div>
-<div class="article" title="Introduction to the Course">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2560661"></a>Introduction to the Course</h2></div></div>
-<hr>
-</div>
-<p id="x_1"></a>Engineering students use computers for a large number of curricular tasks – mostly computation centred. However, they do not see this as coding or programming tasks and usually are not even aware of the tools and techniques that will help them to handle these tasks better. This results in less than optimal use of their time and resources. This also causes difficulties when it comes tocollaboration and building on other people’s work. This course is intended to train such students in good software practices and tools for producing code and documentation.</p>
-<p id="x_2"></a>After successfully completing the program, the participants will be able to:</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="-">
-<li class="listitem" style="list-style-type: -"><p id="x_3"></a>understand how software tools work together and how they can be used in tandem to carry out tasks,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_4"></a>use unix command line tools to carry out common (mostly text processing tasks,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_5"></a>to generate professional documents,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_6"></a>use version control effectively – for both code and documents,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_7"></a>automate tasks by writing shell scripts and python scripts,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_8"></a>realise the impact of coding style and readbility on quality,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_9"></a>write mid-sized programs that carry out typical engineering / numerical computations such as those that involve (basic) manipulation of large arrays in an efficient manner,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_a"></a>generate 2D and simple 3D plots,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_b"></a>debug programs using a standardised approach,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_c"></a>understand the importance of tests and the philosophy of Test Driven Development,</p></li>
-<li class="listitem" style="list-style-type: -"><p id="x_d"></a>write unit tests and improve the quality of code.</p></li>
-</ul></div>
-</div>
-</div>
-
-</body>
-</html>
--- a/web/html/ch02-basic_intro.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,658 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Basic Python</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" lang="en" id="chap02_basic">
-<div class="article" title="Basic Python">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2957059"></a>Basic Python</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#introduction">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#the-python-interpreter">2. The Python Interpreter</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#the-interactive-interpreter">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#ipython-an-enhanced-interactive-python-interpreter">2.2. 
-        <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter
-      </a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#editing-and-running-a-python-file">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#basic-datatypes-and-operators-in-python">4. Basic Datatypes and operators in Python</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#numbers">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#variables">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#strings">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#boolean">4.4. Boolean</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#the-while-loop">5. The 
-      <span class="strong"><strong>while</strong></span> loop
-    </a></span></dt>
-<dt><span class="section"><a href="#the-if-conditional">6. The 
-      <span class="strong"><strong>if</strong></span> conditional
-    </a></span></dt>
-<dt><span class="section"><a href="#raw_input">7.       <span class="strong"><strong>raw_input()</strong></span>
-    </a></span></dt>
-<dt><span class="section"><a href="#int-method">8. 
-      <span class="strong"><strong>int()</strong></span> method
-    </a></span></dt>
-</dl>
-</div>
-<p id="x_197"></a>This document is intended to be handed out at the end of the workshop. It has been designed for Engineering students who are Python beginners and have basic programming skills. The focus is on basic numerics and plotting using Python.</p>
-<p id="x_198"></a>The system requirements:</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_199"></a>Python - version 2.5.x or newer.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_19a"></a>IPython</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_19b"></a>Text editor - scite, vim, emacs or whatever you are comfortable with.</p></li>
-</ul></div>
-<div class="section" title="1. Introduction">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="introduction"></a>1. Introduction</h2></div></div></div>
-<p id="x_19c"></a>The Python programming language was created by a dutch named Guido van Rossum. The idea of Python was conceived in December 1989. The name Python has nothing to do with the reptilian, but its been named after the 70s comedy series "Monty Python's Flying Circus", since it happens to be Guido's favourite TV series.</p>
-<p id="x_19d"></a>Current stable version of Python is 2.6.x, although Python 3.0 is also the stable version, it is not backwards compatible with the previous versions and is hence not entirely popular at the moment. This material will focus on the 2.6.x series.</p>
-<p id="x_19e"></a>Python is licensed under the Python Software Foundation License (PSF License) which is GPL compatible Free Software license (excepting license version 1.6 and 2.0) It is a no strings attached license, which means the source code is free to modify and redistribute.</p>
-<p id="x_19f"></a>The Python docs define Python as "Python is an interpreted, object-oriented, high-level programming language with dynamic semantics." A more detailed summary can be found at 
-      <a class="ulink" href="http://www.python.org/doc/essays/blurb.html" target="_top">http://www.python.org/doc/essays/blurb.html</a>. Python is a language that has been designed to help the programmer concentrate on solving the problem at hand and not worry about the programming language idiosyncrasies.
-    </p>
-<p id="x_1a0"></a>Python is a highly cross platform compatible language on account of it being an interpreted language. It is highly scalable and hence has been adapted to run on the Nokia 60 series phones. Python has been designed to be readable and easy to use</p>
-<p id="x_1a1"></a>
-      <span class="strong"><strong>Resources available for reference</strong></span>
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_1a2"></a>Web: 
-          <a class="ulink" href="http://www.python.org" target="_top">http://www.python.org</a>
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1a3"></a>Doc: 
-          <a class="ulink" href="http://www.python.org/doc" target="_top">http://www.python.org/doc</a>
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1a4"></a>Free Tutorials: 
-          <span class="emphasis"><em> Official Python Tutorial: 
-            <a class="ulink" href="http://docs.python.org/tut/tut.html" target="_top">http://docs.python.org/tut/tut.html</a> 
-          </em></span> Byte of Python: 
-          <a class="ulink" href="http://www.byteofpython.info" target="_top">http://www.byteofpython.info</a>/ * Dive into Python: 
-          <a class="ulink" href="http://diveintopython.org" target="_top">http://diveintopython.org</a>/
-        </p></li>
-</ul></div>
-<p id="x_1a5"></a>
-      <span class="strong"><strong>Advantages of Python - Why Python??</strong></span>
-    </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_1a6"></a>Python has been designed for readability and ease of use. Its been designed in  such a fashion that it imposes readability on the programmer. Python does away with the braces and the semicolons and instead implements code blocks based on indentation, thus enhancing readability.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1a7"></a>Python is a high level, interpreted, modular and object oriented language. Python performs memory management on its own, thus the programmer need not bother about allocating and deallocating memory to variables. Python provides extensibility by providing modules which can be easily imported similar to headers in C and packages in Java. Python is object oriented and hence provides all the object oriented characteristics such as inheritance, encapsulation and polymorphism.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1a8"></a>Python offers a highly powerful interactive programming interface in the form of the 'Interactive Interpreter' which will be discussed in more detail in the following sections.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1a9"></a>Python provides a rich standard library and an extensive set of modules. The  power of Python modules can be seen in this slightly exaggerated cartoon 
-          <a class="ulink" href="http://xkcd.com/353" target="_top">http://xkcd.com/353</a>/
-        </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1aa"></a>Python interfaces well with most other programming languages such as C, C++  and FORTRAN.</p></li>
-</ul></div>
-<p id="x_1ab"></a>Although, Python has one setback. Python is not fast as some of the compiled languages like C or C++. Yet, the amount of flexibility and power more than make up for this setback.</p>
-</div>
-<div class="section" title="2. The Python Interpreter">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-python-interpreter"></a>2. The Python Interpreter</h2></div></div></div>
-<div class="section" title="2.1. The Interactive Interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="the-interactive-interpreter"></a>2.1. The Interactive Interpreter</h3></div></div></div>
-<p id="x_1ac"></a>Typing 
-        <span class="emphasis"><em>python</em></span> at the shell prompt on any standard Unix/Gnu-Linux system and hitting the enter key fires up the Python 'Interactive Interpreter'. The Python interpreter is one of the most integral features of Python. The prompt obtained when the interactive interpreter is similar to what is shown below. The exact appearance might differ based on the version of Python being used. The 
-        <code class="literal">&gt;&gt;&gt;</code> thing shown is the python prompt. When something is typed at the prompt and the enter key is hit, the python interpreter interprets the command entered and performs the appropriate action. All the examples presented in this document are to be tried hands on, on the interactive interpreter.
-      </p>
-<pre class="programlisting">Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
-[GCC 4.3.2] on linux2
-Type "help", "copyright", "credits" or "license" for more information.
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_1ad"></a>Lets try with an example, type 
-        <code class="literal">print 'Hello, World!'</code> at the prompt and hit the enter key.
-      </p>
-<pre class="programlisting">&gt;&gt;&gt; print 'Hello, World!'
-Hello, World!
-
-</pre>
-<p id="x_1ae"></a>This example was quite straight forward, and thus we have written our first line of Python code. Now let us try typing something arbitrary at the prompt. For example:</p>
-<pre class="programlisting">&gt;&gt;&gt; arbit word
-  File "&lt;stdin&gt;", line 1
-    arbit word
-            ^
-SyntaxError: invalid syntax
-&gt;&gt;&gt;
-
-</pre>
-<p id="x_1af"></a>The interpreter gave an error message saying that 'arbit word' was invalid syntax which is valid. The interpreter is an amazing tool when learning to program in Python. The interpreter provides a help function that provides the necessary documentation regarding all Python syntax, constructs, modules and objects. Typing 
-        <span class="emphasis"><em>help()</em></span> at the prompt gives the following output:
-      </p>
-<pre class="programlisting">&gt;&gt;&gt; help()
-
-Welcome to Python 2.5!  This is the online help utility.
-
-If this is your first time using Python, you should definitely check out
-the tutorial on the Internet at http://www.python.org/doc/tut/.
-
-Enter the name of any module, keyword, or topic to get help on writing
-Python programs and using Python modules.  To quit this help utility and
-return to the interpreter, just type "quit".
-
-To get a list of available modules, keywords, or topics, type "modules",
-"keywords", or "topics".  Each module also comes with a one-line summary
-of what it does; to list the modules whose summaries contain a given word
-such as "spam", type "modules spam".
-
-help&gt; 
-
-
-</pre>
-<p id="x_1b0"></a>As mentioned in the output, entering the name of any module, keyword or topic will provide the documentation and help regarding the same through the online help utility. Pressing 
-        <span class="emphasis"><em>Ctrl+d</em></span> exits the help prompt and returns to the python prompt.
-      </p>
-<p id="x_1b1"></a>Let us now try a few examples at the python interpreter.</p>
-<p id="x_1b2"></a>Eg 1:</p>
-<pre class="programlisting">&gt;&gt;&gt; print 'Hello, python!'
-Hello, python!
-&gt;&gt;&gt;
-
-</pre>
-<p id="x_1b3"></a>Eg 2:</p>
-<pre class="programlisting">&gt;&gt;&gt; print 4321*567890
-2453852690
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_1b4"></a>Eg 3:</p>
-<pre class="programlisting">&gt;&gt;&gt; 4321*567890
-2453852690L
-&gt;&gt;&gt;
-
-</pre>
-<pre class="programlisting">Note: Notice the 'L' at the end of the output. The 'L' signifies that the
-output of the operation is of type *long*. It was absent in the previous
-example because we used the print statement. This is because *print* formats
-the output before displaying.
-
-</pre>
-<p id="x_1b5"></a>Eg 4:</p>
-<pre class="programlisting">&gt;&gt;&gt; big = 12345678901234567890 ** 3
-&gt;&gt;&gt; print big
-1881676372353657772490265749424677022198701224860897069000
-&gt;&gt;&gt; 
-
-</pre>
-<pre class="programlisting">This example is to show that unlike in C or C++ there is no limit on the
-value of an integer.
-
-</pre>
-<p id="x_1b6"></a>Try this on the interactive interpreter: 
-        <code class="literal">import this</code>
-      </p>
-<p id="x_1b7"></a>
-        <span class="emphasis"><em>Hint: The output gives an idea of Power of Python</em></span>
-      </p>
-</div>
-<div class="section" title="2.2.  ipython - An enhanced interactive Python interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="ipython-an-enhanced-interactive-python-interpreter"></a>2.2. 
-        <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter
-      </h3></div></div></div>
-<p id="x_1b8"></a>The power and the importance of the interactive interpreter was the highlight of the previous section. This section provides insight into the enhanced interpreter with more advanced set of features called 
-        <span class="strong"><strong>ipython</strong></span>. Entering 
-        <span class="emphasis"><em>ipython</em></span> at the shell prompt fires up the interactive interpreter.
-      </p>
-<pre class="programlisting">$ ipython
-Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
-Type "copyright", "credits" or "license" for more information.
-
-IPython 0.8.4 -- An enhanced Interactive Python.
-?         -&gt; Introduction and overview of IPython's features.
-%quickref -&gt; Quick reference.
-help      -&gt; Python's own help system.
-object?   -&gt; Details about 'object'. ?object also works, ?? prints more.
-
-In [1]: 
-
-</pre>
-<p id="x_1b9"></a>This is the output obtained upon firing ipython. The exact appearance may change based on the Python version installed. The following are some of the various features provided by 
-        <span class="strong"><strong>ipython</strong></span>:
-      </p>
-<div class="variablelist"><dl>
-<dt><span class="term"></span></dt>
-<dd>
-<p></p>
-<p id="x_1ba"></a>Suggestions - ipython provides suggestions of the possible methods and operations available for the given python object.</p>
-</dd>
-</dl></div>
-<p id="x_1bb"></a>Eg 5:</p>
-<pre class="programlisting">In [4]: a = 6
-
-In [5]: a.
-a.__abs__           a.__divmod__        a.__index__         a.__neg__          a.__rand__          a.__rmod__          a.__rxor__
-a.__add__           a.__doc__           a.__init__          a.__new__          a.__rdiv__          a.__rmul__          a.__setattr__
-a.__and__           a.__float__         a.__int__           a.__nonzero__      a.__rdivmod__       a.__ror__           a.__str__
-a.__class__         a.__floordiv__      a.__invert__        a.__oct__          a.__reduce__        a.__rpow__          a.__sub__
-a.__cmp__           a.__getattribute__  a.__long__          a.__or__           a.__reduce_ex__     a.__rrshift__       a.__truediv__
-a.__coerce__        a.__getnewargs__    a.__lshift__        a.__pos__          a.__repr__          a.__rshift__        a.__xor__
-a.__delattr__       a.__hash__          a.__mod__           a.__pow__          a.__rfloordiv__     a.__rsub__          
-a.__div__           a.__hex__           a.__mul__           a.__radd__         a.__rlshift__       a.__rtruediv__      
-
-</pre>
-<p id="x_1bc"></a>In this example, we initialized 'a' (a variable - a concept that will be discussed in the subsequent sections.) to 6. In the next line when the 
-        <span class="emphasis"><em>tab</em></span> key is pressed after typing '
-        <span class="emphasis"><em>a.</em></span>' ipython displays the set of all possible methods that are applicable on the object 'a' (an integer in this context). Ipython provides many such datatype specific features which will be presented in the further sections as and when the datatypes are introduced.
-      </p>
-</div>
-</div>
-<div class="section" title="3. Editing and running a python file">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="editing-and-running-a-python-file"></a>3. Editing and running a python file</h2></div></div></div>
-<p id="x_1bd"></a>The previous sections focused on the use of the interpreter to run python code. While the interpeter is an excellent tool to test simple solutions and experiment with small code snippets, its main disadvantage is that everything written in the interpreter is lost once its quit. Most of the times a program is used by people other than the author. So the programs have to be available in some form suitable for distribution, and hence they are written in files. This section will focus on editing and running python files. Start by opening a text editor ( it is recommended you choose one from the list at the top of this page ). In the editor type down python code and save the file with an extension 
-      <span class="strong"><strong>.py</strong></span> (python files have an extension of .py). Once done with the editing, save the file and exit the editor.
-    </p>
-<p id="x_1be"></a>Let us look at a simple example of calculating the gcd of 2 numbers using Python:</p>
-<p id="x_1bf"></a>
-      <span class="strong"><strong>Creating the first python script(file)</strong></span> :
-    </p>
-<pre class="programlisting">$ emacs gcd.py
-  def gcd(x,y):
-    if x % y == 0:
-      return y
-    return gcd(y, x%y)
-
-  print gcd(72, 92)
-
-</pre>
-<p id="x_1c0"></a>To run the script, open the shell prompt, navigate to the directory that contains the python file and run 
-      <code class="literal">python &lt;filename.py&gt;</code> at the prompt ( in this case filename is gcd.py )
-    </p>
-<p id="x_1c1"></a>
-      <span class="strong"><strong>Running the python script</strong></span> :
-    </p>
-<pre class="programlisting">$ python gcd.py
-4
-$ 
-
-</pre>
-<p id="x_1c2"></a>Another method to run a python script would be to include the line</p>
-<p id="x_1c3"></a>
-      <code class="literal">#! /usr/bin/python</code>
-    </p>
-<p id="x_1c4"></a>at the beginning of the python file and then make the file executable by</p>
-<p id="x_1c5"></a>$ chmod a+x 
-      <span class="emphasis"><em>filename.py</em></span>
-    </p>
-<p id="x_1c6"></a>Once this is done, the script can be run as a standalone program as follows:</p>
-<p id="x_1c7"></a>$ ./
-      <span class="emphasis"><em>filename.py</em></span>
-    </p>
-</div>
-<div class="section" title="4. Basic Datatypes and operators in Python">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="basic-datatypes-and-operators-in-python"></a>4. Basic Datatypes and operators in Python</h2></div></div></div>
-<p id="x_1c8"></a>Python provides the following set of basic datatypes.</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_1c9"></a>Numbers: int, float, long, complex</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1ca"></a>Strings</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1cb"></a>Boolean</p></li>
-</ul></div></blockquote></div>
-<div class="section" title="4.1. Numbers">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="numbers"></a>4.1. Numbers</h3></div></div></div>
-<p id="x_1cc"></a>Numbers were introduced in the examples presented in the interactive interpreter section. Numbers include types as mentioned earlier viz., int (integers), float (floating point numbers), long (large integers), complex (complex numbers with real and imaginary parts). Python is not a strongly typed language, which means the type of a variable need not mentioned during its initialization. Let us look at a few examples.</p>
-<p id="x_1cd"></a>Eg 6:</p>
-<pre class="programlisting">&gt;&gt;&gt; a = 1 #here a is an integer variable
-
-</pre>
-<p id="x_1ce"></a>Eg 7:</p>
-<pre class="programlisting">&gt;&gt;&gt; lng = 122333444455555666666777777788888888999999999 #here lng is a variable of type long
-&gt;&gt;&gt; lng
-122333444455555666666777777788888888999999999L #notice the trailing 'L'
-&gt;&gt;&gt; print lng
-122333444455555666666777777788888888999999999 #notice the absence of the trailing 'L'
-&gt;&gt;&gt; lng+1
-122333444455555666666777777788888889000000000L
-
-
-</pre>
-<p id="x_1cf"></a>Long numbers are the same as integers in almost all aspects. They can be used in operations just like integers and along with integers without any distinction. The only distinction comes during type checking (which is not a healthy practice). Long numbers are tucked with a trailing 'L' just to signify that they are long. Notice that in the example just lng at the prompt displays the value of the variable with the 'L' whereas 
-        <code class="literal">print lng</code> displays without the 'L'. This is because print formats the output before printing. Also in the example, notice that adding an integer to a long does not give any errors and the result is as expected. So for all practical purposes longs can be treated as ints.
-      </p>
-<p id="x_1d0"></a>Eg 8:</p>
-<pre class="programlisting">&gt;&gt;&gt; fl = 3.14159 #fl is a float variable
-&gt;&gt;&gt; e = 1.234e-4 #e is also a float variable, specified in the exponential form
-&gt;&gt;&gt; a = 1
-&gt;&gt;&gt; b = 2
-&gt;&gt;&gt; a/b #integer division
-0
-&gt;&gt;&gt; a/fl #floating point division
-0.31831015504887655
-&gt;&gt;&gt; e/fl
-3.9279473133031364e-05
-
-
-</pre>
-<p id="x_1d1"></a>Floating point numbers, simply called floats are real numbers with a decimal point. The example above shows the initialization of a float variable. Shown also in this example is the difference between integer division and floating point division. 'a' and 'b' here are integer variables and hence the division gives 0 as the quotient. When either of the operands is a float, the operation is a floating point division, and the result is also a float as illustrated.</p>
-<p id="x_1d2"></a>Eg 9:</p>
-<pre class="programlisting">&gt;&gt;&gt; cplx = 3 + 4j #cplx is a complex variable
-&gt;&gt;&gt; cplx
-(3+4j)
-&gt;&gt;&gt; print cplx.real #prints the real part of the complex number
-3.0
-&gt;&gt;&gt; print cplx.imag #prints the imaginary part of the complex number
-4.0
-&gt;&gt;&gt; print cplx*fl  #multiplies the real and imag parts of the complex number with the multiplier
-(9.42477+12.56636j)
-&gt;&gt;&gt; abs(cplx) #returns the absolute value of the complex number
-5.0
-
-</pre>
-<p id="x_1d3"></a>Python provides a datatype for complex numbers. Complex numbers are initialized as shown in the example above. The 
-        <span class="emphasis"><em>real</em></span> and 
-        <span class="emphasis"><em>imag</em></span> operators return the real and imaginary parts of the complex number as shown. The 
-        <span class="emphasis"><em>abs()</em></span> returns the absolute value of the complex number.
-      </p>
-</div>
-<div class="section" title="4.2. Variables">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="variables"></a>4.2. Variables</h3></div></div></div>
-<p id="x_1d4"></a>Variables are just names that represent a value. Variables have already been introduced in the various examples from the previous sections. Certain rules about using variables:</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_1d5"></a>Variables have to be initialized or assigned a value before being used.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1d6"></a>Variable names can consist of letters, digits and 
-              <a class="link" href="#">underscores</a> .
-            </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_1d7"></a>Variable names cannot begin with digits, but can contain digits in them.</p></li>
-</ul></div></blockquote></div>
-<p id="x_1d8"></a>In reference to the previous section examples, 'a', 'b', 'lng', 'fl', 'e' and 'cplx' are all variables of various datatypes.</p>
-<pre class="programlisting">Note: Python is not a strongly typed language and hence an integer variable can at a
-later stage be used as a float variable as well.
-
-</pre>
-</div>
-<div class="section" title="4.3. Strings">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="strings"></a>4.3. Strings</h3></div></div></div>
-<p id="x_1d9"></a>Strings are one of the essential data structures of any programming language. The 
-        <code class="literal">print "Hello, World!"</code> program was introduced in the earlier section, and the 
-        <span class="emphasis"><em>"Hello, World!"</em></span> in the print statement is a string. A string is basically a set of characters. Strings can be represented in various ways shown below:
-      </p>
-<pre class="programlisting">s = 'this is a string'              # a string variable can be represented using single quotes
-s = 'This one has "quotes" inside!' # The string can have quotes inside it as shown
-s = "I have 'single-quotes' inside!"
-l = "A string spanning many lines\
-one more line\
-yet another"                        # a string can span more than a single line.
-t = """A triple quoted string does  # another way of representing multiline strings.
-not need to be escaped at the end and
-"can have nested quotes" etc."""
-
-</pre>
-<p id="x_1da"></a>Try the following on the interpreter: 
-        <code class="literal">s = 'this is a string with 'quotes' of similar kind'</code>
-      </p>
-<p id="x_1db"></a>
-        <span class="strong"><strong>Exercise: How to use single quotes within single quotes in a string as shown in the above example without getting an error?</strong></span>
-      </p>
-<div class="section" title="4.3.1. String operations">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="string-operations"></a>4.3.1. String operations</h4></div></div></div>
-<p id="x_1dc"></a>A few basic string operations are presented here.</p>
-<p id="x_1dd"></a>
-          <span class="strong"><strong>String concatenation</strong></span> String concatenation is done by simple addition of two strings.
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = 'Hello'
-&gt;&gt;&gt; y = ' Python'
-&gt;&gt;&gt; print x+y
-Hello Python
-
-</pre>
-<p id="x_1de"></a>          <span class="emphasis"><em>Try this yourself:</em></span>
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; somenum = 13
-&gt;&gt;&gt; print x+somenum
-
-</pre>
-<p id="x_1df"></a>The problem with the above example is that here a string variable and an integer variable are trying to be concantenated. To obtain the desired result from the above example the str(), repr() and the `` can be used.</p>
-<p id="x_1e0"></a>
-          <span class="strong"><strong>str()</strong></span> simply converts a value to a string in a reasonable form. 
-          <span class="strong"><strong>repr()</strong></span> creates a string that is a representation of the value.
-        </p>
-<p id="x_1e1"></a>The difference can be seen in the example shown below:</p>
-<pre class="programlisting">&gt;&gt;&gt; str(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000'
-&gt;&gt;&gt; repr(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000L'
-
-</pre>
-<p id="x_1e2"></a>It can be observed that the 'L' in the long value shown was omitted by str(), whereas repr() converted that into a string too. An alternative way of using repr(value) is `
-          <code class="literal">value</code>`.
-        </p>
-<p id="x_1e3"></a>A few more examples:</p>
-<pre class="programlisting">&gt;&gt;&gt; x = "Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go 
-to Pycon
-
-</pre>
-<p id="x_1e4"></a>In the above example, notice that the '\n'(newline) character is formatted and the string is printed on two lines. The strings discussed until now were normal strings. Other than these there are two other types of strings namely, raw strings and unicode strings.</p>
-<p id="x_1e5"></a>
-          <span class="strong"><strong>Raw strings</strong></span> are strings which are unformatted, that is the backslashes(\) are not parsed and are left as it is in the string. Raw strings are represented with an 'r' at the start of a string. Let us look at an example
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = r"Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go \nto Pycon
-
-</pre>
-<p id="x_1e6"></a>Note: The '\n' is not being parsed into a new line and is left as it is.</p>
-<p id="x_1e7"></a>
-          <span class="emphasis"><em>Try this yourself:</em></span>
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = r"Let's go to Pycon\"
-
-</pre>
-<p id="x_1e8"></a>          <span class="strong"><strong>Unicode strings</strong></span> are strings where the characters are Unicode characters as opposed to ASCII characters. Unicode strings are represented with a 'u' at the start of the string. Let us look at an example:
-        </p>
-<pre class="programlisting">&gt;&gt;&gt; x = u"Let's go to Pycon!"
-&gt;&gt;&gt; print x
-Let's go to Pycon!
-
-</pre>
-</div>
-</div>
-<div class="section" title="4.4. Boolean">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="boolean"></a>4.4. Boolean</h3></div></div></div>
-<p id="x_1e9"></a>Python also provides special Boolean datatype. A boolean variable can assume a value of either 
-        <span class="emphasis"><em>True</em></span> or 
-        <span class="emphasis"><em>False</em></span> (Note the capitalizations).
-      </p>
-<p id="x_1ea"></a>Let us look at examples:</p>
-<pre class="programlisting">&gt;&gt;&gt; t = True
-&gt;&gt;&gt; f = not t
-&gt;&gt;&gt; print f
-False
-&gt;&gt;&gt; f or t
-True
-&gt;&gt;&gt; f and t
-False
-
-</pre>
-</div>
-</div>
-<div class="section" title="5. The while loop">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-while-loop"></a>5. The 
-      <span class="strong"><strong>while</strong></span> loop
-    </h2></div></div></div>
-<p id="x_1eb"></a>The Python 
-      <span class="strong"><strong>while</strong></span> loop is similar to the C/C++ while loop. The syntax is as follows:
-    </p>
-<pre class="programlisting">statement 0
-while condition:
-  statement 1 #while block
-  statement 2 #while block
-statement 3 #outside the while block.
-
-</pre>
-<p id="x_1ec"></a>Let us look at an example:</p>
-<pre class="programlisting">&gt;&gt;&gt; x = 1  
-&gt;&gt;&gt; while x &lt;= 5:
-...   print x
-...   x += 1
-... 
-1
-2
-3
-4
-5
-
-</pre>
-</div>
-<div class="section" title="6. The if conditional">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="the-if-conditional"></a>6. The 
-      <span class="strong"><strong>if</strong></span> conditional
-    </h2></div></div></div>
-<p id="x_1ed"></a>The Python 
-      <span class="strong"><strong>if</strong></span> block provides the conditional execution of statements. If the condition evaluates as true the block of statements defined under the if block are executed.
-    </p>
-<p id="x_1ee"></a>If the first block is not executed on account of the condition not being satisfied, the set of statements in the 
-      <span class="strong"><strong>else</strong></span> block are executed.
-    </p>
-<p id="x_1ef"></a>The 
-      <span class="strong"><strong>elif</strong></span> block provides the functionality of evaluation of multiple conditions as shown in the example.
-    </p>
-<p id="x_1f0"></a>The syntax is as follows:</p>
-<pre class="programlisting">if condition :
-    statement_1
-    statement_2
-
-elif condition:
-    statement_3
-    statement_4
-else:
-    statement_5
-    statement_6
-
-</pre>
-<p id="x_1f1"></a>Let us look at an example:</p>
-<pre class="programlisting">&gt;&gt;&gt; n = raw_input("Input a number:")
-&gt;&gt;&gt; if n &lt; 0:
-      print n," is negative"
-      elif n &gt; 0:
-      print n," is positive"
-      else:
-      print n, " is 0"
-
-</pre>
-</div>
-<div class="section" title="7.  raw_input()">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="raw_input"></a>7.       <span class="strong"><strong>raw_input()</strong></span>
-    </h2></div></div></div>
-<p id="x_1f2"></a>In the previous example we saw the call to the raw_input() subroutine. The 
-      <span class="strong"><strong>raw_input()</strong></span> method is used to take user inputs through the console. Unlike 
-      <span class="strong"><strong>input()</strong></span> which assumes the data entered by the user as a standard python expression, 
-      <span class="strong"><strong>raw_input()</strong></span> treats all the input data as raw data and converts everything into a string. To illustrate this let us look at an example.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-121
-
-&gt;&gt;&gt; input("Enter your name:")
-Enter your name:PythonFreak
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-  File "&lt;string&gt;", line 1, in &lt;module&gt;
-NameError: name 'PythonFreak' is not defined
-
-</pre>
-<p id="x_1f3"></a>As shown above the 
-      <span class="strong"><strong>input()</strong></span> assumes that the data entered is a valid Python expression. In the first call it prompts for an integer input and when entered it accepts the integer as an integer, whereas in the second call, when the string is entered without the quotes, 
-      <span class="strong"><strong>input()</strong></span> assumes that the entered data is a valid Python expression and hence it raises and exception saying PythonFreak is not defined.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; input("Enter your name:")
-Enter your name:'PythonFreak'
-'PythonFreak'
-&gt;&gt;&gt; 
-
-</pre>
-<p id="x_1f4"></a>Here the name is accepted because its entered as a string (within quotes). But its unreasonable to go on using quotes each time a string is entered. Hence the alternative is to use 
-      <span class="strong"><strong>raw_input()</strong></span>.
-    </p>
-<p id="x_1f5"></a>Let us now look at how 
-      <span class="strong"><strong>raw_input()</strong></span> operates with an example.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; raw_input("Enter your name:")
-Enter your name:PythonFreak
-'PythonFreak'
-
-</pre>
-<p id="x_1f6"></a>Observe that the 
-      <span class="strong"><strong>raw_input()</strong></span> is converting it into a string all by itself.
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-'121'
-
-</pre>
-<p id="x_1f7"></a>Observe that 
-      <span class="strong"><strong>raw_input()</strong></span> is converting the integer 121 also to a string as '121'. Let us look at another example:
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-&gt;&gt;&gt; pal + 2
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: cannot concatenate 'str' and 'int' objects
-&gt;&gt;&gt; pal
-'121'
-
-</pre>
-<p id="x_1f8"></a>Observe here that the variable 
-      <span class="emphasis"><em>pal</em></span> is a string and hence integer operations cannot be performed on it. Hence the exception is raised.
-    </p>
-</div>
-<div class="section" title="8.  int() method">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="int-method"></a>8. 
-      <span class="strong"><strong>int()</strong></span> method
-    </h2></div></div></div>
-<p id="x_1f9"></a>Generally for computing purposes, the data used is not strings or raw data but on integers, floats and similar mathematical data structures. The data obtained from 
-      <span class="strong"><strong>raw_input()</strong></span> is raw data in the form of strings. In order to obtain integers from strings we use the method 
-      <span class="strong"><strong>int()</strong></span>.
-    </p>
-<p id="x_1fa"></a>Let us look at an example.</p>
-<pre class="programlisting">&gt;&gt;&gt; intpal = int(pal)
-&gt;&gt;&gt; intpal
-121
-
-</pre>
-<p id="x_1fb"></a>In the previous example it was observed that 
-      <span class="emphasis"><em>pal</em></span> was a string variable. Here using the 
-      <span class="strong"><strong>int()</strong></span> method the string 
-      <span class="emphasis"><em>pal</em></span> was converted to an integer variable.
-    </p>
-<p id="x_1fc"></a>
-      <span class="emphasis"><em>Try This Yourself:</em></span>
-    </p>
-<pre class="programlisting">&gt;&gt;&gt; stringvar = raw_input("Enter a name:")
-Enter a name:Guido Van Rossum
-&gt;&gt;&gt; stringvar
-'Guido Van Rossum'
-&gt;&gt;&gt; numvar = int(stringvar)
-
-</pre>
-</div>
-</div>
-</div>
-</body>
-</html>
--- a/web/html/ch02-oop.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,82 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Classes and Objects</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" lang="en" id="chap02_basicoop">
-<div class="article" title="Classes and Objects">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2580083"></a>Classes and Objects</h2></div></div>
-<hr>
-</div>
-<p><a name="x_c2"></a>In the previous sections we learnt about functions which provide certain level of abstraction to our code by holding the code which performs one or more specific functionalities. We were able to use this function as many times as we wanted. In addition to functions, Python also higher level of abstractions through 
-    <span class="emphasis"><em>Classes</em></span> and 
-    <span class="emphasis"><em>Objects</em></span>. 
-    <span class="emphasis"><em>Objects</em></span> can be loosely defined as a collection of a set of data items and a set of methods. The data items can be any valid Python variable or any Python object. Functions enclosed within a class are called as 
-    <span class="emphasis"><em>methods</em></span>. If you are thinking if methods are functions why is there a distinction between the two? The answer to this will be given as we walk through the concepts of 
-    <span class="emphasis"><em>Classes</em></span> and 
-    <span class="emphasis"><em>Objects</em></span>. 
-    <span class="emphasis"><em>Classes</em></span> contain the definition for the 
-    <span class="emphasis"><em>Objects</em></span>. 
-    <span class="emphasis"><em>Objects</em></span> are instances of 
-    <span class="emphasis"><em>Classes</em></span>.
-  </p>
-<p><a name="x_c3"></a>A class is defined using the keyword 
-    <span class="strong"><strong>class</strong></span> followed by the class name, in turn followed by a semicolon. The statements that a 
-    <span class="emphasis"><em>Class</em></span> encloses are written in a new block, i.e on the next indentation level:
-  </p>
-<pre class="programlisting">class Employee:
-  def setName(self, name):
-    self.name = name
-
-  def getName(self):
-    return self.name
-
-</pre>
-<p><a name="x_c4"></a>In the above example, we defined a class with the name Employee. We also defined two methods, setName and getName for this class. It is important to note the differences between the normal Python functions and class methods defined above. Each method of the class must take the same instance of the class(object) from which it was called as the first argument. It is conventionally given the name, 
-    <span class="emphasis"><em>self</em></span>. Note that 
-    <span class="emphasis"><em>self</em></span> is only a convention. You can use any other name, but the first argument to the method will always be the same object of the class from which the method was called. The data memebers that belong to the class are called as 
-    <span class="emphasis"><em>class attributes</em></span>. 
-    <span class="emphasis"><em>Class attributes</em></span> are preceded by the object of the class and a dot. In the above example, 
-    <span class="emphasis"><em>name</em></span> is a class attribute since it is preceded by the 
-    <span class="emphasis"><em>self</em></span> object. 
-    <span class="emphasis"><em>Class attributes</em></span> can be accessed from anywhere within the class.
-  </p>
-<p><a name="x_c5"></a>We can create objects of a class outside the class definition by using the same syntax we use to call a function with no parameters. We can assign this object to a variable:</p>
-<pre class="programlisting">emp = Employee()
-
-</pre>
-<p><a name="x_c6"></a>In the above example, we create an object named 
-    <span class="emphasis"><em>emp</em></span> of the class 
-    <span class="emphasis"><em>Employee</em></span>. All the attributes and methods of the class can be accessed by the object of the class using the standard notation 
-    <span class="emphasis"><em>object.attribute</em></span> or 
-    <span class="emphasis"><em>object.method()</em></span>. Although the first parameter of a class method is the self object, it must not be passed as an argument when calling the method. The 
-    <span class="emphasis"><em>self</em></span> object is implicitly passed to the method by the Python interpreter. All other arguments passing rules like default arguments, keyword arguments, argument packing and unpacking follow the same rules as those for ordinary Python functions:
-  </p>
-<pre class="programlisting">&gt;&gt;&gt; emp.setName('John')
-&gt;&gt;&gt; name = emp.getName()
-&gt;&gt;&gt; print name
-John
-&gt;&gt;&gt; print emp.name
-John
-
-</pre>
-<p><a name="x_c7"></a>If we at all try to access a class attribute before assigning a value to it, i.e before creating it, Python raises the same error as it would raise for the accessing undefined variable:</p>
-<pre class="programlisting">&gt;&gt;&gt; emp = Employee()
-&gt;&gt;&gt; emp.name
-Traceback (most recent call last):
-  File "class.py", line 10, in &lt;module&gt;
-    print e.name
-AttributeError: Employee instance has no attribute 'name'
-
-</pre>
-</div></body>
-</html>
--- a/web/html/ch03-session4.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1187 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. </title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" id="ch03-session4">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2404065">More text processing</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#uniq">1. 
-      <code class="literal">uniq</code>
-    </a></span></dt>
-<dt><span class="section"><a href="#join">2.       <code class="literal">join</code>
-    </a></span></dt>
-<dt><span class="section"><a href="#generating-a-word-frequency-list">3. Generating a word frequency list</a></span></dt>
-<dt><span class="section"><a href="#basic-editing-and-editors">4. Basic editing and editors</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#vim">4.1. vim</a></span></dt>
-<dt><span class="section"><a href="#scite">4.2. SciTE</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#personalizing-your-environment">5. Personalizing your Environment</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#bashrc">5.1. .bashrc</a></span></dt>
-<dt><span class="section"><a href="#vimrc">5.2. .vimrc</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#subshells-and-source">6. Subshells and 
-      <code class="literal">source</code>
-    </a></span></dt>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="More text processing">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2404065"></a>More text processing</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#uniq">1. 
-      <code class="literal">uniq</code>
-    </a></span></dt>
-<dt><span class="section"><a href="#join">2.       <code class="literal">join</code>
-    </a></span></dt>
-<dt><span class="section"><a href="#generating-a-word-frequency-list">3. Generating a word frequency list</a></span></dt>
-<dt><span class="section"><a href="#basic-editing-and-editors">4. Basic editing and editors</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#vim">4.1. vim</a></span></dt>
-<dt><span class="section"><a href="#scite">4.2. SciTE</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#personalizing-your-environment">5. Personalizing your Environment</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#bashrc">5.1. .bashrc</a></span></dt>
-<dt><span class="section"><a href="#vimrc">5.2. .vimrc</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#subshells-and-source">6. Subshells and 
-      <code class="literal">source</code>
-    </a></span></dt>
-</dl>
-</div>
-<code class="literal">sort</code><p id="x_e"></a>Let's say we have a file which lists a few of the stalwarts of the open source community and a few details about them, like their "other" name, their homepage address, and what they are well known for or their claim to fame.</p>
-<pre class="programlisting">Richard Stallman%rms%GNU Project
-Eric Raymond%ESR%Jargon File
-Ian Murdock% %Debian
-Lawrence Lessig% %Creative Commons
-Linus Torvalds% %Linux Kernel
-Guido van Rossum%BDFL%Python
-Larry Wall% %Perl
-
-
-</pre>
-<p id="x_f"></a>The sort command enables us to do this in a flash! Just running the sort command with the file name as a parameter sorts the lines of the file alphabetically and prints the output on the terminal. :</p>
-<pre class="programlisting">$ sort stalwarts.txt 
-Eric Raymond%ESR%Jargon File
-Guido van Rossum%BDFL%Python
-Ian Murdock% %Debian
-Larry Wall% %Perl
-Lawrence Lessig% %Creative Commons
-Linus Torvalds% %Linux Kernel
-Richard Stallman%rms%GNU Project
-
-</pre>
-<p id="x_10"></a>If you wish to sort them reverse alphabetically, you just need to pass the 
-    <code class="literal">-r</code> option. Now, you might want to sort the lines, based on each person's claim to fame or their "other" name. What do we do in that case?
-  </p>
-<p id="x_11"></a>Below is an example that sorts the file based on "other" names. :</p>
-<pre class="programlisting">$ sort -t % -k 2,2  stalwarts.txt
-
-Ian Murdock% %Debian
-Larry Wall% %Perl
-Lawrence Lessig% %Creative Commons
-Linus Torvalds% %Linux Kernel
-Guido van Rossum%BDFL%Python
-Eric Raymond%ESR%Jargon File
-Richard Stallman%rms%GNU Project
-
-</pre>
-<p id="x_12"></a>Sort command assumes white space to be the default delimiter for columns in each line. The 
-    <code class="literal">-t</code> option specifies the delimiting character, which is 
-    <code class="literal">%</code> in this case.
-  </p>
-<p id="x_13"></a>The 
-    <code class="literal">-k</code> option starts a key at position 2 and ends it at 2, essentially telling the sort command that it should sort based on the 2nd column, which is the other name. 
-    <code class="literal">sort</code> also supports conflict resolution using multiple columns for sorting. You can see that the first three lines have nothing in the "other" names column. We could resolve the conflict by sorting based on the project names (the 3rd column).
-  </p>
-<pre class="programlisting">$ sort -t % -k 2,2 -k 3,3  stalwarts.txt
-
-Lawrence Lessig% %Creative Commons
-Ian Murdock% %Debian
-Linus Torvalds% %Linux Kernel
-Larry Wall% %Perl
-Guido van Rossum%BDFL%Python
-Eric Raymond%ESR%Jargon File
-Richard Stallman%rms%GNU Project
-
-</pre>
-<p id="x_14"></a>    <code class="literal">sort</code> also has a lot of other options like ignoring case differences, month sort(JAN&lt;FEB&lt;...), merging already sorted files. 
-    <code class="literal">man sort</code> would give you a lot of information.
-  </p>
-<div class="section" title="1.  uniq">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="uniq"></a>1. 
-      <code class="literal">uniq</code>
-    </h2></div></div></div>
-<p id="x_15"></a>Suppose we have a list of items, say books, and we wish to obtain a list which names of all the books only once, without any duplicates. We use the 
-      <code class="literal">uniq</code> command to achieve this.
-    </p>
-<pre class="programlisting">Programming Pearls
-The C Programming Language
-The Mythical Man Month: Essays on Software Engineering 
-Programming Pearls
-The C Programming Language
-Structure and Interpretation of Computer Programs
-Programming Pearls
-Compilers: Principles, Techniques, and Tools
-The C Programming Language
-The Art of UNIX Programming
-Programming Pearls
-The Art of Computer Programming
-Introduction to Algorithms
-The Art of UNIX Programming
-The Pragmatic Programmer: From Journeyman to Master
-Programming Pearls
-Unix Power Tools
-The Art of UNIX Programming
-
-</pre>
-<p id="x_16"></a>Let us try and get rid of the duplicate lines from this file using the 
-      <code class="literal">uniq</code> command.
-    </p>
-<pre class="programlisting">$ uniq items.txt 
-Programming Pearls
-The C Programming Language
-The Mythical Man Month: Essays on Software Engineering 
-Programming Pearls
-The C Programming Language
-Structure and Interpretation of Computer Programs
-Programming Pearls
-Compilers: Principles, Techniques, and Tools
-The C Programming Language
-The Art of UNIX Programming
-Programming Pearls
-The Art of Computer Programming
-Introduction to Algorithms
-The Art of UNIX Programming
-The Pragmatic Programmer: From Journeyman to Master
-Programming Pearls
-Unix Power Tools
-The Art of UNIX Programming
-
-</pre>
-<p id="x_17"></a>Nothing happens! Why? The 
-      <code class="literal">uniq</code> command removes duplicate lines only when they are next to each other. So, we get a sorted file from the original file and work with that file, henceforth.
-    </p>
-<pre class="programlisting">$ sort items.txt &gt; items-sorted.txt
-$ uniq items-sorted.txt
-Compilers: Principles, Techniques, and Tools
-Introduction to Algorithms
-Programming Pearls
-Structure and Interpretation of Computer Programs
-The Art of Computer Programming
-The Art of UNIX Programming
-The C Programming Language
-The Mythical Man Month: Essays on Software Engineering 
-The Pragmatic Programmer: From Journeyman to Master
-Unix Power Tools
-
-</pre>
-<p id="x_18"></a>      <code class="literal">uniq -u</code> command gives the lines which are unique and do not have any duplicates in the file. 
-      <code class="literal">uniq -d</code> outputs only those lines which have duplicates. The 
-      <code class="literal">-c</code> option displays the number of times each line occurs in the file. :
-    </p>
-<pre class="programlisting">$ uniq -u items-sorted.txt 
-Compilers: Principles, Techniques, and Tools
-Introduction to Algorithms
-Structure and Interpretation of Computer Programs
-The Art of Computer Programming
-The Mythical Man Month: Essays on Software Engineering 
-The Pragmatic Programmer: From Journeyman to Master
-Unix Power Tools
-
-$ uniq -dc items-sorted.txt      
-5 Programming Pearls
-3 The Art of UNIX Programming
-3 The C Programming Language
-
-
-</pre>
-</div>
-<div class="section" title="2.  join">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="join"></a>2.       <code class="literal">join</code>
-    </h2></div></div></div>
-<p id="x_19"></a>Now suppose we had the file 
-      <code class="literal">stalwarts1.txt</code>, which lists the home pages of all the people listed in 
-      <code class="literal">stalwarts.txt</code>. :
-    </p>
-<pre class="programlisting">Richard Stallman%http://www.stallman.org
-Eric Raymond%http://www.catb.org/~esr/
-Ian Murdock%http://ianmurdock.com/
-Lawrence Lessig%http://lessig.org
-Linus Torvalds%http://torvalds-family.blogspot.com/
-Guido van Rossum%http://www.python.org/~guido/
-Larry Wall%http://www.wall.org/~larry/
-
-</pre>
-<p id="x_1a"></a>It would be nice to have a single file with the information in both the files. To achieve this we use the 
-      <code class="literal">join</code> command. :
-    </p>
-<pre class="programlisting">$ join stalwarts.txt stalwarts1.txt -t %
-Richard Stallman%rms%GNU Project%http://www.stallman.org
-Eric Raymond%ESR%Jargon File%http://www.catb.org/~esr/
-Ian Murdock% %Debian%http://ianmurdock.com/
-Lawrence Lessig% %Creative Commons%http://lessig.org
-Linus Torvalds% %Linux Kernel%http://torvalds-family.blogspot.com/
-Guido van Rossum%BDFL%Python%http://www.python.org/~guido/
-Larry Wall% %Perl%http://www.wall.org/~larry/
-
-</pre>
-<p id="x_1b"></a>The 
-      <code class="literal">join</code> command joins the two files, based on the common field present in both the files, which is the name, in this case.
-    </p>
-<p id="x_1c"></a>The 
-      <code class="literal">-t</code> option again specifies the delimiting character. Unless that is specified, join assumes that the fields are separated by spaces.
-    </p>
-<p id="x_1d"></a>Note that, for 
-      <code class="literal">join</code> to work, the common field should be in the same order in both the files. If this is not so, you could use 
-      <code class="literal">sort</code>, to sort the files on the common field and then join the files. In the above example, we have the common field to be the first column in both the files. If this is not the case we could use the 
-      <code class="literal">-1</code> and 
-      <code class="literal">-2</code> options to specify the field to be used for joining the files. :
-    </p>
-<pre class="programlisting">$ join -2 2 stalwarts.txt stalwarts2.txt -t %
-Richard Stallman%rms%GNU Project%http://www.stallman.org
-Eric Raymond%ESR%Jargon File%http://www.catb.org/~esr/
-Ian Murdock% %Debian%http://ianmurdock.com/
-Lawrence Lessig% %Creative Commons%http://lessig.org
-Linus Torvalds% %Linux Kernel%http://torvalds-family.blogspot.com/
-Guido van Rossum%BDFL%Python%http://www.python.org/~guido/
-Larry Wall% %Perl%http://www.wall.org/~larry/
-
-
-</pre>
-</div>
-<div class="section" title="3. Generating a word frequency list">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="generating-a-word-frequency-list"></a>3. Generating a word frequency list</h2></div></div></div>
-<p id="x_1e"></a>Now, let us use the tools we have learnt to use, to generate a word frequency list of a text file. We shall use the free text of Alice in Wonderland.</p>
-<p id="x_1f"></a>The basic steps to achieve this task would be -</p>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p id="x_20"></a>Eliminate the punctuation and spaces from the document.</p></li>
-<li class="listitem"><p id="x_21"></a>Generate a list of words.</p></li>
-<li class="listitem"><p id="x_22"></a>Count the words.</p></li>
-</ol></div>
-<p id="x_23"></a>We first use 
-      <code class="literal">grep</code> and some elementary 
-      <code class="literal">regex</code> to eliminate the non-alpha-characters. :
-    </p>
-<pre class="programlisting">$ grep "[A-Za-z]*" alice-in-wonderland.txt
-
-</pre>
-<p id="x_24"></a>This outputs all the lines which has any alphabetic characters on it. This isn't of much use, since we haven't done anything with the code. We only require the alphabetic characters, without any of the other junk. 
-      <code class="literal">man grep</code> shows us the 
-      <code class="literal">-o</code> option for outputting only the text which matches the regular expression. :
-    </p>
-<pre class="programlisting">$ grep "[A-Za-z]*" -o alice-in-wonderland.txt
-
-</pre>
-<p id="x_25"></a>Not very surprisingly, we have all the words, spit out in the form of a list! Now that we have a list of words, it is quite simple to count the occurrences of the words. You would've realized that we can make use of 
-      <code class="literal">sort</code> and 
-      <code class="literal">uniq</code> commands. We pipe the output from the 
-      <code class="literal">grep</code> to the 
-      <code class="literal">sort</code> and then pipe it's output to 
-      <code class="literal">uniq</code>. :
-    </p>
-<pre class="programlisting">$ grep "[A-Za-z]*" -o alice-in-wonderland.txt | sort | uniq -c 
-
-</pre>
-<p id="x_26"></a>Notice that you get the list of all words in the document in the alphabetical order, with it's frequency written next to it. But, you might have observed that Capitalized words and lower case words are being counted as different words. We therefore, replace all the Upper case characters with lower case ones, using the 
-      <code class="literal">tr</code> command. :
-    </p>
-<pre class="programlisting">$ grep  "[A-Za-z]*" -o alice-in-wonderland.txt | tr 'A-Z' 'a-z' | sort | uniq -c 
-
-</pre>
-<p id="x_27"></a>Now, it would also be nice to have the list ordered in the decreasing order of the frequency of the appearance of the words. We sort the output of the 
-      <code class="literal">uniq</code> command with 
-      <code class="literal">-n</code> and 
-      <code class="literal">-r</code> options, to get the desired output. :
-    </p>
-<pre class="programlisting">$ grep  "[A-Za-z]*" -o alice-in-wonderland.txt | tr 'A-Z' 'a-z' | sort | uniq -c | sort -nr
-
-</pre>
-</div>
-<div class="section" title="4. Basic editing and editors">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="basic-editing-and-editors"></a>4. Basic editing and editors</h2></div></div></div>
-<div class="section" title="4.1. vim">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="vim"></a>4.1. vim</h3></div></div></div>
-<p id="x_28"></a>Vim is a very powerful editor. It has a lot of commands, and all of them cannot be explained here. We shall try and look at a few, so that you can find your way around in vim.</p>
-<p id="x_29"></a>To open a file in vim, we pass the filename as a parameter to the 
-        <code class="literal">vim</code> command. If a file with that filename does not exist, a new file is created. :
-      </p>
-<pre class="programlisting">$ vim first.txt
-
-</pre>
-<p id="x_2a"></a>To start inserting text into the new file that we have opened, we need to press the 
-        <code class="literal">i</code> key. This will take us into the 
-        <span class="emphasis"><em>insert</em></span> mode from the 
-        <span class="emphasis"><em>command</em></span> mode. Hitting the 
-        <code class="literal">esc</code> key, will bring us back to the 
-        <span class="emphasis"><em>command</em></span> mode. There is also another mode of vim, called the 
-        <span class="emphasis"><em>visual</em></span> mode which will be discussed later in the course.
-      </p>
-<p id="x_2b"></a>In general, it is good to spend as little time as possible in the insert mode and extensively use the command mode to achieve various tasks.</p>
-<p id="x_2c"></a>To save the file, use 
-        <code class="literal">:w</code> in the command mode. From here on, it is understood that we are in the command mode, whenever we are issuing any command to vim.
-      </p>
-<p id="x_2d"></a>To save a file and continue editing, use 
-        <code class="literal">:w FILENAME</code> The file name is optional. If you do not specify a filename, it is saved in the same file that you opened. If a file name different from the one you opened is specified, the text is saved with the new name, but you continue editing the file that you opened. The next time you save it without specifying a name, it gets saved with the name of the file that you initially opened.
-      </p>
-<p id="x_2e"></a>To save file with a new name and continue editing the new file, use 
-        <code class="literal">:saveas FILENAME</code>
-      </p>
-<p id="x_2f"></a>To save and quit, use 
-        <code class="literal">:wq</code>
-      </p>
-<p id="x_30"></a>To quit, use 
-        <code class="literal">:q</code>
-      </p>
-<p id="x_31"></a>To quit without saving, use 
-        <code class="literal">:q!</code>
-      </p>
-<div class="section" title="4.1.1. Moving around">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="moving-around"></a>4.1.1. Moving around</h4></div></div></div>
-<p id="x_32"></a>While you are typing in a file, it is in-convenient to keep moving your fingers from the standard position for typing to the arrow keys. Vim, therefore, provides alternate keys for moving in the document. Note again that, you should be in the command mode, when issuing any commands to vim.</p>
-<p id="x_33"></a>The basic cursor movement can be achieved using the keys, 
-          <code class="literal">h</code> (left), 
-          <code class="literal">l</code> (right), 
-          <code class="literal">k</code> (up) and 
-          <code class="literal">j</code> (down). :
-        </p>
-<pre class="programlisting">^
-k              
-</pre>
-<div class="variablelist"><dl>
-<dt><span class="term">&lt; h       l &gt;</span></dt>
-<dd>
-<p></p>
-<p id="x_34"></a>j v</p>
-</dd>
-</dl></div>
-<p id="x_35"></a>Note: Most commands can be prefixed with a number, to repeat the command. For instance, 
-          <code class="literal">10j</code> will move the cursor down 10 lines.
-        </p>
-<div class="section" title="4.1.1.1. Moving within a line">
-<div class="titlepage"><div><div><h5 class="title">
-<a name="moving-within-a-line"></a>4.1.1.1. Moving within a line</h5></div></div></div>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="41">
-<col width="10">
-</colgroup>
-<thead><tr>
-<th>
-                    <p id="x_36"></a>Cursor Movement</p>
-                  </th>
-<th>
-                    <p id="x_37"></a>Command</p>
-                  </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                    <p id="x_38"></a>Beginning of line</p>
-                  </td>
-<td>
-                    <p id="x_39"></a>
-                      <code class="literal">0</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_3a"></a>First non-space character of line</p>
-                  </td>
-<td>
-                    <p id="x_3b"></a>
-                      <code class="literal">^</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_3c"></a>End of line</p>
-                  </td>
-<td>
-                    <p id="x_3d"></a>
-                      <code class="literal">$</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_3e"></a>Last non-space character of line</p>
-                  </td>
-<td>
-                    <p id="x_3f"></a>
-                      <code class="literal">g_</code>
-                    </p>
-                  </td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<div class="section" title="4.1.1.2. Moving by words and sentences">
-<div class="titlepage"><div><div><h5 class="title">
-<a name="moving-by-words-and-sentences"></a>4.1.1.2. Moving by words and sentences</h5></div></div></div>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="31">
-<col width="10">
-</colgroup>
-<thead><tr>
-<th>
-                    <p id="x_40"></a>Cursor Movement</p>
-                  </th>
-<th>
-                    <p id="x_41"></a>Command</p>
-                  </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                    <p id="x_42"></a>Forward, word beginning</p>
-                  </td>
-<td>
-                    <p id="x_43"></a>
-                      <code class="literal">w</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_44"></a>Backward, word beginning</p>
-                  </td>
-<td>
-                    <p id="x_45"></a>
-                      <code class="literal">b</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_46"></a>Forward, word end</p>
-                  </td>
-<td>
-                    <p id="x_47"></a>
-                      <code class="literal">e</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_48"></a>Backward, word end</p>
-                  </td>
-<td>
-                    <p id="x_49"></a>
-                      <code class="literal">ge</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_4a"></a>Forward, sentence beginning</p>
-                  </td>
-<td>
-                    <p id="x_4b"></a>
-                      <code class="literal">)</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_4c"></a>Backward, sentence beginning</p>
-                  </td>
-<td>
-                    <p id="x_4d"></a>
-                      <code class="literal">(</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_4e"></a>Forward, paragraph beginning</p>
-                  </td>
-<td>
-                    <p id="x_4f"></a>
-                      <code class="literal">}</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_50"></a>Backward, paragraph beginning</p>
-                  </td>
-<td>
-                    <p id="x_51"></a>
-                      <code class="literal">{</code>
-                    </p>
-                  </td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<div class="section" title="4.1.1.3. More movement commands">
-<div class="titlepage"><div><div><h5 class="title">
-<a name="more-movement-commands"></a>4.1.1.3. More movement commands</h5></div></div></div>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="34">
-<col width="13">
-</colgroup>
-<thead><tr>
-<th>
-                    <p id="x_52"></a>Cursor Movement</p>
-                  </th>
-<th>
-                    <p id="x_53"></a>Command</p>
-                  </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                    <p id="x_54"></a>Forward by a screenful of text</p>
-                  </td>
-<td>
-                    <p id="x_55"></a>
-                      <code class="literal">C-f</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_56"></a>Backward by a screenful of text</p>
-                  </td>
-<td>
-                    <p id="x_57"></a>
-                      <code class="literal">C-b</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_58"></a>Beginning of the screen</p>
-                  </td>
-<td>
-                    <p id="x_59"></a>
-                      <code class="literal">H</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_5a"></a>Middle of the screen</p>
-                  </td>
-<td>
-                    <p id="x_5b"></a>
-                      <code class="literal">M</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_5c"></a>End of the screen</p>
-                  </td>
-<td>
-                    <p id="x_5d"></a>
-                      <code class="literal">L</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_5e"></a>End of file</p>
-                  </td>
-<td>
-                    <p id="x_5f"></a>
-                      <code class="literal">G</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_60"></a>Line number 
-                      <code class="literal">num</code>
-                    </p>
-                  </td>
-<td>
-                    <p id="x_61"></a>
-                      <code class="literal">[num]G</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_62"></a>Beginning of file</p>
-                  </td>
-<td>
-                    <p id="x_63"></a>
-                      <code class="literal">gg</code>
-                    </p>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_64"></a>Next occurrence of the text under the cursor</p>
-                  </td>
-<td>
-                    <div class="variablelist"><dl>
-<dt><span class="term">
-                          <code class="literal">*</code>
-                        </span></dt>
-<dd><p></p></dd>
-</dl></div>
-                  </td>
-</tr>
-<tr>
-<td>
-                    <p id="x_65"></a>Previous occurrence of the text under the cursor</p>
-                  </td>
-<td>
-                    <div class="variablelist"><dl>
-<dt><span class="term">
-                          <code class="literal">#</code>
-                        </span></dt>
-<dd><p></p></dd>
-</dl></div>
-                  </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_66"></a>Note: 
-            <code class="literal">C-x</code> is 
-            <code class="literal">Ctrl</code> + 
-            <code class="literal">x</code>
-          </p>
-</div>
-</div>
-<div class="section" title="4.1.2. The visual mode">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="the-visual-mode"></a>4.1.2. The visual mode</h4></div></div></div>
-<p id="x_67"></a>The visual mode is a special mode that is not present in the original vi editor. It allows us to highlight text and perform actions on it. All the movement commands that have been discussed till now work in the visual mode also. The editing commands that will be discussed in the future work on the visual blocks selected, too.</p>
-</div>
-<div class="section" title="4.1.3. Editing commands">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="editing-commands"></a>4.1.3. Editing commands</h4></div></div></div>
-<p id="x_68"></a>The editing commands usually take the movements as arguments. A movement is equivalent to a selection in the visual mode. The cursor is assumed to have moved over the text in between the initial and the final points of the movement. The motion or the visual block that's been highlighted can be passed as arguments to the editing commands.</p>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="26">
-<col width="10">
-</colgroup>
-<thead><tr>
-<th>
-                  <p id="x_69"></a>Editing effect</p>
-                </th>
-<th>
-                  <p id="x_6a"></a>Command</p>
-                </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                  <p id="x_6b"></a>Cutting text</p>
-                </td>
-<td>
-                  <p id="x_6c"></a>
-                    <code class="literal">d</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_6d"></a>Copying/Yanking text</p>
-                </td>
-<td>
-                  <p id="x_6e"></a>
-                    <code class="literal">y</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_6f"></a>Pasting copied/cut text</p>
-                </td>
-<td>
-                  <p id="x_70"></a>
-                    <code class="literal">p</code>
-                  </p>
-                </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_71"></a>The cut and copy commands take the motions or visual blocks as arguments and act on them. For instance, if you wish to delete the text from the current text position to the beginning of the next word, type 
-          <code class="literal">dw</code>. If you wish to copy the text from the current position to the end of this sentence, type 
-          <code class="literal">y)</code>.
-        </p>
-<p id="x_72"></a>Apart from the above commands, that take any motion or visual block as an argument, there are additional special commands.</p>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="41">
-<col width="10">
-</colgroup>
-<thead><tr>
-<th>
-                  <p id="x_73"></a>Editing effect</p>
-                </th>
-<th>
-                  <p id="x_74"></a>Command</p>
-                </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                  <p id="x_75"></a>Cut the character under the cursor</p>
-                </td>
-<td>
-                  <p id="x_76"></a>
-                    <code class="literal">x</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_77"></a>Replace the character under the cursor with 
-                    <code class="literal">a</code>
-                  </p>
-                </td>
-<td>
-                  <div class="variablelist"><dl>
-<dt><span class="term">
-                        <code class="literal">ra</code>
-                      </span></dt>
-<dd><p></p></dd>
-</dl></div>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_78"></a>Cut an entire line</p>
-                </td>
-<td>
-                  <p id="x_79"></a>
-                    <code class="literal">dd</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_7a"></a>Copy/yank an entire line</p>
-                </td>
-<td>
-                  <p id="x_7b"></a>
-                    <code class="literal">yy</code>
-                  </p>
-                </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_7c"></a>Note: You can prefix numbers to any of the commands, to repeat them.</p>
-</div>
-<div class="section" title="4.1.4. Undo and Redo">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="undo-and-redo"></a>4.1.4. Undo and Redo</h4></div></div></div>
-<p id="x_7d"></a>You can undo almost anything using 
-          <code class="literal">u</code>.
-        </p>
-<p id="x_7e"></a>To undo the undo command type 
-          <code class="literal">C-r</code>
-        </p>
-</div>
-<div class="section" title="4.1.5. Searching and Replacing">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="searching-and-replacing"></a>4.1.5. Searching and Replacing</h4></div></div></div>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="42">
-<col width="10">
-</colgroup>
-<thead><tr>
-<th>
-                  <p id="x_7f"></a>Finding</p>
-                </th>
-<th>
-                  <p id="x_80"></a>Command</p>
-                </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                  <p id="x_81"></a>Next occurrence of 
-                    <code class="literal">text</code>, forward
-                  </p>
-                </td>
-<td>
-                  <p id="x_82"></a>
-                    <code class="literal">\text</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_83"></a>Next occurrence of 
-                    <code class="literal">text</code>, backward
-                  </p>
-                </td>
-<td>
-                  <p id="x_84"></a>
-                    <code class="literal">?text</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_85"></a>Search again in the same direction</p>
-                </td>
-<td>
-                  <p id="x_86"></a>
-                    <code class="literal">n</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_87"></a>Search again in the opposite direction</p>
-                </td>
-<td>
-                  <p id="x_88"></a>
-                    <code class="literal">N</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_89"></a>Next occurrence of 
-                    <code class="literal">x</code> in the line
-                  </p>
-                </td>
-<td>
-                  <p id="x_8a"></a>
-                    <code class="literal">fx</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_8b"></a>Previous occurrence of 
-                    <code class="literal">x</code> in the line
-                  </p>
-                </td>
-<td>
-                  <p id="x_8c"></a>
-                    <code class="literal">Fx</code>
-                  </p>
-                </td>
-</tr>
-</tbody>
-</table></div>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="40">
-<col width="19">
-</colgroup>
-<thead><tr>
-<th>
-                  <p id="x_8d"></a>Finding and Replacing</p>
-                </th>
-<th>
-                  <p id="x_8e"></a>Command</p>
-                </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                  <p id="x_8f"></a>Replace the first instance of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the current line.
-                  </p>
-                </td>
-<td>
-                  <p id="x_90"></a>
-                    <code class="literal">:s/old/new</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_91"></a>Replace all instances of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the current line.
-                  </p>
-                </td>
-<td>
-                  <p id="x_92"></a>
-                    <code class="literal">:s/old/new/g</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_93"></a>Replace all instances of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the current line, but ask for confirmation each time.
-                  </p>
-                </td>
-<td>
-                  <p id="x_94"></a>
-                    <code class="literal">:s/old/new/gc</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_95"></a>Replace the first instance of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the entire file.
-                  </p>
-                </td>
-<td>
-                  <p id="x_96"></a>
-                    <code class="literal">:%s/old/new</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_97"></a>Replace all instances of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the entire file.
-                  </p>
-                </td>
-<td>
-                  <p id="x_98"></a>
-                    <code class="literal">:%s/old/new/g</code>
-                  </p>
-                </td>
-</tr>
-<tr>
-<td>
-                  <p id="x_99"></a>Replace all instances of 
-                    <code class="literal">old</code> with 
-                    <code class="literal">new</code> in the entire file but ask for confirmation each time.
-                  </p>
-                </td>
-<td>
-                  <p id="x_9a"></a>
-                    <code class="literal">:%s/old/new/gc</code>
-                  </p>
-                </td>
-</tr>
-</tbody>
-</table></div>
-</div>
-</div>
-<div class="section" title="4.2. SciTE">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="scite"></a>4.2. SciTE</h3></div></div></div>
-<p id="x_9b"></a>SciTE is a 
-        <span class="emphasis"><em>source code</em></span> editor, that has a feel similar to the commonly used GUI text editors. It has a wide range of features that are extremely useful for a programmer, editing code. Also it aims to keep configuration simple, and the user needs to edit a text file to configure SciTE to his/her liking.
-      </p>
-<p id="x_9c"></a>Opening, Saving, Editing files with SciTE is extremely simple and trivial. Knowledge of using a text editor will suffice.</p>
-<p id="x_9d"></a>SciTE can syntax highlight code in various languages. It also has auto-indentation, code-folding and other such features which are useful when editing code.</p>
-<p id="x_9e"></a>SciTE also gives you the option to (compile and) run your code, from within the editor.</p>
-</div>
-</div>
-<div class="section" title="5. Personalizing your Environment">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="personalizing-your-environment"></a>5. Personalizing your Environment</h2></div></div></div>
-<div class="section" title="5.1. .bashrc">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="bashrc"></a>5.1. .bashrc</h3></div></div></div>
-<p id="x_9f"></a>What would you do, if you want bash to execute a particular command each time you start it up? For instance, say you want the current directory to be your Desktop instead of your home folder, each time bash starts up. How would you achieve this? Bash reads and executes commands in a whole bunch of files called start-up files, when it starts up.</p>
-<p id="x_a0"></a>When bash starts up as an interactive login shell, it reads the files 
-        <code class="literal">/etc/profile</code>, 
-        <code class="literal">~/.bash_profile</code>, 
-        <code class="literal">~/.bash_login</code>, and 
-        <code class="literal">~/.profile</code> in that order.
-      </p>
-<p id="x_a1"></a>When it is a shell that is not a login shell, 
-        <code class="literal">~/.bashrc</code> is read and the commands in it are executed. This can be prevented using the 
-        <code class="literal">--norc</code> option. To force bash to use another file, instead of the 
-        <code class="literal">~/.bashrc</code> file on start-up, the 
-        <code class="literal">--rcfile</code> option may be used.
-      </p>
-<p id="x_a2"></a>Now, you know what you should do, to change the current directory to you Desktop. Just put a 
-        <code class="literal">cd ~/Desktop</code> into your 
-        <code class="literal">~/.bashrc</code> and you are set!
-      </p>
-<p id="x_a3"></a>This example is quite a simple and lame one. The start-up files are used for a lot more complex things than this. You could set (or unset) aliases and a whole bunch of environment variables in the 
-        <code class="literal">.bashrc</code>. We shall look at them, in the next section where we look at environment variables and 
-        <code class="literal">set</code> command.
-      </p>
-</div>
-<div class="section" title="5.2. .vimrc">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="vimrc"></a>5.2. .vimrc</h3></div></div></div>
-<p id="x_a4"></a>
-        <code class="literal">.vimrc</code> is a file similar to 
-        <code class="literal">.bashrc</code> for vim. It is a start-up file that vim reads and executes, each time it starts up. The options that you would like to be set every time you use vim, are placed in the 
-        <code class="literal">.vimrc</code> file, so that they are automatically set each time vim starts. The recommended place for having your 
-        <code class="literal">.vimrc</code> is also your home directory.
-      </p>
-<p id="x_a5"></a>The file 
-        <code class="literal">/etc/vimrc</code> is the global config file and shouldn't usually be edited. You can instead edit the 
-        <code class="literal">~/.vimrc</code> file that is present in your home folder.
-      </p>
-<p id="x_a6"></a>There are a whole bunch of variables that you could set in the 
-        <code class="literal">.vimrc</code> file. You can look at all the options available, using the 
-        <code class="literal">:set all</code> command in vim. You could use the 
-        <code class="literal">:help option_name</code> to get more information about the option that you want to set. Once you are comfortable with what you want to set a particular variable to, you could add it to 
-        <code class="literal">.vimrc</code>. You should also look at 
-        <code class="literal">:help vimrc</code> for more info on the 
-        <code class="literal">.vimrc</code> file. If you already have a 
-        <code class="literal">.vimrc</code> file, you can edit it from within vim, using 
-        <code class="literal">:e $MYVIMRC</code> command. We shall look at some of the most commonly used options.
-      </p>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="35">
-<col width="84">
-</colgroup>
-<thead><tr>
-<th>
-                <p id="x_a7"></a>Command</p>
-              </th>
-<th>
-                <p id="x_a8"></a>Vim action</p>
-              </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                <p id="x_a9"></a>
-                  <code class="literal">set nocompatible</code>
-                </p>
-              </td>
-<td>
-                <p id="x_aa"></a>Explicitly disable compatibility with vi</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <div class="variablelist"><dl>
-<dt><span class="term">
-                      <code class="literal">set backspace=indent,eol,start</code>
-                    </span></dt>
-<dd><p></p></dd>
-</dl></div>
-              </td>
-<td>
-                <p id="x_ab"></a>In the insert mode, vim allows the backspace key to delete white spaces at the start of line, line breaks and the character before which insert mode started.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_ac"></a>set autoindent</p>
-              </td>
-<td>
-                <p id="x_ad"></a>Vim indents a new line with the same indentation of the previous line.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_ae"></a>set backup</p>
-              </td>
-<td>
-                <p id="x_af"></a>Vim keeps a backup copy of a file when overwriting it.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_b0"></a>set history=50</p>
-              </td>
-<td>
-                <p id="x_b1"></a>Vim keeps 50 commands and 50 search patterns in the history.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_b2"></a>set ruler</p>
-              </td>
-<td>
-                <p id="x_b3"></a>Displays the current cursor position in the lower right corner of the vim window.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_b4"></a>set showcmd</p>
-              </td>
-<td>
-                <p id="x_b5"></a>Displays the incomplete command in the lower right corner.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_b6"></a>set incsearch</p>
-              </td>
-<td>
-                <p id="x_b7"></a>Turns on incremental searching. Displays search results while you type.</p>
-              </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_b8"></a>You can see the effect of the changes made to your 
-        <code class="literal">.vimrc</code> file by restarting vim. If you want to see the changes that you made to your 
-        <code class="literal">.vimrc</code> file immediately, you could source the file from within vim.
-      </p>
-<p id="x_b9"></a>If the 
-        <code class="literal">.vimrc</code> file has been sourced when this instance of vim was started, you could just resource the file again:
-      </p>
-<p id="x_ba"></a>:so $MYVIMRC</p>
-<p id="x_bb"></a>If you just created the 
-        <code class="literal">.vimrc</code> file or it was not sourced when you stared this instance of vim, just replace the 
-        <code class="literal">$MYVIMRC</code> variable above, with the location of the 
-        <code class="literal">.vimrc</code> file that you created/edited.
-      </p>
-</div>
-</div>
-<div class="section" title="6. Subshells and source">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="subshells-and-source"></a>6. Subshells and 
-      <code class="literal">source</code>
-    </h2></div></div></div>
-<p id="x_bc"></a>A subshell is just a separate instance of the shell which is a child process of the shell that launches it. Bash creates a subshell in various circumstances. Creation of subshells allows the execution of various processes simultaneously.</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_bd"></a>When an external command is executed, a new subshell is created. Any built-in commands of bash are executed with int the same shell, and no new subshell is started. When an external command is run, the bash shell copies itself (along with it's environment) creating a subshell and the process is changed to the external command executed. The subshell is a child process of this shell.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_be"></a>Any pipes being used, create a subshell. The commands on the input and output ends of the pipe are run in different subshells.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_bf"></a>You could also, explicitly tell bash to start a subshell by enclosing a list of commands between parentheses. Each of the commands in the list is executed within a single new subshell.</p></li>
-</ul></div></blockquote></div>
-<p id="x_c0"></a>To avoid creating a subshell, when running a shell script, you could use the 
-      <code class="literal">source</code> command. :
-    </p>
-<pre class="programlisting">$ source script.sh
-
-</pre>
-<p id="x_c1"></a>This will run the 
-      <code class="literal">script.sh</code> within the present shell without creating a subshell. The 
-      <code class="literal">.</code> command is an alias for the source command. 
-      <code class="literal">. script.sh</code> is therefore equivalent to 
-      <code class="literal">source script.sh</code>.
-    </p>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch04-handout.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,1380 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. </title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="chap04_handout">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2325149">LaTeX</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#tex-latex">1. TeX &amp; LaTeX</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#tex">1.1. TeX</a></span></dt>
-<dt><span class="section"><a href="#latex">1.2. LaTeX</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#wysiwg-vs-wysiwm">2. WYSIWG vs. WYSIWM</a></span></dt>
-<dt><span class="section"><a href="#hello-world">3. Hello World</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#compiling-output">3.1. Compiling &amp; Output</a></span></dt>
-<dt><span class="section"><a href="#a-peek-at-the-source">3.2. A peek at the source</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#where-do-we-want-to-go">4. Where do we want to go</a></span></dt>
-<dt><span class="section"><a href="#some-basics">5. Some Basics</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#spaces">5.1. Spaces</a></span></dt>
-<dt><span class="section"><a href="#line-page-breaks">5.2. Line &amp; Page Breaks</a></span></dt>
-<dt><span class="section"><a href="#paragraphs">5.3. Paragraphs</a></span></dt>
-<dt><span class="section"><a href="#special-characters">5.4. Special Characters</a></span></dt>
-<dt><span class="section"><a href="#commands">5.5. Commands</a></span></dt>
-<dt><span class="section"><a href="#environments">5.6. Environments</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#some-structural-elements">6. Some Structural Elements</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#documentclass">6.1. 
-        <code class="literal">\documentclass</code>
-      </a></span></dt>
-<dt><span class="section"><a href="#parts-chapters-and-sections">6.2. Parts, Chapters and Sections</a></span></dt>
-<dt><span class="section"><a href="#top-matter">6.3. Top Matter</a></span></dt>
-<dt><span class="section"><a href="#abstract">6.4. Abstract</a></span></dt>
-<dt><span class="section"><a href="#appendices">6.5. Appendices</a></span></dt>
-<dt><span class="section"><a href="#table-of-contents">6.6. Table of Contents</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#elementary-text-typesetting">7. Elementary Text Typesetting</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#emphasizing">7.1. Emphasizing</a></span></dt>
-<dt><span class="section"><a href="#quotation-marks">7.2. Quotation Marks</a></span></dt>
-<dt><span class="section"><a href="#dashes-and-hyphens">7.3. Dashes and Hyphens</a></span></dt>
-<dt><span class="section"><a href="#footnotes">7.4. Footnotes</a></span></dt>
-<dt><span class="section"><a href="#flushleft-flushright-and-center">7.5. Flushleft, Flushright, and Center</a></span></dt>
-<dt><span class="section"><a href="#itemize-enumerate-and-description">7.6. Itemize, Enumerate, and Description</a></span></dt>
-<dt><span class="section"><a href="#quote-quotation-and-verse">7.7. Quote, Quotation, and Verse</a></span></dt>
-<dt><span class="section"><a href="#verbatim">7.8. Verbatim</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#tables-figures-and-captions">8. Tables, Figures and Captions</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#the-tabular-environment">8.1. The 
-        <code class="literal">\tabular</code> environment
-      </a></span></dt>
-<dt><span class="section"><a href="#importing-graphics">8.2. Importing Graphics</a></span></dt>
-<dt><span class="section"><a href="#floats">8.3. Floats</a></span></dt>
-<dt><span class="section"><a href="#captions">8.4. Captions</a></span></dt>
-<dt><span class="section"><a href="#list-of-figures-tables">8.5. List of Figures, Tables</a></span></dt>
-<dt><span class="section"><a href="#cross-references">8.6. Cross References</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#bibliography">9. Bibliography</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#thebibliography-environment">9.1. 
-        <code class="literal">thebibliography</code> environment
-      </a></span></dt>
-<dt><span class="section"><a href="#bibtex">9.2. BibTeX</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#typesetting-math">10. Typesetting Math</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#math-mode">10.1. Math Mode</a></span></dt>
-<dt><span class="section"><a href="#single-equations">10.2. Single Equations</a></span></dt>
-<dt><span class="section"><a href="#basic-elements">10.3. Basic Elements</a></span></dt>
-<dt><span class="section"><a href="#multiple-equations">10.4. Multiple Equations</a></span></dt>
-<dt><span class="section"><a href="#arrays-and-matrices">10.5. Arrays and Matrices</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#miscellaneous-stuff">11. Miscellaneous Stuff</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#presentations">11.1. Presentations</a></span></dt>
-<dt><span class="section"><a href="#including-code">11.2. Including Code</a></span></dt>
-<dt><span class="section"><a href="#including-files">11.3. Including files</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#recommended-reading">12. Recommended Reading</a></span></dt>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="LaTeX">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2325149"></a>LaTeX</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#tex-latex">1. TeX &amp; LaTeX</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#tex">1.1. TeX</a></span></dt>
-<dt><span class="section"><a href="#latex">1.2. LaTeX</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#wysiwg-vs-wysiwm">2. WYSIWG vs. WYSIWM</a></span></dt>
-<dt><span class="section"><a href="#hello-world">3. Hello World</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#compiling-output">3.1. Compiling &amp; Output</a></span></dt>
-<dt><span class="section"><a href="#a-peek-at-the-source">3.2. A peek at the source</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#where-do-we-want-to-go">4. Where do we want to go</a></span></dt>
-<dt><span class="section"><a href="#some-basics">5. Some Basics</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#spaces">5.1. Spaces</a></span></dt>
-<dt><span class="section"><a href="#line-page-breaks">5.2. Line &amp; Page Breaks</a></span></dt>
-<dt><span class="section"><a href="#paragraphs">5.3. Paragraphs</a></span></dt>
-<dt><span class="section"><a href="#special-characters">5.4. Special Characters</a></span></dt>
-<dt><span class="section"><a href="#commands">5.5. Commands</a></span></dt>
-<dt><span class="section"><a href="#environments">5.6. Environments</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#some-structural-elements">6. Some Structural Elements</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#documentclass">6.1. 
-        <code class="literal">\documentclass</code>
-      </a></span></dt>
-<dt><span class="section"><a href="#parts-chapters-and-sections">6.2. Parts, Chapters and Sections</a></span></dt>
-<dt><span class="section"><a href="#top-matter">6.3. Top Matter</a></span></dt>
-<dt><span class="section"><a href="#abstract">6.4. Abstract</a></span></dt>
-<dt><span class="section"><a href="#appendices">6.5. Appendices</a></span></dt>
-<dt><span class="section"><a href="#table-of-contents">6.6. Table of Contents</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#elementary-text-typesetting">7. Elementary Text Typesetting</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#emphasizing">7.1. Emphasizing</a></span></dt>
-<dt><span class="section"><a href="#quotation-marks">7.2. Quotation Marks</a></span></dt>
-<dt><span class="section"><a href="#dashes-and-hyphens">7.3. Dashes and Hyphens</a></span></dt>
-<dt><span class="section"><a href="#footnotes">7.4. Footnotes</a></span></dt>
-<dt><span class="section"><a href="#flushleft-flushright-and-center">7.5. Flushleft, Flushright, and Center</a></span></dt>
-<dt><span class="section"><a href="#itemize-enumerate-and-description">7.6. Itemize, Enumerate, and Description</a></span></dt>
-<dt><span class="section"><a href="#quote-quotation-and-verse">7.7. Quote, Quotation, and Verse</a></span></dt>
-<dt><span class="section"><a href="#verbatim">7.8. Verbatim</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#tables-figures-and-captions">8. Tables, Figures and Captions</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#the-tabular-environment">8.1. The 
-        <code class="literal">\tabular</code> environment
-      </a></span></dt>
-<dt><span class="section"><a href="#importing-graphics">8.2. Importing Graphics</a></span></dt>
-<dt><span class="section"><a href="#floats">8.3. Floats</a></span></dt>
-<dt><span class="section"><a href="#captions">8.4. Captions</a></span></dt>
-<dt><span class="section"><a href="#list-of-figures-tables">8.5. List of Figures, Tables</a></span></dt>
-<dt><span class="section"><a href="#cross-references">8.6. Cross References</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#bibliography">9. Bibliography</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#thebibliography-environment">9.1. 
-        <code class="literal">thebibliography</code> environment
-      </a></span></dt>
-<dt><span class="section"><a href="#bibtex">9.2. BibTeX</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#typesetting-math">10. Typesetting Math</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#math-mode">10.1. Math Mode</a></span></dt>
-<dt><span class="section"><a href="#single-equations">10.2. Single Equations</a></span></dt>
-<dt><span class="section"><a href="#basic-elements">10.3. Basic Elements</a></span></dt>
-<dt><span class="section"><a href="#multiple-equations">10.4. Multiple Equations</a></span></dt>
-<dt><span class="section"><a href="#arrays-and-matrices">10.5. Arrays and Matrices</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#miscellaneous-stuff">11. Miscellaneous Stuff</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#presentations">11.1. Presentations</a></span></dt>
-<dt><span class="section"><a href="#including-code">11.2. Including Code</a></span></dt>
-<dt><span class="section"><a href="#including-files">11.3. Including files</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#recommended-reading">12. Recommended Reading</a></span></dt>
-</dl>
-</div>Introduction
-  <p id="x_c8"></a>LaTeX is a typesetting program used to produce excellently typeset documents. It is extensively used for producing high quality scientific and mathematical documents. It may also be used for producing other kinds of documents, ranging from simple one page articles or letters</p>
-<div class="section" title="1. TeX &amp; LaTeX">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="tex-latex"></a>1. TeX &amp; LaTeX</h2></div></div></div>
-<div class="section" title="1.1. TeX">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="tex"></a>1.1. TeX</h3></div></div></div>
-<p id="x_c9"></a>TeX is a typesetting system designed by Donald Knuth, the renowned Computer Scientist and Emeritus professor at Stanford University. Typesetting is placing text onto a page with all the style formatting defined, so that content looks as intended.</p>
-<p id="x_ca"></a>It was designed with two goals in mind-</p>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p id="x_cb"></a>To allow anybody to produce high-quality books using a reasonable amount of effort.</p></li>
-<li class="listitem"><p id="x_cc"></a>To provide a system that would give the exact same results on all computers, now and in the future</p></li>
-</ol></div>
-<p id="x_cd"></a>TeX is well known for it's stability and portability.</p>
-<p id="x_ce"></a>TeX is pronounced as "tech".</p>
-<p id="x_cf"></a>The current version of TeX is 3.1415926 and is converging to π.</p>
-</div>
-<div class="section" title="1.2. LaTeX">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="latex"></a>1.2. LaTeX</h3></div></div></div>
-<p id="x_d0"></a>LaTeX was originally written by Leslie Lamport in the early 1980s. It is an extension of TeX, consisting of TeX macros and a program to parse the LaTeX files. It is easier to use than TeX itself, at the same time producing the same quality of output.</p>
-<p id="x_d1"></a>LaTeX is pronounced either as "Lah-tech" or "Lay-tech"</p>
-</div>
-</div>
-<div class="section" title="2. WYSIWG vs. WYSIWM">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="wysiwg-vs-wysiwm"></a>2. WYSIWG vs. WYSIWM</h2></div></div></div>
-<p id="x_d2"></a>WYSIWG is an acronym for "What You See Is What You Get". Word processors, are typically WYSIWG tools. LaTeX, TeX or other TeX based tools are not. They are typesetting or text formatting or document description programs. They can be called WYSIWM or "What You See Is What you Mean" systems, since you give a description of how things look, and LaTeX typesets the document for you.</p>
-<p id="x_d3"></a>Here are a few reasons, why you should use LaTeX -</p>
-<div class="blockquote"><blockquote class="blockquote"><div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_d4"></a>LaTeX produces documents with excellent visual quality, especially mathematical and scientific documents.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_d5"></a>It does the typesetting to you. Typically, when one works with a word-processor, the user is doing the text formatting or typesetting along with typing out the content. LaTeX allows the user to concentrate on the content leaving aside the typesetting to LaTeX.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_d6"></a>It is light on your resources as compared to most of the word processors available today.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_d7"></a>It is well known for it's stability and for it's virtually bug free code base.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_d8"></a>It encourages users to structure documents by meaning rather than appearance, thereby helping produce well structured documents.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_d9"></a>It uses plain text files as input, which have a lot of well known advantages over binary files. To state a few, they can be opened with any editor on any operating system, they are smaller in size compared to the binaries, can be version controlled and can be processed using widely used text processing utilities.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_da"></a>The output can be generated in more than one formats.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_db"></a>It is free software (free as in freedom) and gratis too.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_dc"></a>It is widely used.</p></li>
-</ul></div></blockquote></div>
-</div>
-<div class="section" title="3. Hello World">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="hello-world"></a>3. Hello World</h2></div></div></div>
-<p id="x_dd"></a>OK, let's get started with our first LaTeX document. Open up your favorite editor and type in the following code.</p>
-<pre class="programlisting">%hello.tex - First LaTeX document
-\documentclass{article}
-
-\begin{document}
-  Hello, World!
-\end{document}
-
-</pre>
-<p id="x_de"></a>Save the file as 
-      <code class="literal">hello.tex</code> and open up a terminal to compile your 
-      <code class="literal">tex</code> file to get the output in a 
-      <code class="literal">pdf</code> format.
-    </p>
-<div class="section" title="3.1. Compiling &amp; Output">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="compiling-output"></a>3.1. Compiling &amp; Output</h3></div></div></div>
-<pre class="programlisting">$pdflatex hello.tex
-
-Output written on hello.pdf (1 page, 5733 bytes).
-Transcript written on hello.log.
-
-</pre>
-<p id="x_df"></a>Open the 
-        <code class="literal">hello.pdf</code> to see the output as shown.
-      </p>
-<div class="mediaobject"><img src="examples/hello.jpg"></div>
-<p id="x_e0"></a>Note: The command 
-        <code class="literal">latex</code> is often used to get the 
-        <code class="literal">dvi</code> output. But, throughout this course, we shall use pdflatex to compile our documents.
-      </p>
-</div>
-<div class="section" title="3.2. A peek at the source">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="a-peek-at-the-source"></a>3.2. A peek at the source</h3></div></div></div>
-<p id="x_e1"></a>
-        <code class="literal">%hello.tex - First LaTeX document</code>
-      </p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_e2"></a>This line is a comment. LaTeX ignores this line and it is meant only for the human readers. LaTeX ignores anything after a 
-          <code class="literal">%</code> symbol to the end of the line.
-        </p></blockquote></div>
-<p id="x_e3"></a>
-        <code class="literal">\documentclass{article}</code>
-      </p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_e4"></a>This line is a command and sets the 
-          <code class="literal">documentclass</code> of the document to 
-          <code class="literal">article</code>. LaTeX has other classes like 
-          <code class="literal">report</code>, 
-          <code class="literal">book</code>, 
-          <code class="literal">letter</code>, etc. The typesetting of the document varies depending on the 
-          <code class="literal">documentclass</code> of the document.
-        </p></blockquote></div>
-<p id="x_e5"></a>
-        <code class="literal">\begin{document}</code>
-      </p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_e6"></a>This line informs LaTeX that this is the beginning of the content of the document.</p></blockquote></div>
-<p id="x_e7"></a>
-        <code class="literal">Hello, World!</code>
-      </p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_e8"></a>This is the actual text displayed in the document.</p></blockquote></div>
-<p id="x_e9"></a>
-        <code class="literal">\end{document}</code>
-      </p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_ea"></a>This line tells LaTeX that the document is complete and LaTeX will simply ignore anything written after this line.</p></blockquote></div>
-</div>
-</div>
-<div class="section" title="4. Where do we want to go">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="where-do-we-want-to-go"></a>4. Where do we want to go</h2></div></div></div>
-<p id="x_eb"></a>During the course of this session we will learn how to do various things in LaTeX and try to produce the sample document provided.</p>
-</div>
-<div class="section" title="5. Some Basics">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="some-basics"></a>5. Some Basics</h2></div></div></div>
-<p id="x_ec"></a>Before we get started with creating the document, let's try to understand a few things that would be useful during the course of this session.</p>
-<div class="section" title="5.1. Spaces">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="spaces"></a>5.1. Spaces</h3></div></div></div>
-<p id="x_ed"></a>LaTeX treats multiple empty spaces (or lines) as a single space (or line). An empty line between two lines of text is considered as a change of paragraphs.</p>
-</div>
-<div class="section" title="5.2. Line &amp; Page Breaks">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="line-page-breaks"></a>5.2. Line &amp; Page Breaks</h3></div></div></div>
-<p id="x_ee"></a>LaTeX usually does the job of breaking up your content into lines and pages, and does it well. But under some circumstances, you might want to instruct LaTeX to break line or start a new page at a particular point.</p>
-<p id="x_ef"></a>
-        <code class="literal">\\</code> or 
-        <code class="literal">\newline</code> command is used to create a new line at the point where the command is issued. Appending 
-        <code class="literal">*</code> to 
-        <code class="literal">\\</code>,  instructs LaTeX to create a new line, without creating a new page at that point.
-      </p>
-</div>
-<div class="section" title="5.3. Paragraphs">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="paragraphs"></a>5.3. Paragraphs</h3></div></div></div>
-<p id="x_f0"></a>As already mentioned, LaTeX considers an empty line between two lines of text as a new paragraph. 
-        <code class="literal">\par</code> command may also be used to start a newline. It is equivalent to the blank line.
-      </p>
-<p id="x_f1"></a>By default LaTeX indents new paragraphs. If you do not wish to have the paragraph indented, you can use the 
-        <code class="literal">\nointend</code> command at the beginning of the paragraph.
-      </p>
-</div>
-<div class="section" title="5.4. Special Characters">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="special-characters"></a>5.4. Special Characters</h3></div></div></div>
-<p id="x_f2"></a>LaTeX associates special meaning to the  characters 
-        <code class="literal">~ # $ % ^ &amp; _ { } \</code>.
-      </p>
-<p id="x_f3"></a>To have these characters in the text of your document, you need to prefix a backslash to them. 
-        <code class="literal">\~ \# \% \$ \^ \&amp; \_ \{ \} \textbackslash</code>
-      </p>
-</div>
-<div class="section" title="5.5. Commands">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="commands"></a>5.5. Commands</h3></div></div></div>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_f4"></a>All LaTeX commands start with a backslash 
-            <code class="literal">\</code>.
-          </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_f5"></a>Like the commands in Linux, they are case sensitive.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_f6"></a>They usually have a backslash followed by a consisting of letters only. Any character other than letters, like space, numbers or special characters terminate the command.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_f7"></a>The commands for producing special characters in the text, is an exception. They contain a backslash followed by a single special character.</p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_f8"></a>Commands may have parameters, which are supplied to them by enclosing them in curly braces 
-            <code class="literal">{ }</code>.
-          </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_f9"></a>They may also have a few optional parameters which are added after the name in square brackets 
-            <code class="literal">[ ]</code>.
-          </p></li>
-</ul></div>
-</div>
-<div class="section" title="5.6. Environments">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="environments"></a>5.6. Environments</h3></div></div></div>
-<p id="x_fa"></a>Environments are very similar to the commands, except that they effect larger parts of the document. For example, we used the 
-        <code class="literal">document</code> environment in our first LaTeX document.
-      </p>
-<div class="itemizedlist"><ul class="itemizedlist" type="*">
-<li class="listitem" style="list-style-type: *"><p id="x_fb"></a>They begin with a 
-            <code class="literal">\begin</code> and end with a 
-            <code class="literal">\end</code>
-          </p></li>
-<li class="listitem" style="list-style-type: *"><p id="x_fc"></a>In general environments can be nested within each other.</p></li>
-</ul></div>
-</div>
-</div>
-<div class="section" title="6. Some Structural Elements">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="some-structural-elements"></a>6. Some Structural Elements</h2></div></div></div>
-<div class="section" title="6.1.  \documentclass">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="documentclass"></a>6.1. 
-        <code class="literal">\documentclass</code>
-      </h3></div></div></div>
-<p id="x_fd"></a>As already stated, the 
-        <code class="literal">documentclass</code> command tells LaTeX, the type of the document that you intend to create. Each class has a few differences in how the content of the document is typeset. We presently have it set to the article class. Let us try changing it to the report class.
-      </p>
-<p id="x_fe"></a>Note that the top matter of the document appears in a different page for the report class.</p>
-<p id="x_ff"></a>Some of the LaTeX classes that you may want to use are, article, proc, report, book, slides, letter.</p>
-<p id="x_100"></a>The 
-        <code class="literal">documentclass</code> command also accepts a few optional parameters. For example:
-      </p>
-<p id="x_101"></a>\documentclass[12pt,a4paper,oneside,draft]{report}</p>
-<p id="x_102"></a>
-        <code class="literal">12pt</code> specifies the size of the main font in the document. The relative sizes of the various fonts is maintained, when the font size is changed. If no size is specified, 
-        <code class="literal">10pt</code> is assumed by default.
-      </p>
-<p id="x_103"></a>
-        <code class="literal">a4paper</code> specifies the size of the paper to be used for the document.
-      </p>
-<p id="x_104"></a>
-        <code class="literal">oneside</code> specifies that the document will be printed only on one side of the paper. The 
-        <code class="literal">article</code> and 
-        <code class="literal">report</code> classes are 
-        <code class="literal">oneside</code> by default and the 
-        <code class="literal">book</code> class is 
-        <code class="literal">twoside</code>.
-      </p>
-<p id="x_105"></a>
-        <code class="literal">draft</code> marks the hyphenation and justification problems in the document with a small square in the right hand margin of the document, so that they can be easily spotted.
-      </p>
-<p id="x_106"></a>Note: Everything written in between the 
-        <code class="literal">\documentclass</code> command and the 
-        <code class="literal">\begin{document}</code> command is called the Preamble.
-      </p>
-</div>
-<div class="section" title="6.2. Parts, Chapters and Sections">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="parts-chapters-and-sections"></a>6.2. Parts, Chapters and Sections</h3></div></div></div>
-<p id="x_107"></a>Often documents are divided into various parts, chapters, sections and subsections. LaTeX provides an intuitive mechanism to include this in your documents. It has various commands like 
-        <code class="literal">part</code>, 
-        <code class="literal">chapter</code>, 
-        <code class="literal">section</code>, 
-        <code class="literal">subsection</code>, 
-        <code class="literal">subsubsection</code>, 
-        <code class="literal">paragraph</code> and 
-        <code class="literal">subparagraph</code>. Note that all these commands are not available in all the document classes. The 
-        <code class="literal">chapter</code> command is available only in books and reports. Also, the 
-        <code class="literal">letter</code> document class does not have any of these commands.
-      </p>
-<p id="x_108"></a>Let us now give our document some structure, using these commands.</p>
-<p id="x_109"></a>Note that you do not need to provide any numbers to the commands. LaTeX automatically takes care of the numbering. Also, you do not need to enclose the text of a block within 
-        <code class="literal">\begin</code> and 
-        <code class="literal">\end</code> commands. LaTeX starts a new block each time it finds a sectioning command. :
-      </p>
-<pre class="programlisting">\section[Short Title]{This is a very long title and the Short Title will appear in the Table of Contents.}
-
-
-</pre>
-<div class="section" title="6.2.1. Section Numbering">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="section-numbering"></a>6.2.1. Section Numbering</h4></div></div></div>
-<p id="x_10a"></a>As already, you don't need to explicitly do any numbering in LaTeX. Parts are numbered using roman numerals; Chapters and sections are numbered using decimal numbers. When the table of contents is inserted into a document, all the numbered headings automatically appear in it.</p>
-<p id="x_10b"></a>By default LaTeX has numbering up 2 levels, i.e, the parts, chapters, sections and subsections are numbered. You can change this by setting the 
-          <code class="literal">secnumdepth</code> counter using the 
-          <code class="literal">\setcounter</code> command. The following command removes numbering of the subsections. Only parts, chapters and sections are numbered. :
-        </p>
-<pre class="programlisting">\setcounter{secnumdepth}{1}
-
-</pre>
-<p id="x_10c"></a>A sectioning command appended with an asterisk gives an unnumbered heading that is not included in the table of contents. :</p>
-<pre class="programlisting">\section*{Introduction}
-
-</pre>
-</div>
-</div>
-<div class="section" title="6.3. Top Matter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="top-matter"></a>6.3. Top Matter</h3></div></div></div>
-<p id="x_10d"></a>The information about the document such as it's title, the date, the author(s) information etc, is collectively known as the topmatter. Though there is no command called 
-        <code class="literal">topmatter</code>, the term topmatter is frequently used in LaTeX documentation.
-      </p>
-<p id="x_10e"></a>Let us input the top matter for our document now. :</p>
-<pre class="programlisting">\title{LaTeX - A How-to}
-\author{The FOSSEE Team}
-\date
-
-</pre>
-<p id="x_10f"></a>The  commands 
-        <code class="literal">\title</code> and  
-        <code class="literal">\author</code> are self explanatory. The 
-        <code class="literal">\date</code> command automatically puts in today's date into the document. Now let us compile and look at the result.
-      </p>
-<p id="x_110"></a>You would observe that the details do not appear in the document after recompilation. This is because, LaTeX has not been instructed what to do with the top matter information that you have given it. Use the 
-        <code class="literal">\maketitle</code> command within the document environment to instruct LaTeX to place the top matter information into the document.
-      </p>
-</div>
-<div class="section" title="6.4. Abstract">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="abstract"></a>6.4. Abstract</h3></div></div></div>
-<p id="x_111"></a>Lets now place and abstract in the document using the 
-        <code class="literal">abstract</code> environment of LaTeX. The abstract appears in the document after the topmatter but before the main body of the document. :
-      </p>
-<pre class="programlisting">\begin{abstract}
-The abstract abstract.
-\end{abstract}
-
-
-</pre>
-</div>
-<div class="section" title="6.5. Appendices">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="appendices"></a>6.5. Appendices</h3></div></div></div>
-<p id="x_112"></a>LaTeX allows for separate numbering for appendices. 
-        <code class="literal">\appendix</code> command indicates that the sections following are to be included in the appendix. :
-      </p>
-<pre class="programlisting">\appendix
-\chapter{First Appendix}
-
-</pre>
-</div>
-<div class="section" title="6.6. Table of Contents">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="table-of-contents"></a>6.6. Table of Contents</h3></div></div></div>
-<p id="x_113"></a>Parts, chapters or sections that have been auto numbered by LaTeX automatically appear in the Table of Contents (ToC). 
-        <code class="literal">\tableofcontents</code> command places a the ToC, where the command has been issued.
-      </p>
-<p id="x_114"></a>The counter 
-        <code class="literal">tocdepth</code> specifies the depth up to which headings appear in the ToC. It can be set using the 
-        <code class="literal">\setcounter</code> command as shown below. :
-      </p>
-<pre class="programlisting">\setcounter{tocdepth}{3}
-
-</pre>
-<p id="x_115"></a>Unnumbered sections can be placed in the table of contents using the 
-        <code class="literal">\addcontentsline</code> command as shown below. :
-      </p>
-<pre class="programlisting">\section*{Introduction}
-\addcontentsline{toc}{section}{Introduction}
-
-</pre>
-<p id="x_116"></a>Note: To get the correct entries in your table of contents, you will need to run one extra compilation, each time. This is because, the entries of the table of contents are collected during each compilation of the document and utilized during the next compilation.</p>
-</div>
-</div>
-<div class="section" title="7. Elementary Text Typesetting">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="elementary-text-typesetting"></a>7. Elementary Text Typesetting</h2></div></div></div>
-<div class="section" title="7.1. Emphasizing">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="emphasizing"></a>7.1. Emphasizing</h3></div></div></div>
-<p id="x_117"></a>
-        <span class="emphasis"><em>Italic</em></span> font is generally used to emphasize text. The 
-        <code class="literal">\emph</code> command may be used to achieve this effect in LaTeX. :
-      </p>
-<pre class="programlisting">This is the \emph{emphasized text}.
-
-</pre>
-<p id="x_118"></a>If the 
-        <code class="literal">\emph</code> command is nested within another emphasize command, LaTeX emphasized that text using normal fonts. :
-      </p>
-<pre class="programlisting">\emph{Did you wonder what happens when we try \emph{emphasizing text} within \emph{emphasized text}}?
-
-</pre>
-<p id="x_119"></a>        <span class="emphasis"><em>This is emphasized text, and</em></span> this is emphasized text with normal font 
-        <span class="emphasis"><em>, within</em></span> emphasized text.
-      </p>
-</div>
-<div class="section" title="7.2. Quotation Marks">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="quotation-marks"></a>7.2. Quotation Marks</h3></div></div></div>
-<p id="x_11a"></a>When typing in LaTeX, the double quotation mark 
-        <code class="literal">"</code> character shouldn't be used. The grave accent `
-        <code class="literal">
-          <code class="literal"> character produces the left quote and the apostrophe </code>'
-        </code> character produces the right quote. To obtain double quotes they are, each, used twice. :
-      </p>
-<pre class="programlisting">`` Here is an example of putting `text' in quotes ''
-
-</pre>
-</div>
-<div class="section" title="7.3. Dashes and Hyphens">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="dashes-and-hyphens"></a>7.3. Dashes and Hyphens</h3></div></div></div>
-<p id="x_11b"></a>LaTeX has four dashes of different lengths. Three of them can be produces with different number of consecutive dashes. The short dashes are used for hyphens, slightly longer ones for number ranges and the longest ones for comments. The fourth one is a mathematical symbol, the minus sign. :</p>
-<pre class="programlisting">The names of these dashes are: `-' hyphen, `--' en-dash, `---' em-dash and `$-$' minus sign.
-
-</pre>
-<p id="x_11c"></a>The names for these dashes are: ‘‐’ hyphen, ‘–’ en-dash, ‘—’ em-dash and ‘−’ minus sign.</p>
-</div>
-<div class="section" title="7.4. Footnotes">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="footnotes"></a>7.4. Footnotes</h3></div></div></div>
-<p id="x_11d"></a>With the command:</p>
-<pre class="programlisting">\footnote{footnote text}
-
-</pre>
-<p id="x_11e"></a>a footnote is printed at the foot of the current page. Footnotes should always be put after the word or sentence they refer to. Footnotes referring to a sentence or part of it should therefore be put after the comma or period.</p>
-<p id="x_11f"></a>Note: Look at the 
-        <code class="literal">\marginpar</code> command to insert margin notes
-      </p>
-</div>
-<div class="section" title="7.5. Flushleft, Flushright, and Center">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="flushleft-flushright-and-center"></a>7.5. Flushleft, Flushright, and Center</h3></div></div></div>
-<p id="x_120"></a>The environments 
-        <code class="literal">flushleft</code> and 
-        <code class="literal">flushright</code> generate paragraphs that are either left- or right-aligned.
-      </p>
-<p id="x_121"></a>The 
-        <code class="literal">center</code> environment generates centered text.
-      </p>
-</div>
-<div class="section" title="7.6. Itemize, Enumerate, and Description">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="itemize-enumerate-and-description"></a>7.6. Itemize, Enumerate, and Description</h3></div></div></div>
-<p id="x_122"></a>LaTeX has three different environments for producing lists. Itemize, Enumerate and Description allow you to produce lists of various types in LaTeX.</p>
-<p id="x_123"></a>Itemize is used to produce unnumbered lists. The bullets of the list can be easily changed to use any character. Enumerate environment allows you to produce auto-numbered lists. The description environment, allows you to produce a list of definitions. These environments can be nested within each other, easily.</p>
-<pre class="programlisting">\begin{itemize}
-  \item Now we move onto some elementary \emph{Text Typesetting}.
-  \item How do we get \emph{emphasized or italic text}?
-  \item \emph{Did you wonder what happens when we try \emph{emphasizing text} within \emph{emphasized text}}?
-  \item ``Beautiful is better than ugly.''
-\end{itemize}
-
-\begin{description}
-  \item[Description] This list is a description list. 
-  \item[Enumerate] Numbered lists are often useful.
-    \begin{enumerate}
-    \item First
-    \item Second
-    \item Third
-    \item \ldots
-    \end{enumerate}
-  \item[Itemize] The list above this description list is an itemize list.
-\end{description}
-
-</pre>
-</div>
-<div class="section" title="7.7. Quote, Quotation, and Verse">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="quote-quotation-and-verse"></a>7.7. Quote, Quotation, and Verse</h3></div></div></div>
-<p id="x_124"></a>LaTeX provides a 
-        <code class="literal">quote</code> environment that can be used for quoting, highlighting important material, etc. :
-      </p>
-<pre class="programlisting">The Zen of Python
-\begin{quote}
-  The Zen of Python, by Tim Peters
-
-  Beautiful is better than ugly.
-  Explicit is better than implicit.
-  Simple is better than complex.
-  Complex is better than complicated.
-  Flat is better than nested.
-  Sparse is better than dense.
-  Readability counts.
-  Special cases aren't special enough to break the rules.
-  Although practicality beats purity.
-  Errors should never pass silently.
-  Unless explicitly silenced.
-  In the face of ambiguity, refuse the temptation to guess.
-  There should be one-- and preferably only one --obvious way to do it.
-  Although that way may not be obvious at first unless you're Dutch.
-  Now is better than never.
-  Although never is often better than *right* now.
-  If the implementation is hard to explain, it's a bad idea.
-  If the implementation is easy to explain, it may be a good idea.
-  Namespaces are one honking great idea -- let's do more of those!
-\end{quote}
-
-</pre>
-<p id="x_125"></a>LaTeX provides two other similar environments, the quotation and the verse environments.</p>
-<p id="x_126"></a>The quotation environment can be used for longer quotes which have several paragraphs, since it indents the first line of each paragraph.</p>
-<p id="x_127"></a>The verse environment may be used to quote verses or poems, since the line breaks are important in quoting them. The lines are separated using 
-        <code class="literal">\\\\</code> at the end of a line and an empty line after each verse.
-      </p>
-</div>
-<div class="section" title="7.8. Verbatim">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="verbatim"></a>7.8. Verbatim</h3></div></div></div>
-<p id="x_128"></a>The verbatim environment allows us to insert pre-formatted text in a LaTeX document. It is useful for inserting code samples within the document. The verbatim text needs to be enclosed between 
-        <code class="literal">\begin{verbatim}</code> and 
-        <code class="literal">\end{verbatim}</code>. :
-      </p>
-<pre class="programlisting">\begin{verbatim}
-from numpy import *
-a = linspace(0, 5, 50, endpoint = False)
-\end{verbatim}
-
-from numpy import *
-a = linspace(0, 5, 50, endpoint = False)
-
-</pre>
-<p id="x_129"></a>To insert verbatim text in-line, the 
-        <code class="literal">\verb</code> command can be used. :
-      </p>
-<pre class="programlisting">The verb command allows placing \verb|verbatim text| in-line. 
-
-</pre>
-<p id="x_12a"></a>The | is just an example of a delimiter character. You can use any character except letters, * or space.</p>
-</div>
-</div>
-<div class="section" title="8. Tables, Figures and Captions">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="tables-figures-and-captions"></a>8. Tables, Figures and Captions</h2></div></div></div>
-<div class="section" title="8.1. The \tabular environment">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="the-tabular-environment"></a>8.1. The 
-        <code class="literal">\tabular</code> environment
-      </h3></div></div></div>
-<p id="x_12b"></a>The 
-        <code class="literal">tabular</code> environment allows you to typeset tables in LaTeX. 
-        <code class="literal">\begin{tabular}[pos]{col fmt}</code> command can be used to specify the parameters of the table and start creating the table.
-      </p>
-<p id="x_12c"></a>The 
-        <code class="literal">pos</code> argument specifies the vertical position of the table relative to the baseline of the surrounding text. It can take on the values 
-        <code class="literal">t</code> for top, 
-        <code class="literal">b</code> for bottom, or 
-        <code class="literal">c</code> for center.
-      </p>
-<p id="x_12d"></a>The 
-        <code class="literal">col fmt</code> argument specifies the formatting of the columns of the table. You need to explicitly specify the formatting for each of the columns in the table. The 
-        <code class="literal">col fmt</code> argument can take on the following values.
-      </p>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="4">
-<col width="12">
-<col width="37">
-</colgroup>
-<tbody>
-<tr>
-<td>
-                <p id="x_12e"></a>
-                  <code class="literal">l</code>
-                </p>
-              </td>
-<td>
-                <p id="x_12f"></a>left justified column content</p>
-              </td>
-<td class="auto-generated"> </td>
-</tr>
-<tr>
-<td>
-                <p id="x_130"></a>
-                  <code class="literal">r</code>
-                </p>
-              </td>
-<td>
-                <p id="x_131"></a>right justified column content</p>
-              </td>
-<td class="auto-generated"> </td>
-</tr>
-<tr>
-<td>
-                <p id="x_132"></a>
-                  <code class="literal">c</code>
-                </p>
-              </td>
-<td>
-                <p id="x_133"></a>centered column content</p>
-              </td>
-<td class="auto-generated"> </td>
-</tr>
-<tr>
-<td>
-                <div class="variablelist"><dl>
-<dt><span class="term">
-                      <code class="literal">*{n}{col}</code>
-                    </span></dt>
-<dd><p></p></dd>
-</dl></div>
-              </td>
-<td>
-                <p id="x_134"></a>produces 
-                  <code class="literal">n</code> columns with the 
-                  <code class="literal">col</code> type of formatting 
-                  <code class="literal">*{3}{c}</code> is the same as {c c c}
-                </p>
-              </td>
-<td class="auto-generated"> </td>
-</tr>
-<tr>
-<td>
-                <p id="x_135"></a>``|</p>
-              </td>
-<td>
-                <p id="x_136"></a>produces a vertical line.</p>
-              </td>
-<td class="auto-generated"> </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_137"></a>Now we look at how to input the actual entries of the tables. Each horizontal row in a table is separated by 
-        <code class="literal">\\</code>. Each column entry of a row is separated by 
-        <code class="literal">&amp;</code>.
-      </p>
-<p id="x_138"></a>The 
-        <code class="literal">\hline</code> command allows you to draw horizontal lines between two rows of the table. But it does not allow you do draw partial lines. 
-        <code class="literal">\cline{a-b}</code> draws a horizontal line from column 
-        <code class="literal">a</code> to column 
-        <code class="literal">b</code>. :
-      </p>
-<pre class="programlisting">\begin{tabular}{|c|c|}
-  \hline
-  \verb+l+ &amp; left justified column content\\ 
-  \hline
-  \verb+r+ &amp; right justified column content\\ 
-  \hline
-  \verb+c+ &amp; centered column content\\ 
-  \hline
-  \verb+*{n}{col}+ &amp; produces \verb+n+ columns with the\\
-                 &amp; \verb+col+ type of formatting\\
-  \cline{2-2}
-                 &amp;\verb+*{3}{c}+ is the same as \verb+{c c c}+ \\
-  \hline
-  \verb+|+ &amp; produces a vertical line\\ 
-  \hline
-\end{tabular}
-
-</pre>
-</div>
-<div class="section" title="8.2. Importing Graphics">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="importing-graphics"></a>8.2. Importing Graphics</h3></div></div></div>
-<p id="x_139"></a>To include images in LaTeX, we require to use an additional package known as 
-        <code class="literal">graphicx</code>.  To load a package, we use the 
-        <code class="literal">\usepackage</code> directive in the preamble of the document. :
-      </p>
-<pre class="programlisting">\usepackage{graphicx}
-
-</pre>
-<p id="x_13a"></a>When compiling with 
-        <code class="literal">pdflatex</code> command,  
-        <span class="strong"><strong>jpg</strong></span>, 
-        <span class="strong"><strong>png</strong></span>, 
-        <span class="strong"><strong>gif</strong></span> and 
-        <span class="strong"><strong>pdf</strong></span> images can be inserted.
-      </p>
-<pre class="programlisting">\includegraphics[optional arguments]{imagename}
-
-</pre>
-<p id="x_13b"></a>A few 
-        <code class="literal">optional arguments</code>:
-      </p>
-<div class="blockquote"><blockquote class="blockquote">
-<div class="variablelist"><dl>
-<dt><span class="term">
-              <code class="literal">width=x</code>, 
-              <code class="literal">height=x</code>
-            </span></dt>
-<dd>
-<p></p>
-<p id="x_13c"></a>If only the height or width is specified, the image is scaled, maintaining the aspect ratio.</p>
-</dd>
-</dl></div>
-<div class="blockquote"><blockquote class="blockquote">
-<div class="variablelist"><dl>
-<dt><span class="term">
-                <code class="literal">keepaspectratio</code>
-              </span></dt>
-<dd>
-<p></p>
-<p id="x_13d"></a>This parameter can either be set to true or false. When set to true, the image is scaled according to both width and height, without changing the aspect ratio, so that it does not exceed both the width and the height dimensions.</p>
-</dd>
-</dl></div>
-<div class="blockquote"><blockquote class="blockquote">
-<div class="variablelist"><dl>
-<dt><span class="term">
-                  <code class="literal">scale=x</code>
-                </span></dt>
-<dd>
-<p></p>
-<p id="x_13e"></a>Scale the image by a factor of 
-                    <code class="literal">x</code>. For example, 
-                    <code class="literal">scale=2</code>, will double the image size.
-                  </p>
-</dd>
-</dl></div>
-<div class="blockquote"><blockquote class="blockquote"><div class="variablelist"><dl>
-<dt><span class="term">
-                    <code class="literal">angle=x</code>
-                  </span></dt>
-<dd>
-<p></p>
-<div class="blockquote"><blockquote class="blockquote"><p id="x_13f"></a>This option can be used to rotate the image by 
-                        <code class="literal">x</code> degrees, counter-clockwise.
-                      </p></blockquote></div>
-</dd>
-</dl></div></blockquote></div>
-</blockquote></div>
-</blockquote></div>
-</blockquote></div>
-<pre class="programlisting">\includegraphics[scale=0.8, angle=30]{lion_orig.png}
-
-</pre>
-</div>
-<div class="section" title="8.3. Floats">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="floats"></a>8.3. Floats</h3></div></div></div>
-<p id="x_140"></a>Tables and Figures need to be treated in a special manner, since they cannot be split over pages, and they are referred to as floats in LaTeX.</p>
-<p id="x_141"></a>When there is not enough space on a page, to fit in a table or figure, it is floated over to the next page filling up the current page with text. LaTeX has float environments called table and figure for tables and images, respectively.</p>
-<p id="x_142"></a>Anything enclosed within the table or figure environments will be treated as floats. :</p>
-<pre class="programlisting">\begin{figure}[pos] or 
-\begin{table}[pos]
-
-</pre>
-<p id="x_143"></a>The 
-        <code class="literal">pos</code> parameter specifies the placement of the float. The possible values it can take are as follows.
-      </p>
-<div class="informaltable"><table border="1">
-<colgroup>
-<col width="12">
-<col width="68">
-</colgroup>
-<thead><tr>
-<th>
-                <p id="x_144"></a>Specifier</p>
-              </th>
-<th>
-                <p id="x_145"></a>Permission</p>
-              </th>
-</tr></thead>
-<tbody>
-<tr>
-<td>
-                <p id="x_146"></a>h</p>
-              </td>
-<td>
-                <p id="x_147"></a>at approximately the same place where it occurs in the source</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_148"></a>t</p>
-              </td>
-<td>
-                <p id="x_149"></a>at the top of the page.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_14a"></a>b</p>
-              </td>
-<td>
-                <p id="x_14b"></a>at the bottom of the page.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_14c"></a>p</p>
-              </td>
-<td>
-                <p id="x_14d"></a>on a special page for floats only.</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_14e"></a>!</p>
-              </td>
-<td>
-                <p id="x_14f"></a>Override LaTeX's internal parameters for good positions</p>
-              </td>
-</tr>
-<tr>
-<td>
-                <p id="x_150"></a>H</p>
-              </td>
-<td>
-                <p id="x_151"></a>nearly equivalent to h!</p>
-              </td>
-</tr>
-</tbody>
-</table></div>
-<p id="x_152"></a>Examples:</p>
-<pre class="programlisting">\begin{figure}[h]
-\centering
-\includegraphics[scale=0.8, angle=30]{lion_orig.png}
-\end{figure}
-
-
-</pre>
-</div>
-<div class="section" title="8.4. Captions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="captions"></a>8.4. Captions</h3></div></div></div>
-<p id="x_153"></a>The 
-        <code class="literal">\caption{text}</code> command allows you to add captions to images or tables. LaTeX automatically numbers your tables and figures and you need not include numbers in the captions that you write. The caption appears below or on top of the image (or table), depending on whether you place it after or before the 
-        <code class="literal">importgraphics</code> (or 
-        <code class="literal">tabular</code>) command.
-      </p>
-<p id="x_154"></a>\begin{figure}[h] \centering \includegraphics[scale=0.8]{lion_orig.png} \caption{CTAN lion drawing by Duane Bibby; thanks to www.ctan.org} \end{figure}</p>
-<p id="x_155"></a>The caption command also, like the section command, has the short caption optional parameter. The short caption will appear in the list of tables or figures.</p>
-</div>
-<div class="section" title="8.5. List of Figures, Tables">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="list-of-figures-tables"></a>8.5. List of Figures, Tables</h3></div></div></div>
-<p id="x_156"></a>LaTeX can automatically generate a List of Tables or Figures, with the table or figure numbers, the captions and page numbers on which they appear. This can be done using the 
-        <code class="literal">\listoftables</code> or 
-        <code class="literal">listoffigures</code> commands.
-      </p>
-<p id="x_157"></a>Note: Just like table of contents, these lists also require an extra compilation.</p>
-</div>
-<div class="section" title="8.6. Cross References">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="cross-references"></a>8.6. Cross References</h3></div></div></div>
-<p id="x_158"></a>LaTeX has a very efficient mechanism of inserting cross-references in documents.</p>
-<p id="x_159"></a>The command 
-        <code class="literal">\label{name}</code> is used to label figures, tables or segments of text. 
-        <code class="literal">\ref{name}</code> refers to the object marked by the 
-        <code class="literal">name</code> by it's numbering (figure, table, section etc.) 
-        <code class="literal">\pageref{name}</code> gives the page number of the object which has been labeled with 
-        <code class="literal">name</code>.
-      </p>
-<p id="x_15a"></a>Note: Cross referencing also requires an extra compilation, like table of contents.</p>
-</div>
-</div>
-<div class="section" title="9. Bibliography">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="bibliography"></a>9. Bibliography</h2></div></div></div>
-<p id="x_15b"></a>Bibliography or references can be added to LaTeX documents in two ways - using the 
-      <code class="literal">thebibliography</code> environment, or using BibTeX. Let's first look at using the 
-      <code class="literal">\thebibliography</code> environment and then move on to BibTeX.
-    </p>
-<div class="section" title="9.1.  thebibliography environment">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="thebibliography-environment"></a>9.1. 
-        <code class="literal">thebibliography</code> environment
-      </h3></div></div></div>
-<p id="x_15c"></a>Writing bibliographies in LaTeX using the 
-        <code class="literal">thebibliography</code> environment is pretty easy. You simply have to list down all the bibliography items within the bibliography environment.
-      </p>
-<p id="x_15d"></a>Each entry of the bibliography begins with the command 
-        <code class="literal">\bibitem[label]{name}</code>. The name is used to cite the bibliography item within the document using  
-        <code class="literal">\cite{name}</code>. The label option replaces the numbers from the auto enumeration with the labels given. :
-      </p>
-<pre class="programlisting">He used this lion in the illustrations for D Knuth's original TeXbook\cite{DKnuth}, for L Lamport's LaTeX book\cite{LLamport}
-
-\begin{thebibliography}{99}
-  \bibitem{DKnuth} Donald E. Knuth (1984). \emph{The TeXbook} (Computers and Typesetting, Volume A). Reading, Massachusetts: Addison-Wesley. ISBN 0-201-13448-9.
-
-  \bibitem{LLamport} Lamport, Leslie (1994). \emph{LaTeX: A document preparation system: User's guide and reference}.
-   illustrations by Duane Bibby (2nd ed.). Reading, Mass: Addison-Wesley Professional. 
-\end{thebibliography}
-
-</pre>
-<p id="x_15e"></a>The 
-        <code class="literal">99</code> in the example above indicates the maximum width of the label that the references may get. We here assume that the number of Bibliography items will be less than 100. If your document has less than 10 references, you may want to replace 
-        <code class="literal">99</code> with 
-        <code class="literal">9</code>.
-      </p>
-</div>
-<div class="section" title="9.2. BibTeX">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="bibtex"></a>9.2. BibTeX</h3></div></div></div>
-<p id="x_15f"></a>The previous section explained the process of listing references at the end of a document and embedding cross references. In this section let us explore the BibTeX environment for keeping track of references.</p>
-<p id="x_160"></a>Using BibTeX is a very convenient method to use, when writing multiple documents in a single area or field. BibTeX allows you to create a database of all your references and use them as and when required.</p>
-<p id="x_161"></a>The BibTeX database is stored in a 
-        <code class="literal">.bib</code> file. The structure of the file is quite simple and an example is shown below. :
-      </p>
-<pre class="programlisting">@book{Lamport94,
-author    = "Leslie Lamport",
-title     = "A Document Preparation System: User's Guide and Reference",
-publisher = "Addison-Wesley Professional",
-year      = "1994",
-edition    = "second",
-note      = "illustrations by Duane Bibby"
-}
-
-</pre>
-<p id="x_162"></a>Each bibliography entry starts with a declaration of the type of the reference being mentioned. The reference is in the above example is of the book type. BibTeX has a wide range of reference types, for example, 
-        <code class="literal">article, book, conference, manual, proceedings, unpublished</code>.
-      </p>
-<p id="x_163"></a>The type of reference is followed by a left curly brace, and immediately followed by the citation key. The citation key, 
-        <code class="literal">Lamport94</code> in the example above is used to cite this reference using the command 
-        <code class="literal">\cite{Lamport94}</code>.
-      </p>
-<p id="x_164"></a>This is followed by the relevant fields and their values, listed one by one. Each entry must be followed by a comma to delimit one field from the other.</p>
-<p id="x_165"></a>To get your LaTeX document to use the bibliography database, you just add the following lines to your LaTeX document. :</p>
-<pre class="programlisting">\bibliographystyle{plain}
-\bibliography{LaTeX}
-
-</pre>
-<p id="x_166"></a>Bibliography styles are files that tell BibTeX how to format the information stored in the 
-        <code class="literal">.bib</code> database file. The style file for this example is 
-        <code class="literal">plain.bst</code>. Note that you do not need to add the 
-        <code class="literal">.bst</code> extension to the filename.  If you wish to achieve a particular style of listing the bibliography items and citing them, you should use an appropriate style file.
-      </p>
-<p id="x_167"></a>The 
-        <code class="literal">bibliography</code> command specifies the file that should be used as the database for references. The file used in this example is 
-        <code class="literal">LaTeX.bib</code>
-      </p>
-<div class="section" title="9.2.1. Compiling">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="compiling"></a>9.2.1. Compiling</h4></div></div></div>
-<p id="x_168"></a>Adding BibTeX based references, slightly complicates the process of compiling the document to obtain the desired output. The exact workings of LaTeX and BibTeX will not be explained here. The procedure for obtaining the output (without any explanations) is as follows:</p>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p id="x_169"></a>Compile the 
-              <code class="literal">.tex</code> file using 
-              <code class="literal">pdflatex</code> - 
-              <code class="literal">$pdflatex LaTeX(.tex)</code>
-            </p></li>
-<li class="listitem"><p id="x_16a"></a>Compile the 
-              <code class="literal">.bib</code> file using 
-              <code class="literal">bibtex</code> -  
-              <code class="literal">$bibtex LaTeX(.bib)</code>
-            </p></li>
-<li class="listitem"><p id="x_16b"></a>Compile the 
-              <code class="literal">.tex</code> file again.
-            </p></li>
-<li class="listitem"><p id="x_16c"></a>Compile the 
-              <code class="literal">.tex</code> file for one last time!
-            </p></li>
-</ol></div>
-</div>
-</div>
-</div>
-<div class="section" title="10. Typesetting Math">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="typesetting-math"></a>10. Typesetting Math</h2></div></div></div>
-<p id="x_16d"></a>It is advisable to use the AMS-LaTeX bundle to typeset mathematics in LaTeX. It is a collection of packages and classes for mathematical typesetting.</p>
-<p id="x_16e"></a>We load 
-      <code class="literal">amsmath</code> by issuing the 
-      <code class="literal">\usepackage{amsmath}</code> in the preamble. Through out this section, it is assumed that the 
-      <code class="literal">amsmath</code> package has been loaded.
-    </p>
-<div class="section" title="10.1. Math Mode">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="math-mode"></a>10.1. Math Mode</h3></div></div></div>
-<p id="x_16f"></a>There are a few differences between the 
-        <span class="emphasis"><em>math mode</em></span> and the 
-        <span class="emphasis"><em>text mode</em></span>:
-      </p>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p id="x_170"></a>Most spaces and line breaks do not have any significance, as all spaces are either derived logically from the mathematical expressions, or have to be specified with special commands such as 
-            <code class="literal">\</code>, 
-            <code class="literal">\quad</code> or 
-            <code class="literal">\qquad</code>
-          </p></li>
-<li class="listitem"><p id="x_171"></a>Empty lines are not allowed.</p></li>
-<li class="listitem"><p id="x_172"></a>Each letter is considered to be the name of a variable and will be typeset as such. If you want to typeset normal text within a formula, then you have to enter the text using the \text{...} command</p></li>
-</ol></div>
-</div>
-<div class="section" title="10.2. Single Equations">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="single-equations"></a>10.2. Single Equations</h3></div></div></div>
-<p id="x_173"></a>Mathematical equations can be inserted in-line within a paragraph (
-        <span class="emphasis"><em>text style</em></span>), or the paragraph can be broken to typeset it separately (
-        <span class="emphasis"><em>display style</em></span>).
-      </p>
-<p id="x_174"></a>A mathematical equation within a paragraph is entered between 
-        <code class="literal">$</code> and 
-        <code class="literal">$</code>. Larger equations are set apart from the paragraph, by enclosing them within 
-        <code class="literal">\begin{equation}</code> and 
-        <code class="literal">\end{equation}</code>. If you don't wish to number a particular equation, the starred version of equation can be used. 
-        <code class="literal">\begin{equation*}</code> and 
-        <code class="literal">\end{equation*}</code>
-      </p>
-<p id="x_175"></a>The equation can also be cross referenced using the 
-        <code class="literal">\label</code> and 
-        <code class="literal">\eqref</code> commands.
-      </p>
-</div>
-<div class="section" title="10.3. Basic Elements">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="basic-elements"></a>10.3. Basic Elements</h3></div></div></div>
-<p id="x_176"></a>Greek Letters can are entered as 
-        <code class="literal">\alpha, \beta, \gamma, \delta, ...</code> for lowercase letters and 
-        <code class="literal">\Alpha, \Beta, \Gamma, ...</code> for uppercase ones.
-      </p>
-<p id="x_177"></a>Exponents and subscripts can be typeset using the carat 
-        <code class="literal">^</code> and the underscore 
-        <code class="literal">_</code> respectively. Most of the math mode commands act only on the next character. If you want a command to affect several characters, they need to be enclosed in curly braces.
-      </p>
-<p id="x_178"></a>The 
-        <code class="literal">\sqrt</code> command is used to typeset the square root symbol. LaTeX of the root sign is determined automatically. The nth root is generated with 
-        <code class="literal">\sqrt[n]</code>.
-      </p>
-<p id="x_179"></a>To explicitly show a multiplication a dot may be shown. 
-        <code class="literal">\cdot</code> could be used, which typesets the dot to the center. 
-        <code class="literal">\cdots</code> is three centered dots while 
-        <code class="literal">\ldots</code> sets the dots on the baseline. Besides that 
-        <code class="literal">\vdots</code> for vertical and 
-        <code class="literal">\ddots</code> can be used for diagonal dots.
-      </p>
-<p id="x_17a"></a>A fraction can be typeset with the command 
-        <code class="literal">\frac{..}{..}</code>
-      </p>
-<p id="x_17b"></a>The integral operator is generated with 
-        <code class="literal">\int</code>, the sum operator with 
-        <code class="literal">\sum</code>, and the product operator with 
-        <code class="literal">\prod</code>. The upper and lower limits are specified with 
-        <code class="literal">^</code> and 
-        <code class="literal">_</code> like subscripts and superscripts.
-      </p>
-<p id="x_17c"></a>LaTeX provides all kinds of braces as delimiters. The round and square brackets can be produces using the keys on the keyboard and appending a backslash. Other delimiters can be produced using special commands of LaTeX. Placing 
-        <code class="literal">\left</code> in front of an opening delimiter and 
-        <code class="literal">\right</code> in front of a closing delimiter, instructs LaTeX to automatically take care of the sizes of the delimiters.
-      </p>
-</div>
-<div class="section" title="10.4. Multiple Equations">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="multiple-equations"></a>10.4. Multiple Equations</h3></div></div></div>
-<p id="x_17d"></a>Long formulae that run over several lines or equation systems, can be typeset using the 
-        <code class="literal">align</code> or 
-        <code class="literal">align*</code> environments. 
-        <code class="literal">align</code> numbers each of the lines in the environment, and 
-        <code class="literal">align*</code> as expected, does not number any of them.
-      </p>
-<p id="x_17e"></a>The 
-        <code class="literal">&amp;</code> is used to align the equations vertically and the 
-        <code class="literal">\\</code> command is used to break the lines. Line numbering can be skipped for a particular line in the 
-        <code class="literal">align</code> environment by placing a 
-        <code class="literal">\nonumber</code> before the line break.
-      </p>
-<pre class="programlisting">\begin{align}
-\alpha^2 + \beta^2 &amp;= \gamma^2 \\
-\sum_{i=1}^ni &amp;= \frac{n(n+1)}{2}\\
-\sqrt{-1} &amp;= \pm1 \nonumber
-\end{align}
-
-
-</pre>
-</div>
-<div class="section" title="10.5. Arrays and Matrices">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="arrays-and-matrices"></a>10.5. Arrays and Matrices</h3></div></div></div>
-<p id="x_17f"></a>To typeset arrays, use the 
-        <code class="literal">array</code> environment. It works similar to the 
-        <code class="literal">tabular</code> environment. The 
-        <code class="literal">\\</code> command is used to break the lines. :
-      </p>
-<pre class="programlisting">\begin{equation*}
-\mathbf{X} = \left(
- \begin{array}{ccc}
- a_1 &amp; a_2 &amp; \ldots \\
- b_1 &amp; b_2 &amp; \ldots \\
- \vdots &amp; \vdots &amp; \ddots
- \end{array} \right)
-\end{equation*}
-
-</pre>
-<p id="x_180"></a>The 
-        <code class="literal">array</code> environment can also be used to typeset piecewise functions by using a “.” as an invisible 
-        <code class="literal">\right</code> delimiter :
-      </p>
-<pre class="programlisting">\begin{equation*}
-f(x) = \left\{
- \begin{array}{rl}
-   0 &amp; \text{if } x \le 0\\
-   1 &amp; \text{if } x &gt; 0
- \end{array} \right.
- \end{equation*}
-
-</pre>
-<p id="x_181"></a>Six different types of matrix environments are available in the 
-        <code class="literal">amsmath</code> package for typesetting matrices.  They essentially have different delimiters: 
-        <code class="literal">matrix</code> (none), 
-        <code class="literal">pmatrix</code> (, 
-        <code class="literal">bmatrix</code> [, 
-        <code class="literal">Bmatrix</code> {, 
-        <code class="literal">vmatrix</code> | and 
-        <code class="literal">Vmatrix</code> ‖. In these matrix environments, the number of columns need not be specified, unlike the 
-        <code class="literal">array</code> environment. :
-      </p>
-<pre class="programlisting">\begin{equation*}
-  \begin{matrix}
-  1 &amp; 2 \\
-  3 &amp; 4
-  \end{matrix} \qquad
-
-  \begin{bmatrix}
-  1 &amp; 2 &amp; 3 \\
-  4 &amp; 5 &amp; 6 \\
-  7 &amp; 8 &amp; 9
-  \end{bmatrix}
-\end{equation*}
-
-</pre>
-</div>
-</div>
-<div class="section" title="11. Miscellaneous Stuff">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="miscellaneous-stuff"></a>11. Miscellaneous Stuff</h2></div></div></div>
-<div class="section" title="11.1. Presentations">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="presentations"></a>11.1. Presentations</h3></div></div></div>
-<p id="x_182"></a>LaTeX has quite a few options to produce presentation slides. We shall look at the 
-        <code class="literal">beamer</code> class, which is well developed and easy to use. We shall only briefly look at some of the features of beamer. For the best documentation, look at the beamer user guide.
-      </p>
-<p id="x_183"></a>To write a 
-        <code class="literal">beamer</code> presentation, it is recommended that you use one of the templates that beamer provides. We shall use the 
-        <code class="literal">speaker_introduction</code> template to get started with beamer.
-      </p>
-<p id="x_184"></a>As you can see, the document begins with the 
-        <code class="literal">documentclass</code> being set to beamer.
-      </p>
-<p id="x_185"></a>The 
-        <code class="literal">\setbeamertemplate</code> command sets the template for various parameters. The 
-        <code class="literal">background canvas</code>, 
-        <code class="literal">headline</code> and 
-        <code class="literal">footline</code> are being set using the command.
-      </p>
-<p id="x_186"></a>
-        <code class="literal">\usetheme</code> command sets the theme to be used in the presentation.
-      </p>
-<p id="x_187"></a>Notice that each slide is enclosed within 
-        <code class="literal">\begin{frame}</code> and 
-        <code class="literal">\end{frame}</code> commands. The 
-        <code class="literal">\begin{frame}</code> command can be passed the Title and Subtitle of the slide as parameters.
-      </p>
-<p id="x_188"></a>To achieve more with beamer, it is highly recommended that you look at the 
-        <code class="literal">beameruserguide</code>.
-      </p>
-</div>
-<div class="section" title="11.2. Including Code">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="including-code"></a>11.2. Including Code</h3></div></div></div>
-<p id="x_189"></a>The 
-        <code class="literal">listings</code> package can be used to embed source code into your LaTeX document. We shall briefly explore inserting python code into our document.
-      </p>
-<p id="x_18a"></a>Obviously, you first need to tell LaTeX that you want it to use the 
-        <code class="literal">listings</code> package, using the 
-        <code class="literal">\usepackage</code> command. :
-      </p>
-<pre class="programlisting">\usepackage{listings}
-
-</pre>
-<p id="x_18b"></a>Then, we tell LaTeX that we are going to embed Python code into this document. A simple code highlighting for Python code can be achieved using this. :</p>
-<pre class="programlisting">\lstset{language=Python,
-        showstringspaces=false,
-       }
-
-</pre>
-<p id="x_18c"></a>You might want to customize the code highlighting further using other variables like 
-        <code class="literal">basicstyle</code>, 
-        <code class="literal">commentstyle</code>, 
-        <code class="literal">stringstyle</code>, 
-        <code class="literal">keywordstyle</code> etc. For detailed information on all this, you should look at the 
-        <code class="literal">listings</code> package documentation.
-      </p>
-<p id="x_18d"></a>You include a block of code into your document by enclosing it within the 
-        <code class="literal">lstlisting</code> environment. :
-      </p>
-<pre class="programlisting">\begin{lstlisting}
-string="Hello, World! "
-for i in range(10):
-    print string*i
-\end{lstlisting} 
-
-</pre>
-<p id="x_18e"></a>You can also include source code files directly into your latex document, using the 
-        <code class="literal">lstinputlisting</code> command. :
-      </p>
-<pre class="programlisting">\lstinputlisting[lastline=20]{lstexample.py}
-
-</pre>
-<p id="x_18f"></a>This command includes the first 20 lines of the file 
-        <code class="literal">lstexample.py</code> into out LaTeX document.
-      </p>
-</div>
-<div class="section" title="11.3. Including files">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="including-files"></a>11.3. Including files</h3></div></div></div>
-<p id="x_190"></a>When working on a large document, it is convenient sometimes, to split the large file into smaller input files and club them together at the time of compiling.</p>
-<p id="x_191"></a>The 
-        <code class="literal">\input</code> or 
-        <code class="literal">\include</code> commands may be used to embed one LaTeX file into another. The 
-        <code class="literal">\input</code> command is equivalent to a copy and paste of the document, just before the compilation. The 
-        <code class="literal">\include</code> command is exactly similar, except for the fact that it creates a new page every time it is issued.
-      </p>
-<p id="x_192"></a>
-        <code class="literal">\input{file}</code> or 
-        <code class="literal">\include{file}</code> commands will include the file 
-        <code class="literal">file1.tex</code> with in the file where the command has been issued. Note that you do not need to specify the 
-        <code class="literal">.tex</code> extension of the file.
-      </p>
-<p id="x_193"></a>The 
-        <code class="literal">\includeonly</code> is useful for debugging or testing the LaTeX document that you are creating, since it restricts the 
-        <code class="literal">\include</code> command. Only the files which are given as arguments to the 
-        <code class="literal">\includeonly</code> command will be included in the document (wherever a 
-        <code class="literal">\include</code> command for those files, has been issued).
-      </p>
-<div class="section" title="11.3.1. A note on filenames">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="a-note-on-filenames"></a>11.3.1. A note on filenames</h4></div></div></div>
-<p id="x_194"></a>Never use filenames or directories that contain spaces. Make filenames as long or short as you would like, but strictly avoid spaces. Stick to upper or lower case letters (without accents), the digits, the hyphen and the full stop or period.</p>
-</div>
-</div>
-</div>
-<div class="section" title="12. Recommended Reading">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="recommended-reading"></a>12. Recommended Reading</h2></div></div></div>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p id="x_195"></a>
-          <span class="emphasis"><em>LaTeX Wikibook</em></span>
-        </p></li>
-<li class="listitem"><p id="x_196"></a>
-          <span class="emphasis"><em>The Not So Short Introduction to LaTeX2e</em></span> by Tobias Oetikar et al..
-        </p></li>
-</ol></div>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch04-latex.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,66 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. </title>
-<link rel="stylesheet" href="hgbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 1. ">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2439024">Module 3: LaTeX</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#suggested-reading">1. Suggested Reading</a></span></dt>
-<dt><span class="section"><a href="#session-level-split-up">2. Session Level Split-up</a></span></dt>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="Module 3: LaTeX">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2439024"></a>Module 3: LaTeX</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#suggested-reading">1. Suggested Reading</a></span></dt>
-<dt><span class="section"><a href="#session-level-split-up">2. Session Level Split-up</a></span></dt>
-</dl>
-</div>Module Objectives
-  <p><a name="x_1fd"></a>After completing this module, a participant will be successfully able to:</p>
-<div class="itemizedlist"><ul class="itemizedlist" type="-">
-<li class="listitem" style="list-style-type: -"><p><a name="x_1fe"></a>Produce professional documents in LaTeX.  RBT Ap</p></li>
-<li class="listitem" style="list-style-type: -"><p><a name="x_1ff"></a>Typeset Mathematical equations.           RBT Ap</p></li>
-<li class="listitem" style="list-style-type: -"><p><a name="x_200"></a>Include figures, tables and code samples. RBT Ap</p></li>
-<li class="listitem" style="list-style-type: -"><p><a name="x_201"></a>Add References and write BibTeX files.    RBT Ap</p></li>
-</ul></div>
-<div class="section" title="1. Suggested Reading">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="suggested-reading"></a>1. Suggested Reading</h2></div></div></div>
-<div class="orderedlist"><ol class="orderedlist" type="1">
-<li class="listitem"><p><a name="x_202"></a>
-          <span class="emphasis"><em>LaTeX Wikibook</em></span>
-        </p></li>
-<li class="listitem"><p><a name="x_203"></a>
-          <span class="emphasis"><em>The Not So Short Introduction to LaTeX2e</em></span> by Tobias Oetikar et. al.
-        </p></li>
-</ol></div>
-</div>
-<div class="section" title="2. Session Level Split-up">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="session-level-split-up"></a>2. Session Level Split-up</h2></div></div></div>
-<p><a name="x_204"></a>+---------+---------------------------------+---------+ | Session | Topic  			    | Duration| +=========+=================================+=========+ | 1	  | Introduction, TeX &amp; LaTeX       |  5 min  | |         | WYSIWG vs. WYSIWM               |         | |         |                                 |         | |         | Hello World, Compiling,         |  10 min | |         | Where we want to go, Some Basics|         | +---------+---------------------------------+---------+ | 2	  | Some Structural Elements        |  15 min | |         |                                 |         | |         | Top Matter, 
-      <code class="literal">\documentclass</code>, |         | |	  | Abstract,                       |         | |         | Sections, Chapters &amp; Parts,     |         | |         | Appendices, Table of Contents   |         | +---------+---------------------------------+---------+ | 3	  | Emphasizing, Quotation marks,   |  5 min  | |	  | Dashes &amp; Hyphens, Footnotes,    |         | |         | Flushleft, Flushright &amp; Center  |         | |	  |                                 |         | |         | Enumerate, Itemize, Description,|  10 min | |         | Quote, Quotation and Verse,     |         | |         | Verbatim                        |         | +---------+---------------------------------+---------+ | 4	  | 
-      <code class="literal">\tabular</code> environment,       |  20 min | |         | Importing Graphics, Floats,     |         | |         | Captions, List of Figures,      |         | |         | List of Tables, Cross References|         | +---------+---------------------------------+---------+ | 5	  | 
-      <code class="literal">\thebibliography</code>            |  10 min | |         | environment, BibTeX             |         | +---------+---------------------------------+---------+ | 6	  | 
-      <code class="literal">\usepackage{amsmath}</code>,       |  5 min  | |         | Single Equations                |         | |         |                                 |         | |         | Building blocks of an equation, |  15 min | |         | Multiple Equations, Arrays and  |         | |	  | Matrices                        |         | +---------+---------------------------------+---------+ | 7       | 
-      <code class="literal">beamer</code>, 
-      <code class="literal">listing</code>,        |  10 min | |         | Including files                 |         | +---------+---------------------------------+---------+ | 8       | Exercises                       |  15 min | +---------+---------------------------------+---------+
-    </p>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch1Introduction.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch1Introduction.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,7 +1,7 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. Introduction</title>
+<title>Introduction</title>
 <link rel="stylesheet" href="/review/support/styles.css" type="text/css">
 <meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
 
@@ -9,29 +9,1133 @@
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
 <script type="text/javascript" src="/review/support/hsbook.js"></script>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" id="ch1Introduction">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch1Introduction">
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2693294">Introduction to the Course</a></span></dt></dl>
+<dl>
+<dt><span class="article"><a href="#id2906013"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2716138">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2903833">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2957074">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2957346">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2957478">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2957486">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2957764">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2957772">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2957935">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2957995">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2958097">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2958179">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2958358">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2958366">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2958459">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2958668">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2958758">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2958811">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2958820">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2959131">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2959268">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2959439">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2959531">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2959540">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2959626">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2959752">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2959838">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2959970">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2960077">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2960086">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2960272">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2960383">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2960623">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2960892">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2960909">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2960932">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2960940">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2961705">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2961742">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2961811">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2961872">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2962076">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2962110">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2962141">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2962150">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2962338">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2962488">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2962701">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2956810">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
 </div>
-<div class="article" title="Introduction to the Course">
+<div class="article">
 <div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2693294"></a>Introduction to the Course</h2></div></div>
+<div><div><h2 class="title" id="id2906013"></a></h2></div></div>
 <hr>
 </div>
-<p id="ch1Introduction_1">Engineering students use computers for a large number of curricular
-tasks – mostly computation centred. However, they do not see this as coding or programming tasks and usually are not even aware of the tools and
-techniques that will help them to handle these tasks better. This results
-in less than optimal use of their time and resources. This also causes
-difficulties when it comes tocollaboration and building on other people’s
-work. This course is intended to train such students in good software
-practices and tools for producing code and documentation.</p>
-<p id="ch1Introduction_2">fter successfully completing the program, the participants will be able to:</p>
-<span style="color: black"><span style="color: black"><p id="ch1Introduction_3"></a>understand how software tools work together and how they can be used in tandem to carry out tasks,</p></span><span style="color: black"><p id="ch1Introduction_4"></a>use unix command line tools to carry out common (mostly text processing tasks,</p></span><span style="color: black"><p id="ch1Introduction_5"></a>to generate professional documents,</p></span><span style="color: black"><p id="ch1Introduction_6"></a>use version control effectively – for both code and documents,</p></span><span style="color: black"><p id="ch1Introduction_7"></a>automate tasks by writing shell scripts and python scripts,</p></span><span style="color: black"><p id="ch1Introduction_8"></a>realise the impact of coding style and readbility on quality,</p></span><span style="color: black"><p id="ch1Introduction_9"></a>write mid-sized programs that carry out typical engineering / numerical computations such as those that involve (basic) manipulation of large arrays in an efficient manner,</p></span><span style="color: black"><p id="ch1Introduction_a"></a>generate 2D and simple 3D plots,</p></span><span style="color: black"><p id="ch1Introduction_b"></a>debug programs using a standardised approach,</p></span><span style="color: black"><p id="ch1Introduction_c"></a>understand the importance of tests and the philosophy of Test Driven Development,</p></span><span style="color: black"><p id="ch1Introduction_d"></a>write unit tests and improve the quality of code.</p></span></span>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2716138">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2903833">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2957074">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2957346">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2957478">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2957486">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2957764">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2957772">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2957935">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2957995">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2958097">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2958179">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2958358">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2958366">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2958459">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2958668">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2958758">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2958811">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2958820">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2959131">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2959268">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2959439">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2959531">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2959540">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2959626">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2959752">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2959838">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2959970">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2960077">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2960086">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2960272">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2960383">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2960623">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2960892">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2960909">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2960932">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2960940">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2961705">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2961742">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2961811">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2961872">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2962076">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2962110">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2962141">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2962150">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2962338">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2962488">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2962701">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2956810">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2716138"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch1Introduction_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch1Introduction_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch1Introduction_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch1Introduction_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2903833"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2903799"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957029"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch1Introduction_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch1Introduction_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957074"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch1Introduction_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957098"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch1Introduction_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch1Introduction_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957152"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch1Introduction_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch1Introduction_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch1Introduction_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957208"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch1Introduction_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch1Introduction_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch1Introduction_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957253"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch1Introduction_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957299"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch1Introduction_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch1Introduction_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch1Introduction_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957346"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch1Introduction_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch1Introduction_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch1Introduction_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch1Introduction_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch1Introduction_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch1Introduction_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2957478"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957486"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch1Introduction_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957517"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch1Introduction_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch1Introduction_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch1Introduction_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch1Introduction_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch1Introduction_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch1Introduction_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch1Introduction_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch1Introduction_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch1Introduction_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2957675"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch1Introduction_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch1Introduction_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch1Introduction_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch1Introduction_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch1Introduction_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2957764"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957772"></a>3.1. ls</h3></div></div></div>
+<p id="ch1Introduction_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch1Introduction_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch1Introduction_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch1Introduction_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957935"></a>3.2. date</h3></div></div></div>
+<p id="ch1Introduction_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch1Introduction_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch1Introduction_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch1Introduction_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch1Introduction_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2957995"></a>3.3. cd</h3></div></div></div>
+<p id="ch1Introduction_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch1Introduction_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch1Introduction_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch1Introduction_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch1Introduction_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch1Introduction_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch1Introduction_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch1Introduction_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch1Introduction_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch1Introduction_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch1Introduction_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch1Introduction_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958097"></a>3.4. who</h3></div></div></div>
+<p id="ch1Introduction_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch1Introduction_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch1Introduction_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch1Introduction_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch1Introduction_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958179"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch1Introduction_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch1Introduction_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958211"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch1Introduction_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958272"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch1Introduction_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch1Introduction_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch1Introduction_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch1Introduction_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch1Introduction_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2958358"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958366"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch1Introduction_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch1Introduction_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch1Introduction_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch1Introduction_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch1Introduction_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958459"></a>4.2. man</h3></div></div></div>
+<p id="ch1Introduction_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch1Introduction_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch1Introduction_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch1Introduction_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch1Introduction_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch1Introduction_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958541"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch1Introduction_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch1Introduction_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch1Introduction_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch1Introduction_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch1Introduction_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch1Introduction_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch1Introduction_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch1Introduction_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch1Introduction_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch1Introduction_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch1Introduction_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch1Introduction_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958668"></a>4.3. info</h3></div></div></div>
+<p id="ch1Introduction_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch1Introduction_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch1Introduction_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958758"></a>4.4. --help</h3></div></div></div>
+<p id="ch1Introduction_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2958811"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2958820"></a>5.1. cp</h3></div></div></div>
+<p id="ch1Introduction_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958837"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch1Introduction_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch1Introduction_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch1Introduction_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958871"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch1Introduction_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch1Introduction_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch1Introduction_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch1Introduction_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2958969"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch1Introduction_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch1Introduction_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch1Introduction_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch1Introduction_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch1Introduction_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch1Introduction_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch1Introduction_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch1Introduction_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch1Introduction_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch1Introduction_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch1Introduction_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch1Introduction_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch1Introduction_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch1Introduction_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch1Introduction_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959131"></a>5.2. mv</h3></div></div></div>
+<p id="ch1Introduction_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959154"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch1Introduction_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959179"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch1Introduction_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959210"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch1Introduction_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch1Introduction_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959268"></a>5.3. rm</h3></div></div></div>
+<p id="ch1Introduction_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch1Introduction_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959298"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch1Introduction_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch1Introduction_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch1Introduction_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch1Introduction_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959399"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch1Introduction_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch1Introduction_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch1Introduction_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2959439"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch1Introduction_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch1Introduction_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch1Introduction_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch1Introduction_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch1Introduction_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch1Introduction_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch1Introduction_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2959531"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959540"></a>7.1. head</h3></div></div></div>
+<p id="ch1Introduction_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch1Introduction_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch1Introduction_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch1Introduction_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959590"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch1Introduction_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch1Introduction_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch1Introduction_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959626"></a>7.2. tail</h3></div></div></div>
+<p id="ch1Introduction_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch1Introduction_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch1Introduction_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch1Introduction_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch1Introduction_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch1Introduction_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch1Introduction_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2959704"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch1Introduction_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch1Introduction_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch1Introduction_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959752"></a>7.3. cut</h3></div></div></div>
+<p id="ch1Introduction_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch1Introduction_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch1Introduction_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch1Introduction_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch1Introduction_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch1Introduction_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch1Introduction_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2959838"></a>7.4. paste</h3></div></div></div>
+<p id="ch1Introduction_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch1Introduction_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch1Introduction_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch1Introduction_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2959970"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch1Introduction_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch1Introduction_df"></a>The shell meta characters include:</p>
+<p id="ch1Introduction_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch1Introduction_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch1Introduction_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch1Introduction_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch1Introduction_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch1Introduction_e5"></a>because the c* matches that long file name.</p>
+<p id="ch1Introduction_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch1Introduction_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch1Introduction_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2960077"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960086"></a>9.1. cat</h3></div></div></div>
+<p id="ch1Introduction_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch1Introduction_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch1Introduction_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960129"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch1Introduction_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960168"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch1Introduction_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch1Introduction_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch1Introduction_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch1Introduction_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch1Introduction_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch1Introduction_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960239"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch1Introduction_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960272"></a>9.2. more</h3></div></div></div>
+<p id="ch1Introduction_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960292"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch1Introduction_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch1Introduction_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch1Introduction_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch1Introduction_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch1Introduction_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960383"></a>9.3. less</h3></div></div></div>
+<p id="ch1Introduction_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960411"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch1Introduction_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch1Introduction_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch1Introduction_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960466"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960518"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960608"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2960623"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch1Introduction_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch1Introduction_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960892"></a>10.1. man hier</h3></div></div></div>
+<p id="ch1Introduction_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960909"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch1Introduction_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch1Introduction_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2960932"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2960940"></a>11.1. chmod</h3></div></div></div>
+<p id="ch1Introduction_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960966"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch1Introduction_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch1Introduction_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2960994"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch1Introduction_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch1Introduction_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2961030"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch1Introduction_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch1Introduction_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch1Introduction_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch1Introduction_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch1Introduction_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2961577"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch1Introduction_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch1Introduction_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch1Introduction_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2961618"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch1Introduction_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch1Introduction_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2961657"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch1Introduction_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch1Introduction_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2961705"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch1Introduction_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch1Introduction_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2961742"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch1Introduction_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch1Introduction_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch1Introduction_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch1Introduction_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2961811"></a>12.2. Piping</h3></div></div></div>
+<p id="ch1Introduction_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch1Introduction_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch1Introduction_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch1Introduction_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch1Introduction_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2961872"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch1Introduction_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch1Introduction_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch1Introduction_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch1Introduction_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch1Introduction_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch1Introduction_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch1Introduction_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch1Introduction_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch1Introduction_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch1Introduction_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch1Introduction_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2962076"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch1Introduction_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch1Introduction_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2962110"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch1Introduction_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch1Introduction_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2962141"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2962150"></a>13.1. grep</h3></div></div></div>
+<p id="ch1Introduction_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2962181"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch1Introduction_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch1Introduction_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch1Introduction_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch1Introduction_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch1Introduction_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch1Introduction_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2962259"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch1Introduction_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch1Introduction_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch1Introduction_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2962338"></a>13.2. tr</h3></div></div></div>
+<p id="ch1Introduction_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch1Introduction_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch1Introduction_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch1Introduction_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch1Introduction_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch1Introduction_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch1Introduction_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch1Introduction_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch1Introduction_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch1Introduction_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch1Introduction_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch1Introduction_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2962488"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch1Introduction_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch1Introduction_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch1Introduction_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch1Introduction_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2962701"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch1Introduction_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch1Introduction_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch1Introduction_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2956810"></a>15. One Liners</h2></div></div></div>
+<p id="ch1Introduction_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch1Introduction_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch1Introduction_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch1Introduction_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch1Introduction_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch1Introduction_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch1Introduction_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch1Introduction_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch1Introduction_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch1Introduction_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch1Introduction_1d7"></a>Print the total number of input lines:</p>
+<p id="ch1Introduction_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch1Introduction_1d9"></a>Print the tenth input line:</p>
+<p id="ch1Introduction_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch1Introduction_1db"></a>Print the last field of every input line:</p>
+<p id="ch1Introduction_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch1Introduction_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch1Introduction_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch1Introduction_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch1Introduction_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch1Introduction_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
 </div>
 </div></body>
 </html>
--- a/web/html/ch1Introduction.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,37 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. Introduction</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-
-<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
-<script type="text/javascript" src="/review/support/jquery-min.js"></script>
-<script type="text/javascript" src="/review/support/form.js"></script>
-<script type="text/javascript" src="/review/support/hsbook.js"></script>
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" id="ch1Introduction">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2693294">Introduction to the Course</a></span></dt></dl>
-</div>
-<div class="article" title="Introduction to the Course">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2693294"></a>Introduction to the Course</h2></div></div>
-<hr>
-</div>
-<p id="ch1Introduction_1">Engineering students use computers for a large number of curricular
-tasks – mostly computation centred. However, they do not see this as coding or programming tasks and usually are not even aware of the tools and
-techniques that will help them to handle these tasks better. This results
-in less than optimal use of their time and resources. This also causes
-difficulties when it comes tocollaboration and building on other people’s
-work. This course is intended to train such students in good software
-practices and tools for producing code and documentation.</p>
-<p id="ch1Introduction_2">fter successfully completing the program, the participants will be able to:</p>
-<span style="color: black"><span style="color: black"><p id="ch1Introduction_3"></a>understand how software tools work together and how they can be used in tandem to carry out tasks,</p></span><span style="color: black"><p id="ch1Introduction_4"></a>use unix command line tools to carry out common (mostly text processing tasks,</p></span><span style="color: black"><p id="ch1Introduction_5"></a>to generate professional documents,</p></span><span style="color: black"><p id="ch1Introduction_6"></a>use version control effectively – for both code and documents,</p></span><span style="color: black"><p id="ch1Introduction_7"></a>automate tasks by writing shell scripts and python scripts,</p></span><span style="color: black"><p id="ch1Introduction_8"></a>realise the impact of coding style and readbility on quality,</p></span><span style="color: black"><p id="ch1Introduction_9"></a>write mid-sized programs that carry out typical engineering / numerical computations such as those that involve (basic) manipulation of large arrays in an efficient manner,</p></span><span style="color: black"><p id="ch1Introduction_a"></a>generate 2D and simple 3D plots,</p></span><span style="color: black"><p id="ch1Introduction_b"></a>debug programs using a standardised approach,</p></span><span style="color: black"><p id="ch1Introduction_c"></a>understand the importance of tests and the philosophy of Test Driven Development,</p></span><span style="color: black"><p id="ch1Introduction_d"></a>write unit tests and improve the quality of code.</p></span></span>
-</div>
-</div></body>
-</html>
--- a/web/html/ch2intro.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch2intro.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,590 +1,1137 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 2. Basic Python</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-
+<title>Intro</title>
 <link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
 <script type="text/javascript" src="/review/support/hsbook.js"></script>
 <meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" id="ch2intro">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch2intro">
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="article"><a href="#id2706129">Basic Python</a></span></dt>
+<dt><span class="article"><a href="#id2931272"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2741397">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2929092">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2982331">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2982596">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2982723">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2982731">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2983003">3. Basic Commands</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2705187">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#id2757271">2. The Python Interpreter</a></span></dt>
+<dt><span class="section"><a href="#id2983011">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2983169">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2983227">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2983324">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2983404">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2983578">4. Getting Help</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2757279">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#id2757464">2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</a></span></dt>
+<dt><span class="section"><a href="#id2983586">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2983667">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2983870">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2983961">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2984014">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2984023">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2984334">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2984483">5.3. rm</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id2757589">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#id2757696">4. Basic Datatypes and operators in Python</a></span></dt>
+<dt><span class="section"><a href="#id2984653">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2984746">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2984755">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2984842">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2984970">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2985055">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2985190">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2985297">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2985305">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2985493">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2985608">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2985848">10. Directory Structure</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2757731">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#id2757854">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#id2757903">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#id2758097">4.4. Boolean</a></span></dt>
+<dt><span class="section"><a href="#id2986117">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2986133">10.2. ls -l</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id2758126">5. The <span class="strong"><strong>while</strong></span> loop</a></span></dt>
-<dt><span class="section"><a href="#id2758163">6. The <span class="strong"><strong>if</strong></span> conditional</a></span></dt>
-<dt><span class="section"><a href="#id2758232">7. <span class="strong"><strong>raw_input()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id2758387">8. <span class="strong"><strong>int()</strong></span> method</a></span></dt>
+<dt><span class="section"><a href="#id2986156">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2986165">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2986929">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2986966">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2987035">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2987096">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2987301">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2987335">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2987365">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2987374">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2987563">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2987713">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2988062">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2988138">15. One Liners</a></span></dt>
 </dl></dd>
 </dl>
 </div>
-<div class="article" title="Basic Python">
+<div class="article">
 <div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2706129"></a>Basic Python</h2></div></div>
+<div><div><h2 class="title" id="id2931272"></a></h2></div></div>
 <hr>
 </div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="section"><a href="#id2705187">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#id2757271">2. The Python Interpreter</a></span></dt>
+<dt><span class="section"><a href="#id2741397">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2929092">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2982331">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2982596">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2982723">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2982731">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2983003">3. Basic Commands</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2757279">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#id2757464">2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</a></span></dt>
+<dt><span class="section"><a href="#id2983011">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2983169">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2983227">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2983324">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2983404">3.5. mkdir</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id2757589">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#id2757696">4. Basic Datatypes and operators in Python</a></span></dt>
+<dt><span class="section"><a href="#id2983578">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2983586">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2983667">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2983870">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2983961">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2984014">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2984023">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2984334">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2984483">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2984653">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2984746">7. Basic Text Processing</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2757731">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#id2757854">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#id2757903">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#id2758097">4.4. Boolean</a></span></dt>
+<dt><span class="section"><a href="#id2984755">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2984842">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2984970">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2985055">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2985190">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2985297">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2985305">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2985493">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2985608">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2985848">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2986117">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2986133">10.2. ls -l</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id2758126">5. The <span class="strong"><strong>while</strong></span> loop</a></span></dt>
-<dt><span class="section"><a href="#id2758163">6. The <span class="strong"><strong>if</strong></span> conditional</a></span></dt>
-<dt><span class="section"><a href="#id2758232">7. <span class="strong"><strong>raw_input()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id2758387">8. <span class="strong"><strong>int()</strong></span> method</a></span></dt>
+<dt><span class="section"><a href="#id2986156">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2986165">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2986929">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2986966">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2987035">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2987096">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2987301">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2987335">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2987365">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2987374">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2987563">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2987713">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2988062">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2988138">15. One Liners</a></span></dt>
 </dl>
 </div>
-<p id="ch2intro_1"></a>This document is intended to be handed out at the end of the workshop. It has
-been designed for Engineering students who are Python beginners and have basic
-programming skills. The focus is on basic numerics and plotting using Python.</p>
-<span style="color: black"><span style="color: black"><span style="color: black">The system requirements:</span><span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_2"></a>Python - version 2.5.x or newer.</p></span><span style="color: black"><p id="ch2intro_3"></a>IPython</p></span><span style="color: black"><p id="ch2intro_4"></a>Text editor - scite, vim, emacs or whatever you are comfortable with.</p></span></span></span></span></span><div class="section" title="1. Introduction">
+<div class="section" title="1. Introducing Linux">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2705187"></a>1. Introduction</h2></div></div></div>
-<p id="ch2intro_5"></a>The Python programming language was created by a dutch named Guido van Rossum.
-The idea of Python was conceived in December 1989. The name Python has nothing
-to do with the reptilian, but its been named after the 70s comedy series
-"Monty Python's Flying Circus", since it happens to be Guido's favourite
-TV series.</p>
-<p id="ch2intro_6"></a>Current stable version of Python is 2.6.x, although Python 3.0 is also the stable
-version, it is not backwards compatible with the previous versions and is hence
-not entirely popular at the moment. This material will focus on the 2.6.x series.</p>
-<p id="ch2intro_7"></a>Python is licensed under the Python Software Foundation License (PSF License)
-which is GPL compatible Free Software license (excepting license version 1.6 and 2.0)
-It is a no strings attached license, which means the source code is free to modify
-and redistribute.</p>
-<p id="ch2intro_8"></a>The Python docs define Python as "Python is an interpreted, object-oriented,
-high-level programming language with dynamic semantics." A more detailed summary
-can be found at </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org/doc/essays/blurb.html</div>
-<p>. Python is a language that
-has been designed to help the programmer concentrate on solving the problem at hand
-and not worry about the programming language idiosyncrasies.</p>
-<p id="ch2intro_9"></a>Python is a highly cross platform compatible language on account of it being an
-interpreted language. It is highly scalable and hence has been adapted to run on
-the Nokia 60 series phones. Python has been designed to be readable and easy to use</p>
-<p id="ch2intro_a"></a><span class="strong"><strong>Resources available for reference</strong></span></p>
-<span style="color: black"><span style="color: black"><p id="ch2intro_b"></a>Web: </p>
+<a name="id2741397"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch2intro_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch2intro_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch2intro_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch2intro_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2929092"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2928965"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982286"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch2intro_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch2intro_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2982331"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch2intro_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982356"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch2intro_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch2intro_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982408"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch2intro_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch2intro_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch2intro_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982463"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch2intro_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch2intro_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch2intro_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982506"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch2intro_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982552"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch2intro_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch2intro_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch2intro_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2982596"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch2intro_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch2intro_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch2intro_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch2intro_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch2intro_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch2intro_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2982723"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2982731"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch2intro_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982761"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch2intro_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch2intro_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch2intro_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch2intro_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch2intro_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch2intro_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch2intro_29"></a>Another common form for a prompt is this one:
+[</p>
 <div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org</div></span><span style="color: black"><p id="ch2intro_c"></a>Doc: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org/doc</div></span><span style="color: black"><span style="color: black"><span style="color: black"><span style="color: black">Free Tutorials:</span><span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_d"></a>Official Python Tutorial: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://docs.python.org/tut/tut.html</div></span><span style="color: black"><p id="ch2intro_e"></a>Byte of Python: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.byteofpython.info/</div></span><span style="color: black"><p id="ch2intro_f"></a>Dive into Python: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://diveintopython.org/</div></span></span></span></span></span></span></span><p id="ch2intro_10"></a><span class="strong"><strong>Advantages of Python - Why Python??</strong></span></p>
-<span style="color: black"><span style="color: black"><p id="ch2intro_11"></a>Python has been designed for readability and ease of use. Its been designed in
-such a fashion that it imposes readability on the programmer. Python does away
-with the braces and the semicolons and instead implements code blocks based on
-indentation, thus enhancing readability.</p></span><span style="color: black"><p id="ch2intro_12"></a>Python is a high level, interpreted, modular and object oriented language.
-Python performs memory management on its own, thus the programmer need not bother
-about allocating and deallocating memory to variables. Python provides extensibility
-by providing modules which can be easily imported similar to headers in C and
-packages in Java. Python is object oriented and hence provides all the object oriented
-characteristics such as inheritance, encapsulation and polymorphism.</p></span><span style="color: black"><p id="ch2intro_13"></a>Python offers a highly powerful interactive programming interface in the form
-of the 'Interactive Interpreter' which will be discussed in more detail in the
-following sections.</p></span><span style="color: black"><p id="ch2intro_14"></a>Python provides a rich standard library and an extensive set of modules. The
-power of Python modules can be seen in this slightly exaggerated cartoon
-</p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://xkcd.com/353/</div></span><span style="color: black"><p id="ch2intro_15"></a>Python interfaces well with most other programming languages such as C, C++
-and FORTRAN.</p></span></span><p id="ch2intro_16"></a>Although, Python has one setback. Python is not fast as some of the compiled
-languages like C or C++. Yet, the amount of flexibility and power more than make
-up for this setback.</p>
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch2intro_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch2intro_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2982916"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch2intro_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch2intro_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch2intro_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch2intro_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch2intro_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2983003"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983011"></a>3.1. ls</h3></div></div></div>
+<p id="ch2intro_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch2intro_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch2intro_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch2intro_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch2intro_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
 </div>
-<div class="section" title="2. The Python Interpreter">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757271"></a>2. The Python Interpreter</h2></div></div></div>
-<div class="section" title="2.1. The Interactive Interpreter">
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983169"></a>3.2. date</h3></div></div></div>
+<p id="ch2intro_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch2intro_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch2intro_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch2intro_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch2intro_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983227"></a>3.3. cd</h3></div></div></div>
+<p id="ch2intro_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch2intro_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch2intro_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch2intro_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch2intro_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch2intro_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch2intro_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch2intro_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch2intro_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch2intro_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch2intro_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch2intro_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983324"></a>3.4. who</h3></div></div></div>
+<p id="ch2intro_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch2intro_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch2intro_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch2intro_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch2intro_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2757279"></a>2.1. The Interactive Interpreter</h3></div></div></div>
-<p id="ch2intro_17"></a>Typing <span class="emphasis"><em>python</em></span> at the shell prompt on any standard Unix/Gnu-Linux system and
-hitting the enter key fires up the Python 'Interactive Interpreter'. The Python
-interpreter is one of the most integral features of Python. The prompt obtained
-when the interactive interpreter is similar to what is shown below. The exact
-appearance might differ based on the version of Python being used. The <code class="literal">&gt;&gt;&gt;</code>
-thing shown is the python prompt. When something is typed at the prompt and the
-enter key is hit, the python interpreter interprets the command entered and
-performs the appropriate action. All the examples presented in this document are
-to be tried hands on, on the interactive interpreter.</p>
-<pre class="programlisting"> Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49)
-[GCC 4.3.2] on linux2
-Type "help", "copyright", "credits" or "license" for more information.
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_18"></a>Lets try with an example, type <code class="literal">print 'Hello, World!'</code> at the prompt and hit
-the enter key.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 'Hello, World!'
-Hello, World!</pre>
-<p id="ch2intro_19"></a>This example was quite straight forward, and thus we have written our first
-line of Python code. Now let us try typing something arbitrary at the prompt.
-For example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; arbit word
-  File "&lt;stdin&gt;", line 1
-    arbit word
-            ^
-SyntaxError: invalid syntax
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1a"></a>The interpreter gave an error message saying that 'arbit word' was invalid
-syntax which is valid. The interpreter is an amazing tool when learning to
-program in Python. The interpreter provides a help function that provides the
-necessary documentation regarding all Python syntax, constructs, modules and
-objects. Typing <span class="emphasis"><em>help()</em></span> at the prompt gives the following output:</p>
-<pre class="programlisting"> &gt;&gt;&gt; help()
-
-Welcome to Python 2.5!  This is the online help utility.
-
-If this is your first time using Python, you should definitely check out
-the tutorial on the Internet at http://www.python.org/doc/tut/.
-
-Enter the name of any module, keyword, or topic to get help on writing
-Python programs and using Python modules.  To quit this help utility and
-return to the interpreter, just type "quit".
-
-To get a list of available modules, keywords, or topics, type "modules",
-"keywords", or "topics".  Each module also comes with a one-line summary
-of what it does; to list the modules whose summaries contain a given word
-such as "spam", type "modules spam".
+<a name="id2983404"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch2intro_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch2intro_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2983435"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch2intro_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch2intro_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2983494"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch2intro_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch2intro_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch2intro_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch2intro_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch2intro_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2983578"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983586"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch2intro_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch2intro_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch2intro_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch2intro_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch2intro_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983667"></a>4.2. man</h3></div></div></div>
+<p id="ch2intro_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch2intro_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch2intro_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch2intro_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch2intro_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch2intro_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2983747"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch2intro_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch2intro_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch2intro_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch2intro_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch2intro_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch2intro_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch2intro_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch2intro_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch2intro_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch2intro_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch2intro_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch2intro_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983870"></a>4.3. info</h3></div></div></div>
+<p id="ch2intro_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch2intro_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch2intro_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch2intro_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2983961"></a>4.4. --help</h3></div></div></div>
+<p id="ch2intro_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
 
-help&gt;</pre>
-<p id="ch2intro_1b"></a>As mentioned in the output, entering the name of any module, keyword or topic
-will provide the documentation and help regarding the same through the online
-help utility. Pressing <span class="emphasis"><em>Ctrl+d</em></span> exits the help prompt and returns to the
-python prompt.</p>
-<p id="ch2intro_1c"></a>Let us now try a few examples at the python interpreter.</p>
-<p id="ch2intro_1d"></a>Eg 1:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 'Hello, python!'
-Hello, python!
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1e"></a>Eg 2:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 4321*567890
-2453852690
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1f"></a>Eg 3:</p>
-<pre class="programlisting"> &gt;&gt;&gt; 4321*567890
-2453852690L
-&gt;&gt;&gt;</pre>
-<pre class="programlisting"> Note: Notice the 'L' at the end of the output. The 'L' signifies that the
-output of the operation is of type *long*. It was absent in the previous
-example because we used the print statement. This is because *print* formats
-the output before displaying.</pre>
-<p id="ch2intro_20"></a>Eg 4:</p>
-<pre class="programlisting"> &gt;&gt;&gt; big = 12345678901234567890 ** 3
-&gt;&gt;&gt; print big
-1881676372353657772490265749424677022198701224860897069000
-&gt;&gt;&gt;</pre>
-<pre class="programlisting"> This example is to show that unlike in C or C++ there is no limit on the
-value of an integer.</pre>
-<p id="ch2intro_21"></a>Try this on the interactive interpreter:
-<code class="literal">import this</code></p>
-<p id="ch2intro_22"></a><span class="emphasis"><em>Hint: The output gives an idea of Power of Python</em></span></p>
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
 </div>
-<div class="section" title="2.2. ipython - An enhanced interactive Python interpreter">
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2984014"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2757464"></a>2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</h3></div></div></div>
-<p id="ch2intro_23"></a>The power and the importance of the interactive interpreter was the highlight
-of the previous section. This section provides insight into the enhanced
-interpreter with more advanced set of features called <span class="strong"><strong>ipython</strong></span>. Entering
-<span class="emphasis"><em>ipython</em></span> at the shell prompt fires up the interactive interpreter.</p>
-<pre class="programlisting"> $ ipython
-Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49)
-Type "copyright", "credits" or "license" for more information.
-
-IPython 0.8.4 -- An enhanced Interactive Python.
-?         -&gt; Introduction and overview of IPython's features.
-%quickref -&gt; Quick reference.
-help      -&gt; Python's own help system.
-object?   -&gt; Details about 'object'. ?object also works, ?? prints more.
-
-In [1]:</pre>
-<p id="ch2intro_24"></a>This is the output obtained upon firing ipython. The exact appearance may
-change based on the Python version installed. The following are some of the
-various features provided by <span class="strong"><strong>ipython</strong></span>:</p>
-<span style="color: black"><p id="ch2intro_25"></a>Suggestions - ipython provides suggestions of the possible methods and
-operations available for the given python object.</p></span><p id="ch2intro_26"></a>Eg 5:</p>
-<pre class="programlisting"> In [4]: a = 6
-
-In [5]: a.
-a.__abs__           a.__divmod__        a.__index__         a.__neg__          a.__rand__          a.__rmod__          a.__rxor__
-a.__add__           a.__doc__           a.__init__          a.__new__          a.__rdiv__          a.__rmul__          a.__setattr__
-a.__and__           a.__float__         a.__int__           a.__nonzero__      a.__rdivmod__       a.__ror__           a.__str__
-a.__class__         a.__floordiv__      a.__invert__        a.__oct__          a.__reduce__        a.__rpow__          a.__sub__
-a.__cmp__           a.__getattribute__  a.__long__          a.__or__           a.__reduce_ex__     a.__rrshift__       a.__truediv__
-a.__coerce__        a.__getnewargs__    a.__lshift__        a.__pos__          a.__repr__          a.__rshift__        a.__xor__
-a.__delattr__       a.__hash__          a.__mod__           a.__pow__          a.__rfloordiv__     a.__rsub__
-a.__div__           a.__hex__           a.__mul__           a.__radd__         a.__rlshift__       a.__rtruediv__</pre>
-<p id="ch2intro_27"></a>In this example, we initialized 'a' (a variable - a concept that will be
-discussed in the subsequent sections.) to 6. In the next line when the <span class="emphasis"><em>tab</em></span> key
-is pressed after typing '<span class="emphasis"><em>a.</em></span>' ipython displays the set of all possible methods
-that are applicable on the object 'a' (an integer in this context). Ipython
-provides many such datatype specific features which will be presented in the
-further sections as and when the datatypes are introduced.</p>
+<a name="id2984023"></a>5.1. cp</h3></div></div></div>
+<p id="ch2intro_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984040"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch2intro_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch2intro_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch2intro_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984074"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch2intro_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch2intro_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch2intro_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch2intro_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch2intro_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984172"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch2intro_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch2intro_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch2intro_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch2intro_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch2intro_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch2intro_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch2intro_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch2intro_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch2intro_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch2intro_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch2intro_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch2intro_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch2intro_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch2intro_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch2intro_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2984334"></a>5.2. mv</h3></div></div></div>
+<p id="ch2intro_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984358"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch2intro_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984377"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch2intro_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984423"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch2intro_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch2intro_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2984483"></a>5.3. rm</h3></div></div></div>
+<p id="ch2intro_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch2intro_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984512"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch2intro_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch2intro_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch2intro_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch2intro_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch2intro_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984613"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch2intro_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch2intro_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch2intro_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
 </div>
 </div>
-<div class="section" title="3. Editing and running a python file">
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2984653"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch2intro_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch2intro_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch2intro_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch2intro_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch2intro_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch2intro_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch2intro_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757589"></a>3. Editing and running a python file</h2></div></div></div>
-<p id="ch2intro_28"></a>The previous sections focused on the use of the interpreter to run python code.
-While the interpeter is an excellent tool to test simple solutions and
-experiment with small code snippets, its main disadvantage is that everything
-written in the interpreter is lost once its quit. Most of the times a program is
-used by people other than the author. So the programs have to be available in
-some form suitable for distribution, and hence they are written in files. This
-section will focus on editing and running python files. Start by opening a text
-editor ( it is recommended you choose one from the list at the top of this page ).
-In the editor type down python code and save the file with an extension <span class="strong"><strong>.py</strong></span>
-(python files have an extension of .py). Once done with the editing, save the
-file and exit the editor.</p>
-<p id="ch2intro_29"></a>Let us look at a simple example of calculating the gcd of 2 numbers using Python:</p>
-<p id="ch2intro_2a"></a><span class="strong"><strong>Creating the first python script(file)</strong></span></p>
-<pre class="programlisting"> $ emacs gcd.py
-  def gcd(x,y):
-    if x % y == 0:
-      return y
-    return gcd(y, x%y)
-
-  print gcd(72, 92)</pre>
-<p id="ch2intro_2b"></a>To run the script, open the shell prompt, navigate to the directory that
-contains the python file and run <code class="literal">python &lt;filename.py&gt;</code> at the prompt ( in this
-case filename is gcd.py )</p>
-<p id="ch2intro_2c"></a><span class="strong"><strong>Running the python script</strong></span></p>
-<pre class="programlisting"> $ python gcd.py
-4
-$</pre>
-<p id="ch2intro_2d"></a>Another method to run a python script would be to include the line</p>
-<p id="ch2intro_2e"></a><code class="literal">#! /usr/bin/python</code></p>
-<p id="ch2intro_2f"></a>at the beginning of the python file and then make the file executable by</p>
-<p id="ch2intro_30"></a>$ chmod a+x <span class="emphasis"><em>filename.py</em></span></p>
-<p id="ch2intro_31"></a>Once this is done, the script can be run as a standalone program as follows:</p>
-<p id="ch2intro_32"></a>$ ./<span class="emphasis"><em>filename.py</em></span></p>
+<a name="id2984746"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2984755"></a>7.1. head</h3></div></div></div>
+<p id="ch2intro_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch2intro_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch2intro_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch2intro_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984806"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch2intro_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch2intro_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch2intro_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2984842"></a>7.2. tail</h3></div></div></div>
+<p id="ch2intro_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch2intro_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch2intro_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch2intro_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch2intro_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch2intro_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch2intro_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2984920"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch2intro_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch2intro_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch2intro_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
 </div>
-<div class="section" title="4. Basic Datatypes and operators in Python">
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2984970"></a>7.3. cut</h3></div></div></div>
+<p id="ch2intro_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch2intro_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch2intro_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch2intro_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch2intro_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch2intro_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch2intro_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2985055"></a>7.4. paste</h3></div></div></div>
+<p id="ch2intro_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch2intro_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch2intro_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch2intro_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757696"></a>4. Basic Datatypes and operators in Python</h2></div></div></div>
-<p id="ch2intro_33"></a>Python provides the following set of basic datatypes.</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_34"></a>Numbers: int, float, long, complex</p></span><span style="color: black"><p id="ch2intro_35"></a>Strings</p></span><span style="color: black"><p id="ch2intro_36"></a>Boolean</p></span></span></span><div class="section" title="4.1. Numbers">
+<a name="id2985190"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch2intro_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch2intro_df"></a>The shell meta characters include:</p>
+<p id="ch2intro_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch2intro_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch2intro_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch2intro_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch2intro_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch2intro_e5"></a>because the c* matches that long file name.</p>
+<p id="ch2intro_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch2intro_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch2intro_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2985297"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2757731"></a>4.1. Numbers</h3></div></div></div>
-<p id="ch2intro_37"></a>Numbers were introduced in the examples presented in the interactive interpreter
-section. Numbers include types as mentioned earlier viz., int (integers), float
-(floating point numbers), long (large integers), complex (complex numbers with
-real and imaginary parts). Python is not a strongly typed language, which means
-the type of a variable need not mentioned during its initialization. Let us look
-at a few examples.</p>
-<p id="ch2intro_38"></a>Eg 6:</p>
-<pre class="programlisting"> &gt;&gt;&gt; a = 1 #here a is an integer variable</pre>
-<p id="ch2intro_39"></a>Eg 7:</p>
-<pre class="programlisting"> &gt;&gt;&gt; lng = 122333444455555666666777777788888888999999999 #here lng is a variable of type long
-&gt;&gt;&gt; lng
-122333444455555666666777777788888888999999999L #notice the trailing 'L'
-&gt;&gt;&gt; print lng
-122333444455555666666777777788888888999999999 #notice the absence of the trailing 'L'
-&gt;&gt;&gt; lng+1
-122333444455555666666777777788888889000000000L</pre>
-<p id="ch2intro_3a"></a>Long numbers are the same as integers in almost all aspects. They can be used in
-operations just like integers and along with integers without any distinction.
-The only distinction comes during type checking (which is not a healthy practice).
-Long numbers are tucked with a trailing 'L' just to signify that they are long.
-Notice that in the example just lng at the prompt displays the value of the variable
-with the 'L' whereas <code class="literal">print lng</code> displays without the 'L'. This is because print
-formats the output before printing. Also in the example, notice that adding an
-integer to a long does not give any errors and the result is as expected. So for
-all practical purposes longs can be treated as ints.</p>
-<p id="ch2intro_3b"></a>Eg 8:</p>
-<pre class="programlisting"> &gt;&gt;&gt; fl = 3.14159 #fl is a float variable
-&gt;&gt;&gt; e = 1.234e-4 #e is also a float variable, specified in the exponential form
-&gt;&gt;&gt; a = 1
-&gt;&gt;&gt; b = 2
-&gt;&gt;&gt; a/b #integer division
-0
-&gt;&gt;&gt; a/fl #floating point division
-0.31831015504887655
-&gt;&gt;&gt; e/fl
-3.9279473133031364e-05</pre>
-<p id="ch2intro_3c"></a>Floating point numbers, simply called floats are real numbers with a decimal point.
-The example above shows the initialization of a float variable. Shown also in this
-example is the difference between integer division and floating point division.
-'a' and 'b' here are integer variables and hence the division gives 0 as the quotient.
-When either of the operands is a float, the operation is a floating point division,
-and the result is also a float as illustrated.</p>
-<p id="ch2intro_3d"></a>Eg 9:</p>
-<pre class="programlisting"> &gt;&gt;&gt; cplx = 3 + 4j #cplx is a complex variable
-&gt;&gt;&gt; cplx
-(3+4j)
-&gt;&gt;&gt; print cplx.real #prints the real part of the complex number
-3.0
-&gt;&gt;&gt; print cplx.imag #prints the imaginary part of the complex number
-4.0
-&gt;&gt;&gt; print cplx*fl  #multiplies the real and imag parts of the complex number with the multiplier
-(9.42477+12.56636j)
-&gt;&gt;&gt; abs(cplx) #returns the absolute value of the complex number
-5.0</pre>
-<p id="ch2intro_3e"></a>Python provides a datatype for complex numbers. Complex numbers are initialized
-as shown in the example above. The <span class="emphasis"><em>real</em></span> and <span class="emphasis"><em>imag</em></span> operators return the real and
-imaginary parts of the complex number as shown. The <span class="emphasis"><em>abs()</em></span> returns the absolute
-value of the complex number.</p>
+<a name="id2985305"></a>9.1. cat</h3></div></div></div>
+<p id="ch2intro_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch2intro_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch2intro_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985349"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch2intro_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
 </div>
-<div class="section" title="4.2. Variables">
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985388"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch2intro_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch2intro_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch2intro_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch2intro_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch2intro_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch2intro_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985457"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch2intro_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2757854"></a>4.2. Variables</h3></div></div></div>
-<p id="ch2intro_3f"></a>Variables are just names that represent a value. Variables have already been
-introduced in the various examples from the previous sections. Certain rules about
-using variables:</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_40"></a>Variables have to be initialized or assigned a value before being used.</p></span><span style="color: black"><p id="ch2intro_41"></a>Variable names can consist of letters, digits and underscores(_).</p></span><span style="color: black"><p id="ch2intro_42"></a>Variable names cannot begin with digits, but can contain digits in them.</p></span></span></span><p id="ch2intro_43"></a>In reference to the previous section examples, 'a', 'b', 'lng', 'fl', 'e' and 'cplx'
-are all variables of various datatypes.</p>
-<pre class="programlisting"> Note: Python is not a strongly typed language and hence an integer variable can at a
-later stage be used as a float variable as well.</pre>
+<a name="id2985493"></a>9.2. more</h3></div></div></div>
+<p id="ch2intro_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985513"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch2intro_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch2intro_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch2intro_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch2intro_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch2intro_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
 </div>
-<div class="section" title="4.3. Strings">
+<div class="section" title="9.3. less">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2757903"></a>4.3. Strings</h3></div></div></div>
-<p id="ch2intro_44"></a>Strings are one of the essential data structures of any programming language.
-The <code class="literal">print "Hello, World!"</code> program was introduced in the earlier section, and
-the <span class="emphasis"><em>"Hello, World!"</em></span> in the print statement is a string. A string is basically
-a set of characters. Strings can be represented in various ways shown below:</p>
-<pre class="programlisting"> s = 'this is a string'              # a string variable can be represented using single quotes
-s = 'This one has "quotes" inside!' # The string can have quotes inside it as shown
-s = "I have 'single-quotes' inside!"
-l = "A string spanning many lines\
-one more line\
-yet another"                        # a string can span more than a single line.
-t = """A triple quoted string does  # another way of representing multiline strings.
-not need to be escaped at the end and
-"can have nested quotes" etc."""</pre>
-<p id="ch2intro_45"></a>Try the following on the interpreter:
-<code class="literal">s = 'this is a string with 'quotes' of similar kind'</code></p>
-<p id="ch2intro_46"></a><span class="strong"><strong>Exercise: How to use single quotes within single quotes in a string as shown
-in the above example without getting an error?</strong></span></p>
-<div class="section" title="4.3.1. String operations">
+<a name="id2985608"></a>9.3. less</h3></div></div></div>
+<p id="ch2intro_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985637"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch2intro_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch2intro_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch2intro_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985691"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id2757955"></a>4.3.1. String operations</h4></div></div></div>
-<p id="ch2intro_47"></a>A few basic string operations are presented here.</p>
-<p id="ch2intro_48"></a><span class="strong"><strong>String concatenation</strong></span>
-String concatenation is done by simple addition of two strings.</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = 'Hello'
-&gt;&gt;&gt; y = ' Python'
-&gt;&gt;&gt; print x+y
-Hello Python</pre>
-<p id="ch2intro_49"></a><span class="emphasis"><em>Try this yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; somenum = 13
-&gt;&gt;&gt; print x+somenum</pre>
-<p id="ch2intro_4a"></a>The problem with the above example is that here a string variable and an integer
-variable are trying to be concantenated. To obtain the desired result from the
-above example the str(), repr() and the `` can be used.</p>
-<p id="ch2intro_4b"></a><span class="strong"><strong>str()</strong></span> simply converts a value to a string in a reasonable form.
-<span class="strong"><strong>repr()</strong></span> creates a string that is a representation of the value.</p>
-<p id="ch2intro_4c"></a>The difference can be seen in the example shown below:</p>
-<pre class="programlisting"> &gt;&gt;&gt; str(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000'
-&gt;&gt;&gt; repr(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000L'</pre>
-<p id="ch2intro_4d"></a>It can be observed that the 'L' in the long value shown was omitted by str(),
-whereas repr() converted that into a string too. An alternative way of using
-repr(value) is <code class="literal">`value`</code>.</p>
-<p id="ch2intro_4e"></a>A few more examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = "Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go
-to Pycon</pre>
-<p id="ch2intro_4f"></a>In the above example, notice that the 'n'(newline) character is formatted and
-the string is printed on two lines. The strings discussed until now were normal
-strings. Other than these there are two other types of strings namely, raw strings
-and unicode strings.</p>
-<p id="ch2intro_50"></a><span class="strong"><strong>Raw strings</strong></span> are strings which are unformatted, that is the backslashes() are
-not parsed and are left as it is in the string. Raw strings are represented with
-an 'r' at the start of a string.
-Let us look at an example</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = r"Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go \nto Pycon</pre>
-<p id="ch2intro_51"></a>Note: The 'n' is not being parsed into a new line and is left as it is.</p>
-<p id="ch2intro_52"></a><span class="emphasis"><em>Try this yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; x = r"Let's go to Pycon\"</pre>
-<p id="ch2intro_53"></a><span class="strong"><strong>Unicode strings</strong></span> are strings where the characters are Unicode characters as
-opposed to ASCII characters. Unicode strings are represented with a 'u' at the
-start of the string.
-Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = u"Let's go to Pycon!"
-&gt;&gt;&gt; print x
-Let's go to Pycon!</pre>
+<a name="id2985743"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2985832"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2985848"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch2intro_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch2intro_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2986117"></a>10.1. man hier</h3></div></div></div>
+<p id="ch2intro_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2986133"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch2intro_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch2intro_138"></a>This can be done after entering the required directory.</p>
 </div>
 </div>
-<div class="section" title="4.4. Boolean">
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2986156"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id2758097"></a>4.4. Boolean</h3></div></div></div>
-<p id="ch2intro_54"></a>Python also provides special Boolean datatype. A boolean variable can assume a
-value of either <span class="emphasis"><em>True</em></span> or <span class="emphasis"><em>False</em></span> (Note the capitalizations).</p>
-<p id="ch2intro_55"></a>Let us look at examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; t = True
-&gt;&gt;&gt; f = not t
-&gt;&gt;&gt; print f
-False
-&gt;&gt;&gt; f or t
-True
-&gt;&gt;&gt; f and t
-False</pre>
+<a name="id2986165"></a>11.1. chmod</h3></div></div></div>
+<p id="ch2intro_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2986191"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch2intro_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch2intro_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2986219"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch2intro_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch2intro_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2986255"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch2intro_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch2intro_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch2intro_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch2intro_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch2intro_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2986802"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch2intro_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch2intro_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch2intro_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2986842"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch2intro_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch2intro_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2986882"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch2intro_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch2intro_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
 </div>
 </div>
-<div class="section" title="5. The while loop">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758126"></a>5. The <span class="strong"><strong>while</strong></span> loop</h2></div></div></div>
-<p id="ch2intro_56"></a>The Python <span class="strong"><strong>while</strong></span> loop is similar to the C/C++ while loop. The syntax is as
-follows:</p>
-<pre class="programlisting"> statement 0
-while condition:
-  statement 1 #while block
-  statement 2 #while block
-statement 3 #outside the while block.</pre>
-<p id="ch2intro_57"></a>Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = 1
-&gt;&gt;&gt; while x &lt;= 5:
-...   print x
-...   x += 1
-...
-1
-2
-3
-4
-5</pre>
-</div>
-<div class="section" title="6. The if conditional">
+<div class="section" title="12. Redirection and Piping">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758163"></a>6. The <span class="strong"><strong>if</strong></span> conditional</h2></div></div></div>
-<p id="ch2intro_58"></a>The Python <span class="strong"><strong>if</strong></span> block provides the conditional execution of statements.
-If the condition evaluates as true the block of statements defined under the if
-block are executed.</p>
-<p id="ch2intro_59"></a>If the first block is not executed on account of the condition not being satisfied,
-the set of statements in the <span class="strong"><strong>else</strong></span> block are executed.</p>
-<p id="ch2intro_5a"></a>The <span class="strong"><strong>elif</strong></span> block provides the functionality of evaluation of multiple conditions
-as shown in the example.</p>
-<p id="ch2intro_5b"></a>The syntax is as follows:</p>
-<pre class="programlisting"> if condition :
-    statement_1
-    statement_2
-
-elif condition:
-    statement_3
-    statement_4
-else:
-    statement_5
-    statement_6</pre>
-<p id="ch2intro_5c"></a>Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; n = raw_input("Input a number:")
-&gt;&gt;&gt; if n &lt; 0:
-      print n," is negative"
-      elif n &gt; 0:
-      print n," is positive"
-      else:
-      print n, " is 0"</pre>
+<a name="id2986929"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch2intro_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch2intro_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2986966"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch2intro_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch2intro_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch2intro_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch2intro_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987035"></a>12.2. Piping</h3></div></div></div>
+<p id="ch2intro_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch2intro_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch2intro_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch2intro_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch2intro_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
 </div>
-<div class="section" title="7. raw_input()">
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987096"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch2intro_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch2intro_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch2intro_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch2intro_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch2intro_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch2intro_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch2intro_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch2intro_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch2intro_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch2intro_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch2intro_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987301"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch2intro_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch2intro_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987335"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch2intro_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch2intro_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758232"></a>7. <span class="strong"><strong>raw_input()</strong></span>
-</h2></div></div></div>
-<p id="ch2intro_5d"></a>In the previous example we saw the call to the raw_input() subroutine.
-The <span class="strong"><strong>raw_input()</strong></span> method is used to take user inputs through the console.
-Unlike <span class="strong"><strong>input()</strong></span> which assumes the data entered by the user as a standard python
-expression, <span class="strong"><strong>raw_input()</strong></span> treats all the input data as raw data and converts
-everything into a string. To illustrate this let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-121
+<a name="id2987365"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987374"></a>13.1. grep</h3></div></div></div>
+<p id="ch2intro_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2987405"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch2intro_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch2intro_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch2intro_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch2intro_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch2intro_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch2intro_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2987484"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch2intro_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch2intro_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch2intro_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2987563"></a>13.2. tr</h3></div></div></div>
+<p id="ch2intro_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch2intro_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch2intro_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch2intro_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch2intro_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch2intro_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch2intro_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch2intro_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch2intro_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch2intro_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch2intro_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch2intro_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2987713"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch2intro_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch2intro_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch2intro_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch2intro_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2988062"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch2intro_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch2intro_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch2intro_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2988138"></a>15. One Liners</h2></div></div></div>
+<p id="ch2intro_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch2intro_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch2intro_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch2intro_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch2intro_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch2intro_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch2intro_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch2intro_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch2intro_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch2intro_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch2intro_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch2intro_1d7"></a>Print the total number of input lines:</p>
+<p id="ch2intro_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch2intro_1d9"></a>Print the tenth input line:</p>
+<p id="ch2intro_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch2intro_1db"></a>Print the last field of every input line:</p>
+<p id="ch2intro_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch2intro_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch2intro_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch2intro_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch2intro_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
 
-&gt;&gt;&gt; input("Enter your name:")
-Enter your name:PythonFreak
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-  File "&lt;string&gt;", line 1, in &lt;module&gt;
-NameError: name 'PythonFreak' is not defined</pre>
-<p id="ch2intro_5e"></a>As shown above the <span class="strong"><strong>input()</strong></span> assumes that the data entered is a valid Python
-expression. In the first call it prompts for an integer input and when entered
-it accepts the integer as an integer, whereas in the second call, when the string
-is entered without the quotes, <span class="strong"><strong>input()</strong></span> assumes that the entered data is a valid
-Python expression and hence it raises and exception saying PythonFreak is not
-defined.</p>
-<pre class="programlisting"> &gt;&gt;&gt; input("Enter your name:")
-Enter your name:'PythonFreak'
-'PythonFreak'
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_5f"></a>Here the name is accepted because its entered as a string (within quotes). But
-its unreasonable to go on using quotes each time a string is entered. Hence the
-alternative is to use <span class="strong"><strong>raw_input()</strong></span>.</p>
-<p id="ch2intro_60"></a>Let us now look at how <span class="strong"><strong>raw_input()</strong></span> operates with an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; raw_input("Enter your name:")
-Enter your name:PythonFreak
-'PythonFreak'</pre>
-<p id="ch2intro_61"></a>Observe that the <span class="strong"><strong>raw_input()</strong></span> is converting it into a string all by itself.</p>
-<pre class="programlisting"> &gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-'121'</pre>
-<p id="ch2intro_62"></a>Observe that <span class="strong"><strong>raw_input()</strong></span> is converting the integer 121 also to a string as
-'121'. Let us look at another example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-&gt;&gt;&gt; pal + 2
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: cannot concatenate 'str' and 'int' objects
-&gt;&gt;&gt; pal
-'121'</pre>
-<p id="ch2intro_63"></a>Observe here that the variable <span class="emphasis"><em>pal</em></span> is a string and hence integer operations
-cannot be performed on it. Hence the exception is raised.</p>
-</div>
-<div class="section" title="8. int() method">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758387"></a>8. <span class="strong"><strong>int()</strong></span> method</h2></div></div></div>
-<p id="ch2intro_64"></a>Generally for computing purposes, the data used is not strings or raw data but
-on integers, floats and similar mathematical data structures. The data obtained
-from <span class="strong"><strong>raw_input()</strong></span> is raw data in the form of strings. In order to obtain integers
-from strings we use the method <span class="strong"><strong>int()</strong></span>.</p>
-<p id="ch2intro_65"></a>Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; intpal = int(pal)
-&gt;&gt;&gt; intpal
-121</pre>
-<p id="ch2intro_66"></a>In the previous example it was observed that <span class="emphasis"><em>pal</em></span> was a string variable. Here
-using the <span class="strong"><strong>int()</strong></span> method the string <span class="emphasis"><em>pal</em></span> was converted to an integer variable.</p>
-<p id="ch2intro_67"></a><span class="emphasis"><em>Try This Yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; stringvar = raw_input("Enter a name:")
-Enter a name:Guido Van Rossum
-&gt;&gt;&gt; stringvar
-'Guido Van Rossum'
-&gt;&gt;&gt; numvar = int(stringvar)</pre>
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch2intro_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
 </div>
 </div>
 </div></body>
--- a/web/html/ch2intro.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,591 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 2. Basic Python</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
-<div class="chapter" id="ch2intro">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2706129">Basic Python</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2705187">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#id2757271">2. The Python Interpreter</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2757279">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#id2757464">2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id2757589">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#id2757696">4. Basic Datatypes and operators in Python</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2757731">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#id2757854">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#id2757903">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#id2758097">4.4. Boolean</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id2758126">5. The <span class="strong"><strong>while</strong></span> loop</a></span></dt>
-<dt><span class="section"><a href="#id2758163">6. The <span class="strong"><strong>if</strong></span> conditional</a></span></dt>
-<dt><span class="section"><a href="#id2758232">7. <span class="strong"><strong>raw_input()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id2758387">8. <span class="strong"><strong>int()</strong></span> method</a></span></dt>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="Basic Python">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2706129"></a>Basic Python</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#id2705187">1. Introduction</a></span></dt>
-<dt><span class="section"><a href="#id2757271">2. The Python Interpreter</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2757279">2.1. The Interactive Interpreter</a></span></dt>
-<dt><span class="section"><a href="#id2757464">2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id2757589">3. Editing and running a python file</a></span></dt>
-<dt><span class="section"><a href="#id2757696">4. Basic Datatypes and operators in Python</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2757731">4.1. Numbers</a></span></dt>
-<dt><span class="section"><a href="#id2757854">4.2. Variables</a></span></dt>
-<dt><span class="section"><a href="#id2757903">4.3. Strings</a></span></dt>
-<dt><span class="section"><a href="#id2758097">4.4. Boolean</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id2758126">5. The <span class="strong"><strong>while</strong></span> loop</a></span></dt>
-<dt><span class="section"><a href="#id2758163">6. The <span class="strong"><strong>if</strong></span> conditional</a></span></dt>
-<dt><span class="section"><a href="#id2758232">7. <span class="strong"><strong>raw_input()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id2758387">8. <span class="strong"><strong>int()</strong></span> method</a></span></dt>
-</dl>
-</div>
-<p id="ch2intro_1"></a>This document is intended to be handed out at the end of the workshop. It has
-been designed for Engineering students who are Python beginners and have basic
-programming skills. The focus is on basic numerics and plotting using Python.</p>
-<span style="color: black"><span style="color: black"><span style="color: black">The system requirements:</span><span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_2"></a>Python - version 2.5.x or newer.</p></span><span style="color: black"><p id="ch2intro_3"></a>IPython</p></span><span style="color: black"><p id="ch2intro_4"></a>Text editor - scite, vim, emacs or whatever you are comfortable with.</p></span></span></span></span></span><div class="section" title="1. Introduction">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2705187"></a>1. Introduction</h2></div></div></div>
-<p id="ch2intro_5"></a>The Python programming language was created by a dutch named Guido van Rossum.
-The idea of Python was conceived in December 1989. The name Python has nothing
-to do with the reptilian, but its been named after the 70s comedy series
-"Monty Python's Flying Circus", since it happens to be Guido's favourite
-TV series.</p>
-<p id="ch2intro_6"></a>Current stable version of Python is 2.6.x, although Python 3.0 is also the stable
-version, it is not backwards compatible with the previous versions and is hence
-not entirely popular at the moment. This material will focus on the 2.6.x series.</p>
-<p id="ch2intro_7"></a>Python is licensed under the Python Software Foundation License (PSF License)
-which is GPL compatible Free Software license (excepting license version 1.6 and 2.0)
-It is a no strings attached license, which means the source code is free to modify
-and redistribute.</p>
-<p id="ch2intro_8"></a>The Python docs define Python as "Python is an interpreted, object-oriented,
-high-level programming language with dynamic semantics." A more detailed summary
-can be found at </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org/doc/essays/blurb.html</div>
-<p>. Python is a language that
-has been designed to help the programmer concentrate on solving the problem at hand
-and not worry about the programming language idiosyncrasies.</p>
-<p id="ch2intro_9"></a>Python is a highly cross platform compatible language on account of it being an
-interpreted language. It is highly scalable and hence has been adapted to run on
-the Nokia 60 series phones. Python has been designed to be readable and easy to use</p>
-<p id="ch2intro_a"></a><span class="strong"><strong>Resources available for reference</strong></span></p>
-<span style="color: black"><span style="color: black"><p id="ch2intro_b"></a>Web: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org</div></span><span style="color: black"><p id="ch2intro_c"></a>Doc: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.python.org/doc</div></span><span style="color: black"><span style="color: black"><span style="color: black"><span style="color: black">Free Tutorials:</span><span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_d"></a>Official Python Tutorial: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://docs.python.org/tut/tut.html</div></span><span style="color: black"><p id="ch2intro_e"></a>Byte of Python: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://www.byteofpython.info/</div></span><span style="color: black"><p id="ch2intro_f"></a>Dive into Python: </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://diveintopython.org/</div></span></span></span></span></span></span></span><p id="ch2intro_10"></a><span class="strong"><strong>Advantages of Python - Why Python??</strong></span></p>
-<span style="color: black"><span style="color: black"><p id="ch2intro_11"></a>Python has been designed for readability and ease of use. Its been designed in
-such a fashion that it imposes readability on the programmer. Python does away
-with the braces and the semicolons and instead implements code blocks based on
-indentation, thus enhancing readability.</p></span><span style="color: black"><p id="ch2intro_12"></a>Python is a high level, interpreted, modular and object oriented language.
-Python performs memory management on its own, thus the programmer need not bother
-about allocating and deallocating memory to variables. Python provides extensibility
-by providing modules which can be easily imported similar to headers in C and
-packages in Java. Python is object oriented and hence provides all the object oriented
-characteristics such as inheritance, encapsulation and polymorphism.</p></span><span style="color: black"><p id="ch2intro_13"></a>Python offers a highly powerful interactive programming interface in the form
-of the 'Interactive Interpreter' which will be discussed in more detail in the
-following sections.</p></span><span style="color: black"><p id="ch2intro_14"></a>Python provides a rich standard library and an extensive set of modules. The
-power of Python modules can be seen in this slightly exaggerated cartoon
-</p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://xkcd.com/353/</div></span><span style="color: black"><p id="ch2intro_15"></a>Python interfaces well with most other programming languages such as C, C++
-and FORTRAN.</p></span></span><p id="ch2intro_16"></a>Although, Python has one setback. Python is not fast as some of the compiled
-languages like C or C++. Yet, the amount of flexibility and power more than make
-up for this setback.</p>
-</div>
-<div class="section" title="2. The Python Interpreter">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757271"></a>2. The Python Interpreter</h2></div></div></div>
-<div class="section" title="2.1. The Interactive Interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2757279"></a>2.1. The Interactive Interpreter</h3></div></div></div>
-<p id="ch2intro_17"></a>Typing <span class="emphasis"><em>python</em></span> at the shell prompt on any standard Unix/Gnu-Linux system and
-hitting the enter key fires up the Python 'Interactive Interpreter'. The Python
-interpreter is one of the most integral features of Python. The prompt obtained
-when the interactive interpreter is similar to what is shown below. The exact
-appearance might differ based on the version of Python being used. The <code class="literal">&gt;&gt;&gt;</code>
-thing shown is the python prompt. When something is typed at the prompt and the
-enter key is hit, the python interpreter interprets the command entered and
-performs the appropriate action. All the examples presented in this document are
-to be tried hands on, on the interactive interpreter.</p>
-<pre class="programlisting"> Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49)
-[GCC 4.3.2] on linux2
-Type "help", "copyright", "credits" or "license" for more information.
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_18"></a>Lets try with an example, type <code class="literal">print 'Hello, World!'</code> at the prompt and hit
-the enter key.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 'Hello, World!'
-Hello, World!</pre>
-<p id="ch2intro_19"></a>This example was quite straight forward, and thus we have written our first
-line of Python code. Now let us try typing something arbitrary at the prompt.
-For example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; arbit word
-  File "&lt;stdin&gt;", line 1
-    arbit word
-            ^
-SyntaxError: invalid syntax
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1a"></a>The interpreter gave an error message saying that 'arbit word' was invalid
-syntax which is valid. The interpreter is an amazing tool when learning to
-program in Python. The interpreter provides a help function that provides the
-necessary documentation regarding all Python syntax, constructs, modules and
-objects. Typing <span class="emphasis"><em>help()</em></span> at the prompt gives the following output:</p>
-<pre class="programlisting"> &gt;&gt;&gt; help()
-
-Welcome to Python 2.5!  This is the online help utility.
-
-If this is your first time using Python, you should definitely check out
-the tutorial on the Internet at http://www.python.org/doc/tut/.
-
-Enter the name of any module, keyword, or topic to get help on writing
-Python programs and using Python modules.  To quit this help utility and
-return to the interpreter, just type "quit".
-
-To get a list of available modules, keywords, or topics, type "modules",
-"keywords", or "topics".  Each module also comes with a one-line summary
-of what it does; to list the modules whose summaries contain a given word
-such as "spam", type "modules spam".
-
-help&gt;</pre>
-<p id="ch2intro_1b"></a>As mentioned in the output, entering the name of any module, keyword or topic
-will provide the documentation and help regarding the same through the online
-help utility. Pressing <span class="emphasis"><em>Ctrl+d</em></span> exits the help prompt and returns to the
-python prompt.</p>
-<p id="ch2intro_1c"></a>Let us now try a few examples at the python interpreter.</p>
-<p id="ch2intro_1d"></a>Eg 1:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 'Hello, python!'
-Hello, python!
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1e"></a>Eg 2:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print 4321*567890
-2453852690
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_1f"></a>Eg 3:</p>
-<pre class="programlisting"> &gt;&gt;&gt; 4321*567890
-2453852690L
-&gt;&gt;&gt;</pre>
-<pre class="programlisting"> Note: Notice the 'L' at the end of the output. The 'L' signifies that the
-output of the operation is of type *long*. It was absent in the previous
-example because we used the print statement. This is because *print* formats
-the output before displaying.</pre>
-<p id="ch2intro_20"></a>Eg 4:</p>
-<pre class="programlisting"> &gt;&gt;&gt; big = 12345678901234567890 ** 3
-&gt;&gt;&gt; print big
-1881676372353657772490265749424677022198701224860897069000
-&gt;&gt;&gt;</pre>
-<pre class="programlisting"> This example is to show that unlike in C or C++ there is no limit on the
-value of an integer.</pre>
-<p id="ch2intro_21"></a>Try this on the interactive interpreter:
-<code class="literal">import this</code></p>
-<p id="ch2intro_22"></a><span class="emphasis"><em>Hint: The output gives an idea of Power of Python</em></span></p>
-</div>
-<div class="section" title="2.2. ipython - An enhanced interactive Python interpreter">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2757464"></a>2.2. <span class="emphasis"><em>ipython</em></span> - An enhanced interactive Python interpreter</h3></div></div></div>
-<p id="ch2intro_23"></a>The power and the importance of the interactive interpreter was the highlight
-of the previous section. This section provides insight into the enhanced
-interpreter with more advanced set of features called <span class="strong"><strong>ipython</strong></span>. Entering
-<span class="emphasis"><em>ipython</em></span> at the shell prompt fires up the interactive interpreter.</p>
-<pre class="programlisting"> $ ipython
-Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49)
-Type "copyright", "credits" or "license" for more information.
-
-IPython 0.8.4 -- An enhanced Interactive Python.
-?         -&gt; Introduction and overview of IPython's features.
-%quickref -&gt; Quick reference.
-help      -&gt; Python's own help system.
-object?   -&gt; Details about 'object'. ?object also works, ?? prints more.
-
-In [1]:</pre>
-<p id="ch2intro_24"></a>This is the output obtained upon firing ipython. The exact appearance may
-change based on the Python version installed. The following are some of the
-various features provided by <span class="strong"><strong>ipython</strong></span>:</p>
-<span style="color: black"><p id="ch2intro_25"></a>Suggestions - ipython provides suggestions of the possible methods and
-operations available for the given python object.</p></span><p id="ch2intro_26"></a>Eg 5:</p>
-<pre class="programlisting"> In [4]: a = 6
-
-In [5]: a.
-a.__abs__           a.__divmod__        a.__index__         a.__neg__          a.__rand__          a.__rmod__          a.__rxor__
-a.__add__           a.__doc__           a.__init__          a.__new__          a.__rdiv__          a.__rmul__          a.__setattr__
-a.__and__           a.__float__         a.__int__           a.__nonzero__      a.__rdivmod__       a.__ror__           a.__str__
-a.__class__         a.__floordiv__      a.__invert__        a.__oct__          a.__reduce__        a.__rpow__          a.__sub__
-a.__cmp__           a.__getattribute__  a.__long__          a.__or__           a.__reduce_ex__     a.__rrshift__       a.__truediv__
-a.__coerce__        a.__getnewargs__    a.__lshift__        a.__pos__          a.__repr__          a.__rshift__        a.__xor__
-a.__delattr__       a.__hash__          a.__mod__           a.__pow__          a.__rfloordiv__     a.__rsub__
-a.__div__           a.__hex__           a.__mul__           a.__radd__         a.__rlshift__       a.__rtruediv__</pre>
-<p id="ch2intro_27"></a>In this example, we initialized 'a' (a variable - a concept that will be
-discussed in the subsequent sections.) to 6. In the next line when the <span class="emphasis"><em>tab</em></span> key
-is pressed after typing '<span class="emphasis"><em>a.</em></span>' ipython displays the set of all possible methods
-that are applicable on the object 'a' (an integer in this context). Ipython
-provides many such datatype specific features which will be presented in the
-further sections as and when the datatypes are introduced.</p>
-</div>
-</div>
-<div class="section" title="3. Editing and running a python file">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757589"></a>3. Editing and running a python file</h2></div></div></div>
-<p id="ch2intro_28"></a>The previous sections focused on the use of the interpreter to run python code.
-While the interpeter is an excellent tool to test simple solutions and
-experiment with small code snippets, its main disadvantage is that everything
-written in the interpreter is lost once its quit. Most of the times a program is
-used by people other than the author. So the programs have to be available in
-some form suitable for distribution, and hence they are written in files. This
-section will focus on editing and running python files. Start by opening a text
-editor ( it is recommended you choose one from the list at the top of this page ).
-In the editor type down python code and save the file with an extension <span class="strong"><strong>.py</strong></span>
-(python files have an extension of .py). Once done with the editing, save the
-file and exit the editor.</p>
-<p id="ch2intro_29"></a>Let us look at a simple example of calculating the gcd of 2 numbers using Python:</p>
-<p id="ch2intro_2a"></a><span class="strong"><strong>Creating the first python script(file)</strong></span></p>
-<pre class="programlisting"> $ emacs gcd.py
-  def gcd(x,y):
-    if x % y == 0:
-      return y
-    return gcd(y, x%y)
-
-  print gcd(72, 92)</pre>
-<p id="ch2intro_2b"></a>To run the script, open the shell prompt, navigate to the directory that
-contains the python file and run <code class="literal">python &lt;filename.py&gt;</code> at the prompt ( in this
-case filename is gcd.py )</p>
-<p id="ch2intro_2c"></a><span class="strong"><strong>Running the python script</strong></span></p>
-<pre class="programlisting"> $ python gcd.py
-4
-$</pre>
-<p id="ch2intro_2d"></a>Another method to run a python script would be to include the line</p>
-<p id="ch2intro_2e"></a><code class="literal">#! /usr/bin/python</code></p>
-<p id="ch2intro_2f"></a>at the beginning of the python file and then make the file executable by</p>
-<p id="ch2intro_30"></a>$ chmod a+x <span class="emphasis"><em>filename.py</em></span></p>
-<p id="ch2intro_31"></a>Once this is done, the script can be run as a standalone program as follows:</p>
-<p id="ch2intro_32"></a>$ ./<span class="emphasis"><em>filename.py</em></span></p>
-</div>
-<div class="section" title="4. Basic Datatypes and operators in Python">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2757696"></a>4. Basic Datatypes and operators in Python</h2></div></div></div>
-<p id="ch2intro_33"></a>Python provides the following set of basic datatypes.</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_34"></a>Numbers: int, float, long, complex</p></span><span style="color: black"><p id="ch2intro_35"></a>Strings</p></span><span style="color: black"><p id="ch2intro_36"></a>Boolean</p></span></span></span><div class="section" title="4.1. Numbers">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2757731"></a>4.1. Numbers</h3></div></div></div>
-<p id="ch2intro_37"></a>Numbers were introduced in the examples presented in the interactive interpreter
-section. Numbers include types as mentioned earlier viz., int (integers), float
-(floating point numbers), long (large integers), complex (complex numbers with
-real and imaginary parts). Python is not a strongly typed language, which means
-the type of a variable need not mentioned during its initialization. Let us look
-at a few examples.</p>
-<p id="ch2intro_38"></a>Eg 6:</p>
-<pre class="programlisting"> &gt;&gt;&gt; a = 1 #here a is an integer variable</pre>
-<p id="ch2intro_39"></a>Eg 7:</p>
-<pre class="programlisting"> &gt;&gt;&gt; lng = 122333444455555666666777777788888888999999999 #here lng is a variable of type long
-&gt;&gt;&gt; lng
-122333444455555666666777777788888888999999999L #notice the trailing 'L'
-&gt;&gt;&gt; print lng
-122333444455555666666777777788888888999999999 #notice the absence of the trailing 'L'
-&gt;&gt;&gt; lng+1
-122333444455555666666777777788888889000000000L</pre>
-<p id="ch2intro_3a"></a>Long numbers are the same as integers in almost all aspects. They can be used in
-operations just like integers and along with integers without any distinction.
-The only distinction comes during type checking (which is not a healthy practice).
-Long numbers are tucked with a trailing 'L' just to signify that they are long.
-Notice that in the example just lng at the prompt displays the value of the variable
-with the 'L' whereas <code class="literal">print lng</code> displays without the 'L'. This is because print
-formats the output before printing. Also in the example, notice that adding an
-integer to a long does not give any errors and the result is as expected. So for
-all practical purposes longs can be treated as ints.</p>
-<p id="ch2intro_3b"></a>Eg 8:</p>
-<pre class="programlisting"> &gt;&gt;&gt; fl = 3.14159 #fl is a float variable
-&gt;&gt;&gt; e = 1.234e-4 #e is also a float variable, specified in the exponential form
-&gt;&gt;&gt; a = 1
-&gt;&gt;&gt; b = 2
-&gt;&gt;&gt; a/b #integer division
-0
-&gt;&gt;&gt; a/fl #floating point division
-0.31831015504887655
-&gt;&gt;&gt; e/fl
-3.9279473133031364e-05</pre>
-<p id="ch2intro_3c"></a>Floating point numbers, simply called floats are real numbers with a decimal point.
-The example above shows the initialization of a float variable. Shown also in this
-example is the difference between integer division and floating point division.
-'a' and 'b' here are integer variables and hence the division gives 0 as the quotient.
-When either of the operands is a float, the operation is a floating point division,
-and the result is also a float as illustrated.</p>
-<p id="ch2intro_3d"></a>Eg 9:</p>
-<pre class="programlisting"> &gt;&gt;&gt; cplx = 3 + 4j #cplx is a complex variable
-&gt;&gt;&gt; cplx
-(3+4j)
-&gt;&gt;&gt; print cplx.real #prints the real part of the complex number
-3.0
-&gt;&gt;&gt; print cplx.imag #prints the imaginary part of the complex number
-4.0
-&gt;&gt;&gt; print cplx*fl  #multiplies the real and imag parts of the complex number with the multiplier
-(9.42477+12.56636j)
-&gt;&gt;&gt; abs(cplx) #returns the absolute value of the complex number
-5.0</pre>
-<p id="ch2intro_3e"></a>Python provides a datatype for complex numbers. Complex numbers are initialized
-as shown in the example above. The <span class="emphasis"><em>real</em></span> and <span class="emphasis"><em>imag</em></span> operators return the real and
-imaginary parts of the complex number as shown. The <span class="emphasis"><em>abs()</em></span> returns the absolute
-value of the complex number.</p>
-</div>
-<div class="section" title="4.2. Variables">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2757854"></a>4.2. Variables</h3></div></div></div>
-<p id="ch2intro_3f"></a>Variables are just names that represent a value. Variables have already been
-introduced in the various examples from the previous sections. Certain rules about
-using variables:</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch2intro_40"></a>Variables have to be initialized or assigned a value before being used.</p></span><span style="color: black"><p id="ch2intro_41"></a>Variable names can consist of letters, digits and underscores(_).</p></span><span style="color: black"><p id="ch2intro_42"></a>Variable names cannot begin with digits, but can contain digits in them.</p></span></span></span><p id="ch2intro_43"></a>In reference to the previous section examples, 'a', 'b', 'lng', 'fl', 'e' and 'cplx'
-are all variables of various datatypes.</p>
-<pre class="programlisting"> Note: Python is not a strongly typed language and hence an integer variable can at a
-later stage be used as a float variable as well.</pre>
-</div>
-<div class="section" title="4.3. Strings">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2757903"></a>4.3. Strings</h3></div></div></div>
-<p id="ch2intro_44"></a>Strings are one of the essential data structures of any programming language.
-The <code class="literal">print "Hello, World!"</code> program was introduced in the earlier section, and
-the <span class="emphasis"><em>"Hello, World!"</em></span> in the print statement is a string. A string is basically
-a set of characters. Strings can be represented in various ways shown below:</p>
-<pre class="programlisting"> s = 'this is a string'              # a string variable can be represented using single quotes
-s = 'This one has "quotes" inside!' # The string can have quotes inside it as shown
-s = "I have 'single-quotes' inside!"
-l = "A string spanning many lines\
-one more line\
-yet another"                        # a string can span more than a single line.
-t = """A triple quoted string does  # another way of representing multiline strings.
-not need to be escaped at the end and
-"can have nested quotes" etc."""</pre>
-<p id="ch2intro_45"></a>Try the following on the interpreter:
-<code class="literal">s = 'this is a string with 'quotes' of similar kind'</code></p>
-<p id="ch2intro_46"></a><span class="strong"><strong>Exercise: How to use single quotes within single quotes in a string as shown
-in the above example without getting an error?</strong></span></p>
-<div class="section" title="4.3.1. String operations">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id2757955"></a>4.3.1. String operations</h4></div></div></div>
-<p id="ch2intro_47"></a>A few basic string operations are presented here.</p>
-<p id="ch2intro_48"></a><span class="strong"><strong>String concatenation</strong></span>
-String concatenation is done by simple addition of two strings.</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = 'Hello'
-&gt;&gt;&gt; y = ' Python'
-&gt;&gt;&gt; print x+y
-Hello Python</pre>
-<p id="ch2intro_49"></a><span class="emphasis"><em>Try this yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; somenum = 13
-&gt;&gt;&gt; print x+somenum</pre>
-<p id="ch2intro_4a"></a>The problem with the above example is that here a string variable and an integer
-variable are trying to be concantenated. To obtain the desired result from the
-above example the str(), repr() and the `` can be used.</p>
-<p id="ch2intro_4b"></a><span class="strong"><strong>str()</strong></span> simply converts a value to a string in a reasonable form.
-<span class="strong"><strong>repr()</strong></span> creates a string that is a representation of the value.</p>
-<p id="ch2intro_4c"></a>The difference can be seen in the example shown below:</p>
-<pre class="programlisting"> &gt;&gt;&gt; str(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000'
-&gt;&gt;&gt; repr(1000000000000000000000000000000000000000000000000L)
-'1000000000000000000000000000000000000000000000000L'</pre>
-<p id="ch2intro_4d"></a>It can be observed that the 'L' in the long value shown was omitted by str(),
-whereas repr() converted that into a string too. An alternative way of using
-repr(value) is <code class="literal">`value`</code>.</p>
-<p id="ch2intro_4e"></a>A few more examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = "Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go
-to Pycon</pre>
-<p id="ch2intro_4f"></a>In the above example, notice that the 'n'(newline) character is formatted and
-the string is printed on two lines. The strings discussed until now were normal
-strings. Other than these there are two other types of strings namely, raw strings
-and unicode strings.</p>
-<p id="ch2intro_50"></a><span class="strong"><strong>Raw strings</strong></span> are strings which are unformatted, that is the backslashes() are
-not parsed and are left as it is in the string. Raw strings are represented with
-an 'r' at the start of a string.
-Let us look at an example</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = r"Let's go \nto Pycon"
-&gt;&gt;&gt; print x
-Let's go \nto Pycon</pre>
-<p id="ch2intro_51"></a>Note: The 'n' is not being parsed into a new line and is left as it is.</p>
-<p id="ch2intro_52"></a><span class="emphasis"><em>Try this yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; x = r"Let's go to Pycon\"</pre>
-<p id="ch2intro_53"></a><span class="strong"><strong>Unicode strings</strong></span> are strings where the characters are Unicode characters as
-opposed to ASCII characters. Unicode strings are represented with a 'u' at the
-start of the string.
-Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = u"Let's go to Pycon!"
-&gt;&gt;&gt; print x
-Let's go to Pycon!</pre>
-</div>
-</div>
-<div class="section" title="4.4. Boolean">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2758097"></a>4.4. Boolean</h3></div></div></div>
-<p id="ch2intro_54"></a>Python also provides special Boolean datatype. A boolean variable can assume a
-value of either <span class="emphasis"><em>True</em></span> or <span class="emphasis"><em>False</em></span> (Note the capitalizations).</p>
-<p id="ch2intro_55"></a>Let us look at examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; t = True
-&gt;&gt;&gt; f = not t
-&gt;&gt;&gt; print f
-False
-&gt;&gt;&gt; f or t
-True
-&gt;&gt;&gt; f and t
-False</pre>
-</div>
-</div>
-<div class="section" title="5. The while loop">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758126"></a>5. The <span class="strong"><strong>while</strong></span> loop</h2></div></div></div>
-<p id="ch2intro_56"></a>The Python <span class="strong"><strong>while</strong></span> loop is similar to the C/C++ while loop. The syntax is as
-follows:</p>
-<pre class="programlisting"> statement 0
-while condition:
-  statement 1 #while block
-  statement 2 #while block
-statement 3 #outside the while block.</pre>
-<p id="ch2intro_57"></a>Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; x = 1
-&gt;&gt;&gt; while x &lt;= 5:
-...   print x
-...   x += 1
-...
-1
-2
-3
-4
-5</pre>
-</div>
-<div class="section" title="6. The if conditional">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758163"></a>6. The <span class="strong"><strong>if</strong></span> conditional</h2></div></div></div>
-<p id="ch2intro_58"></a>The Python <span class="strong"><strong>if</strong></span> block provides the conditional execution of statements.
-If the condition evaluates as true the block of statements defined under the if
-block are executed.</p>
-<p id="ch2intro_59"></a>If the first block is not executed on account of the condition not being satisfied,
-the set of statements in the <span class="strong"><strong>else</strong></span> block are executed.</p>
-<p id="ch2intro_5a"></a>The <span class="strong"><strong>elif</strong></span> block provides the functionality of evaluation of multiple conditions
-as shown in the example.</p>
-<p id="ch2intro_5b"></a>The syntax is as follows:</p>
-<pre class="programlisting"> if condition :
-    statement_1
-    statement_2
-
-elif condition:
-    statement_3
-    statement_4
-else:
-    statement_5
-    statement_6</pre>
-<p id="ch2intro_5c"></a>Let us look at an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; n = raw_input("Input a number:")
-&gt;&gt;&gt; if n &lt; 0:
-      print n," is negative"
-      elif n &gt; 0:
-      print n," is positive"
-      else:
-      print n, " is 0"</pre>
-</div>
-<div class="section" title="7. raw_input()">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758232"></a>7. <span class="strong"><strong>raw_input()</strong></span>
-</h2></div></div></div>
-<p id="ch2intro_5d"></a>In the previous example we saw the call to the raw_input() subroutine.
-The <span class="strong"><strong>raw_input()</strong></span> method is used to take user inputs through the console.
-Unlike <span class="strong"><strong>input()</strong></span> which assumes the data entered by the user as a standard python
-expression, <span class="strong"><strong>raw_input()</strong></span> treats all the input data as raw data and converts
-everything into a string. To illustrate this let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-121
-
-&gt;&gt;&gt; input("Enter your name:")
-Enter your name:PythonFreak
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-  File "&lt;string&gt;", line 1, in &lt;module&gt;
-NameError: name 'PythonFreak' is not defined</pre>
-<p id="ch2intro_5e"></a>As shown above the <span class="strong"><strong>input()</strong></span> assumes that the data entered is a valid Python
-expression. In the first call it prompts for an integer input and when entered
-it accepts the integer as an integer, whereas in the second call, when the string
-is entered without the quotes, <span class="strong"><strong>input()</strong></span> assumes that the entered data is a valid
-Python expression and hence it raises and exception saying PythonFreak is not
-defined.</p>
-<pre class="programlisting"> &gt;&gt;&gt; input("Enter your name:")
-Enter your name:'PythonFreak'
-'PythonFreak'
-&gt;&gt;&gt;</pre>
-<p id="ch2intro_5f"></a>Here the name is accepted because its entered as a string (within quotes). But
-its unreasonable to go on using quotes each time a string is entered. Hence the
-alternative is to use <span class="strong"><strong>raw_input()</strong></span>.</p>
-<p id="ch2intro_60"></a>Let us now look at how <span class="strong"><strong>raw_input()</strong></span> operates with an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; raw_input("Enter your name:")
-Enter your name:PythonFreak
-'PythonFreak'</pre>
-<p id="ch2intro_61"></a>Observe that the <span class="strong"><strong>raw_input()</strong></span> is converting it into a string all by itself.</p>
-<pre class="programlisting"> &gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-'121'</pre>
-<p id="ch2intro_62"></a>Observe that <span class="strong"><strong>raw_input()</strong></span> is converting the integer 121 also to a string as
-'121'. Let us look at another example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; pal = raw_input("Enter a number thats a palindrome:")
-Enter a number thats a palindrome:121
-&gt;&gt;&gt; pal + 2
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: cannot concatenate 'str' and 'int' objects
-&gt;&gt;&gt; pal
-'121'</pre>
-<p id="ch2intro_63"></a>Observe here that the variable <span class="emphasis"><em>pal</em></span> is a string and hence integer operations
-cannot be performed on it. Hence the exception is raised.</p>
-</div>
-<div class="section" title="8. int() method">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2758387"></a>8. <span class="strong"><strong>int()</strong></span> method</h2></div></div></div>
-<p id="ch2intro_64"></a>Generally for computing purposes, the data used is not strings or raw data but
-on integers, floats and similar mathematical data structures. The data obtained
-from <span class="strong"><strong>raw_input()</strong></span> is raw data in the form of strings. In order to obtain integers
-from strings we use the method <span class="strong"><strong>int()</strong></span>.</p>
-<p id="ch2intro_65"></a>Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; intpal = int(pal)
-&gt;&gt;&gt; intpal
-121</pre>
-<p id="ch2intro_66"></a>In the previous example it was observed that <span class="emphasis"><em>pal</em></span> was a string variable. Here
-using the <span class="strong"><strong>int()</strong></span> method the string <span class="emphasis"><em>pal</em></span> was converted to an integer variable.</p>
-<p id="ch2intro_67"></a><span class="emphasis"><em>Try This Yourself:</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; stringvar = raw_input("Enter a name:")
-Enter a name:Guido Van Rossum
-&gt;&gt;&gt; stringvar
-'Guido Van Rossum'
-&gt;&gt;&gt; numvar = int(stringvar)</pre>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch4strings_dicts.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch4strings_dicts.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,465 +1,1139 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 4. strings_dicts</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
+<title>Strings and Dicts </title>
 <link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
 <script type="text/javascript" src="/review/support/hsbook.js"></script>
 <meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch4strings_dicts">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch4strings_dicts ">
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="article"><a href="#id2983496">Strings</a></span></dt>
+<dt><span class="article"><a href="#id2633629"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2443754">1. Introducing Linux</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2982083">1. String Formatting</a></span></dt>
-<dt><span class="section"><a href="#id3034500">2. String Methods</a></span></dt>
+<dt><span class="section"><a href="#id2631449">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2684690">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2684962">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2685094">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2685102">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2684456">3. Basic Commands</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3034515">2.1. <span class="strong"><strong>find</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034545">2.2. <span class="strong"><strong>join</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034585">2.3. <span class="strong"><strong>lower</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034615">2.4. <span class="strong"><strong>replace</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034672">2.5. <span class="strong"><strong>split</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034731">2.6. <span class="strong"><strong>strip</strong></span></a></span></dt>
+<dt><span class="section"><a href="#id2684464">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2685688">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2685748">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2685850">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2685932">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2686111">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2686119">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2686212">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2686421">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2686511">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2686564">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2686572">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2686884">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2687015">5.3. rm</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id3034775">3. Introduction to the standard library</a></span></dt>
-<dt><span class="section"><a href="#id3034853">4. I/O: Reading and Writing Files</a></span></dt>
+<dt><span class="section"><a href="#id2687186">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2687278">7. Basic Text Processing</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3034883">4.1. Opening Files</a></span></dt>
-<dt><span class="section"><a href="#id3035057">4.2. Reading and Writing files</a></span></dt>
+<dt><span class="section"><a href="#id2687287">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2687373">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2687499">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2687585">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2687717">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2687825">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2687833">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2688020">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2688130">9.3. less</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id3035222">5. Dictionaries</a></span></dt>
+<dt><span class="section"><a href="#id2688372">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2688647">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2688663">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2688686">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2688695">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2689472">12. Redirection and Piping</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3035278">5.1. <span class="strong"><strong>dict()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3035342">5.2. Dictionary Methods</a></span></dt>
+<dt><span class="section"><a href="#id2689508">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2689576">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2689638">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2689846">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2689880">12.5. Redirect to multiple outputs</a></span></dt>
 </dl></dd>
+<dt><span class="section"><a href="#id2689911">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2689920">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2690110">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2690261">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2690477">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2690554">15. One Liners</a></span></dt>
 </dl></dd>
 </dl>
 </div>
-<div class="article" title="Strings">
+<div class="article">
 <div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2983496"></a>Strings</h2></div></div>
+<div><div><h2 class="title" id="id2633629"></a></h2></div></div>
 <hr>
 </div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="section"><a href="#id2982083">1. String Formatting</a></span></dt>
-<dt><span class="section"><a href="#id3034500">2. String Methods</a></span></dt>
+<dt><span class="section"><a href="#id2443754">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2631449">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2684690">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2684962">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2685094">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2685102">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2684456">3. Basic Commands</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3034515">2.1. <span class="strong"><strong>find</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034545">2.2. <span class="strong"><strong>join</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034585">2.3. <span class="strong"><strong>lower</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034615">2.4. <span class="strong"><strong>replace</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034672">2.5. <span class="strong"><strong>split</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034731">2.6. <span class="strong"><strong>strip</strong></span></a></span></dt>
+<dt><span class="section"><a href="#id2684464">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2685688">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2685748">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2685850">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2685932">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2686111">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2686119">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2686212">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2686421">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2686511">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2686564">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2686572">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2686884">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2687015">5.3. rm</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id3034775">3. Introduction to the standard library</a></span></dt>
-<dt><span class="section"><a href="#id3034853">4. I/O: Reading and Writing Files</a></span></dt>
+<dt><span class="section"><a href="#id2687186">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2687278">7. Basic Text Processing</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3034883">4.1. Opening Files</a></span></dt>
-<dt><span class="section"><a href="#id3035057">4.2. Reading and Writing files</a></span></dt>
+<dt><span class="section"><a href="#id2687287">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2687373">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2687499">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2687585">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2687717">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2687825">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2687833">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2688020">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2688130">9.3. less</a></span></dt>
 </dl></dd>
-<dt><span class="section"><a href="#id3035222">5. Dictionaries</a></span></dt>
+<dt><span class="section"><a href="#id2688372">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2688647">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2688663">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2688686">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2688695">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2689472">12. Redirection and Piping</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id3035278">5.1. <span class="strong"><strong>dict()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3035342">5.2. Dictionary Methods</a></span></dt>
+<dt><span class="section"><a href="#id2689508">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2689576">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2689638">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2689846">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2689880">12.5. Redirect to multiple outputs</a></span></dt>
 </dl></dd>
+<dt><span class="section"><a href="#id2689911">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2689920">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2690110">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2690261">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2690477">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2690554">15. One Liners</a></span></dt>
 </dl>
 </div>
-<p id="ch4strings_dicts_1"></a>Strings were briefly introduced previously in the introduction document. In this
-section strings will be presented in greater detail. All the standard operations
-that can be performed on sequences such as indexing, slicing, multiplication, length
-minimum and maximum can be performed on string variables as well. One thing to
-be noted is that strings are immutable, which means that string variables are
-unchangeable. Hence, all item and slice assignments on strings are illegal.
-Let us look at a few example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; name = 'PythonFreak'
-&gt;&gt;&gt; print name[3]
-h
-&gt;&gt;&gt; print name[-1]
-k
-&gt;&gt;&gt; print name[6:]
-Freak
-&gt;&gt;&gt; name[6:0] = 'Maniac'
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: 'str' object does not support item assignment</pre>
-<p id="ch4strings_dicts_2"></a>This is quite expected, since string objects are immutable as already mentioned.
-The error message is clear in mentioning that 'str' object does not support item
-assignment.</p>
-<div class="section" title="1. String Formatting">
+<div class="section" title="1. Introducing Linux">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2982083"></a>1. String Formatting</h2></div></div></div>
-<p id="ch4strings_dicts_3"></a>String formatting can be performed using the string formatting operator represented
-as the percent (%) sign. The string placed before the % sign is formatted with
-the value placed to the right of it. Let us look at a simple example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; format = 'Hello %s, from PythonFreak'
-&gt;&gt;&gt; str1 = 'world!'
-&gt;&gt;&gt; print format % str1
-Hello world!, from PythonFreak</pre>
-<p id="ch4strings_dicts_4"></a>The %s parts of the format string are called the coversion specifiers. The coversion
-specifiers mark the places where the formatting has to be performed in a string.
-In the example the %s is replaced by the value of str1. More than one value can
-also be formatted at a time by specifying the values to be formatted using tuples
-and dictionaries (explained in later sections). Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; format = 'Hello %s, from %s'
-&gt;&gt;&gt; values = ('world!', 'PythonFreak')
-&gt;&gt;&gt; print format % values
-Hello world!, from PythonFreak</pre>
-<p id="ch4strings_dicts_5"></a>In this example it can be observed that the format string contains two conversion
-specifiers and they are formatted using the tuple of values as shown.</p>
-<p id="ch4strings_dicts_6"></a>The s in %s specifies that the value to be replaced is of type string. Values of
-other types can be specified as well such as integers and floats. Integers are
-specified as %d and floats as %f. The precision with which the integer or the
-float values are to be represented can also be specified using a <span class="strong"><strong>.</strong></span> (<span class="strong"><strong>dot</strong></span>)
-followed by the precision value.</p>
+<a name="id2443754"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch4strings_dicts_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch4strings_dicts_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch4strings_dicts_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch4strings_dicts_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2631449"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2631415"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
 </div>
-<div class="section" title="2. String Methods">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034500"></a>2. String Methods</h2></div></div></div>
-<p id="ch4strings_dicts_7"></a>Similar to list methods, strings also have a rich set of methods to perform various
-operations on strings. Some of the most important and popular ones are presented
-in this section.</p>
-<div class="section" title="2.1. find">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034515"></a>2.1. <span class="strong"><strong>find</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_8"></a>The <span class="strong"><strong>find</strong></span> method is used to search for a substring within a given string. It
-returns the left most index of the first occurence of the substring. If the
-substring is not found in the string then it returns -1. Let us look at a few
-examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; longstring = 'Hello world!, from PythonFreak'
-&gt;&gt;&gt; longstring.find('Python')
-19
-&gt;&gt;&gt; longstring.find('Perl')
--1</pre>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684645"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch4strings_dicts_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch4strings_dicts_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
 </div>
-<div class="section" title="2.2. join">
+</div>
+<div class="section" title="1.2. Design and Implications">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3034545"></a>2.2. <span class="strong"><strong>join</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_9"></a>The <span class="strong"><strong>join</strong></span> method is used to join the elements of a sequence. The sequence
-elements that are to be join ed should all be strings. Let us look at a few
-examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; seq = ['With', 'great', 'power', 'comes', 'great', 'responsibility']
-&gt;&gt;&gt; sep = ' '
-&gt;&gt;&gt; sep.join(seq)
-'With great power comes great responsibility'
-&gt;&gt;&gt; sep = ',!'
-&gt;&gt;&gt; sep.join(seq)
-'With,!great,!power,!comes,!great,!responsibility'</pre>
-<p id="ch4strings_dicts_a"></a><span class="emphasis"><em>Try this yourself</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; seq = [12,34,56,78]
-&gt;&gt;&gt; sep.join(seq)</pre>
+<a name="id2684690"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch4strings_dicts_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684714"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch4strings_dicts_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch4strings_dicts_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684768"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch4strings_dicts_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch4strings_dicts_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch4strings_dicts_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
 </div>
-<div class="section" title="2.3. lower">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034585"></a>2.3. <span class="strong"><strong>lower</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_b"></a>The <span class="strong"><strong>lower</strong></span> method, as the name indicates, converts the entire text of a string
-to lower case. It is specially useful in cases where the programmers deal with case
-insensitive data. Let us look at a few examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; sometext = 'Hello world!, from PythonFreak'
-&gt;&gt;&gt; sometext.lower()
-'hello world!, from pythonfreak'</pre>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684824"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch4strings_dicts_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch4strings_dicts_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch4strings_dicts_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
 </div>
-<div class="section" title="2.4. replace">
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684869"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch4strings_dicts_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2684915"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch4strings_dicts_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch4strings_dicts_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch4strings_dicts_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3034615"></a>2.4. <span class="strong"><strong>replace</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_c"></a>The <span class="strong"><strong>replace</strong></span> method replaces a substring with another substring within
-a given string and returns the new string. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; sometext = 'Concise, precise and criticise is some of the words that end with ise'
-&gt;&gt;&gt; sometext.replace('is', 'are')
-'Concaree, precaree and criticaree are some of the words that end with aree'</pre>
-<p id="ch4strings_dicts_d"></a>Observe here that all the occurences of the substring <span class="emphasis"><em>is</em></span> have been replaced,
-even the <span class="emphasis"><em>is</em></span> in <span class="emphasis"><em>concise</em></span>, <span class="emphasis"><em>precise</em></span> and <span class="emphasis"><em>criticise</em></span> have been replaced.</p>
-</div>
-<div class="section" title="2.5. split">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034672"></a>2.5. <span class="strong"><strong>split</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_e"></a>The <span class="strong"><strong>split</strong></span> is one of the very important string methods. split is the opposite of the
-<span class="strong"><strong>join</strong></span> method. It is used to split a string based on the argument passed as the
-delimiter. It returns a list of strings. By default when no argument is passed it
-splits with <span class="emphasis"><em>space</em></span> (' ') as the delimiter. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; grocerylist = 'butter, cucumber, beer(a grocery item??), wheatbread'
-&gt;&gt;&gt; grocerylist.split(',')
-['butter', ' cucumber', ' beer(a grocery item??)', ' wheatbread']
-&gt;&gt;&gt; grocerylist.split()
-['butter,', 'cucumber,', 'beer(a', 'grocery', 'item??),', 'wheatbread']</pre>
-<p id="ch4strings_dicts_f"></a>Observe here that in the second case when the delimiter argument was not set
-<span class="strong"><strong>split</strong></span> was done with <span class="emphasis"><em>space</em></span> as the delimiter.</p>
-</div>
-<div class="section" title="2.6. strip">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034731"></a>2.6. <span class="strong"><strong>strip</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_10"></a>The <span class="strong"><strong>strip</strong></span> method is used to remove or <span class="strong"><strong>strip</strong></span> off any whitespaces that exist
-to the left and right of a string, but not the whitespaces within a string. Let
-us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; spacedtext = "               Where's the text??                 "
-&gt;&gt;&gt; spacedtext.strip()
-"Where's the text??"</pre>
-<p id="ch4strings_dicts_11"></a>Observe that the whitespaces between the words have not been removed.</p>
-<pre class="programlisting"> Note: Very important thing to note is that all the methods shown above do not
-      transform the source string. The source string still remains the same.
-      Remember that **strings are immutable**.</pre>
+<a name="id2684962"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch4strings_dicts_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch4strings_dicts_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch4strings_dicts_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch4strings_dicts_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch4strings_dicts_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch4strings_dicts_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
 </div>
 </div>
-<div class="section" title="3. Introduction to the standard library">
+<div class="section" title="2. Getting Started">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034775"></a>3. Introduction to the standard library</h2></div></div></div>
-<p id="ch4strings_dicts_12"></a>Python is often referred to as a "Batteries included!" language, mainly because
-of the Python Standard Library. The Python Standard Library provides an extensive
-set of features some of which are available directly for use while some require to
-import a few <span class="strong"><strong>modules</strong></span>. The Standard Library provides various built-in functions
-like:</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch4strings_dicts_13"></a><span class="strong"><strong>abs()</strong></span></p></span><span style="color: black"><p id="ch4strings_dicts_14"></a><span class="strong"><strong>dict()</strong></span></p></span><span style="color: black"><p id="ch4strings_dicts_15"></a><span class="strong"><strong>enumerate()</strong></span></p></span></span></span><p id="ch4strings_dicts_16"></a>The built-in constants like <span class="strong"><strong>True</strong></span> and <span class="strong"><strong>False</strong></span> are provided by the Standard Library.
-More information about the Python Standard Library is available </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://docs.python.org/library/</div>
-</div>
-<div class="section" title="4. I/O: Reading and Writing Files">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034853"></a>4. I/O: Reading and Writing Files</h2></div></div></div>
-<p id="ch4strings_dicts_17"></a>Files are very important aspects when it comes to computing and programming.
-Up until now the focus has been on small programs that interacted with users
-through <span class="strong"><strong>input()</strong></span> and <span class="strong"><strong>raw_input()</strong></span>. Generally, for computational purposes
-it becomes necessary to handle files, which are usually large in size as well.
-This section focuses on basics of file handling.</p>
-<div class="section" title="4.1. Opening Files">
+<a name="id2685094"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3034883"></a>4.1. Opening Files</h3></div></div></div>
-<p id="ch4strings_dicts_18"></a>Files can be opened using the <span class="strong"><strong>open()</strong></span> method. <span class="strong"><strong>open()</strong></span> accepts 3 arguments
-out of which 2 are optional. Let us look at the syntax of <span class="strong"><strong>open()</strong></span>:</p>
-<p id="ch4strings_dicts_19"></a><span class="emphasis"><em>f = open( filename, mode, buffering)</em></span></p>
-<p id="ch4strings_dicts_1a"></a>The <span class="emphasis"><em>filename</em></span> is a compulsory argument while the <span class="emphasis"><em>mode</em></span> and <span class="emphasis"><em>buffering</em></span> are
-optional. The <span class="emphasis"><em>filename</em></span> should be a string and it should be the complete path
-to the file to be opened (The path can be absolute or relative). Let us look at
-an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('basic_python/interim_assessment.rst')</pre>
-<p id="ch4strings_dicts_1b"></a>The <span class="emphasis"><em>mode</em></span> argument specifies the mode in which the file has to be opened.
-The following are the valid mode arguments:</p>
-<p id="ch4strings_dicts_1c"></a><span class="strong"><strong>r</strong></span> - Read mode
-<span class="strong"><strong>w</strong></span> - Write mode
-<span class="strong"><strong>a</strong></span> - Append mode
-<span class="strong"><strong>b</strong></span> - Binary mode
-<span class="strong"><strong>+</strong></span> - Read/Write mode</p>
-<p id="ch4strings_dicts_1d"></a>The read mode opens the file as a read-only document. The write mode opens the
-file in the Write only mode. In the write mode, if the file existed prior to the
-opening, the previous contents of the file are erased. The append mode opens the
-file in the write mode but the previous contents of the file are not erased and
-the current data is appended onto the file.
-The binary and the read/write modes are special in the sense that they are added
-onto other modes. The read/write mode opens the file in the reading and writing
-mode combined. The binary mode can be used to open a files that do not contain
-text. Binary files such as images should be opened in the binary mode. Let us look
-at a few examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('basic_python/interim_assessment.rst', 'r')
-&gt;&gt;&gt; f = open ('armstrong.py', 'r+')</pre>
-<p id="ch4strings_dicts_1e"></a>The third argument to the <span class="strong"><strong>open()</strong></span> method is the <span class="emphasis"><em>buffering</em></span> argument. This takes
-a boolean value, <span class="emphasis"><em>True</em></span> or <span class="emphasis"><em>1</em></span> indicates that buffering has to be enabled on the file,
-that is the file is loaded on to the main memory and the changes made to the file are
-not immediately written to the disk. If the <span class="emphasis"><em>buffering</em></span> argument is <span class="emphasis"><em>0</em></span> or <span class="emphasis"><em>False</em></span> the
-changes are directly written on to the disk immediately.</p>
+<a name="id2685102"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch4strings_dicts_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2685133"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch4strings_dicts_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch4strings_dicts_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch4strings_dicts_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch4strings_dicts_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch4strings_dicts_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch4strings_dicts_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch4strings_dicts_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch4strings_dicts_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch4strings_dicts_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2685291"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch4strings_dicts_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch4strings_dicts_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch4strings_dicts_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch4strings_dicts_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch4strings_dicts_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2684456"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2684464"></a>3.1. ls</h3></div></div></div>
+<p id="ch4strings_dicts_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch4strings_dicts_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch4strings_dicts_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch4strings_dicts_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
 </div>
-<div class="section" title="4.2. Reading and Writing files">
+<div class="section" title="3.2. date">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3035057"></a>4.2. Reading and Writing files</h3></div></div></div>
-<div class="section" title="4.2.1. write()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035066"></a>4.2.1. <span class="strong"><strong>write()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_1f"></a><span class="strong"><strong>write()</strong></span>, evidently, is used to write data onto a file. It takes the data to
-be written as the argument. The data can be a string, an integer, a float or any
-other datatype. In order to be able to write data onto a file, the file has to
-be opened in one of <span class="strong"><strong>w</strong></span>, <span class="strong"><strong>a</strong></span> or <span class="strong"><strong>+</strong></span> modes.</p>
+<a name="id2685688"></a>3.2. date</h3></div></div></div>
+<p id="ch4strings_dicts_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch4strings_dicts_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch4strings_dicts_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch4strings_dicts_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch4strings_dicts_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
 </div>
-<div class="section" title="4.2.2. read()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035105"></a>4.2.2. <span class="strong"><strong>read()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_20"></a><span class="strong"><strong>read()</strong></span> is used to read data from a file. It takes the number of bytes of data
-to be read as the argument. If nothing is specified by default it reads the entire
-contents from the current position to the end of file.</p>
-<p id="ch4strings_dicts_21"></a>Let us look at a few examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('randomtextfile', 'w')
-&gt;&gt;&gt; f.write('Hello all, this is PythonFreak. This is a random text file.')
-&gt;&gt;&gt; f = open ('../randomtextfile', 'r')
-&gt;&gt;&gt; f = open ('../randomtextfile', 'r')
-&gt;&gt;&gt; f.read(5)
-'Hello'
-&gt;&gt;&gt; f.read()
-' all, this is PythonFreak. This is a random text file.'
-&gt;&gt;&gt; f.close()</pre>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2685748"></a>3.3. cd</h3></div></div></div>
+<p id="ch4strings_dicts_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch4strings_dicts_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch4strings_dicts_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch4strings_dicts_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch4strings_dicts_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch4strings_dicts_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch4strings_dicts_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch4strings_dicts_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch4strings_dicts_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch4strings_dicts_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
 </div>
-<div class="section" title="4.2.3. readline()">
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2685850"></a>3.4. who</h3></div></div></div>
+<p id="ch4strings_dicts_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch4strings_dicts_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch4strings_dicts_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch4strings_dicts_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch4strings_dicts_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2685932"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch4strings_dicts_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch4strings_dicts_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035140"></a>4.2.3. <span class="strong"><strong>readline()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_22"></a><span class="strong"><strong>readline()</strong></span> is used to read a file line by line. <span class="strong"><strong>readline()</strong></span> reads a line
-of a file at a time. When an argument is passed to <span class="strong"><strong>readline()</strong></span> it reads that
-many bytes from the current line.</p>
-<p id="ch4strings_dicts_23"></a>One other method to read a file line by line is using the <span class="strong"><strong>read()</strong></span> and the
-<span class="strong"><strong>for</strong></span> construct. Let us look at this block of code as an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open('../randomtextfile', 'r')
-&gt;&gt;&gt; for line in f:
-...     print line
-...
-Hello all!
-
-This is PythonFreak on the second line.
-
-This is a random text file on line 3</pre>
+<a name="id2685964"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch4strings_dicts_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
 </div>
-<div class="section" title="4.2.4. close()">
+<div class="section" title="3.5.2. Examples">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035199"></a>4.2.4. <span class="strong"><strong>close()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_24"></a>One must always close all the files that have been opened. Although, files opened
-will be closed automatically when the program ends. When files opened in read mode
-are not closed it might lead to uselessly locked sometimes. In case of files
-opened in the write mode it is more important to close the files. This is because,
-Python maybe using the file in the buffering mode and when the file is not closed
-the buffer maybe lost completely and the changes made to the file are lost forever.</p>
+<a name="id2686025"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch4strings_dicts_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch4strings_dicts_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch4strings_dicts_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch4strings_dicts_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
 </div>
 </div>
 </div>
-<div class="section" title="5. Dictionaries">
+<div class="section" title="4. Getting Help">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3035222"></a>5. Dictionaries</h2></div></div></div>
-<p id="ch4strings_dicts_25"></a>A dictionary in general, are designed to be able to look up meanings of words.
-Similarly, the Python dictionaries are also designed to look up for a specific
-key and retrieve the corresponding value. Dictionaries are data structures that
-provide key-value mappings. Dictionaries are similar to lists except that instead
-of the values having integer indexes, dictionaries have keys or strings as indexes.
-Let us look at an example of how to define dictionaries.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct = { 'Sachin': 'Tendulkar', 'Rahul': 'Dravid', 'Anil': 'Kumble'}</pre>
-<p id="ch4strings_dicts_26"></a>The dictionary consists of pairs of strings, which are called <span class="emphasis"><em>keys</em></span> and their
-corresponding <span class="emphasis"><em>values</em></span> separated by <span class="emphasis"><em>:</em></span> and each of these <span class="emphasis"><em>key-value</em></span> pairs are
-comma(',') separated and the entire structure wrapped in a pair curly braces <span class="emphasis"><em>{}</em></span>.</p>
-<pre class="programlisting"> Note: The data inside a dictionary is not ordered. The order in which you enter
-the key-value pairs is not the order in which they are stored in the dictionary.
-Python has an internal storage mechanism for that which is out of the purview
-of this document.</pre>
-<div class="section" title="5.1. dict()">
+<a name="id2686111"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2686119"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch4strings_dicts_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch4strings_dicts_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch4strings_dicts_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch4strings_dicts_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch4strings_dicts_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2686212"></a>4.2. man</h3></div></div></div>
+<p id="ch4strings_dicts_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch4strings_dicts_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch4strings_dicts_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch4strings_dicts_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch4strings_dicts_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch4strings_dicts_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686294"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch4strings_dicts_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch4strings_dicts_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch4strings_dicts_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch4strings_dicts_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch4strings_dicts_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch4strings_dicts_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch4strings_dicts_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch4strings_dicts_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch4strings_dicts_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch4strings_dicts_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch4strings_dicts_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch4strings_dicts_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2686421"></a>4.3. info</h3></div></div></div>
+<p id="ch4strings_dicts_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch4strings_dicts_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch4strings_dicts_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2686511"></a>4.4. --help</h3></div></div></div>
+<p id="ch4strings_dicts_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2686564"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3035278"></a>5.1. <span class="strong"><strong>dict()</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_27"></a>The <span class="strong"><strong>dict()</strong></span> function is used to create dictionaries from other mappings or other
-dictionaries. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; diction = dict(mat = 133, avg = 52.53)</pre>
-<p id="ch4strings_dicts_28"></a><span class="strong"><strong>String Formatting with Dictionaries:</strong></span></p>
-<p id="ch4strings_dicts_29"></a>String formatting was discussed in the previous section and it was mentioned that
-dictionaries can also be used for formatting more than one value. This section
-focuses on the formatting of strings using dictionaries. String formatting using
-dictionaries is more appealing than doing the same with tuples. Here the <span class="emphasis"><em>keyword</em></span>
-can be used as a place holder and the <span class="emphasis"><em>value</em></span> corresponding to it is replaced in
-the formatted string. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; player = { 'Name':'Rahul Dravid', 'Matches':133, 'Avg':52.53, '100s':26 }
-&gt;&gt;&gt; strng = '%(Name)s has played %(Matches)d with an average of %(Avg).2f and has %(100s)d hundreds to his name.'
-&gt;&gt;&gt; print strng % player
-Rahul Dravid has played 133 with an average of 52.53 and has 26 hundreds to his name.</pre>
+<a name="id2686572"></a>5.1. cp</h3></div></div></div>
+<p id="ch4strings_dicts_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686590"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch4strings_dicts_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch4strings_dicts_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch4strings_dicts_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686624"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch4strings_dicts_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch4strings_dicts_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch4strings_dicts_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch4strings_dicts_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686722"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch4strings_dicts_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch4strings_dicts_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch4strings_dicts_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch4strings_dicts_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch4strings_dicts_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch4strings_dicts_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch4strings_dicts_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch4strings_dicts_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch4strings_dicts_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch4strings_dicts_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch4strings_dicts_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch4strings_dicts_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch4strings_dicts_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch4strings_dicts_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2686884"></a>5.2. mv</h3></div></div></div>
+<p id="ch4strings_dicts_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686907"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch4strings_dicts_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686927"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch4strings_dicts_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2686957"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch4strings_dicts_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch4strings_dicts_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
 </div>
-<div class="section" title="5.2. Dictionary Methods">
+<div class="section" title="5.3. rm">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="id3035342"></a>5.2. Dictionary Methods</h3></div></div></div>
-<div class="section" title="5.2.1. clear()">
+<a name="id2687015"></a>5.3. rm</h3></div></div></div>
+<p id="ch4strings_dicts_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch4strings_dicts_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2687045"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch4strings_dicts_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch4strings_dicts_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch4strings_dicts_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch4strings_dicts_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035351"></a>5.2.1. <span class="strong"><strong>clear()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2a"></a>The <span class="strong"><strong>clear()</strong></span> method removes all the existing <span class="emphasis"><em>key-value</em></span> pairs from a dictionary.
-It returns <span class="emphasis"><em>None</em></span> or rather does not return anything. It is a method that changes
-the object. It has to be noted here that dictionaries are not immutable. Let us
-look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dct.clear()
-&gt;&gt;&gt; dct
-{}</pre>
+<a name="id2687147"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch4strings_dicts_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch4strings_dicts_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch4strings_dicts_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2687186"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch4strings_dicts_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch4strings_dicts_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch4strings_dicts_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch4strings_dicts_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch4strings_dicts_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch4strings_dicts_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch4strings_dicts_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
 </div>
-<div class="section" title="5.2.2. copy()">
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2687278"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2687287"></a>7.1. head</h3></div></div></div>
+<p id="ch4strings_dicts_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch4strings_dicts_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch4strings_dicts_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch4strings_dicts_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2687338"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch4strings_dicts_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch4strings_dicts_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch4strings_dicts_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2687373"></a>7.2. tail</h3></div></div></div>
+<p id="ch4strings_dicts_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch4strings_dicts_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch4strings_dicts_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch4strings_dicts_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch4strings_dicts_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch4strings_dicts_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch4strings_dicts_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035386"></a>5.2.2. <span class="strong"><strong>copy()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2b"></a>The <span class="strong"><strong>copy()</strong></span> returns a copy of a given dictionary. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct = {'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dctcopy = dct.copy()
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}</pre>
+<a name="id2687451"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch4strings_dicts_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch4strings_dicts_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch4strings_dicts_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2687499"></a>7.3. cut</h3></div></div></div>
+<p id="ch4strings_dicts_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch4strings_dicts_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch4strings_dicts_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch4strings_dicts_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch4strings_dicts_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch4strings_dicts_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch4strings_dicts_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
 </div>
-<div class="section" title="5.2.3. get()">
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2687585"></a>7.4. paste</h3></div></div></div>
+<p id="ch4strings_dicts_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch4strings_dicts_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch4strings_dicts_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch4strings_dicts_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2687717"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch4strings_dicts_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch4strings_dicts_df"></a>The shell meta characters include:</p>
+<p id="ch4strings_dicts_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch4strings_dicts_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch4strings_dicts_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch4strings_dicts_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch4strings_dicts_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch4strings_dicts_e5"></a>because the c* matches that long file name.</p>
+<p id="ch4strings_dicts_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch4strings_dicts_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch4strings_dicts_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2687825"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2687833"></a>9.1. cat</h3></div></div></div>
+<p id="ch4strings_dicts_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch4strings_dicts_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch4strings_dicts_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035417"></a>5.2.3. <span class="strong"><strong>get()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2c"></a><span class="strong"><strong>get()</strong></span> returns the <span class="emphasis"><em>value</em></span> for the <span class="emphasis"><em>key</em></span> passed as the argument and if the
-<span class="emphasis"><em>key</em></span> does not exist in the dictionary, it returns <span class="emphasis"><em>None</em></span>. Let us look at an
-example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.get('Saurav')
-None
-&gt;&gt;&gt; print dctcopy.get('Anil')
-Kumble</pre>
+<a name="id2687876"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch4strings_dicts_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
 </div>
-<div class="section" title="5.2.4. has_key()">
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2687915"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch4strings_dicts_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch4strings_dicts_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch4strings_dicts_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch4strings_dicts_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch4strings_dicts_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch4strings_dicts_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035455"></a>5.2.4. <span class="strong"><strong>has_key()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2d"></a>This method returns <span class="emphasis"><em>True</em></span> if the given <span class="emphasis"><em>key</em></span> is in the dictionary, else it returns
-<span class="emphasis"><em>False</em></span>.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dctcopy.has_key('Saurav')
-False
-&gt;&gt;&gt; dctcopy.has_key('Sachin')
-True</pre>
+<a name="id2687986"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch4strings_dicts_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
 </div>
-<div class="section" title="5.2.5. pop()">
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2688020"></a>9.2. more</h3></div></div></div>
+<p id="ch4strings_dicts_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2688039"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch4strings_dicts_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch4strings_dicts_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch4strings_dicts_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch4strings_dicts_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch4strings_dicts_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2688130"></a>9.3. less</h3></div></div></div>
+<p id="ch4strings_dicts_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035485"></a>5.2.5. <span class="strong"><strong>pop()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2e"></a>This method is used to retrieve the <span class="emphasis"><em>value</em></span> of a given <span class="emphasis"><em>key</em></span> and subsequently
-remove the <span class="emphasis"><em>key-value</em></span> pair from the dictionary. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.pop('Sachin')
-Tendulkar
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Rahul': 'Dravid'}</pre>
+<a name="id2688158"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch4strings_dicts_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch4strings_dicts_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch4strings_dicts_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2688213"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
 </div>
-<div class="section" title="5.2.6. popitem()">
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2688266"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035519"></a>5.2.6. <span class="strong"><strong>popitem()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2f"></a>This method randomly pops a <span class="emphasis"><em>key-value</em></span> pair from a dictionary and returns it.
-The <span class="emphasis"><em>key-value</em></span> pair returned is removed from the dictionary. Let us look at an
-example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.popitem()
-('Anil', 'Kumble')
-&gt;&gt;&gt; dctcopy
-{'Rahul': 'Dravid'}
-
-Note that the item chosen is completely random since dictionaries are unordered
-as mentioned earlier.</pre>
+<a name="id2688357"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2688372"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch4strings_dicts_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch4strings_dicts_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2688647"></a>10.1. man hier</h3></div></div></div>
+<p id="ch4strings_dicts_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2688663"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch4strings_dicts_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch4strings_dicts_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2688686"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2688695"></a>11.1. chmod</h3></div></div></div>
+<p id="ch4strings_dicts_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2688721"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch4strings_dicts_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch4strings_dicts_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
 </div>
-<div class="section" title="5.2.7. update()">
+<div class="section" title="11.1.2. Command line options">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="id3035555"></a>5.2.7. <span class="strong"><strong>update()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_30"></a>The <span class="strong"><strong>update()</strong></span> method updates the contents of one dictionary with the contents
-of another dictionary. For items with existing <span class="emphasis"><em>keys</em></span> their <span class="emphasis"><em>values</em></span> are updated,
-and the rest of the items are added. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dctcopy.update(dct)
-&gt;&gt;&gt; dct
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}</pre>
+<a name="id2688749"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch4strings_dicts_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch4strings_dicts_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2688786"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch4strings_dicts_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch4strings_dicts_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch4strings_dicts_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch4strings_dicts_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch4strings_dicts_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2689347"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch4strings_dicts_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch4strings_dicts_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch4strings_dicts_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2689390"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch4strings_dicts_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch4strings_dicts_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2689428"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch4strings_dicts_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch4strings_dicts_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
 </div>
 </div>
 </div>
 </div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2689472"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch4strings_dicts_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch4strings_dicts_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689508"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch4strings_dicts_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch4strings_dicts_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch4strings_dicts_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch4strings_dicts_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689576"></a>12.2. Piping</h3></div></div></div>
+<p id="ch4strings_dicts_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch4strings_dicts_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch4strings_dicts_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch4strings_dicts_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch4strings_dicts_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689638"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch4strings_dicts_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch4strings_dicts_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch4strings_dicts_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch4strings_dicts_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch4strings_dicts_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch4strings_dicts_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch4strings_dicts_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch4strings_dicts_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch4strings_dicts_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch4strings_dicts_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch4strings_dicts_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689846"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch4strings_dicts_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch4strings_dicts_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689880"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch4strings_dicts_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch4strings_dicts_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2689911"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2689920"></a>13.1. grep</h3></div></div></div>
+<p id="ch4strings_dicts_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2689951"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch4strings_dicts_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch4strings_dicts_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch4strings_dicts_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch4strings_dicts_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch4strings_dicts_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch4strings_dicts_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2690030"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch4strings_dicts_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch4strings_dicts_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch4strings_dicts_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2690110"></a>13.2. tr</h3></div></div></div>
+<p id="ch4strings_dicts_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch4strings_dicts_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch4strings_dicts_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch4strings_dicts_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch4strings_dicts_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch4strings_dicts_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch4strings_dicts_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch4strings_dicts_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch4strings_dicts_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch4strings_dicts_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch4strings_dicts_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch4strings_dicts_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2690261"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch4strings_dicts_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch4strings_dicts_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch4strings_dicts_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch4strings_dicts_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2690477"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch4strings_dicts_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch4strings_dicts_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch4strings_dicts_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2690554"></a>15. One Liners</h2></div></div></div>
+<p id="ch4strings_dicts_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch4strings_dicts_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch4strings_dicts_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch4strings_dicts_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch4strings_dicts_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch4strings_dicts_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch4strings_dicts_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch4strings_dicts_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch4strings_dicts_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch4strings_dicts_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch4strings_dicts_1d7"></a>Print the total number of input lines:</p>
+<p id="ch4strings_dicts_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch4strings_dicts_1d9"></a>Print the tenth input line:</p>
+<p id="ch4strings_dicts_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch4strings_dicts_1db"></a>Print the last field of every input line:</p>
+<p id="ch4strings_dicts_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch4strings_dicts_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch4strings_dicts_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch4strings_dicts_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch4strings_dicts_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch4strings_dicts_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
 </div></body>
 </html>
--- a/web/html/ch4strings_dicts.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,465 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 4. strings_dicts</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch4strings_dicts">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2983496">Strings</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2982083">1. String Formatting</a></span></dt>
-<dt><span class="section"><a href="#id3034500">2. String Methods</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3034515">2.1. <span class="strong"><strong>find</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034545">2.2. <span class="strong"><strong>join</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034585">2.3. <span class="strong"><strong>lower</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034615">2.4. <span class="strong"><strong>replace</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034672">2.5. <span class="strong"><strong>split</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034731">2.6. <span class="strong"><strong>strip</strong></span></a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id3034775">3. Introduction to the standard library</a></span></dt>
-<dt><span class="section"><a href="#id3034853">4. I/O: Reading and Writing Files</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3034883">4.1. Opening Files</a></span></dt>
-<dt><span class="section"><a href="#id3035057">4.2. Reading and Writing files</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id3035222">5. Dictionaries</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3035278">5.1. <span class="strong"><strong>dict()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3035342">5.2. Dictionary Methods</a></span></dt>
-</dl></dd>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="Strings">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2983496"></a>Strings</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#id2982083">1. String Formatting</a></span></dt>
-<dt><span class="section"><a href="#id3034500">2. String Methods</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3034515">2.1. <span class="strong"><strong>find</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034545">2.2. <span class="strong"><strong>join</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034585">2.3. <span class="strong"><strong>lower</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034615">2.4. <span class="strong"><strong>replace</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034672">2.5. <span class="strong"><strong>split</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3034731">2.6. <span class="strong"><strong>strip</strong></span></a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id3034775">3. Introduction to the standard library</a></span></dt>
-<dt><span class="section"><a href="#id3034853">4. I/O: Reading and Writing Files</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3034883">4.1. Opening Files</a></span></dt>
-<dt><span class="section"><a href="#id3035057">4.2. Reading and Writing files</a></span></dt>
-</dl></dd>
-<dt><span class="section"><a href="#id3035222">5. Dictionaries</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id3035278">5.1. <span class="strong"><strong>dict()</strong></span></a></span></dt>
-<dt><span class="section"><a href="#id3035342">5.2. Dictionary Methods</a></span></dt>
-</dl></dd>
-</dl>
-</div>
-<p id="ch4strings_dicts_1"></a>Strings were briefly introduced previously in the introduction document. In this
-section strings will be presented in greater detail. All the standard operations
-that can be performed on sequences such as indexing, slicing, multiplication, length
-minimum and maximum can be performed on string variables as well. One thing to
-be noted is that strings are immutable, which means that string variables are
-unchangeable. Hence, all item and slice assignments on strings are illegal.
-Let us look at a few example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; name = 'PythonFreak'
-&gt;&gt;&gt; print name[3]
-h
-&gt;&gt;&gt; print name[-1]
-k
-&gt;&gt;&gt; print name[6:]
-Freak
-&gt;&gt;&gt; name[6:0] = 'Maniac'
-Traceback (most recent call last):
-  File "&lt;stdin&gt;", line 1, in &lt;module&gt;
-TypeError: 'str' object does not support item assignment</pre>
-<p id="ch4strings_dicts_2"></a>This is quite expected, since string objects are immutable as already mentioned.
-The error message is clear in mentioning that 'str' object does not support item
-assignment.</p>
-<div class="section" title="1. String Formatting">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2982083"></a>1. String Formatting</h2></div></div></div>
-<p id="ch4strings_dicts_3"></a>String formatting can be performed using the string formatting operator represented
-as the percent (%) sign. The string placed before the % sign is formatted with
-the value placed to the right of it. Let us look at a simple example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; format = 'Hello %s, from PythonFreak'
-&gt;&gt;&gt; str1 = 'world!'
-&gt;&gt;&gt; print format % str1
-Hello world!, from PythonFreak</pre>
-<p id="ch4strings_dicts_4"></a>The %s parts of the format string are called the coversion specifiers. The coversion
-specifiers mark the places where the formatting has to be performed in a string.
-In the example the %s is replaced by the value of str1. More than one value can
-also be formatted at a time by specifying the values to be formatted using tuples
-and dictionaries (explained in later sections). Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; format = 'Hello %s, from %s'
-&gt;&gt;&gt; values = ('world!', 'PythonFreak')
-&gt;&gt;&gt; print format % values
-Hello world!, from PythonFreak</pre>
-<p id="ch4strings_dicts_5"></a>In this example it can be observed that the format string contains two conversion
-specifiers and they are formatted using the tuple of values as shown.</p>
-<p id="ch4strings_dicts_6"></a>The s in %s specifies that the value to be replaced is of type string. Values of
-other types can be specified as well such as integers and floats. Integers are
-specified as %d and floats as %f. The precision with which the integer or the
-float values are to be represented can also be specified using a <span class="strong"><strong>.</strong></span> (<span class="strong"><strong>dot</strong></span>)
-followed by the precision value.</p>
-</div>
-<div class="section" title="2. String Methods">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034500"></a>2. String Methods</h2></div></div></div>
-<p id="ch4strings_dicts_7"></a>Similar to list methods, strings also have a rich set of methods to perform various
-operations on strings. Some of the most important and popular ones are presented
-in this section.</p>
-<div class="section" title="2.1. find">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034515"></a>2.1. <span class="strong"><strong>find</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_8"></a>The <span class="strong"><strong>find</strong></span> method is used to search for a substring within a given string. It
-returns the left most index of the first occurence of the substring. If the
-substring is not found in the string then it returns -1. Let us look at a few
-examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; longstring = 'Hello world!, from PythonFreak'
-&gt;&gt;&gt; longstring.find('Python')
-19
-&gt;&gt;&gt; longstring.find('Perl')
--1</pre>
-</div>
-<div class="section" title="2.2. join">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034545"></a>2.2. <span class="strong"><strong>join</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_9"></a>The <span class="strong"><strong>join</strong></span> method is used to join the elements of a sequence. The sequence
-elements that are to be join ed should all be strings. Let us look at a few
-examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; seq = ['With', 'great', 'power', 'comes', 'great', 'responsibility']
-&gt;&gt;&gt; sep = ' '
-&gt;&gt;&gt; sep.join(seq)
-'With great power comes great responsibility'
-&gt;&gt;&gt; sep = ',!'
-&gt;&gt;&gt; sep.join(seq)
-'With,!great,!power,!comes,!great,!responsibility'</pre>
-<p id="ch4strings_dicts_a"></a><span class="emphasis"><em>Try this yourself</em></span></p>
-<pre class="programlisting"> &gt;&gt;&gt; seq = [12,34,56,78]
-&gt;&gt;&gt; sep.join(seq)</pre>
-</div>
-<div class="section" title="2.3. lower">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034585"></a>2.3. <span class="strong"><strong>lower</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_b"></a>The <span class="strong"><strong>lower</strong></span> method, as the name indicates, converts the entire text of a string
-to lower case. It is specially useful in cases where the programmers deal with case
-insensitive data. Let us look at a few examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; sometext = 'Hello world!, from PythonFreak'
-&gt;&gt;&gt; sometext.lower()
-'hello world!, from pythonfreak'</pre>
-</div>
-<div class="section" title="2.4. replace">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034615"></a>2.4. <span class="strong"><strong>replace</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_c"></a>The <span class="strong"><strong>replace</strong></span> method replaces a substring with another substring within
-a given string and returns the new string. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; sometext = 'Concise, precise and criticise is some of the words that end with ise'
-&gt;&gt;&gt; sometext.replace('is', 'are')
-'Concaree, precaree and criticaree are some of the words that end with aree'</pre>
-<p id="ch4strings_dicts_d"></a>Observe here that all the occurences of the substring <span class="emphasis"><em>is</em></span> have been replaced,
-even the <span class="emphasis"><em>is</em></span> in <span class="emphasis"><em>concise</em></span>, <span class="emphasis"><em>precise</em></span> and <span class="emphasis"><em>criticise</em></span> have been replaced.</p>
-</div>
-<div class="section" title="2.5. split">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034672"></a>2.5. <span class="strong"><strong>split</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_e"></a>The <span class="strong"><strong>split</strong></span> is one of the very important string methods. split is the opposite of the
-<span class="strong"><strong>join</strong></span> method. It is used to split a string based on the argument passed as the
-delimiter. It returns a list of strings. By default when no argument is passed it
-splits with <span class="emphasis"><em>space</em></span> (' ') as the delimiter. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; grocerylist = 'butter, cucumber, beer(a grocery item??), wheatbread'
-&gt;&gt;&gt; grocerylist.split(',')
-['butter', ' cucumber', ' beer(a grocery item??)', ' wheatbread']
-&gt;&gt;&gt; grocerylist.split()
-['butter,', 'cucumber,', 'beer(a', 'grocery', 'item??),', 'wheatbread']</pre>
-<p id="ch4strings_dicts_f"></a>Observe here that in the second case when the delimiter argument was not set
-<span class="strong"><strong>split</strong></span> was done with <span class="emphasis"><em>space</em></span> as the delimiter.</p>
-</div>
-<div class="section" title="2.6. strip">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034731"></a>2.6. <span class="strong"><strong>strip</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_10"></a>The <span class="strong"><strong>strip</strong></span> method is used to remove or <span class="strong"><strong>strip</strong></span> off any whitespaces that exist
-to the left and right of a string, but not the whitespaces within a string. Let
-us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; spacedtext = "               Where's the text??                 "
-&gt;&gt;&gt; spacedtext.strip()
-"Where's the text??"</pre>
-<p id="ch4strings_dicts_11"></a>Observe that the whitespaces between the words have not been removed.</p>
-<pre class="programlisting"> Note: Very important thing to note is that all the methods shown above do not
-      transform the source string. The source string still remains the same.
-      Remember that **strings are immutable**.</pre>
-</div>
-</div>
-<div class="section" title="3. Introduction to the standard library">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034775"></a>3. Introduction to the standard library</h2></div></div></div>
-<p id="ch4strings_dicts_12"></a>Python is often referred to as a "Batteries included!" language, mainly because
-of the Python Standard Library. The Python Standard Library provides an extensive
-set of features some of which are available directly for use while some require to
-import a few <span class="strong"><strong>modules</strong></span>. The Standard Library provides various built-in functions
-like:</p>
-<span style="color: black"><span style="color: black"><span style="color: black"><p id="ch4strings_dicts_13"></a><span class="strong"><strong>abs()</strong></span></p></span><span style="color: black"><p id="ch4strings_dicts_14"></a><span class="strong"><strong>dict()</strong></span></p></span><span style="color: black"><p id="ch4strings_dicts_15"></a><span class="strong"><strong>enumerate()</strong></span></p></span></span></span><p id="ch4strings_dicts_16"></a>The built-in constants like <span class="strong"><strong>True</strong></span> and <span class="strong"><strong>False</strong></span> are provided by the Standard Library.
-More information about the Python Standard Library is available </p>
-<div class="reference">
-<div class="titlepage"><hr></div>http://docs.python.org/library/</div>
-</div>
-<div class="section" title="4. I/O: Reading and Writing Files">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3034853"></a>4. I/O: Reading and Writing Files</h2></div></div></div>
-<p id="ch4strings_dicts_17"></a>Files are very important aspects when it comes to computing and programming.
-Up until now the focus has been on small programs that interacted with users
-through <span class="strong"><strong>input()</strong></span> and <span class="strong"><strong>raw_input()</strong></span>. Generally, for computational purposes
-it becomes necessary to handle files, which are usually large in size as well.
-This section focuses on basics of file handling.</p>
-<div class="section" title="4.1. Opening Files">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3034883"></a>4.1. Opening Files</h3></div></div></div>
-<p id="ch4strings_dicts_18"></a>Files can be opened using the <span class="strong"><strong>open()</strong></span> method. <span class="strong"><strong>open()</strong></span> accepts 3 arguments
-out of which 2 are optional. Let us look at the syntax of <span class="strong"><strong>open()</strong></span>:</p>
-<p id="ch4strings_dicts_19"></a><span class="emphasis"><em>f = open( filename, mode, buffering)</em></span></p>
-<p id="ch4strings_dicts_1a"></a>The <span class="emphasis"><em>filename</em></span> is a compulsory argument while the <span class="emphasis"><em>mode</em></span> and <span class="emphasis"><em>buffering</em></span> are
-optional. The <span class="emphasis"><em>filename</em></span> should be a string and it should be the complete path
-to the file to be opened (The path can be absolute or relative). Let us look at
-an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('basic_python/interim_assessment.rst')</pre>
-<p id="ch4strings_dicts_1b"></a>The <span class="emphasis"><em>mode</em></span> argument specifies the mode in which the file has to be opened.
-The following are the valid mode arguments:</p>
-<p id="ch4strings_dicts_1c"></a><span class="strong"><strong>r</strong></span> - Read mode
-<span class="strong"><strong>w</strong></span> - Write mode
-<span class="strong"><strong>a</strong></span> - Append mode
-<span class="strong"><strong>b</strong></span> - Binary mode
-<span class="strong"><strong>+</strong></span> - Read/Write mode</p>
-<p id="ch4strings_dicts_1d"></a>The read mode opens the file as a read-only document. The write mode opens the
-file in the Write only mode. In the write mode, if the file existed prior to the
-opening, the previous contents of the file are erased. The append mode opens the
-file in the write mode but the previous contents of the file are not erased and
-the current data is appended onto the file.
-The binary and the read/write modes are special in the sense that they are added
-onto other modes. The read/write mode opens the file in the reading and writing
-mode combined. The binary mode can be used to open a files that do not contain
-text. Binary files such as images should be opened in the binary mode. Let us look
-at a few examples.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('basic_python/interim_assessment.rst', 'r')
-&gt;&gt;&gt; f = open ('armstrong.py', 'r+')</pre>
-<p id="ch4strings_dicts_1e"></a>The third argument to the <span class="strong"><strong>open()</strong></span> method is the <span class="emphasis"><em>buffering</em></span> argument. This takes
-a boolean value, <span class="emphasis"><em>True</em></span> or <span class="emphasis"><em>1</em></span> indicates that buffering has to be enabled on the file,
-that is the file is loaded on to the main memory and the changes made to the file are
-not immediately written to the disk. If the <span class="emphasis"><em>buffering</em></span> argument is <span class="emphasis"><em>0</em></span> or <span class="emphasis"><em>False</em></span> the
-changes are directly written on to the disk immediately.</p>
-</div>
-<div class="section" title="4.2. Reading and Writing files">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3035057"></a>4.2. Reading and Writing files</h3></div></div></div>
-<div class="section" title="4.2.1. write()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035066"></a>4.2.1. <span class="strong"><strong>write()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_1f"></a><span class="strong"><strong>write()</strong></span>, evidently, is used to write data onto a file. It takes the data to
-be written as the argument. The data can be a string, an integer, a float or any
-other datatype. In order to be able to write data onto a file, the file has to
-be opened in one of <span class="strong"><strong>w</strong></span>, <span class="strong"><strong>a</strong></span> or <span class="strong"><strong>+</strong></span> modes.</p>
-</div>
-<div class="section" title="4.2.2. read()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035105"></a>4.2.2. <span class="strong"><strong>read()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_20"></a><span class="strong"><strong>read()</strong></span> is used to read data from a file. It takes the number of bytes of data
-to be read as the argument. If nothing is specified by default it reads the entire
-contents from the current position to the end of file.</p>
-<p id="ch4strings_dicts_21"></a>Let us look at a few examples:</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open ('randomtextfile', 'w')
-&gt;&gt;&gt; f.write('Hello all, this is PythonFreak. This is a random text file.')
-&gt;&gt;&gt; f = open ('../randomtextfile', 'r')
-&gt;&gt;&gt; f = open ('../randomtextfile', 'r')
-&gt;&gt;&gt; f.read(5)
-'Hello'
-&gt;&gt;&gt; f.read()
-' all, this is PythonFreak. This is a random text file.'
-&gt;&gt;&gt; f.close()</pre>
-</div>
-<div class="section" title="4.2.3. readline()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035140"></a>4.2.3. <span class="strong"><strong>readline()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_22"></a><span class="strong"><strong>readline()</strong></span> is used to read a file line by line. <span class="strong"><strong>readline()</strong></span> reads a line
-of a file at a time. When an argument is passed to <span class="strong"><strong>readline()</strong></span> it reads that
-many bytes from the current line.</p>
-<p id="ch4strings_dicts_23"></a>One other method to read a file line by line is using the <span class="strong"><strong>read()</strong></span> and the
-<span class="strong"><strong>for</strong></span> construct. Let us look at this block of code as an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; f = open('../randomtextfile', 'r')
-&gt;&gt;&gt; for line in f:
-...     print line
-...
-Hello all!
-
-This is PythonFreak on the second line.
-
-This is a random text file on line 3</pre>
-</div>
-<div class="section" title="4.2.4. close()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035199"></a>4.2.4. <span class="strong"><strong>close()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_24"></a>One must always close all the files that have been opened. Although, files opened
-will be closed automatically when the program ends. When files opened in read mode
-are not closed it might lead to uselessly locked sometimes. In case of files
-opened in the write mode it is more important to close the files. This is because,
-Python maybe using the file in the buffering mode and when the file is not closed
-the buffer maybe lost completely and the changes made to the file are lost forever.</p>
-</div>
-</div>
-</div>
-<div class="section" title="5. Dictionaries">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id3035222"></a>5. Dictionaries</h2></div></div></div>
-<p id="ch4strings_dicts_25"></a>A dictionary in general, are designed to be able to look up meanings of words.
-Similarly, the Python dictionaries are also designed to look up for a specific
-key and retrieve the corresponding value. Dictionaries are data structures that
-provide key-value mappings. Dictionaries are similar to lists except that instead
-of the values having integer indexes, dictionaries have keys or strings as indexes.
-Let us look at an example of how to define dictionaries.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct = { 'Sachin': 'Tendulkar', 'Rahul': 'Dravid', 'Anil': 'Kumble'}</pre>
-<p id="ch4strings_dicts_26"></a>The dictionary consists of pairs of strings, which are called <span class="emphasis"><em>keys</em></span> and their
-corresponding <span class="emphasis"><em>values</em></span> separated by <span class="emphasis"><em>:</em></span> and each of these <span class="emphasis"><em>key-value</em></span> pairs are
-comma(',') separated and the entire structure wrapped in a pair curly braces <span class="emphasis"><em>{}</em></span>.</p>
-<pre class="programlisting"> Note: The data inside a dictionary is not ordered. The order in which you enter
-the key-value pairs is not the order in which they are stored in the dictionary.
-Python has an internal storage mechanism for that which is out of the purview
-of this document.</pre>
-<div class="section" title="5.1. dict()">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3035278"></a>5.1. <span class="strong"><strong>dict()</strong></span>
-</h3></div></div></div>
-<p id="ch4strings_dicts_27"></a>The <span class="strong"><strong>dict()</strong></span> function is used to create dictionaries from other mappings or other
-dictionaries. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; diction = dict(mat = 133, avg = 52.53)</pre>
-<p id="ch4strings_dicts_28"></a><span class="strong"><strong>String Formatting with Dictionaries:</strong></span></p>
-<p id="ch4strings_dicts_29"></a>String formatting was discussed in the previous section and it was mentioned that
-dictionaries can also be used for formatting more than one value. This section
-focuses on the formatting of strings using dictionaries. String formatting using
-dictionaries is more appealing than doing the same with tuples. Here the <span class="emphasis"><em>keyword</em></span>
-can be used as a place holder and the <span class="emphasis"><em>value</em></span> corresponding to it is replaced in
-the formatted string. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; player = { 'Name':'Rahul Dravid', 'Matches':133, 'Avg':52.53, '100s':26 }
-&gt;&gt;&gt; strng = '%(Name)s has played %(Matches)d with an average of %(Avg).2f and has %(100s)d hundreds to his name.'
-&gt;&gt;&gt; print strng % player
-Rahul Dravid has played 133 with an average of 52.53 and has 26 hundreds to his name.</pre>
-</div>
-<div class="section" title="5.2. Dictionary Methods">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id3035342"></a>5.2. Dictionary Methods</h3></div></div></div>
-<div class="section" title="5.2.1. clear()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035351"></a>5.2.1. <span class="strong"><strong>clear()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2a"></a>The <span class="strong"><strong>clear()</strong></span> method removes all the existing <span class="emphasis"><em>key-value</em></span> pairs from a dictionary.
-It returns <span class="emphasis"><em>None</em></span> or rather does not return anything. It is a method that changes
-the object. It has to be noted here that dictionaries are not immutable. Let us
-look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dct.clear()
-&gt;&gt;&gt; dct
-{}</pre>
-</div>
-<div class="section" title="5.2.2. copy()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035386"></a>5.2.2. <span class="strong"><strong>copy()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2b"></a>The <span class="strong"><strong>copy()</strong></span> returns a copy of a given dictionary. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dct = {'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dctcopy = dct.copy()
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}</pre>
-</div>
-<div class="section" title="5.2.3. get()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035417"></a>5.2.3. <span class="strong"><strong>get()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2c"></a><span class="strong"><strong>get()</strong></span> returns the <span class="emphasis"><em>value</em></span> for the <span class="emphasis"><em>key</em></span> passed as the argument and if the
-<span class="emphasis"><em>key</em></span> does not exist in the dictionary, it returns <span class="emphasis"><em>None</em></span>. Let us look at an
-example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.get('Saurav')
-None
-&gt;&gt;&gt; print dctcopy.get('Anil')
-Kumble</pre>
-</div>
-<div class="section" title="5.2.4. has_key()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035455"></a>5.2.4. <span class="strong"><strong>has_key()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2d"></a>This method returns <span class="emphasis"><em>True</em></span> if the given <span class="emphasis"><em>key</em></span> is in the dictionary, else it returns
-<span class="emphasis"><em>False</em></span>.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dctcopy.has_key('Saurav')
-False
-&gt;&gt;&gt; dctcopy.has_key('Sachin')
-True</pre>
-</div>
-<div class="section" title="5.2.5. pop()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035485"></a>5.2.5. <span class="strong"><strong>pop()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2e"></a>This method is used to retrieve the <span class="emphasis"><em>value</em></span> of a given <span class="emphasis"><em>key</em></span> and subsequently
-remove the <span class="emphasis"><em>key-value</em></span> pair from the dictionary. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.pop('Sachin')
-Tendulkar
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Rahul': 'Dravid'}</pre>
-</div>
-<div class="section" title="5.2.6. popitem()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035519"></a>5.2.6. <span class="strong"><strong>popitem()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_2f"></a>This method randomly pops a <span class="emphasis"><em>key-value</em></span> pair from a dictionary and returns it.
-The <span class="emphasis"><em>key-value</em></span> pair returned is removed from the dictionary. Let us look at an
-example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; print dctcopy.popitem()
-('Anil', 'Kumble')
-&gt;&gt;&gt; dctcopy
-{'Rahul': 'Dravid'}
-
-Note that the item chosen is completely random since dictionaries are unordered
-as mentioned earlier.</pre>
-</div>
-<div class="section" title="5.2.7. update()">
-<div class="titlepage"><div><div><h4 class="title">
-<a name="id3035555"></a>5.2.7. <span class="strong"><strong>update()</strong></span>
-</h4></div></div></div>
-<p id="ch4strings_dicts_30"></a>The <span class="strong"><strong>update()</strong></span> method updates the contents of one dictionary with the contents
-of another dictionary. For items with existing <span class="emphasis"><em>keys</em></span> their <span class="emphasis"><em>values</em></span> are updated,
-and the rest of the items are added. Let us look at an example.</p>
-<pre class="programlisting"> &gt;&gt;&gt; dctcopy.update(dct)
-&gt;&gt;&gt; dct
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}
-&gt;&gt;&gt; dctcopy
-{'Anil': 'Kumble', 'Sachin': 'Tendulkar', 'Rahul': 'Dravid'}</pre>
-</div>
-</div>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch5func.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch5func.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,341 +1,1137 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 5. Functions </title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
+<title>Functions</title>
 <link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
 <script type="text/javascript" src="/review/support/hsbook.js"></script>
 <meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch5func">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch5func ">
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="article"><a href="#id2436407">Functional Approach</a></span></dt>
+<dt><span class="article"><a href="#id2679232"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2489356">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2677051">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2730291">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2730555">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730682">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2730690">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2730962">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730971">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2731128">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2731186">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2731284">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2731364">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2731537">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2731546">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2731626">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2731830">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2731920">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2731974">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2731982">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2732293">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2730087">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2732733">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2732826">7. Basic Text Processing</a></span></dt>
 <dd><dl>
-<dt><span class="section"><a href="#id2487445">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2487503">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487542">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487658">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2487758">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2487811">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2488001">6.1. List Comprehensions</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2732834">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2732922">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2733049">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2733135">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2733270">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2733377">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2733385">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2733573">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2733687">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2733925">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2734190">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2734206">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2734228">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2734237">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2734996">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2735033">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2735102">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2735162">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2735363">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2735397">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2735427">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2735436">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2735624">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2735772">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2735981">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2736057">15. One Liners</a></span></dt>
 </dl></dd>
 </dl>
 </div>
-<div class="article" title="Functional Approach">
+<div class="article">
 <div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2436407"></a>Functional Approach</h2></div></div>
+<div><div><h2 class="title" id="id2679232"></a></h2></div></div>
 <hr>
 </div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
 <dl>
-<dt><span class="section"><a href="#id2487445">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2487503">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487542">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487658">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2487758">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2487811">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2488001">6.1. List Comprehensions</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2489356">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2677051">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2730291">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2730555">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730682">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2730690">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2730962">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730971">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2731128">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2731186">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2731284">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2731364">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2731537">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2731546">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2731626">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2731830">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2731920">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2731974">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2731982">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2732293">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2730087">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2732733">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2732826">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2732834">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2732922">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2733049">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2733135">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2733270">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2733377">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2733385">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2733573">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2733687">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2733925">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2734190">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2734206">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2734228">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2734237">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2734996">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2735033">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2735102">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2735162">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2735363">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2735397">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2735427">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2735436">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2735624">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2735772">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2735981">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2736057">15. One Liners</a></span></dt>
 </dl>
 </div>
-<p id="ch5func_1"></a><span class="emphasis"><em>Functions</em></span> allow us to enclose a set of statements and call the function again
-and again instead of repeating the group of statements everytime. Functions also
-allow us to isolate a piece of code from all the other code and provides the
-convenience of not polluting the global variables.</p>
-<p id="ch5func_2"></a><span class="emphasis"><em>Function</em></span> in python is defined with the keyword <span class="strong"><strong>def</strong></span> followed by the name
-of the function, in turn followed by a pair of parenthesis which encloses the
-list of parameters to the function. The definition line ends with a ':'. The
-definition line is followed by the body of the function intended by one block.
-The <span class="emphasis"><em>Function</em></span> must return a value:</p>
-<pre class="programlisting"> def factorial(n):
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p id="ch5func_3"></a>The code snippet above defines a function with the name factorial, takes the
-number for which the factorial must be computed, computes the factorial and
-returns the value.</p>
-<p id="ch5func_4"></a>A <span class="emphasis"><em>Function</em></span> once defined can be used or called anywhere else in the program. We
-call a fucntion with its name followed by a pair of parenthesis which encloses
-the arguments to the function.</p>
-<p id="ch5func_5"></a>The value that function returns can be assigned to a variable. Let's call the
-above function and store the factorial in a variable:</p>
-<pre class="programlisting"> fact5 = factorial(5)</pre>
-<p id="ch5func_6"></a>The value of fact5 will now be 120, which is the factorial of 5. Note that we
-passed 5 as the argument to the function.</p>
-<p id="ch5func_7"></a>It may be necessary to document what the function does, for each of the function
-to help the person who reads our code to understand it better. In order to do
-this Python allows the first line of the function body to be a string. This
-string is called as <span class="emphasis"><em>Documentation String</em></span> or <span class="emphasis"><em>docstring</em></span>. <span class="emphasis"><em>docstrings</em></span> prove
-to be very handy since there are number of tools which can pull out all the
-docstrings from Python functions and generate the documentation automatically
-from it. <span class="emphasis"><em>docstrings</em></span> for functions can be written as follows:</p>
-<pre class="programlisting"> def factorial(n):
-  'Returns the factorial for the number n.'
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p id="ch5func_8"></a>An important point to note at this point is that, a function can return any
-Python value or a Python object, which also includes a <span class="emphasis"><em>Tuple</em></span>. A <span class="emphasis"><em>Tuple</em></span> is
-just a collection of values and those values themselves can be of any other
-valid Python datatypes, including <span class="emphasis"><em>Lists</em></span>, <span class="emphasis"><em>Tuples</em></span>, <span class="emphasis"><em>Dictionaries</em></span> among other
-things. So effectively, if a function can return a tuple, it can return any
-number of values through a tuple</p>
-<p id="ch5func_9"></a>Let us write a small function to swap two values:</p>
-<pre class="programlisting"> def swap(a, b):
-  return b, a
-
-c, d = swap(a, b)</pre>
-<div class="section" title="1. Function scope">
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2489356"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch5func_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch5func_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch5func_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch5func_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2677051"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2676925"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730246"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch5func_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch5func_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730291"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch5func_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730315"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch5func_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch5func_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730367"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch5func_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch5func_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch5func_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730422"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch5func_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch5func_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch5func_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730466"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch5func_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730511"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch5func_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch5func_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch5func_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730555"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch5func_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch5func_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch5func_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch5func_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch5func_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch5func_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2730682"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730690"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch5func_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730720"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch5func_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch5func_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch5func_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch5func_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch5func_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch5func_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch5func_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch5func_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch5func_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730875"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch5func_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch5func_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch5func_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch5func_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch5func_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487445"></a>1. Function scope</h2></div></div></div>
-<p id="ch5func_a"></a>The variables used inside the function are confined to the function's scope
-and doesn't pollute the variables of the same name outside the scope of the
-function. Also the arguments passed to the function are passed by-value if
-it is of basic Python data type:</p>
-<pre class="programlisting"> def cant_change(n):
-  n = 10
-
-n = 5
-cant_change(n)</pre>
-<p id="ch5func_b"></a>Upon running this code, what do you think would have happened to value of n
-which was assigned 5 before the function call? If you have already tried out
-that snippet on the interpreter you already know that the value of n is not
-changed. This is true of any immutable types of Python like <span class="emphasis"><em>Numbers</em></span>, <span class="emphasis"><em>Strings</em></span>
-and <span class="emphasis"><em>Tuples</em></span>. But when you pass mutable objects like <span class="emphasis"><em>Lists</em></span> and <span class="emphasis"><em>Dictionaries</em></span>
-the values are manipulated even outside the function:</p>
-<pre class="programlisting"> &gt;&gt;&gt; def can_change(n):
-...   n[1] = James
-...
-
-&gt;&gt;&gt; name = ['Mr.', 'Steve', 'Gosling']
-&gt;&gt;&gt; can_change(name)
-&gt;&gt;&gt; name
-['Mr.', 'James', 'Gosling']</pre>
-<p id="ch5func_c"></a>If nothing is returned by the function explicitly, Python takes care to return
-None when the funnction is called.</p>
+<a name="id2730962"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730971"></a>3.1. ls</h3></div></div></div>
+<p id="ch5func_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch5func_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch5func_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch5func_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch5func_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731128"></a>3.2. date</h3></div></div></div>
+<p id="ch5func_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch5func_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch5func_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch5func_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch5func_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
 </div>
-<div class="section" title="2. Default Arguments">
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731186"></a>3.3. cd</h3></div></div></div>
+<p id="ch5func_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch5func_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch5func_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch5func_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch5func_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch5func_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch5func_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch5func_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch5func_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch5func_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch5func_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch5func_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731284"></a>3.4. who</h3></div></div></div>
+<p id="ch5func_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch5func_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch5func_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch5func_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch5func_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731364"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch5func_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch5func_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2731395"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch5func_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch5func_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2731454"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch5func_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch5func_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch5func_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch5func_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch5func_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487503"></a>2. Default Arguments</h2></div></div></div>
-<p id="ch5func_d"></a>There may be situations where we need to allow the functions to take the
-arguments optionally. Python allows us to define function this way by providing
-a facility called <span class="emphasis"><em>Default Arguments</em></span>. For example, we need to write a function
-that returns a list of fibonacci numbers. Since our function cannot generate an
-infinite list of fibonacci numbers, we need to specify the number of elements
-that the fibonacci sequence must contain. Suppose, additionally, we want to the
-function to return 10 numbers in the sequence if no option is specified we can
-define the function as follows:</p>
-<pre class="programlisting"> def fib(n=10):
-  fib_list = [0, 1]
-  for i in range(n - 2):
-    next = fib_list[-2] + fib_list[-1]
-    fib_list.append(next)
-  return fib_list</pre>
-<p id="ch5func_e"></a>When we call this function, we can optionally specify the value for the
-parameter n, during the call as an argument. Calling with no argument and
-argument with n=5 returns the following fibonacci sequences:</p>
-<pre class="programlisting"> fib()
-[0, 1, 1, 2, 3, 5, 8, 13, 21, 34]
-fib(5)
-[0, 1, 1, 2, 3]</pre>
+<a name="id2731537"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731546"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch5func_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch5func_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch5func_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch5func_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch5func_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
 </div>
-<div class="section" title="3. Keyword Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487542"></a>3. Keyword Arguments</h2></div></div></div>
-<p id="ch5func_f"></a>When a function takes a large number of arguments, it may be difficult to
-remember the order of the parameters in the function definition or it may
-be necessary to pass values to only certain parameters since others take
-the default value. In either of these cases, Python provides the facility
-of passing arguments by specifying the name of the parameter as defined in
-the function definition. This is known as <span class="emphasis"><em>Keyword Arguments</em></span>.</p>
-<p id="ch5func_10"></a>In a function call, <span class="emphasis"><em>Keyword arguments</em></span> can be used for each argument, in the
-following fashion:</p>
-<pre class="programlisting"> argument_name=argument_value
-Also denoted as: keyword=argument
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731626"></a>4.2. man</h3></div></div></div>
+<p id="ch5func_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch5func_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch5func_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch5func_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch5func_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch5func_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2731706"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch5func_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch5func_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch5func_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch5func_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch5func_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch5func_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch5func_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch5func_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch5func_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch5func_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch5func_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch5func_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731830"></a>4.3. info</h3></div></div></div>
+<p id="ch5func_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch5func_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch5func_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch5func_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731920"></a>4.4. --help</h3></div></div></div>
+<p id="ch5func_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
 
-def wish(name='World', greetings='Hello'):
-  print "%s, %s!" % (greetings, name)</pre>
-<p id="ch5func_11"></a>This function can be called in one of the following ways. It is important to
-note that no restriction is imposed in the order in which <span class="emphasis"><em>Keyword arguments</em></span>
-can be specified. Also note, that we have combined <span class="emphasis"><em>Keyword arguments</em></span> with
-<span class="emphasis"><em>Default arguments</em></span> in this example, however it is not necessary:</p>
-<pre class="programlisting"> wish(name='Guido', greetings='Hey')
-wish(greetings='Hey', name='Guido')</pre>
-<p id="ch5func_12"></a>Calling functions by specifying arguments in the order of parameters specified
-in the function definition is called as <span class="emphasis"><em>Positional arguments</em></span>, as opposed to
-<span class="emphasis"><em>Keyword arguments</em></span>. It is possible to use both <span class="emphasis"><em>Positional arguments</em></span> and
-<span class="emphasis"><em>Keyword arguments</em></span> in a single function call. But Python doesn't allow us to
-bungle up both of them. The arguments to the function, in the call, must always
-start with <span class="emphasis"><em>Positional arguments</em></span> which is in turn followed by <span class="emphasis"><em>Keyword
-arguments</em></span>:</p>
-<pre class="programlisting"> def my_func(x, y, z, u, v, w):
-  # initialize variables.
-  ...
-  # do some stuff
-  ...
-  # return the value</pre>
-<p id="ch5func_13"></a>It is valid to call the above functions in the following ways:</p>
-<pre class="programlisting"> my_func(10, 20, 30, u=1.0, v=2.0, w=3.0)
-my_func(10, 20, 30, 1.0, 2.0, w=3.0)
-my_func(10, 20, z=30, u=1.0, v=2.0, w=3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, w=3.0)</pre>
-<p id="ch5func_14"></a>Following lists some of the invalid calls:</p>
-<pre class="programlisting"> my_func(10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, 3.0)</pre>
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2731974"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731982"></a>5.1. cp</h3></div></div></div>
+<p id="ch5func_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732000"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch5func_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch5func_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch5func_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732034"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch5func_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch5func_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch5func_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch5func_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch5func_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732132"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch5func_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch5func_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch5func_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch5func_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch5func_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch5func_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch5func_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch5func_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch5func_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch5func_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch5func_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch5func_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch5func_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch5func_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch5func_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
 </div>
-<div class="section" title="4. Parameter Packing and Unpacking">
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2732293"></a>5.2. mv</h3></div></div></div>
+<p id="ch5func_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732317"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch5func_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732336"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch5func_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730028"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch5func_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch5func_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730087"></a>5.3. rm</h3></div></div></div>
+<p id="ch5func_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch5func_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730116"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch5func_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch5func_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch5func_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch5func_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch5func_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732693"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch5func_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch5func_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch5func_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2732733"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch5func_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch5func_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch5func_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch5func_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch5func_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch5func_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch5func_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487658"></a>4. Parameter Packing and Unpacking</h2></div></div></div>
-<p id="ch5func_15"></a>The positional arguments passed to a function can be collected in a tuple
-parameter and keyword arguments can be collected in a dictionary. Since keyword
-arguments must always be the last set of arguments passed to a function, the
-keyword dictionary parameter must be the last parameter. The function definition
-must include a list explicit parameters, followed by tuple paramter collecting
-parameter, whose name is preceded by a <span class="strong"><strong>*</strong></span>, for collecting positional
-parameters, in turn followed by the dictionary collecting parameter, whose name
-is preceded by a <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, *args, **name):
-  """Structure of *args*
-  (age, email-id)
-  Structure of *name*
-  {
-      'first': First Name
-      'middle': Middle Name
-      'last': Last Name
-  }
-  """
+<a name="id2732826"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2732834"></a>7.1. head</h3></div></div></div>
+<p id="ch5func_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch5func_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch5func_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch5func_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2732886"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch5func_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch5func_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch5func_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2732922"></a>7.2. tail</h3></div></div></div>
+<p id="ch5func_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch5func_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch5func_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch5func_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch5func_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch5func_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch5func_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733000"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch5func_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch5func_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch5func_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2733049"></a>7.3. cut</h3></div></div></div>
+<p id="ch5func_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch5func_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch5func_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch5func_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch5func_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch5func_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch5func_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2733135"></a>7.4. paste</h3></div></div></div>
+<p id="ch5func_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch5func_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch5func_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch5func_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2733270"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch5func_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch5func_df"></a>The shell meta characters include:</p>
+<p id="ch5func_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch5func_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch5func_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch5func_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch5func_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch5func_e5"></a>because the c* matches that long file name.</p>
+<p id="ch5func_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch5func_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch5func_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2733377"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2733385"></a>9.1. cat</h3></div></div></div>
+<p id="ch5func_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch5func_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch5func_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733428"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch5func_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
 
-  print "Title: %s" % (title)
-  print "Full name: %(first)s %(middle)s %(last)s" % name
-  print "Age: %d\nEmail-ID: %s" % args</pre>
-<p id="ch5func_16"></a>The above function can be called as. Note, the order of keyword parameters can
-be interchanged:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print_report('Employee Report', 29, 'johny@example.com', first='Johny',
-                 last='Charles', middle='Douglas')
-Title: Employee Report
-Full name: Johny Douglas Charles
-Age: 29
-Email-ID: johny@example.com</pre>
-<p id="ch5func_17"></a>The reverse of this can also be achieved by using a very identical syntax while
-calling the function. A tuple or a dictionary can be passed as arguments in
-place of a list of <span class="emphasis"><em>Positional arguments</em></span> or <span class="emphasis"><em>Keyword arguments</em></span> respectively
-using <span class="strong"><strong>*</strong></span> or <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, age, email, first, middle, last):
-  print "Title: %s" % (title)
-  print "Full name: %s %s %s" % (first, middle, last)
-  print "Age: %d\nEmail-ID: %s" % (age, email)
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
 
-&gt;&gt;&gt; args = (29, 'johny@example.com')
-&gt;&gt;&gt; name = {
-        'first': 'Johny',
-        'middle': 'Charles',
-        'last': 'Douglas'
-        }
-&gt;&gt;&gt; print_report('Employee Report', *args, **name)
-Title: Employee Report
-Full name: Johny Charles Douglas
-Age: 29
-Email-ID: johny@example.com</pre>
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733467"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch5func_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch5func_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch5func_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch5func_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch5func_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch5func_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733537"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch5func_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2733573"></a>9.2. more</h3></div></div></div>
+<p id="ch5func_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733593"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch5func_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch5func_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch5func_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch5func_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch5func_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2733687"></a>9.3. less</h3></div></div></div>
+<p id="ch5func_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733716"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch5func_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch5func_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch5func_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
 </div>
-<div class="section" title="5. Nested Functions and Scopes">
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733770"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733822"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2733910"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2733925"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch5func_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch5func_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2734190"></a>10.1. man hier</h3></div></div></div>
+<p id="ch5func_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2734206"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch5func_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch5func_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487758"></a>5. Nested Functions and Scopes</h2></div></div></div>
-<p id="ch5func_18"></a>Python allows nesting one function inside another. This style of programming
-turns out to be extremely flexible and powerful features when we use <span class="emphasis"><em>Python
-decorators</em></span>. We will not talk about decorators is beyond the scope of this
-course. If you are interested in knowing more about <span class="emphasis"><em>decorator programming</em></span> in
-Python you are suggested to read:</p>
-<span style="color: black">&lt;line_block&gt;<span style="color: black">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://avinashv.net/2008/04/python-decorators-syntactic-sugar/</div>&lt;/line&gt;</span><span style="color: black">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://personalpages.tds.net/~kent37/kk/00001.html</div>&lt;/line&gt;</span>&lt;/line_block&gt;</span><p id="ch5func_19"></a>However, the following is an example for nested functions in Python:</p>
-<pre class="programlisting"> def outer():
-  print "Outer..."
-  def inner():
-    print "Inner..."
-  print "Outer..."
-  inner()
-
-&gt;&gt;&gt; outer()</pre>
+<a name="id2734228"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2734237"></a>11.1. chmod</h3></div></div></div>
+<p id="ch5func_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2734263"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch5func_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch5func_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2734290"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch5func_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch5func_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch5func_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2734326"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch5func_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch5func_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch5func_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch5func_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch5func_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2734874"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch5func_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch5func_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch5func_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2734915"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch5func_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch5func_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2734953"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch5func_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch5func_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2734996"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch5func_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch5func_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735033"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch5func_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch5func_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch5func_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch5func_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
 </div>
-<div class="section" title="6. map, reduce and filter functions">
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735102"></a>12.2. Piping</h3></div></div></div>
+<p id="ch5func_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch5func_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch5func_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch5func_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch5func_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735162"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch5func_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch5func_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch5func_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch5func_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch5func_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch5func_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch5func_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch5func_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch5func_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch5func_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch5func_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735363"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch5func_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch5func_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735397"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch5func_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch5func_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487811"></a>6. map, reduce and filter functions</h2></div></div></div>
-<p id="ch5func_1a"></a>Python provides several built-in functions for convenience. The <span class="strong"><strong>map()</strong></span>,
-<span class="strong"><strong>reduce()</strong></span> and <span class="strong"><strong>filter()</strong></span> functions prove to be very useful with sequences like
-<span class="emphasis"><em>Lists</em></span>.</p>
-<p id="ch5func_1b"></a>The <span class="strong"><strong>map</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments: <span class="emphasis"><em>function</em></span>
-and a <span class="emphasis"><em>sequence</em></span> argument. The <span class="emphasis"><em>function</em></span> argument must be the name of the
-function which in turn takes a single argument, the individual element of the
-<span class="emphasis"><em>sequence</em></span>. The <span class="strong"><strong>map</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each item in the
-sequence and returns a list of values, where each value is the value returned
-by each call to <span class="emphasis"><em>function(item)</em></span>. <span class="strong"><strong>map()</strong></span> function allows to pass more than
-one sequence. In this case, the first argument, <span class="emphasis"><em>function</em></span> must take as many
-arguments as the number of sequences passed. This function is called with each
-corresponding element in the each of the sequences, or <span class="strong"><strong>None</strong></span> if one of the
-sequence is exhausted:</p>
-<pre class="programlisting"> def square(x):
-  return x*x
-
-&gt;&gt;&gt; map(square, [1, 2, 3, 4])
-[1, 4, 9, 16]
+<a name="id2735427"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735436"></a>13.1. grep</h3></div></div></div>
+<p id="ch5func_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2735467"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch5func_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch5func_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch5func_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch5func_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch5func_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch5func_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2735545"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch5func_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch5func_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch5func_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735624"></a>13.2. tr</h3></div></div></div>
+<p id="ch5func_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch5func_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch5func_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch5func_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch5func_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch5func_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch5func_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch5func_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch5func_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch5func_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch5func_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch5func_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2735772"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch5func_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch5func_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch5func_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch5func_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2735981"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch5func_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch5func_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch5func_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2736057"></a>15. One Liners</h2></div></div></div>
+<p id="ch5func_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch5func_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch5func_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch5func_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch5func_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch5func_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch5func_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch5func_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch5func_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch5func_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch5func_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch5func_1d7"></a>Print the total number of input lines:</p>
+<p id="ch5func_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch5func_1d9"></a>Print the tenth input line:</p>
+<p id="ch5func_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch5func_1db"></a>Print the last field of every input line:</p>
+<p id="ch5func_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch5func_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch5func_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch5func_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch5func_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
 
-def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; map(mul, [1, 2, 3, 4], [6, 7, 8, 9])</pre>
-<p id="ch5func_1c"></a>The <span class="strong"><strong>filter</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-the <span class="strong"><strong>map()</strong></span> function. The <span class="strong"><strong>filter</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each
-item in the sequence and returns all the elements in the sequence for which
-<span class="emphasis"><em>function(item)</em></span> returned True:</p>
-<pre class="programlisting"> def even(x):
-  if x % 2:
-    return True
-  else:
-    return False
-
-&gt;&gt;&gt; filter(even, range(1, 10))
-[1, 3, 5, 7, 9]</pre>
-<p id="ch5func_1d"></a>The <span class="strong"><strong>reduce</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-<span class="strong"><strong>map</strong></span> function, however multiple sequences are not allowed. The <span class="strong"><strong>reduce</strong></span>
-function calls <span class="emphasis"><em>function</em></span> with first two consecutive elements in the sequence,
-obtains the result, calls <span class="emphasis"><em>function</em></span> with the result and the subsequent element
-in the sequence and so on until the end of the list and returns the final result:</p>
-<pre class="programlisting"> def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; reduce(mul, [1, 2, 3, 4])
-24</pre>
-<div class="section" title="6.1. List Comprehensions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2488001"></a>6.1. List Comprehensions</h3></div></div></div>
-<p id="ch5func_1e"></a>List Comprehension is a convenvience utility provided by Python. It is a
-syntatic sugar to create <span class="emphasis"><em>Lists</em></span>. Using <span class="emphasis"><em>List Comprehensions</em></span> one can create
-<span class="emphasis"><em>Lists</em></span> from other type of sequential data structures or other <span class="emphasis"><em>Lists</em></span> itself.
-The syntax of <span class="emphasis"><em>List Comprehensions</em></span> consists of a square brackets to indicate
-the result is a <span class="emphasis"><em>List</em></span> within which we include at least one <span class="strong"><strong>for</strong></span> clause and
-multiple <span class="strong"><strong>if</strong></span> clauses. It will be more clear with an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; num = [1, 2, 3]
-&gt;&gt;&gt; sq = [x*x for x in num]
-&gt;&gt;&gt; sq
-[1, 4, 9]
-&gt;&gt;&gt; all_num = [1, 2, 3, 4, 5, 6, 7, 8, 9]
-&gt;&gt;&gt; even = [x for x in all_num if x%2 == 0]</pre>
-<p id="ch5func_1f"></a>The syntax used here is very clear from the way it is written. It can be
-translated into english as, "for each element x in the list all_num,
-if remainder of x divided by 2 is 0, add x to the list."</p>
-</div>
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch5func_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
 </div>
 </div>
 </div></body>
--- a/web/html/ch5func.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,342 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 5. Functions </title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch5func">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2436407">Functional Approach</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2487445">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2487503">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487542">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487658">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2487758">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2487811">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2488001">6.1. List Comprehensions</a></span></dt></dl></dd>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="Functional Approach">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2436407"></a>Functional Approach</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#id2487445">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2487503">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487542">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2487658">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2487758">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2487811">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2488001">6.1. List Comprehensions</a></span></dt></dl></dd>
-</dl>
-</div>
-<p id="ch5func_1"></a><span class="emphasis"><em>Functions</em></span> allow us to enclose a set of statements and call the function again
-and again instead of repeating the group of statements everytime. Functions also
-allow us to isolate a piece of code from all the other code and provides the
-convenience of not polluting the global variables.</p>
-<p id="ch5func_2"></a><span class="emphasis"><em>Function</em></span> in python is defined with the keyword <span class="strong"><strong>def</strong></span> followed by the name
-of the function, in turn followed by a pair of parenthesis which encloses the
-list of parameters to the function. The definition line ends with a ':'. The
-definition line is followed by the body of the function intended by one block.
-The <span class="emphasis"><em>Function</em></span> must return a value:</p>
-<pre class="programlisting"> def factorial(n):
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p id="ch5func_3"></a>The code snippet above defines a function with the name factorial, takes the
-number for which the factorial must be computed, computes the factorial and
-returns the value.</p>
-<p id="ch5func_4"></a>A <span class="emphasis"><em>Function</em></span> once defined can be used or called anywhere else in the program. We
-call a fucntion with its name followed by a pair of parenthesis which encloses
-the arguments to the function.</p>
-<p id="ch5func_5"></a>The value that function returns can be assigned to a variable. Let's call the
-above function and store the factorial in a variable:</p>
-<pre class="programlisting"> fact5 = factorial(5)</pre>
-<p id="ch5func_6"></a>The value of fact5 will now be 120, which is the factorial of 5. Note that we
-passed 5 as the argument to the function.</p>
-<p id="ch5func_7"></a>It may be necessary to document what the function does, for each of the function
-to help the person who reads our code to understand it better. In order to do
-this Python allows the first line of the function body to be a string. This
-string is called as <span class="emphasis"><em>Documentation String</em></span> or <span class="emphasis"><em>docstring</em></span>. <span class="emphasis"><em>docstrings</em></span> prove
-to be very handy since there are number of tools which can pull out all the
-docstrings from Python functions and generate the documentation automatically
-from it. <span class="emphasis"><em>docstrings</em></span> for functions can be written as follows:</p>
-<pre class="programlisting"> def factorial(n):
-  'Returns the factorial for the number n.'
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p id="ch5func_8"></a>An important point to note at this point is that, a function can return any
-Python value or a Python object, which also includes a <span class="emphasis"><em>Tuple</em></span>. A <span class="emphasis"><em>Tuple</em></span> is
-just a collection of values and those values themselves can be of any other
-valid Python datatypes, including <span class="emphasis"><em>Lists</em></span>, <span class="emphasis"><em>Tuples</em></span>, <span class="emphasis"><em>Dictionaries</em></span> among other
-things. So effectively, if a function can return a tuple, it can return any
-number of values through a tuple</p>
-<p id="ch5func_9"></a>Let us write a small function to swap two values:</p>
-<pre class="programlisting"> def swap(a, b):
-  return b, a
-
-c, d = swap(a, b)</pre>
-<div class="section" title="1. Function scope">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487445"></a>1. Function scope</h2></div></div></div>
-<p id="ch5func_a"></a>The variables used inside the function are confined to the function's scope
-and doesn't pollute the variables of the same name outside the scope of the
-function. Also the arguments passed to the function are passed by-value if
-it is of basic Python data type:</p>
-<pre class="programlisting"> def cant_change(n):
-  n = 10
-
-n = 5
-cant_change(n)</pre>
-<p id="ch5func_b"></a>Upon running this code, what do you think would have happened to value of n
-which was assigned 5 before the function call? If you have already tried out
-that snippet on the interpreter you already know that the value of n is not
-changed. This is true of any immutable types of Python like <span class="emphasis"><em>Numbers</em></span>, <span class="emphasis"><em>Strings</em></span>
-and <span class="emphasis"><em>Tuples</em></span>. But when you pass mutable objects like <span class="emphasis"><em>Lists</em></span> and <span class="emphasis"><em>Dictionaries</em></span>
-the values are manipulated even outside the function:</p>
-<pre class="programlisting"> &gt;&gt;&gt; def can_change(n):
-...   n[1] = James
-...
-
-&gt;&gt;&gt; name = ['Mr.', 'Steve', 'Gosling']
-&gt;&gt;&gt; can_change(name)
-&gt;&gt;&gt; name
-['Mr.', 'James', 'Gosling']</pre>
-<p id="ch5func_c"></a>If nothing is returned by the function explicitly, Python takes care to return
-None when the funnction is called.</p>
-</div>
-<div class="section" title="2. Default Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487503"></a>2. Default Arguments</h2></div></div></div>
-<p id="ch5func_d"></a>There may be situations where we need to allow the functions to take the
-arguments optionally. Python allows us to define function this way by providing
-a facility called <span class="emphasis"><em>Default Arguments</em></span>. For example, we need to write a function
-that returns a list of fibonacci numbers. Since our function cannot generate an
-infinite list of fibonacci numbers, we need to specify the number of elements
-that the fibonacci sequence must contain. Suppose, additionally, we want to the
-function to return 10 numbers in the sequence if no option is specified we can
-define the function as follows:</p>
-<pre class="programlisting"> def fib(n=10):
-  fib_list = [0, 1]
-  for i in range(n - 2):
-    next = fib_list[-2] + fib_list[-1]
-    fib_list.append(next)
-  return fib_list</pre>
-<p id="ch5func_e"></a>When we call this function, we can optionally specify the value for the
-parameter n, during the call as an argument. Calling with no argument and
-argument with n=5 returns the following fibonacci sequences:</p>
-<pre class="programlisting"> fib()
-[0, 1, 1, 2, 3, 5, 8, 13, 21, 34]
-fib(5)
-[0, 1, 1, 2, 3]</pre>
-</div>
-<div class="section" title="3. Keyword Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487542"></a>3. Keyword Arguments</h2></div></div></div>
-<p id="ch5func_f"></a>When a function takes a large number of arguments, it may be difficult to
-remember the order of the parameters in the function definition or it may
-be necessary to pass values to only certain parameters since others take
-the default value. In either of these cases, Python provides the facility
-of passing arguments by specifying the name of the parameter as defined in
-the function definition. This is known as <span class="emphasis"><em>Keyword Arguments</em></span>.</p>
-<p id="ch5func_10"></a>In a function call, <span class="emphasis"><em>Keyword arguments</em></span> can be used for each argument, in the
-following fashion:</p>
-<pre class="programlisting"> argument_name=argument_value
-Also denoted as: keyword=argument
-
-def wish(name='World', greetings='Hello'):
-  print "%s, %s!" % (greetings, name)</pre>
-<p id="ch5func_11"></a>This function can be called in one of the following ways. It is important to
-note that no restriction is imposed in the order in which <span class="emphasis"><em>Keyword arguments</em></span>
-can be specified. Also note, that we have combined <span class="emphasis"><em>Keyword arguments</em></span> with
-<span class="emphasis"><em>Default arguments</em></span> in this example, however it is not necessary:</p>
-<pre class="programlisting"> wish(name='Guido', greetings='Hey')
-wish(greetings='Hey', name='Guido')</pre>
-<p id="ch5func_12"></a>Calling functions by specifying arguments in the order of parameters specified
-in the function definition is called as <span class="emphasis"><em>Positional arguments</em></span>, as opposed to
-<span class="emphasis"><em>Keyword arguments</em></span>. It is possible to use both <span class="emphasis"><em>Positional arguments</em></span> and
-<span class="emphasis"><em>Keyword arguments</em></span> in a single function call. But Python doesn't allow us to
-bungle up both of them. The arguments to the function, in the call, must always
-start with <span class="emphasis"><em>Positional arguments</em></span> which is in turn followed by <span class="emphasis"><em>Keyword
-arguments</em></span>:</p>
-<pre class="programlisting"> def my_func(x, y, z, u, v, w):
-  # initialize variables.
-  ...
-  # do some stuff
-  ...
-  # return the value</pre>
-<p id="ch5func_13"></a>It is valid to call the above functions in the following ways:</p>
-<pre class="programlisting"> my_func(10, 20, 30, u=1.0, v=2.0, w=3.0)
-my_func(10, 20, 30, 1.0, 2.0, w=3.0)
-my_func(10, 20, z=30, u=1.0, v=2.0, w=3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, w=3.0)</pre>
-<p id="ch5func_14"></a>Following lists some of the invalid calls:</p>
-<pre class="programlisting"> my_func(10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, 3.0)</pre>
-</div>
-<div class="section" title="4. Parameter Packing and Unpacking">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487658"></a>4. Parameter Packing and Unpacking</h2></div></div></div>
-<p id="ch5func_15"></a>The positional arguments passed to a function can be collected in a tuple
-parameter and keyword arguments can be collected in a dictionary. Since keyword
-arguments must always be the last set of arguments passed to a function, the
-keyword dictionary parameter must be the last parameter. The function definition
-must include a list explicit parameters, followed by tuple paramter collecting
-parameter, whose name is preceded by a <span class="strong"><strong>*</strong></span>, for collecting positional
-parameters, in turn followed by the dictionary collecting parameter, whose name
-is preceded by a <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, *args, **name):
-  """Structure of *args*
-  (age, email-id)
-  Structure of *name*
-  {
-      'first': First Name
-      'middle': Middle Name
-      'last': Last Name
-  }
-  """
-
-  print "Title: %s" % (title)
-  print "Full name: %(first)s %(middle)s %(last)s" % name
-  print "Age: %d\nEmail-ID: %s" % args</pre>
-<p id="ch5func_16"></a>The above function can be called as. Note, the order of keyword parameters can
-be interchanged:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print_report('Employee Report', 29, 'johny@example.com', first='Johny',
-                 last='Charles', middle='Douglas')
-Title: Employee Report
-Full name: Johny Douglas Charles
-Age: 29
-Email-ID: johny@example.com</pre>
-<p id="ch5func_17"></a>The reverse of this can also be achieved by using a very identical syntax while
-calling the function. A tuple or a dictionary can be passed as arguments in
-place of a list of <span class="emphasis"><em>Positional arguments</em></span> or <span class="emphasis"><em>Keyword arguments</em></span> respectively
-using <span class="strong"><strong>*</strong></span> or <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, age, email, first, middle, last):
-  print "Title: %s" % (title)
-  print "Full name: %s %s %s" % (first, middle, last)
-  print "Age: %d\nEmail-ID: %s" % (age, email)
-
-&gt;&gt;&gt; args = (29, 'johny@example.com')
-&gt;&gt;&gt; name = {
-        'first': 'Johny',
-        'middle': 'Charles',
-        'last': 'Douglas'
-        }
-&gt;&gt;&gt; print_report('Employee Report', *args, **name)
-Title: Employee Report
-Full name: Johny Charles Douglas
-Age: 29
-Email-ID: johny@example.com</pre>
-</div>
-<div class="section" title="5. Nested Functions and Scopes">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487758"></a>5. Nested Functions and Scopes</h2></div></div></div>
-<p id="ch5func_18"></a>Python allows nesting one function inside another. This style of programming
-turns out to be extremely flexible and powerful features when we use <span class="emphasis"><em>Python
-decorators</em></span>. We will not talk about decorators is beyond the scope of this
-course. If you are interested in knowing more about <span class="emphasis"><em>decorator programming</em></span> in
-Python you are suggested to read:</p>
-<span style="color: black">&lt;line_block&gt;<span style="color: black">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://avinashv.net/2008/04/python-decorators-syntactic-sugar/</div>&lt;/line&gt;</span><span style="color: black">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://personalpages.tds.net/~kent37/kk/00001.html</div>&lt;/line&gt;</span>&lt;/line_block&gt;</span><p id="ch5func_19"></a>However, the following is an example for nested functions in Python:</p>
-<pre class="programlisting"> def outer():
-  print "Outer..."
-  def inner():
-    print "Inner..."
-  print "Outer..."
-  inner()
-
-&gt;&gt;&gt; outer()</pre>
-</div>
-<div class="section" title="6. map, reduce and filter functions">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2487811"></a>6. map, reduce and filter functions</h2></div></div></div>
-<p id="ch5func_1a"></a>Python provides several built-in functions for convenience. The <span class="strong"><strong>map()</strong></span>,
-<span class="strong"><strong>reduce()</strong></span> and <span class="strong"><strong>filter()</strong></span> functions prove to be very useful with sequences like
-<span class="emphasis"><em>Lists</em></span>.</p>
-<p id="ch5func_1b"></a>The <span class="strong"><strong>map</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments: <span class="emphasis"><em>function</em></span>
-and a <span class="emphasis"><em>sequence</em></span> argument. The <span class="emphasis"><em>function</em></span> argument must be the name of the
-function which in turn takes a single argument, the individual element of the
-<span class="emphasis"><em>sequence</em></span>. The <span class="strong"><strong>map</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each item in the
-sequence and returns a list of values, where each value is the value returned
-by each call to <span class="emphasis"><em>function(item)</em></span>. <span class="strong"><strong>map()</strong></span> function allows to pass more than
-one sequence. In this case, the first argument, <span class="emphasis"><em>function</em></span> must take as many
-arguments as the number of sequences passed. This function is called with each
-corresponding element in the each of the sequences, or <span class="strong"><strong>None</strong></span> if one of the
-sequence is exhausted:</p>
-<pre class="programlisting"> def square(x):
-  return x*x
-
-&gt;&gt;&gt; map(square, [1, 2, 3, 4])
-[1, 4, 9, 16]
-
-def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; map(mul, [1, 2, 3, 4], [6, 7, 8, 9])</pre>
-<p id="ch5func_1c"></a>The <span class="strong"><strong>filter</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-the <span class="strong"><strong>map()</strong></span> function. The <span class="strong"><strong>filter</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each
-item in the sequence and returns all the elements in the sequence for which
-<span class="emphasis"><em>function(item)</em></span> returned True:</p>
-<pre class="programlisting"> def even(x):
-  if x % 2:
-    return True
-  else:
-    return False
-
-&gt;&gt;&gt; filter(even, range(1, 10))
-[1, 3, 5, 7, 9]</pre>
-<p id="ch5func_1d"></a>The <span class="strong"><strong>reduce</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-<span class="strong"><strong>map</strong></span> function, however multiple sequences are not allowed. The <span class="strong"><strong>reduce</strong></span>
-function calls <span class="emphasis"><em>function</em></span> with first two consecutive elements in the sequence,
-obtains the result, calls <span class="emphasis"><em>function</em></span> with the result and the subsequent element
-in the sequence and so on until the end of the list and returns the final result:</p>
-<pre class="programlisting"> def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; reduce(mul, [1, 2, 3, 4])
-24</pre>
-<div class="section" title="6.1. List Comprehensions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2488001"></a>6.1. List Comprehensions</h3></div></div></div>
-<p id="ch5func_1e"></a>List Comprehension is a convenvience utility provided by Python. It is a
-syntatic sugar to create <span class="emphasis"><em>Lists</em></span>. Using <span class="emphasis"><em>List Comprehensions</em></span> one can create
-<span class="emphasis"><em>Lists</em></span> from other type of sequential data structures or other <span class="emphasis"><em>Lists</em></span> itself.
-The syntax of <span class="emphasis"><em>List Comprehensions</em></span> consists of a square brackets to indicate
-the result is a <span class="emphasis"><em>List</em></span> within which we include at least one <span class="strong"><strong>for</strong></span> clause and
-multiple <span class="strong"><strong>if</strong></span> clauses. It will be more clear with an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; num = [1, 2, 3]
-&gt;&gt;&gt; sq = [x*x for x in num]
-&gt;&gt;&gt; sq
-[1, 4, 9]
-&gt;&gt;&gt; all_num = [1, 2, 3, 4, 5, 6, 7, 8, 9]
-&gt;&gt;&gt; even = [x for x in all_num if x%2 == 0]</pre>
-<p id="ch5func_1f"></a>The syntax used here is very clear from the way it is written. It can be
-translated into english as, "for each element x in the list all_num,
-if remainder of x divided by 2 is 0, add x to the list."</p>
-</div>
-</div>
-</div>
-</div></body>
-</html>
--- a/web/html/ch6oop.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch6oop.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,86 +1,1138 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 6. OOP</title>
-<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
+<title>Strings and Dicts </title>
 <link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
 <script type="text/javascript" src="/review/support/hsbook.js"></script>
 <meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
 </head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch6oop">
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch6op">
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2582702">Classes and Objects</a></span></dt></dl>
+<dl>
+<dt><span class="article"><a href="#id2674385"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2484509">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2672204">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2725444">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2725708">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2725835">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2725844">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2726115">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2726124">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2726281">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2726339">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2726437">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2726517">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2726690">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2726699">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2726779">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2726983">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2727073">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2727127">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2727136">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2727446">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2725240">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2727886">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2727979">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2727988">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2728075">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2728202">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2728288">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2728423">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2728530">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2728538">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2728726">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2728840">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2729078">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2729343">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2729359">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2729381">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2729390">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2730149">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730186">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2730255">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2730315">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2730516">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2730550">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730580">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730589">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2730777">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730925">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2731134">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2731210">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
 </div>
-<div class="article" title="Classes and Objects">
+<div class="article">
 <div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2582702"></a>Classes and Objects</h2></div></div>
+<div><div><h2 class="title" id="id2674385"></a></h2></div></div>
 <hr>
 </div>
-<p id="ch6oop_1"></a>In the previous sections we learnt about functions which provide certain level
-of abstraction to our code by holding the code which performs one or more
-specific functionalities. We were able to use this function as many times as we
-wanted. In addition to functions, Python also higher level of abstractions
-through <span class="emphasis"><em>Classes</em></span> and <span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Objects</em></span> can be loosely defined as a
-collection of a set of data items and a set of methods. The data items can be
-any valid Python variable or any Python object. Functions enclosed within a class
-are called as <span class="emphasis"><em>methods</em></span>. If you are thinking if methods are functions why is there
-a distinction between the two? The answer to this will be given as we walk through
-the concepts of <span class="emphasis"><em>Classes</em></span> and <span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Classes</em></span> contain the definition for the
-<span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Objects</em></span> are instances of <span class="emphasis"><em>Classes</em></span>.</p>
-<p id="ch6oop_2"></a>A class is defined using the keyword <span class="strong"><strong>class</strong></span> followed by the class name, in
-turn followed by a semicolon. The statements that a <span class="emphasis"><em>Class</em></span> encloses are written
-in a new block, i.e on the next indentation level:</p>
-<pre class="programlisting"> class Employee:
-  def setName(self, name):
-    self.name = name
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2484509">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2672204">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2725444">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2725708">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2725835">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2725844">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2726115">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2726124">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2726281">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2726339">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2726437">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2726517">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2726690">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2726699">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2726779">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2726983">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2727073">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2727127">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2727136">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2727446">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2725240">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2727886">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2727979">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2727988">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2728075">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2728202">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2728288">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2728423">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2728530">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2728538">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2728726">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2728840">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2729078">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2729343">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2729359">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2729381">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2729390">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2730149">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730186">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2730255">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2730315">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2730516">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2730550">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730580">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2730589">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2730777">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2730925">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2731134">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2731210">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2484509"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch6oop_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch6oop_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch6oop_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch6oop_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2672204"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2672078"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725399"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch6oop_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch6oop_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2725444"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch6oop_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725468"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch6oop_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch6oop_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725520"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch6oop_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch6oop_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch6oop_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725575"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch6oop_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch6oop_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch6oop_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725619"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch6oop_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725664"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch6oop_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch6oop_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch6oop_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2725708"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch6oop_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch6oop_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch6oop_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch6oop_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch6oop_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch6oop_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2725835"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2725844"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch6oop_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725874"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch6oop_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch6oop_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch6oop_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch6oop_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch6oop_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch6oop_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch6oop_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch6oop_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch6oop_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2726028"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch6oop_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch6oop_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch6oop_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch6oop_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch6oop_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2726115"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726124"></a>3.1. ls</h3></div></div></div>
+<p id="ch6oop_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch6oop_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch6oop_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch6oop_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch6oop_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726281"></a>3.2. date</h3></div></div></div>
+<p id="ch6oop_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch6oop_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch6oop_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch6oop_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch6oop_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726339"></a>3.3. cd</h3></div></div></div>
+<p id="ch6oop_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch6oop_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch6oop_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch6oop_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch6oop_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch6oop_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch6oop_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch6oop_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch6oop_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch6oop_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch6oop_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch6oop_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726437"></a>3.4. who</h3></div></div></div>
+<p id="ch6oop_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch6oop_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch6oop_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch6oop_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch6oop_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726517"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch6oop_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch6oop_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2726548"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch6oop_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch6oop_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2726607"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch6oop_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch6oop_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch6oop_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch6oop_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch6oop_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2726690"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726699"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch6oop_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch6oop_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch6oop_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch6oop_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch6oop_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726779"></a>4.2. man</h3></div></div></div>
+<p id="ch6oop_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch6oop_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch6oop_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch6oop_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch6oop_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch6oop_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2726859"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch6oop_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch6oop_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch6oop_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch6oop_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch6oop_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch6oop_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch6oop_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch6oop_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch6oop_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch6oop_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch6oop_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch6oop_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2726983"></a>4.3. info</h3></div></div></div>
+<p id="ch6oop_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch6oop_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch6oop_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch6oop_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2727073"></a>4.4. --help</h3></div></div></div>
+<p id="ch6oop_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
 
-  def getName(self):
-    return self.name</pre>
-<p id="ch6oop_3"></a>In the above example, we defined a class with the name Employee. We also defined
-two methods, setName and getName for this class. It is important to note the
-differences between the normal Python functions and class methods defined above.
-Each method of the class must take the same instance of the class(object) from
-which it was called as the first argument. It is conventionally given the name,
-<span class="emphasis"><em>self</em></span>. Note that <span class="emphasis"><em>self</em></span> is only a convention. You can use any other name, but
-the first argument to the method will always be the same object of the class
-from which the method was called. The data memebers that belong to the class are
-called as <span class="emphasis"><em>class attributes</em></span>. <span class="emphasis"><em>Class attributes</em></span> are preceded by the object of
-the class and a dot. In the above example, <span class="emphasis"><em>name</em></span> is a class attribute since it
-is preceded by the <span class="emphasis"><em>self</em></span> object. <span class="emphasis"><em>Class attributes</em></span> can be accessed from
-anywhere within the class.</p>
-<p id="ch6oop_4"></a>We can create objects of a class outside the class definition by using the same
-syntax we use to call a function with no parameters. We can assign this object
-to a variable:</p>
-<pre class="programlisting"> emp = Employee()</pre>
-<p id="ch6oop_5"></a>In the above example, we create an object named <span class="emphasis"><em>emp</em></span> of the class <span class="emphasis"><em>Employee</em></span>.
-All the attributes and methods of the class can be accessed by the object of the
-class using the standard notation <span class="emphasis"><em>object.attribute</em></span> or <span class="emphasis"><em>object.method()</em></span>.
-Although the first parameter of a class method is the self object, it must not
-be passed as an argument when calling the method. The <span class="emphasis"><em>self</em></span> object is implicitly
-passed to the method by the Python interpreter. All other arguments passing rules
-like default arguments, keyword arguments, argument packing and unpacking follow
-the same rules as those for ordinary Python functions:</p>
-<pre class="programlisting"> &gt;&gt;&gt; emp.setName('John')
-&gt;&gt;&gt; name = emp.getName()
-&gt;&gt;&gt; print name
-John
-&gt;&gt;&gt; print emp.name
-John</pre>
-<p id="ch6oop_6"></a>If we at all try to access a class attribute before assigning a value to it, i.e
-before creating it, Python raises the same error as it would raise for the
-accessing undefined variable:</p>
-<pre class="programlisting"> &gt;&gt;&gt; emp = Employee()
-&gt;&gt;&gt; emp.name
-Traceback (most recent call last):
-  File "class.py", line 10, in &lt;module&gt;
-    print e.name
-AttributeError: Employee instance has no attribute 'name'</pre>
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2727127"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2727136"></a>5.1. cp</h3></div></div></div>
+<p id="ch6oop_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727153"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch6oop_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch6oop_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch6oop_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727187"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch6oop_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch6oop_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch6oop_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch6oop_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch6oop_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727285"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch6oop_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch6oop_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch6oop_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch6oop_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch6oop_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch6oop_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch6oop_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch6oop_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch6oop_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch6oop_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch6oop_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch6oop_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch6oop_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch6oop_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch6oop_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2727446"></a>5.2. mv</h3></div></div></div>
+<p id="ch6oop_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727470"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch6oop_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727489"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch6oop_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725181"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch6oop_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch6oop_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2725240"></a>5.3. rm</h3></div></div></div>
+<p id="ch6oop_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch6oop_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2725269"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch6oop_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch6oop_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch6oop_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch6oop_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch6oop_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2727846"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch6oop_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch6oop_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch6oop_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2727886"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch6oop_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch6oop_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch6oop_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch6oop_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch6oop_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch6oop_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch6oop_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2727979"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2727988"></a>7.1. head</h3></div></div></div>
+<p id="ch6oop_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch6oop_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch6oop_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch6oop_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728039"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch6oop_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch6oop_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch6oop_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728075"></a>7.2. tail</h3></div></div></div>
+<p id="ch6oop_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch6oop_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch6oop_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch6oop_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch6oop_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch6oop_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch6oop_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728153"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch6oop_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch6oop_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch6oop_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728202"></a>7.3. cut</h3></div></div></div>
+<p id="ch6oop_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch6oop_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch6oop_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch6oop_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch6oop_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch6oop_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch6oop_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728288"></a>7.4. paste</h3></div></div></div>
+<p id="ch6oop_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch6oop_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch6oop_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch6oop_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2728423"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch6oop_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch6oop_df"></a>The shell meta characters include:</p>
+<p id="ch6oop_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch6oop_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch6oop_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch6oop_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch6oop_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch6oop_e5"></a>because the c* matches that long file name.</p>
+<p id="ch6oop_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch6oop_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch6oop_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2728530"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728538"></a>9.1. cat</h3></div></div></div>
+<p id="ch6oop_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch6oop_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch6oop_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728582"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch6oop_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728620"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch6oop_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch6oop_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch6oop_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch6oop_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch6oop_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch6oop_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728690"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch6oop_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728726"></a>9.2. more</h3></div></div></div>
+<p id="ch6oop_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728746"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch6oop_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch6oop_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch6oop_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch6oop_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch6oop_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2728840"></a>9.3. less</h3></div></div></div>
+<p id="ch6oop_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728870"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch6oop_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch6oop_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch6oop_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728924"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2728975"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2729063"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2729078"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch6oop_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch6oop_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2729343"></a>10.1. man hier</h3></div></div></div>
+<p id="ch6oop_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2729359"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch6oop_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch6oop_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2729381"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2729390"></a>11.1. chmod</h3></div></div></div>
+<p id="ch6oop_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2729416"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch6oop_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch6oop_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2729443"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch6oop_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch6oop_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2729480"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch6oop_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch6oop_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch6oop_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch6oop_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch6oop_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2730027"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch6oop_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch6oop_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch6oop_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2730068"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch6oop_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch6oop_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2730106"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch6oop_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch6oop_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2730149"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch6oop_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch6oop_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730186"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch6oop_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch6oop_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch6oop_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch6oop_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730255"></a>12.2. Piping</h3></div></div></div>
+<p id="ch6oop_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch6oop_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch6oop_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch6oop_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch6oop_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730315"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch6oop_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch6oop_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch6oop_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch6oop_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch6oop_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch6oop_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch6oop_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch6oop_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch6oop_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch6oop_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch6oop_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730516"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch6oop_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch6oop_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730550"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch6oop_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch6oop_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2730580"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730589"></a>13.1. grep</h3></div></div></div>
+<p id="ch6oop_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2730620"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch6oop_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch6oop_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch6oop_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch6oop_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch6oop_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch6oop_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2730698"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch6oop_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch6oop_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch6oop_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2730777"></a>13.2. tr</h3></div></div></div>
+<p id="ch6oop_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch6oop_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch6oop_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch6oop_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch6oop_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch6oop_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch6oop_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch6oop_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch6oop_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch6oop_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch6oop_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch6oop_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2730925"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch6oop_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch6oop_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch6oop_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch6oop_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2731134"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch6oop_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch6oop_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch6oop_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2731210"></a>15. One Liners</h2></div></div></div>
+<p id="ch6oop_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch6oop_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch6oop_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch6oop_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch6oop_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch6oop_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch6oop_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch6oop_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch6oop_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch6oop_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch6oop_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch6oop_1d7"></a>Print the total number of input lines:</p>
+<p id="ch6oop_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch6oop_1d9"></a>Print the tenth input line:</p>
+<p id="ch6oop_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch6oop_1db"></a>Print the last field of every input line:</p>
+<p id="ch6oop_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch6oop_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch6oop_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch6oop_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch6oop_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch6oop_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
 </div>
 </div></body>
 </html>
--- a/web/html/ch6oop.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,86 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 6. OOP</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch6oop">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2582702">Classes and Objects</a></span></dt></dl>
-</div>
-<div class="article" title="Classes and Objects">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2582702"></a>Classes and Objects</h2></div></div>
-<hr>
-</div>
-<p id="ch6oop_1"></a>In the previous sections we learnt about functions which provide certain level
-of abstraction to our code by holding the code which performs one or more
-specific functionalities. We were able to use this function as many times as we
-wanted. In addition to functions, Python also higher level of abstractions
-through <span class="emphasis"><em>Classes</em></span> and <span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Objects</em></span> can be loosely defined as a
-collection of a set of data items and a set of methods. The data items can be
-any valid Python variable or any Python object. Functions enclosed within a class
-are called as <span class="emphasis"><em>methods</em></span>. If you are thinking if methods are functions why is there
-a distinction between the two? The answer to this will be given as we walk through
-the concepts of <span class="emphasis"><em>Classes</em></span> and <span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Classes</em></span> contain the definition for the
-<span class="emphasis"><em>Objects</em></span>. <span class="emphasis"><em>Objects</em></span> are instances of <span class="emphasis"><em>Classes</em></span>.</p>
-<p id="ch6oop_2"></a>A class is defined using the keyword <span class="strong"><strong>class</strong></span> followed by the class name, in
-turn followed by a semicolon. The statements that a <span class="emphasis"><em>Class</em></span> encloses are written
-in a new block, i.e on the next indentation level:</p>
-<pre class="programlisting"> class Employee:
-  def setName(self, name):
-    self.name = name
-
-  def getName(self):
-    return self.name</pre>
-<p id="ch6oop_3"></a>In the above example, we defined a class with the name Employee. We also defined
-two methods, setName and getName for this class. It is important to note the
-differences between the normal Python functions and class methods defined above.
-Each method of the class must take the same instance of the class(object) from
-which it was called as the first argument. It is conventionally given the name,
-<span class="emphasis"><em>self</em></span>. Note that <span class="emphasis"><em>self</em></span> is only a convention. You can use any other name, but
-the first argument to the method will always be the same object of the class
-from which the method was called. The data memebers that belong to the class are
-called as <span class="emphasis"><em>class attributes</em></span>. <span class="emphasis"><em>Class attributes</em></span> are preceded by the object of
-the class and a dot. In the above example, <span class="emphasis"><em>name</em></span> is a class attribute since it
-is preceded by the <span class="emphasis"><em>self</em></span> object. <span class="emphasis"><em>Class attributes</em></span> can be accessed from
-anywhere within the class.</p>
-<p id="ch6oop_4"></a>We can create objects of a class outside the class definition by using the same
-syntax we use to call a function with no parameters. We can assign this object
-to a variable:</p>
-<pre class="programlisting"> emp = Employee()</pre>
-<p id="ch6oop_5"></a>In the above example, we create an object named <span class="emphasis"><em>emp</em></span> of the class <span class="emphasis"><em>Employee</em></span>.
-All the attributes and methods of the class can be accessed by the object of the
-class using the standard notation <span class="emphasis"><em>object.attribute</em></span> or <span class="emphasis"><em>object.method()</em></span>.
-Although the first parameter of a class method is the self object, it must not
-be passed as an argument when calling the method. The <span class="emphasis"><em>self</em></span> object is implicitly
-passed to the method by the Python interpreter. All other arguments passing rules
-like default arguments, keyword arguments, argument packing and unpacking follow
-the same rules as those for ordinary Python functions:</p>
-<pre class="programlisting"> &gt;&gt;&gt; emp.setName('John')
-&gt;&gt;&gt; name = emp.getName()
-&gt;&gt;&gt; print name
-John
-&gt;&gt;&gt; print emp.name
-John</pre>
-<p id="ch6oop_6"></a>If we at all try to access a class attribute before assigning a value to it, i.e
-before creating it, Python raises the same error as it would raise for the
-accessing undefined variable:</p>
-<pre class="programlisting"> &gt;&gt;&gt; emp = Employee()
-&gt;&gt;&gt; emp.name
-Traceback (most recent call last):
-  File "class.py", line 10, in &lt;module&gt;
-    print e.name
-AttributeError: Employee instance has no attribute 'name'</pre>
-</div>
-</div></body>
-</html>
--- a/web/html/ch7interim_assessment.html	Mon Jan 25 18:56:45 2010 +0530
+++ b/web/html/ch7interim_assessment.html	Fri Feb 05 23:42:24 2010 +0530
@@ -1,9 +1,8 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 7. Interim Assessment</title>
+<title>Internal assesment </title>
 <link rel="stylesheet" href="/review/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
 <link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
 <script type="text/javascript" src="/review/support/jquery-min.js"></script>
 <script type="text/javascript" src="/review/support/form.js"></script>
@@ -14,12 +13,1127 @@
 <div class="titlepage"></div>
 <div class="toc">
 <p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2744085">Interim Assessment</a></span></dt></dl>
+<dl>
+<dt><span class="article"><a href="#id2484740"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2294864">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2484544">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2535791">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2536201">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2536342">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2536351">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2536630">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2536639">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2536803">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2536864">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2536967">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2537050">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2537230">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2537239">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2537322">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2537533">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2537625">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2537678">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2537687">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2537999">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2538132">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2538304">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2538397">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2538406">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2538493">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2538621">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2538708">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2538842">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2538959">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2538968">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2539156">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2539267">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2539510">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2539784">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2539801">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2539824">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2539833">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2540610">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2540646">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2540714">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2540776">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2540984">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2541018">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2541049">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2541057">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2541248">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2541399">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2541615">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2541692">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<div class="article">
+<div class="titlepage">
+<div><div><h2 class="title" id="id2484740"></a></h2></div></div>
+<hr>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2294864">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2484544">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2535791">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2536201">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2536342">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2536351">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2536630">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2536639">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2536803">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2536864">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2536967">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2537050">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2537230">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2537239">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2537322">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2537533">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2537625">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2537678">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2537687">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2537999">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2538132">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2538304">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2538397">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2538406">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2538493">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2538621">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2538708">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2538842">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2538959">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2538968">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2539156">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2539267">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2539510">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2539784">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2539801">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2539824">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2539833">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2540610">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2540646">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2540714">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2540776">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2540984">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2541018">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2541049">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2541057">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2541248">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2541399">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2541615">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2541692">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2294864"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch7interim_assessment_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch7interim_assessment_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch7interim_assessment_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch7interim_assessment_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2484544"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2482525"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535756"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch7interim_assessment_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch7interim_assessment_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2535791"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch7interim_assessment_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535816"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch7interim_assessment_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch7interim_assessment_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535870"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch7interim_assessment_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch7interim_assessment_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch7interim_assessment_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535571"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch7interim_assessment_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch7interim_assessment_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch7interim_assessment_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535616"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch7interim_assessment_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2535662"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch7interim_assessment_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch7interim_assessment_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch7interim_assessment_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536201"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch7interim_assessment_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch7interim_assessment_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch7interim_assessment_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch7interim_assessment_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch7interim_assessment_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch7interim_assessment_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2536342"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536351"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch7interim_assessment_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2536381"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch7interim_assessment_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch7interim_assessment_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch7interim_assessment_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch7interim_assessment_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch7interim_assessment_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch7interim_assessment_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch7interim_assessment_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch7interim_assessment_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch7interim_assessment_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2536540"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch7interim_assessment_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch7interim_assessment_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch7interim_assessment_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch7interim_assessment_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch7interim_assessment_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2536630"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536639"></a>3.1. ls</h3></div></div></div>
+<p id="ch7interim_assessment_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch7interim_assessment_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch7interim_assessment_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch7interim_assessment_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536803"></a>3.2. date</h3></div></div></div>
+<p id="ch7interim_assessment_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch7interim_assessment_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch7interim_assessment_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch7interim_assessment_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch7interim_assessment_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536864"></a>3.3. cd</h3></div></div></div>
+<p id="ch7interim_assessment_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch7interim_assessment_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch7interim_assessment_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch7interim_assessment_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch7interim_assessment_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch7interim_assessment_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch7interim_assessment_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch7interim_assessment_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch7interim_assessment_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch7interim_assessment_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2536967"></a>3.4. who</h3></div></div></div>
+<p id="ch7interim_assessment_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch7interim_assessment_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch7interim_assessment_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch7interim_assessment_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch7interim_assessment_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537050"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch7interim_assessment_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch7interim_assessment_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537082"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch7interim_assessment_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537144"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch7interim_assessment_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch7interim_assessment_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch7interim_assessment_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch7interim_assessment_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2537230"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537239"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch7interim_assessment_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch7interim_assessment_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch7interim_assessment_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch7interim_assessment_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch7interim_assessment_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537322"></a>4.2. man</h3></div></div></div>
+<p id="ch7interim_assessment_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch7interim_assessment_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch7interim_assessment_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch7interim_assessment_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch7interim_assessment_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch7interim_assessment_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537405"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch7interim_assessment_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch7interim_assessment_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch7interim_assessment_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch7interim_assessment_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch7interim_assessment_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch7interim_assessment_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch7interim_assessment_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch7interim_assessment_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch7interim_assessment_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch7interim_assessment_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch7interim_assessment_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch7interim_assessment_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537533"></a>4.3. info</h3></div></div></div>
+<p id="ch7interim_assessment_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch7interim_assessment_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch7interim_assessment_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537625"></a>4.4. --help</h3></div></div></div>
+<p id="ch7interim_assessment_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2537678"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537687"></a>5.1. cp</h3></div></div></div>
+<p id="ch7interim_assessment_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537704"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch7interim_assessment_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch7interim_assessment_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch7interim_assessment_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537738"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch7interim_assessment_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch7interim_assessment_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch7interim_assessment_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch7interim_assessment_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2537835"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch7interim_assessment_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch7interim_assessment_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch7interim_assessment_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch7interim_assessment_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch7interim_assessment_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch7interim_assessment_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch7interim_assessment_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch7interim_assessment_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch7interim_assessment_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch7interim_assessment_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch7interim_assessment_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch7interim_assessment_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch7interim_assessment_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch7interim_assessment_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2537999"></a>5.2. mv</h3></div></div></div>
+<p id="ch7interim_assessment_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538023"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch7interim_assessment_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538043"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch7interim_assessment_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538073"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch7interim_assessment_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch7interim_assessment_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
 </div>
-<div class="article" title="Interim Assessment"><div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2744085"></a>Interim Assessment</h2></div></div>
-<hr>
-</div></div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538132"></a>5.3. rm</h3></div></div></div>
+<p id="ch7interim_assessment_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch7interim_assessment_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538162"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch7interim_assessment_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch7interim_assessment_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch7interim_assessment_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch7interim_assessment_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538265"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch7interim_assessment_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch7interim_assessment_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch7interim_assessment_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2538304"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch7interim_assessment_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch7interim_assessment_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch7interim_assessment_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch7interim_assessment_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch7interim_assessment_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch7interim_assessment_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch7interim_assessment_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2538397"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538406"></a>7.1. head</h3></div></div></div>
+<p id="ch7interim_assessment_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch7interim_assessment_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch7interim_assessment_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch7interim_assessment_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538457"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch7interim_assessment_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch7interim_assessment_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch7interim_assessment_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538493"></a>7.2. tail</h3></div></div></div>
+<p id="ch7interim_assessment_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch7interim_assessment_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch7interim_assessment_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch7interim_assessment_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch7interim_assessment_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch7interim_assessment_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch7interim_assessment_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2538572"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch7interim_assessment_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch7interim_assessment_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch7interim_assessment_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538621"></a>7.3. cut</h3></div></div></div>
+<p id="ch7interim_assessment_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch7interim_assessment_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch7interim_assessment_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch7interim_assessment_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch7interim_assessment_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch7interim_assessment_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch7interim_assessment_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538708"></a>7.4. paste</h3></div></div></div>
+<p id="ch7interim_assessment_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch7interim_assessment_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch7interim_assessment_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch7interim_assessment_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2538842"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch7interim_assessment_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch7interim_assessment_df"></a>The shell meta characters include:</p>
+<p id="ch7interim_assessment_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch7interim_assessment_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch7interim_assessment_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch7interim_assessment_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch7interim_assessment_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch7interim_assessment_e5"></a>because the c* matches that long file name.</p>
+<p id="ch7interim_assessment_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch7interim_assessment_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch7interim_assessment_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2538959"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2538968"></a>9.1. cat</h3></div></div></div>
+<p id="ch7interim_assessment_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch7interim_assessment_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch7interim_assessment_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539011"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch7interim_assessment_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539050"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch7interim_assessment_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch7interim_assessment_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch7interim_assessment_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch7interim_assessment_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch7interim_assessment_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch7interim_assessment_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539122"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch7interim_assessment_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2539156"></a>9.2. more</h3></div></div></div>
+<p id="ch7interim_assessment_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539175"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch7interim_assessment_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch7interim_assessment_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch7interim_assessment_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch7interim_assessment_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch7interim_assessment_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2539267"></a>9.3. less</h3></div></div></div>
+<p id="ch7interim_assessment_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539296"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch7interim_assessment_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch7interim_assessment_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch7interim_assessment_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539350"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539404"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539494"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2539510"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch7interim_assessment_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch7interim_assessment_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2539784"></a>10.1. man hier</h3></div></div></div>
+<p id="ch7interim_assessment_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2539801"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch7interim_assessment_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch7interim_assessment_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2539824"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2539833"></a>11.1. chmod</h3></div></div></div>
+<p id="ch7interim_assessment_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539859"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch7interim_assessment_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch7interim_assessment_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2539887"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch7interim_assessment_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch7interim_assessment_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2539924"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch7interim_assessment_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch7interim_assessment_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch7interim_assessment_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch7interim_assessment_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch7interim_assessment_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2540485"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch7interim_assessment_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch7interim_assessment_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch7interim_assessment_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2540528"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch7interim_assessment_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch7interim_assessment_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2540566"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch7interim_assessment_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch7interim_assessment_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2540610"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch7interim_assessment_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch7interim_assessment_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2540646"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch7interim_assessment_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch7interim_assessment_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch7interim_assessment_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch7interim_assessment_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2540714"></a>12.2. Piping</h3></div></div></div>
+<p id="ch7interim_assessment_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch7interim_assessment_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch7interim_assessment_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch7interim_assessment_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch7interim_assessment_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2540776"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch7interim_assessment_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch7interim_assessment_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch7interim_assessment_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch7interim_assessment_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch7interim_assessment_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch7interim_assessment_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch7interim_assessment_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch7interim_assessment_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch7interim_assessment_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch7interim_assessment_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch7interim_assessment_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2540984"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch7interim_assessment_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch7interim_assessment_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2541018"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch7interim_assessment_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch7interim_assessment_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2541049"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2541057"></a>13.1. grep</h3></div></div></div>
+<p id="ch7interim_assessment_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2541089"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch7interim_assessment_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch7interim_assessment_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch7interim_assessment_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch7interim_assessment_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch7interim_assessment_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch7interim_assessment_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2541168"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch7interim_assessment_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch7interim_assessment_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch7interim_assessment_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2541248"></a>13.2. tr</h3></div></div></div>
+<p id="ch7interim_assessment_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch7interim_assessment_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch7interim_assessment_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch7interim_assessment_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch7interim_assessment_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch7interim_assessment_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch7interim_assessment_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch7interim_assessment_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch7interim_assessment_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch7interim_assessment_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch7interim_assessment_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch7interim_assessment_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2541399"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch7interim_assessment_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch7interim_assessment_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch7interim_assessment_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch7interim_assessment_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2541615"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch7interim_assessment_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch7interim_assessment_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch7interim_assessment_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2541692"></a>15. One Liners</h2></div></div></div>
+<p id="ch7interim_assessment_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch7interim_assessment_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch7interim_assessment_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch7interim_assessment_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch7interim_assessment_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch7interim_assessment_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch7interim_assessment_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch7interim_assessment_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch7interim_assessment_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch7interim_assessment_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch7interim_assessment_1d7"></a>Print the total number of input lines:</p>
+<p id="ch7interim_assessment_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch7interim_assessment_1d9"></a>Print the tenth input line:</p>
+<p id="ch7interim_assessment_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch7interim_assessment_1db"></a>Print the last field of every input line:</p>
+<p id="ch7interim_assessment_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch7interim_assessment_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch7interim_assessment_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch7interim_assessment_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch7interim_assessment_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch7interim_assessment_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
 </div></body>
 </html>
--- a/web/html/ch7interim_assessment.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,25 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 7. Interim Assessment</title>
-<link rel="stylesheet" href="/support/styles.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.3">
-<link rel="shortcut icon" type="image/png" href="/support/figs/favicon.png">
-<script type="text/javascript" src="/support/jquery-min.js"></script>
-<script type="text/javascript" src="/support/form.js"></script>
-<script type="text/javascript" src="/support/hsbook.js"></script>
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch7interim_assessment">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl><dt><span class="article"><a href="#id2744085">Interim Assessment</a></span></dt></dl>
-</div>
-<div class="article" title="Interim Assessment"><div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2744085"></a>Interim Assessment</h2></div></div>
-<hr>
-</div></div>
-</div></body>
-</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/web/html/ch8ult_module_plan.html	Fri Feb 05 23:42:24 2010 +0530
@@ -0,0 +1,1139 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>ULT Module Plan </title>
+<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
+<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
+<script type="text/javascript" src="/review/support/jquery-min.js"></script>
+<script type="text/javascript" src="/review/support/form.js"></script>
+<script type="text/javascript" src="/review/support/hsbook.js"></script>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch8ult_module_plan">
+<div class="titlepage"></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="article"><a href="#id2718075"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2528200">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2717879">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2769136">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2769410">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2769551">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2769560">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2769839">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2769848">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2770012">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2770073">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2770176">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2770259">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2770440">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2770448">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2770542">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2770752">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2770844">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2770897">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2770906">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2771220">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2771353">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2771662">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2771755">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2771764">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2771851">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2771978">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2772065">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2772200">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2772308">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2772317">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2772505">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2772616">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2772859">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2773133">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2773150">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2773173">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2773182">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2773959">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2773995">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2774063">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2774125">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2774332">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2774367">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2774397">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2774406">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2774596">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2774748">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2774972">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2775048">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<div class="article">
+<div class="titlepage">
+<div><div><h2 class="title" id="id2718075"></a></h2></div></div>
+<hr>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2528200">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2717879">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2769136">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2769410">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2769551">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2769560">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2769839">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2769848">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2770012">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2770073">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2770176">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2770259">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2770440">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2770448">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2770542">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2770752">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2770844">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2770897">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2770906">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2771220">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2771353">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2771662">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2771755">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2771764">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2771851">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2771978">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2772065">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2772200">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2772308">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2772317">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2772505">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2772616">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2772859">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2773133">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2773150">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2773173">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2773182">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2773959">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2773995">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2774063">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2774125">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2774332">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2774367">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2774397">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2774406">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2774596">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2774748">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2774972">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2775048">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2528200"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch8ult_module_plan_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch8ult_module_plan_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch8ult_module_plan_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch8ult_module_plan_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2717879"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2715861"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769092"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch8ult_module_plan_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch8ult_module_plan_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2769136"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch8ult_module_plan_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769161"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch8ult_module_plan_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch8ult_module_plan_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769215"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch8ult_module_plan_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch8ult_module_plan_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch8ult_module_plan_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769272"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch8ult_module_plan_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch8ult_module_plan_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch8ult_module_plan_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769317"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch8ult_module_plan_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769363"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch8ult_module_plan_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch8ult_module_plan_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch8ult_module_plan_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2769410"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch8ult_module_plan_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch8ult_module_plan_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch8ult_module_plan_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch8ult_module_plan_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch8ult_module_plan_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch8ult_module_plan_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2769551"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2769560"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch8ult_module_plan_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769590"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch8ult_module_plan_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch8ult_module_plan_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch8ult_module_plan_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch8ult_module_plan_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch8ult_module_plan_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch8ult_module_plan_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch8ult_module_plan_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch8ult_module_plan_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch8ult_module_plan_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2769750"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch8ult_module_plan_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch8ult_module_plan_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch8ult_module_plan_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch8ult_module_plan_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch8ult_module_plan_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2769839"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2769848"></a>3.1. ls</h3></div></div></div>
+<p id="ch8ult_module_plan_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch8ult_module_plan_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch8ult_module_plan_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch8ult_module_plan_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770012"></a>3.2. date</h3></div></div></div>
+<p id="ch8ult_module_plan_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch8ult_module_plan_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch8ult_module_plan_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch8ult_module_plan_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch8ult_module_plan_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770073"></a>3.3. cd</h3></div></div></div>
+<p id="ch8ult_module_plan_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch8ult_module_plan_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch8ult_module_plan_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch8ult_module_plan_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch8ult_module_plan_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch8ult_module_plan_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch8ult_module_plan_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch8ult_module_plan_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch8ult_module_plan_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch8ult_module_plan_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770176"></a>3.4. who</h3></div></div></div>
+<p id="ch8ult_module_plan_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch8ult_module_plan_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch8ult_module_plan_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch8ult_module_plan_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch8ult_module_plan_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770259"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch8ult_module_plan_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch8ult_module_plan_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2770291"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch8ult_module_plan_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2770353"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch8ult_module_plan_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch8ult_module_plan_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch8ult_module_plan_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch8ult_module_plan_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2770440"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770448"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch8ult_module_plan_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch8ult_module_plan_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch8ult_module_plan_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch8ult_module_plan_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch8ult_module_plan_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770542"></a>4.2. man</h3></div></div></div>
+<p id="ch8ult_module_plan_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch8ult_module_plan_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch8ult_module_plan_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch8ult_module_plan_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch8ult_module_plan_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch8ult_module_plan_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2770624"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch8ult_module_plan_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch8ult_module_plan_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch8ult_module_plan_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch8ult_module_plan_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch8ult_module_plan_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch8ult_module_plan_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch8ult_module_plan_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch8ult_module_plan_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch8ult_module_plan_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch8ult_module_plan_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch8ult_module_plan_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch8ult_module_plan_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770752"></a>4.3. info</h3></div></div></div>
+<p id="ch8ult_module_plan_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch8ult_module_plan_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch8ult_module_plan_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770844"></a>4.4. --help</h3></div></div></div>
+<p id="ch8ult_module_plan_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2770897"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2770906"></a>5.1. cp</h3></div></div></div>
+<p id="ch8ult_module_plan_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2770923"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch8ult_module_plan_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch8ult_module_plan_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch8ult_module_plan_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2770957"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch8ult_module_plan_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch8ult_module_plan_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch8ult_module_plan_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch8ult_module_plan_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771056"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch8ult_module_plan_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch8ult_module_plan_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch8ult_module_plan_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch8ult_module_plan_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch8ult_module_plan_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch8ult_module_plan_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch8ult_module_plan_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch8ult_module_plan_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch8ult_module_plan_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch8ult_module_plan_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch8ult_module_plan_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch8ult_module_plan_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch8ult_module_plan_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch8ult_module_plan_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2771220"></a>5.2. mv</h3></div></div></div>
+<p id="ch8ult_module_plan_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771244"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch8ult_module_plan_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771264"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch8ult_module_plan_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771294"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch8ult_module_plan_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch8ult_module_plan_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2771353"></a>5.3. rm</h3></div></div></div>
+<p id="ch8ult_module_plan_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch8ult_module_plan_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2768880"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch8ult_module_plan_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch8ult_module_plan_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch8ult_module_plan_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch8ult_module_plan_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2768983"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch8ult_module_plan_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch8ult_module_plan_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch8ult_module_plan_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2771662"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch8ult_module_plan_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch8ult_module_plan_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch8ult_module_plan_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch8ult_module_plan_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch8ult_module_plan_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch8ult_module_plan_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch8ult_module_plan_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2771755"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2771764"></a>7.1. head</h3></div></div></div>
+<p id="ch8ult_module_plan_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch8ult_module_plan_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch8ult_module_plan_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch8ult_module_plan_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771815"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch8ult_module_plan_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch8ult_module_plan_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch8ult_module_plan_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2771851"></a>7.2. tail</h3></div></div></div>
+<p id="ch8ult_module_plan_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch8ult_module_plan_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch8ult_module_plan_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch8ult_module_plan_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch8ult_module_plan_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch8ult_module_plan_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch8ult_module_plan_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2771929"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch8ult_module_plan_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch8ult_module_plan_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch8ult_module_plan_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2771978"></a>7.3. cut</h3></div></div></div>
+<p id="ch8ult_module_plan_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch8ult_module_plan_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch8ult_module_plan_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch8ult_module_plan_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch8ult_module_plan_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch8ult_module_plan_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch8ult_module_plan_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2772065"></a>7.4. paste</h3></div></div></div>
+<p id="ch8ult_module_plan_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch8ult_module_plan_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch8ult_module_plan_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch8ult_module_plan_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2772200"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch8ult_module_plan_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch8ult_module_plan_df"></a>The shell meta characters include:</p>
+<p id="ch8ult_module_plan_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch8ult_module_plan_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch8ult_module_plan_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch8ult_module_plan_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch8ult_module_plan_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch8ult_module_plan_e5"></a>because the c* matches that long file name.</p>
+<p id="ch8ult_module_plan_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch8ult_module_plan_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch8ult_module_plan_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2772308"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2772317"></a>9.1. cat</h3></div></div></div>
+<p id="ch8ult_module_plan_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch8ult_module_plan_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch8ult_module_plan_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772360"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch8ult_module_plan_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772400"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch8ult_module_plan_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch8ult_module_plan_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch8ult_module_plan_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch8ult_module_plan_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch8ult_module_plan_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch8ult_module_plan_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772471"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch8ult_module_plan_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2772505"></a>9.2. more</h3></div></div></div>
+<p id="ch8ult_module_plan_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772524"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch8ult_module_plan_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch8ult_module_plan_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch8ult_module_plan_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch8ult_module_plan_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch8ult_module_plan_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2772616"></a>9.3. less</h3></div></div></div>
+<p id="ch8ult_module_plan_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772644"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch8ult_module_plan_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch8ult_module_plan_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch8ult_module_plan_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772699"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772752"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2772843"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2772859"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch8ult_module_plan_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch8ult_module_plan_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2773133"></a>10.1. man hier</h3></div></div></div>
+<p id="ch8ult_module_plan_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2773150"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch8ult_module_plan_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch8ult_module_plan_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2773173"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2773182"></a>11.1. chmod</h3></div></div></div>
+<p id="ch8ult_module_plan_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2773207"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch8ult_module_plan_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch8ult_module_plan_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2773236"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch8ult_module_plan_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch8ult_module_plan_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2773272"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch8ult_module_plan_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch8ult_module_plan_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch8ult_module_plan_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch8ult_module_plan_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch8ult_module_plan_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2773833"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch8ult_module_plan_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch8ult_module_plan_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch8ult_module_plan_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2773877"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch8ult_module_plan_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch8ult_module_plan_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2773915"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch8ult_module_plan_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch8ult_module_plan_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2773959"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch8ult_module_plan_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch8ult_module_plan_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2773995"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch8ult_module_plan_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch8ult_module_plan_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch8ult_module_plan_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch8ult_module_plan_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774063"></a>12.2. Piping</h3></div></div></div>
+<p id="ch8ult_module_plan_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch8ult_module_plan_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch8ult_module_plan_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch8ult_module_plan_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch8ult_module_plan_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774125"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch8ult_module_plan_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch8ult_module_plan_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch8ult_module_plan_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch8ult_module_plan_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch8ult_module_plan_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch8ult_module_plan_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch8ult_module_plan_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch8ult_module_plan_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch8ult_module_plan_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch8ult_module_plan_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch8ult_module_plan_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774332"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch8ult_module_plan_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch8ult_module_plan_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774367"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch8ult_module_plan_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch8ult_module_plan_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2774397"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774406"></a>13.1. grep</h3></div></div></div>
+<p id="ch8ult_module_plan_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2774437"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch8ult_module_plan_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch8ult_module_plan_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch8ult_module_plan_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch8ult_module_plan_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch8ult_module_plan_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch8ult_module_plan_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2774517"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch8ult_module_plan_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch8ult_module_plan_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch8ult_module_plan_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774596"></a>13.2. tr</h3></div></div></div>
+<p id="ch8ult_module_plan_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch8ult_module_plan_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch8ult_module_plan_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch8ult_module_plan_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch8ult_module_plan_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch8ult_module_plan_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch8ult_module_plan_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch8ult_module_plan_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch8ult_module_plan_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch8ult_module_plan_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch8ult_module_plan_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch8ult_module_plan_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2774748"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch8ult_module_plan_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch8ult_module_plan_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch8ult_module_plan_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch8ult_module_plan_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2774972"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch8ult_module_plan_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch8ult_module_plan_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch8ult_module_plan_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2775048"></a>15. One Liners</h2></div></div></div>
+<p id="ch8ult_module_plan_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch8ult_module_plan_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch8ult_module_plan_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch8ult_module_plan_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch8ult_module_plan_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch8ult_module_plan_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch8ult_module_plan_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch8ult_module_plan_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch8ult_module_plan_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch8ult_module_plan_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch8ult_module_plan_1d7"></a>Print the total number of input lines:</p>
+<p id="ch8ult_module_plan_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch8ult_module_plan_1d9"></a>Print the tenth input line:</p>
+<p id="ch8ult_module_plan_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch8ult_module_plan_1db"></a>Print the last field of every input line:</p>
+<p id="ch8ult_module_plan_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch8ult_module_plan_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch8ult_module_plan_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch8ult_module_plan_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch8ult_module_plan_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch8ult_module_plan_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
+</div></body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/web/html/ch9Using_Linux_Tools.html	Fri Feb 05 23:42:24 2010 +0530
@@ -0,0 +1,1139 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Using Linux tools</title>
+<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
+<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
+<script type="text/javascript" src="/review/support/jquery-min.js"></script>
+<script type="text/javascript" src="/review/support/form.js"></script>
+<script type="text/javascript" src="/review/support/hsbook.js"></script>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch9Using_Linux_Tools">
+<div class="titlepage"></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="article"><a href="#id2938781"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2748906">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2938586">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2989832">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2990243">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2990384">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2990392">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2990672">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2990680">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2990844">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2990905">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2991009">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2991092">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2991272">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2991280">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2991364">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2991575">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2991667">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2991720">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2991728">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2992043">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2992175">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2992348">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2992441">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2992450">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2992537">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2992664">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2992751">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2992886">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2992994">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2993003">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2993191">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2993302">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2993551">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2993825">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2993842">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2993865">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2993874">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2994651">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2994687">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2994755">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2994817">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2995024">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2995059">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2995089">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2995098">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2995288">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2995440">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2995656">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2995732">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<div class="article">
+<div class="titlepage">
+<div><div><h2 class="title" id="id2938781"></a></h2></div></div>
+<hr>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2748906">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2938586">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2989832">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2990243">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2990384">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2990392">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2990672">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2990680">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2990844">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2990905">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2991009">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2991092">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2991272">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2991280">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2991364">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2991575">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2991667">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2991720">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2991728">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2992043">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2992175">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2992348">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2992441">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2992450">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2992537">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2992664">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2992751">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2992886">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2992994">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2993003">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2993191">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2993302">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2993551">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2993825">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2993842">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2993865">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2993874">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2994651">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2994687">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2994755">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2994817">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2995024">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2995059">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2995089">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2995098">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2995288">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2995440">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2995656">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2995732">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2748906"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch9Using_Linux_Tools_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch9Using_Linux_Tools_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch9Using_Linux_Tools_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2938586"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2936567"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989798"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch9Using_Linux_Tools_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2989832"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989857"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch9Using_Linux_Tools_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989911"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch9Using_Linux_Tools_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch9Using_Linux_Tools_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989612"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch9Using_Linux_Tools_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch9Using_Linux_Tools_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989657"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2989703"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch9Using_Linux_Tools_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch9Using_Linux_Tools_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2990243"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch9Using_Linux_Tools_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2990384"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2990392"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2990423"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch9Using_Linux_Tools_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch9Using_Linux_Tools_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch9Using_Linux_Tools_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch9Using_Linux_Tools_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch9Using_Linux_Tools_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch9Using_Linux_Tools_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch9Using_Linux_Tools_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch9Using_Linux_Tools_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2990582"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch9Using_Linux_Tools_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch9Using_Linux_Tools_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch9Using_Linux_Tools_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch9Using_Linux_Tools_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2990672"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2990680"></a>3.1. ls</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch9Using_Linux_Tools_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch9Using_Linux_Tools_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch9Using_Linux_Tools_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2990844"></a>3.2. date</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch9Using_Linux_Tools_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch9Using_Linux_Tools_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch9Using_Linux_Tools_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch9Using_Linux_Tools_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2990905"></a>3.3. cd</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch9Using_Linux_Tools_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch9Using_Linux_Tools_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch9Using_Linux_Tools_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch9Using_Linux_Tools_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch9Using_Linux_Tools_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch9Using_Linux_Tools_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch9Using_Linux_Tools_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch9Using_Linux_Tools_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch9Using_Linux_Tools_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991009"></a>3.4. who</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch9Using_Linux_Tools_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch9Using_Linux_Tools_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch9Using_Linux_Tools_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch9Using_Linux_Tools_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991092"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch9Using_Linux_Tools_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991124"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991185"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch9Using_Linux_Tools_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch9Using_Linux_Tools_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch9Using_Linux_Tools_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2991272"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991280"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch9Using_Linux_Tools_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch9Using_Linux_Tools_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch9Using_Linux_Tools_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch9Using_Linux_Tools_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991364"></a>4.2. man</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch9Using_Linux_Tools_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch9Using_Linux_Tools_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch9Using_Linux_Tools_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch9Using_Linux_Tools_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch9Using_Linux_Tools_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991447"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch9Using_Linux_Tools_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch9Using_Linux_Tools_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch9Using_Linux_Tools_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch9Using_Linux_Tools_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch9Using_Linux_Tools_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch9Using_Linux_Tools_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch9Using_Linux_Tools_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch9Using_Linux_Tools_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch9Using_Linux_Tools_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch9Using_Linux_Tools_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch9Using_Linux_Tools_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991575"></a>4.3. info</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch9Using_Linux_Tools_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch9Using_Linux_Tools_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991667"></a>4.4. --help</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2991720"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2991728"></a>5.1. cp</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991746"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch9Using_Linux_Tools_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch9Using_Linux_Tools_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991780"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch9Using_Linux_Tools_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch9Using_Linux_Tools_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch9Using_Linux_Tools_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2991879"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch9Using_Linux_Tools_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch9Using_Linux_Tools_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch9Using_Linux_Tools_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch9Using_Linux_Tools_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch9Using_Linux_Tools_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch9Using_Linux_Tools_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch9Using_Linux_Tools_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch9Using_Linux_Tools_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch9Using_Linux_Tools_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch9Using_Linux_Tools_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch9Using_Linux_Tools_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch9Using_Linux_Tools_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch9Using_Linux_Tools_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992043"></a>5.2. mv</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992067"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992086"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992117"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch9Using_Linux_Tools_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch9Using_Linux_Tools_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992175"></a>5.3. rm</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch9Using_Linux_Tools_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992205"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch9Using_Linux_Tools_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch9Using_Linux_Tools_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch9Using_Linux_Tools_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992308"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch9Using_Linux_Tools_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch9Using_Linux_Tools_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2992348"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch9Using_Linux_Tools_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch9Using_Linux_Tools_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch9Using_Linux_Tools_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch9Using_Linux_Tools_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch9Using_Linux_Tools_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch9Using_Linux_Tools_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2992441"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992450"></a>7.1. head</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch9Using_Linux_Tools_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch9Using_Linux_Tools_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch9Using_Linux_Tools_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992501"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch9Using_Linux_Tools_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch9Using_Linux_Tools_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch9Using_Linux_Tools_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992537"></a>7.2. tail</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch9Using_Linux_Tools_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch9Using_Linux_Tools_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch9Using_Linux_Tools_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch9Using_Linux_Tools_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch9Using_Linux_Tools_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch9Using_Linux_Tools_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2992615"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch9Using_Linux_Tools_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch9Using_Linux_Tools_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992664"></a>7.3. cut</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch9Using_Linux_Tools_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch9Using_Linux_Tools_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch9Using_Linux_Tools_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch9Using_Linux_Tools_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch9Using_Linux_Tools_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch9Using_Linux_Tools_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2992751"></a>7.4. paste</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch9Using_Linux_Tools_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch9Using_Linux_Tools_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch9Using_Linux_Tools_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2992886"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch9Using_Linux_Tools_df"></a>The shell meta characters include:</p>
+<p id="ch9Using_Linux_Tools_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch9Using_Linux_Tools_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch9Using_Linux_Tools_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch9Using_Linux_Tools_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch9Using_Linux_Tools_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch9Using_Linux_Tools_e5"></a>because the c* matches that long file name.</p>
+<p id="ch9Using_Linux_Tools_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch9Using_Linux_Tools_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch9Using_Linux_Tools_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2992994"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993003"></a>9.1. cat</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch9Using_Linux_Tools_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch9Using_Linux_Tools_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993046"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993086"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch9Using_Linux_Tools_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch9Using_Linux_Tools_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch9Using_Linux_Tools_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch9Using_Linux_Tools_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch9Using_Linux_Tools_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993157"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993191"></a>9.2. more</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993210"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch9Using_Linux_Tools_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch9Using_Linux_Tools_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch9Using_Linux_Tools_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch9Using_Linux_Tools_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993302"></a>9.3. less</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993331"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch9Using_Linux_Tools_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch9Using_Linux_Tools_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993391"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993444"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993535"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2993551"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch9Using_Linux_Tools_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993825"></a>10.1. man hier</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993842"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch9Using_Linux_Tools_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2993865"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2993874"></a>11.1. chmod</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993899"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch9Using_Linux_Tools_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2993928"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch9Using_Linux_Tools_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2993964"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch9Using_Linux_Tools_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch9Using_Linux_Tools_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch9Using_Linux_Tools_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch9Using_Linux_Tools_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch9Using_Linux_Tools_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2994525"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch9Using_Linux_Tools_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch9Using_Linux_Tools_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch9Using_Linux_Tools_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2994569"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch9Using_Linux_Tools_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch9Using_Linux_Tools_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2994607"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch9Using_Linux_Tools_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch9Using_Linux_Tools_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2994651"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch9Using_Linux_Tools_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2994687"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch9Using_Linux_Tools_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch9Using_Linux_Tools_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch9Using_Linux_Tools_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2994755"></a>12.2. Piping</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch9Using_Linux_Tools_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch9Using_Linux_Tools_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch9Using_Linux_Tools_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch9Using_Linux_Tools_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2994817"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch9Using_Linux_Tools_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch9Using_Linux_Tools_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch9Using_Linux_Tools_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch9Using_Linux_Tools_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch9Using_Linux_Tools_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch9Using_Linux_Tools_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch9Using_Linux_Tools_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch9Using_Linux_Tools_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch9Using_Linux_Tools_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch9Using_Linux_Tools_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2995024"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch9Using_Linux_Tools_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2995059"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch9Using_Linux_Tools_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2995089"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2995098"></a>13.1. grep</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2995129"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch9Using_Linux_Tools_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch9Using_Linux_Tools_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch9Using_Linux_Tools_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch9Using_Linux_Tools_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch9Using_Linux_Tools_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch9Using_Linux_Tools_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2995209"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch9Using_Linux_Tools_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch9Using_Linux_Tools_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch9Using_Linux_Tools_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2995288"></a>13.2. tr</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch9Using_Linux_Tools_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch9Using_Linux_Tools_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch9Using_Linux_Tools_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch9Using_Linux_Tools_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch9Using_Linux_Tools_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch9Using_Linux_Tools_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch9Using_Linux_Tools_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch9Using_Linux_Tools_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch9Using_Linux_Tools_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch9Using_Linux_Tools_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch9Using_Linux_Tools_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2995440"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch9Using_Linux_Tools_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch9Using_Linux_Tools_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch9Using_Linux_Tools_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2995656"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch9Using_Linux_Tools_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch9Using_Linux_Tools_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch9Using_Linux_Tools_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2995732"></a>15. One Liners</h2></div></div></div>
+<p id="ch9Using_Linux_Tools_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch9Using_Linux_Tools_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch9Using_Linux_Tools_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch9Using_Linux_Tools_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch9Using_Linux_Tools_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch9Using_Linux_Tools_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch9Using_Linux_Tools_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch9Using_Linux_Tools_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch9Using_Linux_Tools_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch9Using_Linux_Tools_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch9Using_Linux_Tools_1d7"></a>Print the total number of input lines:</p>
+<p id="ch9Using_Linux_Tools_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch9Using_Linux_Tools_1d9"></a>Print the tenth input line:</p>
+<p id="ch9Using_Linux_Tools_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch9Using_Linux_Tools_1db"></a>Print the last field of every input line:</p>
+<p id="ch9Using_Linux_Tools_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch9Using_Linux_Tools_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch9Using_Linux_Tools_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch9Using_Linux_Tools_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch9Using_Linux_Tools_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch9Using_Linux_Tools_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
+</div></body>
+</html>
--- a/web/html/chap_intro.py~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,2 +0,0 @@
-p_list={'chap_intro':['x_38', 'x_39', 'x_3d', 'x_3e', 'x_3f', 'x_40', 'x_41', 'x_42', 'x_46', 'x_4c', 'x_4d', 'x_4e', 'x_4f', 'x_50', 'x_51', 'x_52', 'x_53', 'x_54', 'x_55', 'x_56', 'x_57', 'x_58', 'x_59', 'x_5a', 'x_5b', 'x_5c', 'x_5d', 'x_5e', 'x_5f', 'x_60', 'x_61', 'x_62', 'x_63', 'x_64', 'x_65', 'x_66', 'x_67', 'x_68', 'x_69', 'x_6d', 'x_6e', 'x_6f', 'x_70', 'x_71', 'x_72', 'x_73', 'x_74', 'x_75', 'x_79', 'x_7a', 'x_7b', 'x_7c', 'x_7d', 'x_7e', 'x_7f', 'x_80', 'x_81', 'x_82', 'x_83', 'x_84', 'x_85', 'x_86', 'x_87', 'x_88', 'x_89', 'x_8a', 'x_8b', 'x_8c', 'x_8d', 'x_8e', 'x_8f', 'x_90', 'x_91', 'x_92', 'x_93', 'x_94', 'x_95', 'x_96', 'x_97', 'x_98', 'x_99', 'x_9a', 'x_9b', 'x_9c', 'x_9d']}
-
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/web/html/chn10session4.html	Fri Feb 05 23:42:24 2010 +0530
@@ -0,0 +1,1139 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Session 4 </title>
+<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
+<link rel="stylesheet" href="/review/support/styles.css" type="text/css">
+<script type="text/javascript" src="/review/support/jquery-min.js"></script>
+<script type="text/javascript" src="/review/support/form.js"></script>
+<script type="text/javascript" src="/review/support/hsbook.js"></script>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch10session4">
+<div class="titlepage"></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="article"><a href="#id2855701"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2665826">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2853520">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2906761">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2907033">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2907165">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2907174">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2907452">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2907460">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2907622">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2907682">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2907784">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2907867">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2908045">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2908054">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2908136">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2906583">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2908572">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2908625">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2908633">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2908944">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2909093">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2909263">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2909355">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2909364">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2909450">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2909577">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2909663">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2909795">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2909902">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2909910">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2910114">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2910224">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2910464">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2910734">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2910750">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2910773">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2910782">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2911546">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2911583">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2911652">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2911713">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2911918">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2911952">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2911982">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2911991">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2912180">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2912329">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2912542">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2912618">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<div class="article">
+<div class="titlepage">
+<div><div><h2 class="title" id="id2855701"></a></h2></div></div>
+<hr>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2665826">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2853520">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2906761">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2907033">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2907165">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2907174">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2907452">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2907460">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2907622">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2907682">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2907784">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2907867">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2908045">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2908054">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2908136">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2906583">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2908572">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2908625">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2908633">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2908944">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2909093">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2909263">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2909355">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2909364">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2909450">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2909577">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2909663">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2909795">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2909902">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2909910">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2910114">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2910224">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2910464">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2910734">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2910750">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2910773">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2910782">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2911546">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2911583">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2911652">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2911713">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2911918">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2911952">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2911982">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2911991">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2912180">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2912329">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2912542">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2912618">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2665826"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch10session4_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch10session4_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch10session4_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch10session4_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2853520"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2853486"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906716"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch10session4_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch10session4_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2906761"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch10session4_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906785"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch10session4_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch10session4_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906839"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch10session4_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch10session4_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch10session4_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906896"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch10session4_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch10session4_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch10session4_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906940"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch10session4_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2906986"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch10session4_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch10session4_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch10session4_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907033"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch10session4_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch10session4_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch10session4_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch10session4_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch10session4_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch10session4_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2907165"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907174"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch10session4_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2907204"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch10session4_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch10session4_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch10session4_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch10session4_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch10session4_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch10session4_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch10session4_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch10session4_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch10session4_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2907362"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch10session4_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch10session4_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch10session4_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch10session4_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch10session4_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2907452"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907460"></a>3.1. ls</h3></div></div></div>
+<p id="ch10session4_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch10session4_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch10session4_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch10session4_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch10session4_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907622"></a>3.2. date</h3></div></div></div>
+<p id="ch10session4_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch10session4_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch10session4_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch10session4_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch10session4_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907682"></a>3.3. cd</h3></div></div></div>
+<p id="ch10session4_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch10session4_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch10session4_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch10session4_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch10session4_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch10session4_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch10session4_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch10session4_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch10session4_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch10session4_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch10session4_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch10session4_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907784"></a>3.4. who</h3></div></div></div>
+<p id="ch10session4_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch10session4_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch10session4_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch10session4_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch10session4_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2907867"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch10session4_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch10session4_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2907898"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch10session4_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch10session4_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2907959"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch10session4_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch10session4_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch10session4_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch10session4_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch10session4_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2908045"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2908054"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch10session4_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch10session4_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch10session4_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch10session4_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch10session4_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2908136"></a>4.2. man</h3></div></div></div>
+<p id="ch10session4_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch10session4_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch10session4_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch10session4_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch10session4_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch10session4_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908219"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch10session4_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch10session4_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch10session4_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch10session4_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch10session4_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch10session4_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch10session4_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch10session4_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch10session4_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch10session4_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch10session4_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch10session4_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2906583"></a>4.3. info</h3></div></div></div>
+<p id="ch10session4_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch10session4_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch10session4_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch10session4_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2908572"></a>4.4. --help</h3></div></div></div>
+<p id="ch10session4_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2908625"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2908633"></a>5.1. cp</h3></div></div></div>
+<p id="ch10session4_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908651"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch10session4_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch10session4_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch10session4_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908685"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch10session4_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch10session4_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch10session4_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch10session4_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch10session4_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908782"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch10session4_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch10session4_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch10session4_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch10session4_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch10session4_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch10session4_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch10session4_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch10session4_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch10session4_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch10session4_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch10session4_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch10session4_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch10session4_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch10session4_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch10session4_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2908944"></a>5.2. mv</h3></div></div></div>
+<p id="ch10session4_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908968"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch10session4_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2908988"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch10session4_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909034"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch10session4_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch10session4_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909093"></a>5.3. rm</h3></div></div></div>
+<p id="ch10session4_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch10session4_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909122"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch10session4_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch10session4_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch10session4_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch10session4_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch10session4_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909224"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch10session4_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch10session4_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch10session4_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2909263"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch10session4_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch10session4_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch10session4_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch10session4_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch10session4_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch10session4_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch10session4_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2909355"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909364"></a>7.1. head</h3></div></div></div>
+<p id="ch10session4_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch10session4_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch10session4_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch10session4_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909415"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch10session4_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch10session4_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch10session4_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909450"></a>7.2. tail</h3></div></div></div>
+<p id="ch10session4_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch10session4_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch10session4_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch10session4_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch10session4_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch10session4_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch10session4_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909528"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch10session4_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch10session4_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch10session4_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909577"></a>7.3. cut</h3></div></div></div>
+<p id="ch10session4_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch10session4_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch10session4_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch10session4_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch10session4_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch10session4_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch10session4_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909663"></a>7.4. paste</h3></div></div></div>
+<p id="ch10session4_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch10session4_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch10session4_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch10session4_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2909795"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch10session4_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch10session4_df"></a>The shell meta characters include:</p>
+<p id="ch10session4_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch10session4_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch10session4_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch10session4_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch10session4_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch10session4_e5"></a>because the c* matches that long file name.</p>
+<p id="ch10session4_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch10session4_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch10session4_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2909902"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2909910"></a>9.1. cat</h3></div></div></div>
+<p id="ch10session4_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch10session4_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch10session4_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2909954"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch10session4_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910010"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch10session4_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch10session4_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch10session4_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch10session4_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch10session4_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch10session4_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910080"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch10session4_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2910114"></a>9.2. more</h3></div></div></div>
+<p id="ch10session4_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910133"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch10session4_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch10session4_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch10session4_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch10session4_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch10session4_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2910224"></a>9.3. less</h3></div></div></div>
+<p id="ch10session4_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910253"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch10session4_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch10session4_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch10session4_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910307"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910360"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910449"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2910464"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch10session4_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch10session4_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2910734"></a>10.1. man hier</h3></div></div></div>
+<p id="ch10session4_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2910750"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch10session4_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch10session4_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2910773"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2910782"></a>11.1. chmod</h3></div></div></div>
+<p id="ch10session4_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910807"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch10session4_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch10session4_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2910835"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch10session4_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch10session4_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2910872"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch10session4_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch10session4_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch10session4_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch10session4_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch10session4_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2911418"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch10session4_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch10session4_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch10session4_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2911459"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch10session4_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch10session4_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2911498"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch10session4_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch10session4_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2911546"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch10session4_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch10session4_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911583"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch10session4_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch10session4_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch10session4_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch10session4_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911652"></a>12.2. Piping</h3></div></div></div>
+<p id="ch10session4_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch10session4_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch10session4_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch10session4_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch10session4_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911713"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch10session4_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch10session4_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch10session4_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch10session4_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch10session4_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch10session4_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch10session4_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch10session4_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch10session4_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch10session4_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch10session4_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911918"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch10session4_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch10session4_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911952"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch10session4_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch10session4_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2911982"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2911991"></a>13.1. grep</h3></div></div></div>
+<p id="ch10session4_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2912022"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch10session4_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch10session4_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch10session4_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch10session4_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch10session4_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch10session4_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2912100"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch10session4_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch10session4_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch10session4_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2912180"></a>13.2. tr</h3></div></div></div>
+<p id="ch10session4_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch10session4_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch10session4_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch10session4_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch10session4_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch10session4_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch10session4_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch10session4_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch10session4_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch10session4_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch10session4_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch10session4_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2912329"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch10session4_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch10session4_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch10session4_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch10session4_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2912542"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch10session4_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch10session4_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch10session4_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2912618"></a>15. One Liners</h2></div></div></div>
+<p id="ch10session4_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch10session4_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch10session4_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch10session4_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch10session4_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch10session4_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch10session4_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch10session4_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch10session4_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch10session4_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch10session4_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch10session4_1d7"></a>Print the total number of input lines:</p>
+<p id="ch10session4_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch10session4_1d9"></a>Print the tenth input line:</p>
+<p id="ch10session4_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch10session4_1db"></a>Print the last field of every input line:</p>
+<p id="ch10session4_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch10session4_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch10session4_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch10session4_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch10session4_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch10session4_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
+</div></body>
+</html>
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/web/html/chn11Section_5.html	Fri Feb 05 23:42:24 2010 +0530
@@ -0,0 +1,1138 @@
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Section 5</title>
+<link rel="shortcut icon" type="image/png" href="/review/support/figs/favicon.png">
+<script type="text/javascript" src="/review/support/jquery-min.js"></script>
+<script type="text/javascript" src="/review/support/form.js"></script>
+<script type="text/javascript" src="/review/support/hsbook.js"></script>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" id="ch11Section_5">
+<div class="titlepage"></div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="article"><a href="#id2451767"></a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2261892">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2449586">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2502827">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2503099">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2503232">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2503240">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2503518">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2503526">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2503688">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2503749">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2503851">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2503933">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2504112">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2504120">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2502619">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2504548">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2504638">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2504691">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2504700">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2505011">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2505142">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2505313">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2505405">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2505414">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2505500">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2505634">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2505719">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2505852">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2505959">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2505967">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2506170">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2506281">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2506521">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2506791">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2506807">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2506830">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2506838">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2507603">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2507640">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2507709">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2507770">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2507974">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2508008">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2508039">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2508048">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2508237">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2508386">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2508599">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2508675">15. One Liners</a></span></dt>
+</dl></dd>
+</dl>
+</div>
+<div class="article">
+<div class="titlepage">
+<div><div><h2 class="title" id="id2451767"></a></h2></div></div>
+<hr>
+</div>
+<div class="toc">
+<p><b>Table of Contents</b></p>
+<dl>
+<dt><span class="section"><a href="#id2261892">1. Introducing Linux</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2449586">1.1. Historical Background</a></span></dt>
+<dt><span class="section"><a href="#id2502827">1.2. Design and Implications</a></span></dt>
+<dt><span class="section"><a href="#id2503099">1.3. Reasons for Using Linux</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2503232">2. Getting Started</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2503240">2.1. Logging in, activating the user interface and logging out</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2503518">3. Basic Commands</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2503526">3.1. ls</a></span></dt>
+<dt><span class="section"><a href="#id2503688">3.2. date</a></span></dt>
+<dt><span class="section"><a href="#id2503749">3.3. cd</a></span></dt>
+<dt><span class="section"><a href="#id2503851">3.4. who</a></span></dt>
+<dt><span class="section"><a href="#id2503933">3.5. mkdir</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2504112">4. Getting Help</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2504120">4.1. apropos and whatis</a></span></dt>
+<dt><span class="section"><a href="#id2502619">4.2. man</a></span></dt>
+<dt><span class="section"><a href="#id2504548">4.3. info</a></span></dt>
+<dt><span class="section"><a href="#id2504638">4.4. --help</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2504691">5. Basic file handling</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2504700">5.1. cp</a></span></dt>
+<dt><span class="section"><a href="#id2505011">5.2. mv</a></span></dt>
+<dt><span class="section"><a href="#id2505142">5.3. rm</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2505313">6. Command Line Arguments</a></span></dt>
+<dt><span class="section"><a href="#id2505405">7. Basic Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2505414">7.1. head</a></span></dt>
+<dt><span class="section"><a href="#id2505500">7.2. tail</a></span></dt>
+<dt><span class="section"><a href="#id2505634">7.3. cut</a></span></dt>
+<dt><span class="section"><a href="#id2505719">7.4. paste</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2505852">8. Shell Meta Characters</a></span></dt>
+<dt><span class="section"><a href="#id2505959">9. Looking At Files</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2505967">9.1. cat</a></span></dt>
+<dt><span class="section"><a href="#id2506170">9.2. more</a></span></dt>
+<dt><span class="section"><a href="#id2506281">9.3. less</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2506521">10. Directory Structure</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2506791">10.1. man hier</a></span></dt>
+<dt><span class="section"><a href="#id2506807">10.2. ls -l</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2506830">11. Permissions and Ownership</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2506838">11.1. chmod</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2507603">12. Redirection and Piping</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2507640">12.1. Redirecting standard input and standard output</a></span></dt>
+<dt><span class="section"><a href="#id2507709">12.2. Piping</a></span></dt>
+<dt><span class="section"><a href="#id2507770">12.3. Redirecting to and from the standard file handles</a></span></dt>
+<dt><span class="section"><a href="#id2507974">12.4. Chained pipelines</a></span></dt>
+<dt><span class="section"><a href="#id2508008">12.5. Redirect to multiple outputs</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2508039">13. More Text Processing</a></span></dt>
+<dd><dl>
+<dt><span class="section"><a href="#id2508048">13.1. grep</a></span></dt>
+<dt><span class="section"><a href="#id2508237">13.2. tr</a></span></dt>
+</dl></dd>
+<dt><span class="section"><a href="#id2508386">14. Elementary Regex</a></span></dt>
+<dd><dl><dt><span class="section"><a href="#id2508599">14.1. Lazy quantification</a></span></dt></dl></dd>
+<dt><span class="section"><a href="#id2508675">15. One Liners</a></span></dt>
+</dl>
+</div>
+<div class="section" title="1. Introducing Linux">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2261892"></a>1. Introducing Linux</h2></div></div></div>
+<p id="ch11Section_5_1"></a>(Attribution : A significant chunk of the content under this section is based on data from Wikipedia and the Linux Documentation Project)</p>
+<p id="ch11Section_5_2"></a>Linux (usually pronounced ˈlɪnəks') is a generic term referring to Unix-like computer operating systems based on the Linux kernel, where a kernel is the intermediate layer between the hardware and the applications. The kernel is, on an abstract level, the core of (most) operating systems, that manages the various system resources. The development of the Linux OS is considered the basis for Free and Open Source Software (FOSS) collaboration since typically the underlying source code can be used, modified freely, and redistributed by anyone under the terms of the GNU (a recursive acronym for "GNU's Not Unix!") Global Public License (GPL) and other free software licences. This freedom to access and reuse various components of a system, is one of the primary reasons for the popularity of Linux.</p>
+<p id="ch11Section_5_3"></a>Linux is installed on a variety of computer hardware, that include mobile phones, embedded devices and supercomputers, but is infamous for its use in servers.</p>
+<p id="ch11Section_5_4"></a>The name "Linux"  comes from the Linux kernel, originally written in 1991 by Linus Torvalds. The rest of the system usually comprises components such as the Apache HTTP Server, the X Window System, the GNOME and KDE desktop environments, and utilities and libraries from the GNU Project (announced in 1983 by Richard Stallman). Commonly-used applications with desktop Linux systems include the Mozilla Firefox web-browser and the OpenOffice.org office application suite. The GNU contribution is the basis for the Free Software Foundation's preferred name GNU/Linux. The kernel's mascot is a penguin named "Tux". Mozilla Firefox and OpenOffice.org are open-source projects which can be run on most Operating Systems, including proprietary ones.</p>
+<div class="section" title="1.1. Historical Background">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2449586"></a>1.1. Historical Background</h3></div></div></div>
+<div class="section" title="1.1.1. Events leading to the creation">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2449553"></a>1.1.1. Events leading to the creation</h4></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_5"></a>The Unix operating system was developed in the 1960s and released for public use in 1970. Its accessibility and portability caused it to be widely adopted, copied and modified by academic institutions and businesses. Its design became influential to authors of other systems. Other free operating systems include the Berkeley Software Distribution (BSD), developed at the University of California at Berkeley, and MINIX which was released by Andrew S. Tanenbaum. The development and adoption of BSD and MINIX were limited due to various reasons, and this lack of a widely-adopted and free kernel triggered Linus Torvalds into starting his project.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_6"></a>In 1983, Richard Stallman started the GNU project with the goal of creating a free UNIX-like operating system. As part of this work, he wrote the GNU General Public License (GPL). By the early 1990s there was almost enough available software to create a full operating system. However, the GNU kernel, called Hurd, failed to attract enough attention from developers leaving GNU incomplete.</p></li>
+</ul></div>
+</div>
+<div class="section" title="1.1.2. The Creation of Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2502782"></a>1.1.2. The Creation of Linux</h4></div></div></div>
+<p id="ch11Section_5_7"></a>In 1991, Linus Torvalds began a project at the University of Helsinki that later became the Linux kernel. It was initially a terminal (command-line) emulator, which Torvalds used to access the large UNIX servers of the university. He wrote the program targeting just the hardware he was using and independent of an operating system because he wanted to use the functions of his computer with an 80386 processor. Development was done on Minix using the GNU C compiler. This application is still the main choice for compiling Linux today (although the code can be built with other compilers, such as the Intel C Compiler).</p>
+<p id="ch11Section_5_8"></a>Torvalds continues to direct the development of the kernel. Stallman heads the Free Software Foundation, which in turn supports the GNU components. Finally, individuals and corporations develop third-party non-GNU components, which constitute a vast body of work and including kernel modules, and user applications and libraries. Linux vendors and communities combine and distribute the kernel, GNU components, and non-GNU components, with additional package management software in the form of Linux distributions.</p>
+</div>
+</div>
+<div class="section" title="1.2. Design and Implications">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2502827"></a>1.2. Design and Implications</h3></div></div></div>
+<p id="ch11Section_5_9"></a>A Linux-based system is a modular Unix-like operating system, deriving much of its basic design from principles established in Unix earlier. Such a system uses a monolithic kernel, called the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are integrated directly with the kernel. Separate projects that interface with the kernel provide much of the system's higher-level functionality. The GNU userland is an important part of most Linux-based systems, providing the most common implementation of the C library, a popular shell, and many of the common Unix tools which carry out many basic operating system tasks. The graphical user interface (or GUI) used by most Linux systems is based on the "X Window System".</p>
+<div class="section" title="1.2.1. User Interface">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2502852"></a>1.2.1. User Interface</h4></div></div></div>
+<p id="ch11Section_5_a"></a>Users can control a Linux-based system through a command line interface (or CLI), a graphical user interface (or GUI), or through controls attached to the associated hardware (this is common for embedded systems). For desktop systems, the default mode is usually the GUI. On desktop machines, "KDE", "GNOME" and "Xfce" are the most popular user interfaces,though a variety of additional user interfaces exist. Most popular user interfaces run on top of the "X Window System" (or X), which enables a graphical application running on one machine to be displayed and controlled from another in a network.</p>
+<p id="ch11Section_5_b"></a>A Linux system also provides a CLI of some sort through a shell, which is the traditional way of interacting with a Unix system. A Linux distribution specialized for servers may use the CLI as its only interface. A “headless system” (system run without even a monitor) can be controlled by the command line via a remote-control protocol such as SSH or telnet. The CLI is particularly suited for automation of repetitive or delayed tasks, and provides very simple inter-process communication. A graphical terminal emulator program is often used to access the CLI from a Linux desktop.</p>
+</div>
+<div class="section" title="1.2.2. Development">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2502906"></a>1.2.2. Development</h4></div></div></div>
+<p id="ch11Section_5_c"></a>The primary difference between Linux and many other popular contemporary operating systems is that the Linux kernel and other components are free and open source software. Linux is not the only such operating system, although it is by far the most widely used. Some free and open source software licenses are based on the principle of "copyleft", a kind of reciprocity: any work derived from a copyleft piece of software must also be copyleft itself. The most common free software license, the GNU GPL, is a form of copyleft, and is used for the Linux kernel and many of the components from the GNU project.</p>
+<p id="ch11Section_5_d"></a>Linux based distributions are intended by developers for interoperability with other operating systems and established computing standards. Linux systems adhere to POSIX, SUS, ISO and ANSI standards where possible, although to date only one Linux distribution has been POSIX.1 certified, Linux-FT.Free software projects, although developed in a collaborative fashion, are often produced independently of each other. The fact that the software licenses explicitly permit redistribution, however, provides a basis for larger scale projects that collect the software produced by stand-alone projects and make it available all at once in the form of a Linux distribution.</p>
+<p id="ch11Section_5_e"></a>A Linux distribution, commonly called a "distro", is a project that manages a remote collection of system software and application software packages available for download and installation through a network connection. This allows the user to adapt the operating system to his/her specific needs. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. A distribution can be installed using a CD that contains distribution-specific software for initial system installation and configuration. A package manager such as Synaptic or YAST allows later package upgrades and installations. A distribution is responsible for the default configuration of the installed Linux kernel, general system security, and more generally integration of the different software packages into a coherent whole.</p>
+</div>
+<div class="section" title="1.2.3. Community">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2502962"></a>1.2.3. Community</h4></div></div></div>
+<p id="ch11Section_5_f"></a>A distribution is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis. Examples include Debian and the Debian-based, Ubuntu. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.</p>
+<p id="ch11Section_5_10"></a>In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote their preferred distribution and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. Many Internet communities also provide support to Linux users and developers. Most distributions and free software / open source projects have IRC (Internet Relay Chat) chatrooms or newsgroups. Online forums are another means for support. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list. All these can be found simply by running an appropriate search on Google.</p>
+<p id="ch11Section_5_11"></a>Although Linux distributions are generally available without charge, several large corporations sell, support, and contribute to the development of the components of the system and of free software. These include Dell, IBM, HP, Oracle, Sun Microsystems, Novell, Nokia. A number of corporations, notably Red Hat, have built their entire business around Linux distributions.</p>
+</div>
+<div class="section" title="1.2.4. Can I make a profit out of running a business involving Linux?">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2503007"></a>1.2.4. Can I make a profit out of running a business involving Linux?</h4></div></div></div>
+<p id="ch11Section_5_12"></a>The answer is, "Yes!". The free software licenses, on which the various software packages of a distribution built on the Linux kernel are based, explicitly accommodate and encourage commercialization; the relationship between a Linux distribution as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware. Examples of corporations that are extensively (and sometimes exclusively) open-source and Linux-powered , with successful revenue generation models involving these, are Google, SUN, Mozilla, etc.</p>
+</div>
+<div class="section" title="1.2.5. Programming on Linux">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2503052"></a>1.2.5. Programming on Linux</h4></div></div></div>
+<p id="ch11Section_5_13"></a>Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler, Sun Studio, and IBM XL C/C++ Compiler.</p>
+<p id="ch11Section_5_14"></a>Most distributions also include support for PHP, Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still supported, are C# via the Mono project, sponsored by Novell, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe.</p>
+<p id="ch11Section_5_15"></a>The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated Development Environments (IDEs) available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.</p>
+</div>
+</div>
+<div class="section" title="1.3. Reasons for Using Linux">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503099"></a>1.3. Reasons for Using Linux</h3></div></div></div>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_16"></a>Linux is free:</p></li></ul></div>
+<p id="ch11Section_5_17"></a>As in "free beer". Linux can be downloaded in its entirety from the Internet completely for free. No registration fees, no costs per user, free updates, and freely available source code in case you want to change the behavior of your system.
+Most of all, Linux is free as in "free speech":
+The license commonly used is the GNU Public License (GPL). The license says that anybody who may want to do so, has the right to change Linux and eventually to redistribute a changed version, on the one condition that the code is still available after redistribution. In practice, you are free to grab a kernel image and sell the new code, as long as your customers can still have a copy of that code.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_18"></a>Linux is portable to any hardware platform:</p></li></ul></div>
+<p id="ch11Section_5_19"></a>A vendor, who wants to sell a new type of computer and who does not know what kind of OS his/her new machine will run, can take a Linux kernel and make it work on his/her hardware, because documentation related to this activity is freely available.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_1a"></a>Linux was made to keep on running:</p></li></ul></div>
+<p id="ch11Section_5_1b"></a>As with UNIX, a Linux system expects to run without rebooting all the time. That is why a lot of tasks are being executed at night or scheduled automatically for other times, resulting in higher availability during busier periods and a more balanced use of the hardware. This property allows for Linux to be applicable to environments where people do not have the time or the possibility to control their systems constantly.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_1c"></a>Linux is secure and versatile:</p></li></ul></div>
+<p id="ch11Section_5_1d"></a>The security model used in Linux is based on the UNIX idea of security, which is known to be robust and of proven quality. But Linux is not only safe from attacks from the Internet: it will adapt equally to other situations, utilizing the same high standards for security.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_1e"></a>Linux is scalable:</p></li></ul></div>
+<p id="ch11Section_5_1f"></a>From a Palmtop with 2 MB of memory to a petabyte storage cluster with hundreds of nodes: add or remove the appropriate packages and Linux fits all. One does not need a supercomputer anymore,because you can use Linux to do big things using the building blocks provided with the system. If one wants to do little things, such as making an operating system for an embedded processor or just recycling your old 486, Linux will do that as well.</p>
+<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_20"></a>The Linux OS and Linux applications have very short debug−times:</p></li></ul></div>
+<p id="ch11Section_5_21"></a>Because Linux has been developed and tested by thousands of people, both errors and people to fix them are found very quickly. It often happens that there are only a couple of hours between discovery and fixing of a bug.</p>
+</div>
+</div>
+<div class="section" title="2. Getting Started">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2503232"></a>2. Getting Started</h2></div></div></div>
+<div class="section" title="2.1. Logging in, activating the user interface and logging out">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503240"></a>2.1. Logging in, activating the user interface and logging out</h3></div></div></div>
+<p id="ch11Section_5_22"></a>In order to work on a Linux system directly, one needs to provide a user name and password. You always need to authenticate to the system. Most PC−based Linux systems have two basic modes for a system to run in: either quick and clean in text console mode,which includes with mouse, multitasking and multi−user features, or in graphical console mode, which looks better but eats more system resources.</p>
+<div class="section" title="2.1.1. Graphical Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2503270"></a>2.1.1. Graphical Mode</h4></div></div></div>
+<p id="ch11Section_5_23"></a>This is the default nowadays on most desktop computers. You know you will be connecting to the system using graphical mode when you are first asked for your user name, and then to type your password.</p>
+<p id="ch11Section_5_24"></a>To log in, make sure the mouse pointer is in the login window, provide your user name and password to the system and click <span class="emphasis"><em>OK</em></span> or press <span class="emphasis"><em>Enter</em></span>.
+It is generally considered a bad idea to connect (graphically) using the root user name, the system adminstrator's account, since the use of graphics includes running a lot of extra programs, in root's case with a lot of extra permissions. To keep all risks as low as possible, use a normal user account to connect graphically. But there are enough risks to keep this in mind as a general advice, for all use of the root account: only log in as root when extra privileges are required.</p>
+<p id="ch11Section_5_25"></a>After entering your user name/password combination, it can take a little while before the graphical environment is started, depending on the CPU speed of your computer, on the software you use and on your personal settings.</p>
+<p id="ch11Section_5_26"></a>To continue, you will need to open a <span class="emphasis"><em>terminal window</em></span> or <span class="emphasis"><em>xterm</em></span> for short (X being the name for the underlying software supporting the graphical environment). This program can be found in the <span class="emphasis"><em>Applications−&gt;Utilities-&gt;System Tools</em></span> or <span class="emphasis"><em>Internet menu</em></span>, depending on what window manager you are using. There might be icons that you can use as a shortcut to get an <span class="emphasis"><em>xterm</em></span> window as well, and clicking the right mouse button on the desktop background will usually present you with a menu containing a terminal window application.</p>
+<p id="ch11Section_5_27"></a>While browsing the menus, you will notice that a lot of things can be done without entering commands via the keyboard. For most users, the good old point−n−click method of dealing with the computer will do. But for those who want to enter the "heart" of the system, a tool stronger than a mouse will be required to handle the various tasks. This tool is the shell, and when in graphical mode, we activate our shell by opening a terminal window.</p>
+<p id="ch11Section_5_28"></a>A terminal window should always show a command prompt when you open one. This terminal shows a standard prompt, which displays the user's login name, and the current working directory, represented by the twiddle (~)</p>
+<p id="ch11Section_5_29"></a>Another common form for a prompt is this one:
+[</p>
+<div class="reference">
+<div class="titlepage"><hr></div>user@host</div>
+<p> dir]</p>
+<p id="ch11Section_5_2a"></a>In the above example, <span class="emphasis"><em>user</em></span> will be your login name, <span class="emphasis"><em>hosts</em></span> the name of the machine you are working on, and <span class="emphasis"><em>dir</em></span> an indication of your current location in the file system. Prompts can display all kinds of information, but they are not part of the commands you are giving to your system. To disconnect from the system in graphical mode, you need to close all terminal windows and other applications. After that, hit the <span class="emphasis"><em>logout</em></span> icon or find <span class="emphasis"><em>Log Out</em></span> in the menu. Closing everything is not really necessary, and the system can do this for you, but session management might put all currently open applications back on your screen when you connect again, which takes longer and is not always the desired effect. However, this behavior is configurable.</p>
+<p id="ch11Section_5_2b"></a>When you see the login screen again, asking to enter user name and password, logout was successful.</p>
+</div>
+<div class="section" title="2.1.2. Text Mode">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2503428"></a>2.1.2. Text Mode</h4></div></div></div>
+<p id="ch11Section_5_2c"></a>One is in text mode when the whole screen is black, showing (in most cases white) characters. A text mode login screen typically shows some information about the machine you are working on, the name of the machine and a prompt waiting for you to log in.</p>
+<p id="ch11Section_5_2d"></a>The login is different from a graphical login, in that you have to hit the <span class="emphasis"><em>Enter</em></span> key after providing your user name, because there are no buttons on the screen that you can click with the mouse. Then you should type your password, followed by another <span class="emphasis"><em>Enter</em></span>. You will not see any indication that you are entering something, not even an asterisk, and you won't see the cursor move. But this is normal on Linux and is done for security
+reasons.</p>
+<p id="ch11Section_5_2e"></a>When the system has accepted you as a valid user, you may get some more information, called the <span class="emphasis"><em>message of the day</em></span>, which can be anything. Additionally, it is popular on UNIX systems to display a fortune cookie, which contains some general wise or unwise (this is up to you) thoughts. After that, you will be given a shell, indicated with the same prompt that you would get in graphical mode.</p>
+<p id="ch11Section_5_2f"></a>Also in text mode: log in as root only to do setup and configuration that absolutely requires administrator privileges, such as adding users, installing software packages, and performing network and other system configuration. Once you are finished, immediately leave the special account and resume your work as a non−privileged user.</p>
+<p id="ch11Section_5_30"></a>Logging out is done by entering the <span class="emphasis"><em>logout</em></span> command, followed by Enter. You are successfully disconnected from the system when you see the login screen again.Don't power−off the computer after logging out. It is not meant to be shut off without application of the proper procedures for halting the system. Powering it off without going through the halting process might cause severe damage!</p>
+</div>
+</div>
+</div>
+<div class="section" title="3. Basic Commands">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2503518"></a>3. Basic Commands</h2></div></div></div>
+<div class="section" title="3.1. ls">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503526"></a>3.1. ls</h3></div></div></div>
+<p id="ch11Section_5_31"></a>When invoked without any arguments, <span class="emphasis"><em>ls</em></span> lists the files in the current working directory. A directory that is not the current working directory can be specified and ls will list the files there. The user also may specify any list of files and directories. In this case, all files and all contents of specified directories will be listed. The name <span class="emphasis"><em>ls</em></span> is derived from <span class="emphasis"><em>list segments</em></span> which was used in earlier systems.</p>
+<p id="ch11Section_5_32"></a>Files whose names start with "." are not listed, unless the <span class="emphasis"><em>-a</em></span> flag is specified or the files are specified explicitly.</p>
+<p id="ch11Section_5_33"></a>Without options, <span class="emphasis"><em>ls</em></span> displays files in a bare format. This bare format however makes it difficult to establish the type, permissions, and size of the files. The most common options to reveal this information or change the list of files are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_34"></a><span class="emphasis"><em>-l</em></span> long format, displaying Unix file types, permissions, number of hard links, owner, group, size, date, and filename</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_35"></a><span class="emphasis"><em>-F</em></span> appends a character revealing the nature of a file, for example, * for an executable, or / for a directory. Regular files have no suffix.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_36"></a><span class="emphasis"><em>-a</em></span> lists all files in the given directory, including those whose names start with "." (which are hidden files in Unix). By default, these files are excluded from the list.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_37"></a><span class="emphasis"><em>-R</em></span> recursively lists subdirectories. The command ls -R / would therefore list all files.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_38"></a><span class="emphasis"><em>-d</em></span> shows information about a symbolic link or directory, rather than about the link's target or listing the contents of a directory.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_39"></a><span class="emphasis"><em>-t</em></span> sort the list of files by modification time.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_3a"></a><span class="emphasis"><em>-h</em></span> print sizes in human readable format. (e.g., 1K, 234M, 2G, etc.)</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_3b"></a>In some environments, providing the option <span class="emphasis"><em>--color</em></span> (for GNU ls) or <span class="emphasis"><em>-G</em></span> (FreeBSD ls) causes ls to highlight different types of files with different colors, instead of with characters as <span class="emphasis"><em>-F</em></span> would. To determine what color to use for a file, GNU <span class="emphasis"><em>ls</em></span> checks the Unix file type, the file permissions, and the file extension, while FreeBSD <span class="emphasis"><em>ls</em></span> checks only the Unix file type and file permissions.:</p>
+<pre class="programlisting">$ ls
+jeeves.rst psmith.html blandings.html
+$ ls -l
+drwxr--r--   1 plum  editors   4096  jeeves
+-rw-r--r--   1 plum  editors  30405  psmith
+-r-xr-xr-x   1 plum  plum      8460  blandings</pre>
+<p id="ch11Section_5_3c"></a>Here "$" actually is the beginning of the prompt. This is typical in most Unix-based systems.</p>
+</div>
+<div class="section" title="3.2. date">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503688"></a>3.2. date</h3></div></div></div>
+<p id="ch11Section_5_3d"></a>The Unix date command displays the time and date. The super-user can use it to set the system clock.</p>
+<p id="ch11Section_5_3e"></a>With no options, the date command displays the current date and time, including the abbreviated day name, abbreviated month name, day of the month, the time separated by colons, the timezone name, and the year. For example:</p>
+<pre class="programlisting">$date
+Tue Sep  8 12:01:45 IST 2009</pre>
+<p id="ch11Section_5_3f"></a>On some systems to set the current date and time to September 8, 2004 01:22 you type:</p>
+<pre class="programlisting">$date --set="20040908 01:22"</pre>
+<p id="ch11Section_5_40"></a>In order to view the various options for the <span class="emphasis"><em>date</em></span> command, type:</p>
+<pre class="programlisting">$man date</pre>
+<p id="ch11Section_5_41"></a>This will take you to the "Manual" page comprising of all the details on the <span class="emphasis"><em>date</em></span> command. You can return to the terminal from the "man" page by pressing the <span class="emphasis"><em>Esc</em></span> key in the keyboard and typing ":q" in that order.</p>
+</div>
+<div class="section" title="3.3. cd">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503749"></a>3.3. cd</h3></div></div></div>
+<p id="ch11Section_5_42"></a>This stands for "change directory". When one wants to go up to the parent directory, bypassing the tree of directories one has entered, “ cd ..” can be used.</p>
+<p id="ch11Section_5_43"></a>One dot '.' represents the current directory while two dots '..' represent the parent directory.</p>
+<p id="ch11Section_5_44"></a>“ cd -” will return you to the previous directory (a bit like an “undo”).</p>
+<p id="ch11Section_5_45"></a>You can also use cd absolute path or cd relative path (see below):</p>
+<p id="ch11Section_5_46"></a>Absolute paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch11Section_5_47"></a>An “ absolute path” is easily recognised from the leading forward slash, /. The / means that you start at the top level directory and continue down.</p>&lt;/block_quote&gt;</span><p id="ch11Section_5_48"></a>For example to get to /boot/grub you would type:</p>
+<pre class="programlisting">$cd /boot/grub</pre>
+<p id="ch11Section_5_49"></a>This is an absolute path because you start at the top of the hierarchy and go downwards from there (it doesn't matter where in the filesystem you were when you typed the command).</p>
+<p id="ch11Section_5_4a"></a>Relative paths:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch11Section_5_4b"></a>A “ relative path” doesn't have a preceding slash. Use a relative path when you start from a directory below the top level directory structure. This is dependent on where you are in the filesystem.</p>
+<p id="ch11Section_5_4c"></a>For example if you are in root's home directory and want to get to /root/music, you type:</p>
+<pre class="programlisting">$ cd music</pre>&lt;/block_quote&gt;</span><p id="ch11Section_5_4d"></a>Please note that there is no / using the above cd command. Using a / would cause this to be an absolute path, working from the top of the hierarchy downward.</p>
+</div>
+<div class="section" title="3.4. who">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503851"></a>3.4. who</h3></div></div></div>
+<p id="ch11Section_5_4e"></a>The standard Unix command <span class="emphasis"><em>who</em></span> displays a list of users who are currently logged into a computer.</p>
+<p id="ch11Section_5_4f"></a>The <span class="emphasis"><em>who</em></span> command is related to the command <span class="emphasis"><em>w</em></span>, which provides the same information but also displays additional data and statistics.:</p>
+<pre class="programlisting">$who
+beeblebrox tty7         2009-09-08 10:50 (:0)
+beeblebrox pts/0        2009-09-08 11:25 (:0.0)
+dumbledore pts/1        2009-09-08 18:11 (potter.xyz.in)
+beeblebrox pts/2        2009-09-08 18:53 (:0.0)</pre>
+<p id="ch11Section_5_50"></a>The command can be invoked with the arguments <span class="emphasis"><em>am i</em></span> or <span class="emphasis"><em>am I</em></span> (so it is invoked as <span class="emphasis"><em>who am i</em></span> or * who am I*), showing information about the current terminal only (see the <span class="emphasis"><em>-m</em></span> option below, of which this invocation is equivalent).</p>
+<p id="ch11Section_5_51"></a>In order to find out the various options that can be appended to the <span class="emphasis"><em>who</em></span> command, check the <span class="emphasis"><em>man</em></span> page by typing out the following in the terminal:</p>
+<pre class="programlisting">$man who</pre>
+<p id="ch11Section_5_52"></a>This will take you to the "Manual" page containing details about the <span class="emphasis"><em>who</em></span> command</p>
+</div>
+<div class="section" title="3.5. mkdir">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2503933"></a>3.5. mkdir</h3></div></div></div>
+<p id="ch11Section_5_53"></a>This command is used to make a new directory. Normal usage is as straightforward as follows:</p>
+<pre class="programlisting">$mkdir name_of_directory</pre>
+<p id="ch11Section_5_54"></a>Where <span class="emphasis"><em>name_of_directory</em></span> is the name of the directory one wants to create. When typed as above (ie. normal usage), the new directory would be created within the current directory. On Unix, multiple directories can be specified, and <span class="emphasis"><em>mkdir</em></span> will try to create all of them.</p>
+<div class="section" title="3.5.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2503964"></a>3.5.1. Options</h4></div></div></div>
+<p id="ch11Section_5_55"></a>On Unix-like operating systems, <span class="emphasis"><em>mkdir</em></span> takes options. Three of the most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_56"></a><span class="emphasis"><em>-p</em></span>: will also create all directories leading up to the given directory that do not exist already. If the given directory already exists, ignore the error.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_57"></a><span class="emphasis"><em>-v</em></span>: display each directory that mkdir creates. Most often used with -p.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_58"></a><span class="emphasis"><em>-m</em></span>: specify the octal permissions of directories created by mkdir.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_59"></a><span class="emphasis"><em>-p</em></span> is most often used when using mkdir to build up complex directory hierarchies, in case a necessary directory is missing or already there. -m is commonly used to lock down temporary directories used by shell scripts.</p>
+</div>
+<div class="section" title="3.5.2. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2504026"></a>3.5.2. Examples</h4></div></div></div>
+<p id="ch11Section_5_5a"></a>An example of <span class="emphasis"><em>-p</em></span> in action is:</p>
+<pre class="programlisting">$mkdir -p /tmp/a/b/c</pre>
+<p id="ch11Section_5_5b"></a>If <span class="emphasis"><em>/tmp/a</em></span> exists but <span class="emphasis"><em>/tmp/a/b</em></span> does not, mkdir will create <span class="emphasis"><em>/tmp/a/b</em></span> before creating <span class="emphasis"><em>/tmp/a/b/c</em></span>.</p>
+<p id="ch11Section_5_5c"></a>And an even more powerful command, creating a full tree at once (this however is a Shell extension, nothing mkdir does itself):</p>
+<pre class="programlisting">$mkdir -p tmpdir/{trunk/sources/{includes,docs},branches,tags}</pre>
+<p id="ch11Section_5_5d"></a>This will create:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;tmpdir  - branches&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_5e"></a>tag</p></li>
+<li class="listitem" style="list-style-type: *"><span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;trunk - sources - includes&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*"><li class="listitem" style="list-style-type: *"><p id="ch11Section_5_5f"></a>docs</p></li></ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span></li>
+</ul></div>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span>
+</div>
+</div>
+</div>
+<div class="section" title="4. Getting Help">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2504112"></a>4. Getting Help</h2></div></div></div>
+<div class="section" title="4.1. apropos and whatis">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2504120"></a>4.1. apropos and whatis</h3></div></div></div>
+<p id="ch11Section_5_60"></a>This is a command to search the manual pages files in Unix and Unix-like operating systems.</p>
+<pre class="programlisting">$ apropos grep
+egrep       egrep (1)       Search a file for a pattern using full regular expressions
+fgrep       fgrep (1)       Search a file for a fixed-character string
+fmlgrep     fmlgrep (1)     Search a file for a pattern
+grep        grep (1)        Search a file for a pattern
+gzgrep      gzgrep (1)      Search a possibly compressed file for a regular expression
+nisgrep     nismatch (1)    Utilities for searching NIS+ tables
+pgrep       pgrep (1)       Find or signal a process by name or other attribute
+zgrep       zgrep (1)       Search a possibly compressed file for a regular expression
+...</pre>
+<p id="ch11Section_5_61"></a>In this example, the user uses <span class="emphasis"><em>apropos</em></span> to search for the string "grep", and apropos returns the indicated <span class="emphasis"><em>man</em></span> pages that include the term "grep".</p>
+<p id="ch11Section_5_62"></a>A short index of explanations for commands is available using the <span class="emphasis"><em>whatis</em></span> command, like in the examples below:</p>
+<pre class="programlisting">$whatis ls
+ls (1)           - list directory contents</pre>
+<p id="ch11Section_5_63"></a>This displays short information about a command, and the first section in the collection of man pages that contains an appropriate page.</p>
+<p id="ch11Section_5_64"></a>If you don't know where to get started and which man page to read, <span class="emphasis"><em>apropos</em></span> gives more information. Say that you do not know how to start a browser, then you could enter the following command:</p>
+<pre class="programlisting">$apropos browser
+gmusicbrowser (1)    - Jukebox for large collections of audio files
+infobrowser (1)      - read Info documents
+libsmbclient (7)     - An extension library for browsers and that               can be used...
+opera (1)            - a standards-compliant graphical Web browser
+sensible-browser (1) - sensible editing, paging, and web browsing
+smbtree (1)          - A text based smb network browser
+tvtk_doc (1)         - A GUI based TVTK documentation search browser.
+viewres (1)          - graphical class browser for Xt
+w3m (1)              - a text based Web browser and pager
+www-browser (1)      - a text based Web browser and pager
+...</pre>
+</div>
+<div class="section" title="4.2. man">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2502619"></a>4.2. man</h3></div></div></div>
+<p id="ch11Section_5_65"></a>Man pages (short for "manual pages") are the extensive documentation that comes preinstalled with almost all substantial Unix and Unix-like operating systems. The Unix command used to display them is <span class="emphasis"><em>man</em></span>. Each page is a self-contained document.</p>
+<p id="ch11Section_5_66"></a>To read a manual page for a Unix command, one can use:</p>
+<pre class="programlisting">$ man &lt;command_name&gt;</pre>
+<p id="ch11Section_5_67"></a>at a shell prompt; for example, "man ftp". In order to simplify navigation through the output, <span class="emphasis"><em>man</em></span> generally uses the less terminal pager.</p>
+<p id="ch11Section_5_68"></a>Pages are traditionally referred to using the notation "name(section)"; for example, ftp(1). The same page name may appear in more than one section of the manual, this can occur when the names of system calls, user commands, or macro packages coincide. Two examples are <span class="emphasis"><em>man(1)</em></span> and <span class="emphasis"><em>man(7)</em></span>, or <span class="emphasis"><em>exit(2)</em></span> and <span class="emphasis"><em>exit(3)</em></span>. The syntax for accessing the non-default manual section varies between different man implementations. On Linux and <span class="emphasis"><em>BSD, for example, the syntax for reading *printf(3)</em></span> is:</p>
+<pre class="programlisting">$man 3 printf</pre>
+<p id="ch11Section_5_69"></a>Another example:</p>
+<pre class="programlisting">$man man</pre>
+<p id="ch11Section_5_6a"></a>The previous example will take you to the "Manual" page entry about manual pages!</p>
+<div class="section" title="4.2.1. Layout">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2504422"></a>4.2.1. Layout</h4></div></div></div>
+<p id="ch11Section_5_6b"></a>All man pages follow a common layout that is optimized for presentation on a simple ASCII text display, possibly without any form of highlighting or font control. Sections present may include:</p>
+<span style="color: red">&lt;definition_list&gt;<span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;NAME&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch11Section_5_6c"></a>The name of the command or function, followed by a one-line description of what it does.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SYNOPSIS&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch11Section_5_6d"></a>In the case of a command, you get a formal description of how to run it and what command line options it takes. For program functions, a list of the parameters the function takes and which header file contains its definition. For experienced users, this may be all the documentation they need.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;DESCRIPTION&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch11Section_5_6e"></a>A textual description of the functioning of the command or function.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;EXAMPLES&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch11Section_5_6f"></a>Some examples of common usage.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span><span style="color: red">&lt;definition_list_item&gt;<span style="color: red">&lt;term&gt;SEE ALSO&lt;/term&gt;</span><span style="color: red">&lt;definition&gt;<p id="ch11Section_5_70"></a>A list of related commands or functions.</p>&lt;/definition&gt;</span>&lt;/definition_list_item&gt;</span>&lt;/definition_list&gt;</span><p id="ch11Section_5_71"></a>Other sections may be present, but these are not well standardized across man pages. Common examples include: OPTIONS, EXIT STATUS, ENVIRONMENT, KNOWN BUGS, FILES, AUTHOR, REPORTING BUGS, HISTORY and COPYRIGHT.</p>
+<p id="ch11Section_5_72"></a>These days virtually every Unix command line application comes with its man page, and many Unix users perceive a lack of man pages as a sign of low quality; indeed, some projects, such as Debian, go out of their way to write man pages for programs lacking one. Few alternatives to <span class="emphasis"><em>man</em></span> have enjoyed much popularity, with the possible exception of the GNU project's "info" system, an early and simple hypertext system.</p>
+<p id="ch11Section_5_73"></a>However, the format of a single page for each application, the lack of classification within the sections and the relatively unsophisticated formatting facilities have motivated the development of alternative documentation systems, such as the previously mentioned "info" system.</p>
+<p id="ch11Section_5_74"></a>Most Unix GUI applications (particularly those built using the GNOME and KDE development environments) now provide end-user documentation in HTML and include embedded HTML viewers such as yelp for reading the help within the application.</p>
+<p id="ch11Section_5_75"></a>Usually the man pages are written in English. Translations into other languages can be also available on the system.</p>
+<p id="ch11Section_5_76"></a>The default format of the man pages is troff, with either the macro package man (appearance oriented) or on some systems mdoc (semantic oriented). This makes it possible to typeset a man page to PostScript, PDF and various other formats for viewing or printing.</p>
+</div>
+</div>
+<div class="section" title="4.3. info">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2504548"></a>4.3. info</h3></div></div></div>
+<p id="ch11Section_5_77"></a><span class="emphasis"><em>info</em></span> is a software utility which forms a hypertextual, multipage documentation and help viewer working on a command line interface, useful when there is no GUI available.</p>
+<p id="ch11Section_5_78"></a>The syntax is</p>
+<pre class="programlisting">$ info &lt;command_name&gt;</pre>
+<p id="ch11Section_5_79"></a><span class="emphasis"><em>info</em></span> processes info files, which are Texinfo formatted files, and presents the documentation as a tree, with simple commands to traverse the tree and to follow cross references. For instance</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_7a"></a><span class="emphasis"><em>n</em></span> goes to the next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_7b"></a><span class="emphasis"><em>p</em></span> goes to the previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_7c"></a><span class="emphasis"><em>u</em></span> goes to the upper page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_7d"></a><span class="emphasis"><em>l</em></span> goes to the last(visited) node</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_7e"></a>To follow a cross reference, the cursor can be moved over a link (a word preceded by a <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>) and enter pressed.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_7f"></a>info was initially written for use with GNU/Linux and then ported to other Unix-like operating systems.</p>
+</div>
+<div class="section" title="4.4. --help">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2504638"></a>4.4. --help</h3></div></div></div>
+<p id="ch11Section_5_80"></a>Most GNU commands support the --help, which gives a short explanation about how to use the command and a list of available options. Below is the output of this option with the <span class="emphasis"><em>cat</em></span> command:</p>
+<pre class="programlisting">$ userprompt@host: cat --help
+Usage: cat [OPTION] [FILE]...
+Concatenate FILE(s), or standard input, to standard output.
+
+  -A, --show-all           equivalent to -vET
+  -b, --number-nonblank    number nonempty output lines
+  -e                       equivalent to -vE
+  -E, --show-ends          display $ at end of each line
+  -n, --number             number all output lines
+  -s, --squeeze-blank      suppress repeated empty output lines
+  -t                       equivalent to -vT
+  -T, --show-tabs          display TAB characters as ^I
+  -u                       (ignored)
+  -v, --show-nonprinting   use ^ and M- notation, except for LFD and              TAB
+  --help     display this help and exit
+  --version  output version information and exit
+
+With no FILE, or when FILE is -, read standard input.
+
+Examples:
+  cat f - g  Output f's contents, then standard input, then g's           contents.
+  cat        Copy standard input to standard output.
+
+Report bugs to &lt;bug-coreutils@gnu.org&gt;.</pre>
+</div>
+</div>
+<div class="section" title="5. Basic file handling">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2504691"></a>5. Basic file handling</h2></div></div></div>
+<div class="section" title="5.1. cp">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2504700"></a>5.1. cp</h3></div></div></div>
+<p id="ch11Section_5_81"></a><span class="emphasis"><em>cp</em></span> is the command entered in a Unix shell to copy a file from one place to another, possibly on a different filesystem. The original file remains unchanged, and the new file may have the same or a different name.</p>
+<div class="section" title="5.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2504717"></a>5.1.1. Usage</h4></div></div></div>
+<p id="ch11Section_5_82"></a>To copy a file to another file:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ][ -- ] SourceFile TargetFile</pre>
+<p id="ch11Section_5_83"></a>To copy a file to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -r | -R ] [ -- ] SourceFile ...              TargetDirectory</pre>
+<p id="ch11Section_5_84"></a>To copy a directory to a directory:</p>
+<pre class="programlisting">$ cp [ -f ] [ -H ] [ -i ] [ -p ] [ -- ] { -r | -R }
+SourceDirectory ... TargetDirectory</pre>
+</div>
+<div class="section" title="5.1.2. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2504751"></a>5.1.2. Flags</h4></div></div></div>
+<p id="ch11Section_5_85"></a><span class="emphasis"><em>-f</em></span> (force) – specifies removal of the target file if it cannot be opened for write operations. The removal precedes any copying performed by the cp command.</p>
+<p id="ch11Section_5_86"></a><span class="emphasis"><em>-P</em></span> – makes the cp command copy symbolic links. The default is to follow symbolic links, that is, to copy files to which symbolic links point.</p>
+<p id="ch11Section_5_87"></a><span class="emphasis"><em>-i</em></span> (interactive) – prompts you with the name of a file to be overwritten. This occurs if the TargetDirectory or TargetFile parameter contains a file with the same name as a file specified in the SourceFile or SourceDirectory parameter. If you enter y or the locale's equivalent of y, the cp command continues. Any other answer prevents the cp command from overwriting the file.</p>
+<p id="ch11Section_5_88"></a><span class="emphasis"><em>-p</em></span> (preserve) – duplicates the following characteristics of each SourceFile/SourceDirectory in the corresponding TargetFile and/or TargetDirectory:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_89"></a>The time of the last data modification and the time of the last access.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_8a"></a>The user ID and group ID (only if it has permissions to do this)</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_8b"></a>The file permission bits and the SUID and SGID bits.</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_8c"></a><span class="emphasis"><em>-R</em></span> (recursive) – copy directories (recursively copying all the contents)</p>
+</div>
+<div class="section" title="5.1.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2504849"></a>5.1.3. Examples</h4></div></div></div>
+<p id="ch11Section_5_8d"></a>To make a copy of a file in the current directory, enter:</p>
+<pre class="programlisting">$ cp prog.c prog.bak</pre>
+<p id="ch11Section_5_8e"></a>This copies prog.c to prog.bak. If the prog.bak file does not already exist, the cp command creates it. If it does exist, the cp command replaces it with a copy of the prog.c file.</p>
+<p id="ch11Section_5_8f"></a>To copy a file in your current directory into another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod /home/books/hhgg</pre>
+<p id="ch11Section_5_90"></a>This copies the jones file to /home/books/hhgg/zaphod.</p>
+<p id="ch11Section_5_91"></a>To copy a file to a new file and preserve the modification date, time, and access control list associated with the source file, enter:</p>
+<pre class="programlisting">$ cp -p martin_luther_king martin_luther_king.jr</pre>
+<p id="ch11Section_5_92"></a>This copies the <span class="emphasis"><em>martin_luther_king</em></span> file to the <span class="emphasis"><em>martin_luther_king.jr</em></span> file. Instead of creating the file with the current date and time stamp, the system gives the <span class="emphasis"><em>martin_luther_king.jr</em></span> file the same date and time as the <span class="emphasis"><em>martin_luther_king</em></span> file. The <span class="emphasis"><em>martin_luther_king.jr</em></span> file also inherits the <span class="emphasis"><em>martin_luther_king</em></span> file's access control protection.</p>
+<p id="ch11Section_5_93"></a>To copy all the files in a directory to a new directory, enter:</p>
+<pre class="programlisting">$ cp /home/galactica/clients/* /home/hhgg/customers</pre>
+<p id="ch11Section_5_94"></a>This copies only the files in the clients directory to the customers directory.</p>
+<p id="ch11Section_5_95"></a>To copy a directory, including all its files and subdirectories, to another directory, enter:</p>
+<span style="color: red">&lt;block_quote&gt;<p id="ch11Section_5_96"></a>$ cp -R /home/hhgg/clients /home/hhgg/customers</p>&lt;/block_quote&gt;</span><p id="ch11Section_5_97"></a>This copies the clients directory, including all its files, subdirectories, and the files in those subdirectories, to the customers/clients directory.</p>
+<p id="ch11Section_5_98"></a>To copy a specific set of files of any extension to another directory, enter:</p>
+<pre class="programlisting">$ cp zaphod arthur ford /home/hhgg/clients</pre>
+<p id="ch11Section_5_99"></a>This copies the <span class="emphasis"><em>zaphod</em></span>, <span class="emphasis"><em>arthur</em></span>, and <span class="emphasis"><em>ford</em></span> files in your current working directory to the /home/hhgg/clients directory.</p>
+<p id="ch11Section_5_9a"></a>To use pattern-matching characters to copy files, enter:</p>
+<pre class="programlisting">$ cp programs/*.py .</pre>
+<p id="ch11Section_5_9b"></a>This copies the files in the programs directory that end with <span class="emphasis"><em>.py</em></span> to the current directory, signified by the single "." (dot). You must type a space between the <span class="emphasis"><em>py</em></span> and the final dot.</p>
+</div>
+</div>
+<div class="section" title="5.2. mv">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505011"></a>5.2. mv</h3></div></div></div>
+<p id="ch11Section_5_9c"></a><span class="emphasis"><em>mv</em></span> (short for move) is a Unix command that moves one or more files or directories from one place to another. The original file is deleted, and the new file may have the same or a different name. If possible (i.e. when the original and new files are on the same file system), <span class="emphasis"><em>mv</em></span> will rename the file instead. Write permission is required on all directories being modified.</p>
+<div class="section" title="5.2.1. Conflicting existing file">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505034"></a>5.2.1. Conflicting existing file</h4></div></div></div>
+<p id="ch11Section_5_9d"></a>In all cases, when a file is moved to have the name of an existing file (in the same directory), the existing file is deleted. If the existing file is not writable but is in a directory that is writable, then the mv command asks for confirmation if possible (i.e. if run from a terminal) before proceeding, unless the -f (force) option is used.</p>
+</div>
+<div class="section" title="5.2.2. Differences with copy and delete">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505054"></a>5.2.2. Differences with copy and delete</h4></div></div></div>
+<p id="ch11Section_5_9e"></a>Note that, usually, when moving files within the same volume, moving (and/or renaming) is not the same as simply copying and then deleting the original. When moving a file, the link is simply removed from the old parent directory and added to the new parent directory. However, the file itself is untouched (i.e. it has the same inodes and resides at the same place on the disk). For example, you cannot copy a file you cannot read, but you can move (and/or rename) it (provided you have write permission to its old and new parent directories). Also, suppose there is a non-empty directory you do not have write permission to. You cannot delete this directory (since you cannot delete its contents); but you can move (and/or rename) it. Also, since moving between filenames on a single volume does not involve copying, it is faster and does not place strain of lots of reads and writes on the disk. Moving files across different volumes, however, does necessitate copying and deleting.</p>
+</div>
+<div class="section" title="5.2.3. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505084"></a>5.2.3. Examples</h4></div></div></div>
+<pre class="programlisting">$ mv myfile mynewfilename    renames a file
+$ mv myfile otherfilename    renames a file and deletes the existing            file "myfile"
+$ mv myfile /myfile          moves 'myfile' from the current            directory to the root directory
+$ mv myfile dir/myfile       moves 'myfile' to 'dir/myfile' relative            to the current directory
+$ mv myfile dir              same as the previous command (the          filename is implied to be the same)
+$ mv myfile dir/myfile2      moves 'myfile' to dir and renames it to            'myfile2'
+$ mv foo bar baz dir         moves multiple files to directory dir
+$ mv --help                  shows a very concise help about the                syntax of the command
+$ man mv                     prints an extensive user manual for                'mv' in the terminal</pre>
+<p id="ch11Section_5_9f"></a>In all cases, the file or files being moved or renamed can be a directory.</p>
+<p id="ch11Section_5_a0"></a>Note that when the command is called with two arguments (as <span class="emphasis"><em>mv name1 name2</em></span> or <span class="emphasis"><em>mv name1 /dir/name2</em></span>), it can have three different effects, depending on whether <span class="emphasis"><em>name2</em></span> does not exist, is an existing file, or is an existing directory. If the user intends to refer to an existing directory, <span class="emphasis"><em>/.</em></span> (or in some Unix versions <span class="emphasis"><em>/</em></span> is sufficient) may be appended to the name to force the system to check this. To move a file to a new directory, the directory must be created first.</p>
+</div>
+</div>
+<div class="section" title="5.3. rm">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505142"></a>5.3. rm</h3></div></div></div>
+<p id="ch11Section_5_a1"></a><span class="emphasis"><em>rm</em></span> (short for "remove") is one of several basic Unix command lines that operates on files. It is used to delete files from a filesystem. The data is not actually destroyed. Only the index listing where the file is stored is destroyed, and the storage is made available for reuse. There are undelete utilities that will attempt to reconstruct the index and can bring the file back if the parts were not reused.</p>
+<p id="ch11Section_5_a2"></a>Here's example to remove a file named "foo" from a directory, here shown with the -i option:</p>
+<pre class="programlisting">$ rm -i foo
+remove foo? y</pre>
+<div class="section" title="5.3.1. Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505172"></a>5.3.1. Options</h4></div></div></div>
+<p id="ch11Section_5_a3"></a>Common options that rm accepts include:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_a4"></a><span class="emphasis"><em>-r</em></span>, which removes directories, removing the contents recursively beforehand (so as not to leave files without a directory to reside in) ("recursive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_a5"></a><span class="emphasis"><em>-i</em></span>, which asks for every deletion to be confirmed ("interactive")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_a6"></a><span class="emphasis"><em>-f</em></span>, which ignores non-existent files and overrides any confirmation prompts ("force")</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_a7"></a><span class="emphasis"><em>-v</em></span>, which shows what is being removed as it happens ("verbose")</p></li>
+</ul></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_a8"></a><span class="emphasis"><em>rm</em></span> is often aliased to "rm -i" so as to avoid accidental deletion of files. If a user still wishes to delete a large number of files without confirmation, they can manually cancel out the -i argument by adding the -f option (as the option specified later on the expanded command line "rm -i -f" takes precedence).</p>
+<p id="ch11Section_5_a9"></a><span class="emphasis"><em>rm -rf</em></span> (variously, rm -rf /, rm -rf <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span>, and others) is frequently used in jokes and anecdotes about Unix disasters. The rm -rf variant of the command, if run by a superuser on the root directory, would cause the contents of every writable mounted filesystem on the computer to be deleted.</p>
+<p id="ch11Section_5_aa"></a><span class="emphasis"><em>rm</em></span> is often used in conjunction with xargs to supply a list of files to delete:</p>
+<pre class="programlisting">xargs rm &lt; filelist</pre>
+<p id="ch11Section_5_ab"></a>When <span class="emphasis"><em>rm</em></span> is used on a symbolic link, it deletes the link, but does not affect the target of the link.</p>
+</div>
+<div class="section" title="5.3.2. Permissions">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505274"></a>5.3.2. Permissions</h4></div></div></div>
+<p id="ch11Section_5_ac"></a>Usually, on most filesystems, deleting a file requires write permission on the parent directory (and execute permission, in order to enter the directory in the first place). (Note that, confusingly for beginners, permissions on the file itself are irrelevant. However, GNU rm asks for confirmation if a write-protected file is to be deleted, unless the -f option is used.)</p>
+<p id="ch11Section_5_ad"></a>To delete a directory (with rm -r), one must delete all of its contents recursively. This requires that one must have read and write and execute permission to that directory (if it's not empty) and all non-empty subdirectories recursively (if there are any). The read permissions are needed to list the contents of the directory in order to delete them. This sometimes leads to an odd situation where a non-empty directory cannot be deleted because one doesn't have write permission to it and so cannot delete its contents; but if the same directory were empty, one would be able to delete it.</p>
+<p id="ch11Section_5_ae"></a>If a file resides in a directory with the sticky bit set, then deleting the file requires one to be the owner of the file.</p>
+</div>
+</div>
+</div>
+<div class="section" title="6. Command Line Arguments">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2505313"></a>6. Command Line Arguments</h2></div></div></div>
+<p id="ch11Section_5_af"></a>In computer command line interfaces, a command line argument is an argument sent to a program being called. In general, a program can take any number of command line arguments, which may be necessary for the program to run, or may even be ignored, depending on the function of that program.</p>
+<p id="ch11Section_5_b0"></a>For example, in Unix and Unix-like environments, an example of a command-line argument is:</p>
+<pre class="programlisting">rm file.s</pre>
+<p id="ch11Section_5_b1"></a>"file.s" is a command line argument which tells the program rm to remove the file "file.s".</p>
+<p id="ch11Section_5_b2"></a>Programming languages such as C, C++ and Java allow a program to interpret the command line arguments by handling them as string parameters in the main function.</p>
+<p id="ch11Section_5_b3"></a>A command line option or simply <span class="emphasis"><em>option</em></span> (also known as a command line parameter, flag, or a switch) is an indication by a user that a computer program should change its default output.</p>
+<p id="ch11Section_5_b4"></a>Long options are introduced via "--", and are typically whole words. For example, <span class="emphasis"><em>ls --long --classify --all</em></span>. Arguments to long options are provided with "=", as <span class="emphasis"><em>ls --block-size=1024</em></span>. Some Unix programs use long options with single dashes, for example MPlayer as in <span class="emphasis"><em>mplayer -nosound</em></span>.</p>
+<p id="ch11Section_5_b5"></a>Linux also uses "--" to terminate option lists. For example, an attempt to delete a file called <span class="emphasis"><em>-file1</em></span> by using <span class="emphasis"><em>rm -file1</em></span> may produce an error, since rm may interpret <span class="emphasis"><em>-file1</em></span> as a command line switch. Using <span class="emphasis"><em>rm -- -file1</em></span> removes ambiguity.</p>
+</div>
+<div class="section" title="7. Basic Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2505405"></a>7. Basic Text Processing</h2></div></div></div>
+<div class="section" title="7.1. head">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505414"></a>7.1. head</h3></div></div></div>
+<p id="ch11Section_5_b6"></a><span class="emphasis"><em>head</em></span> is a program on Unix and Unix-like systems used to display the first few lines of a text file or piped data. The command syntax is:</p>
+<pre class="programlisting">$ head [options] &lt;file_name&gt;</pre>
+<p id="ch11Section_5_b7"></a>By default, <span class="emphasis"><em>head</em></span> will print the first 10 lines of its input to the standard output. The number of lines printed may be changed with a command line option. The following example shows the first 20 lines of filename:</p>
+<pre class="programlisting">$ head -n 20 filename</pre>
+<p id="ch11Section_5_b8"></a>This displays the first 5 lines of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ head -n 5 foo*</pre>
+<p id="ch11Section_5_b9"></a>Some versions omit the n and just let you say -5.</p>
+<div class="section" title="7.1.1. Flags">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505465"></a>7.1.1. Flags</h4></div></div></div>
+<pre class="programlisting">-c &lt;x number of bytes&gt; Copy first x number of bytes.</pre>
+<p id="ch11Section_5_ba"></a>Other options: <span class="emphasis"><em>sed</em></span></p>
+<p id="ch11Section_5_bb"></a>Many early versions of Unix did not have this command, and so documentation and books had <span class="emphasis"><em>sed</em></span> do this job:</p>
+<pre class="programlisting">sed 5q foo</pre>
+<p id="ch11Section_5_bc"></a>This says to print every line (implicit), and quit after the fifth.</p>
+</div>
+</div>
+<div class="section" title="7.2. tail">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505500"></a>7.2. tail</h3></div></div></div>
+<p id="ch11Section_5_bd"></a><span class="emphasis"><em>tail</em></span> is a program on Unix and Unix-like systems used to display the last few lines of a text file or piped data.</p>
+<p id="ch11Section_5_be"></a>The command-syntax is:</p>
+<pre class="programlisting">$ tail [options] &lt;file_name&gt;</pre>
+<p id="ch11Section_5_bf"></a>By default, <span class="emphasis"><em>tail</em></span> will print the last 10 lines of its input to the standard output. With command line options the number of lines printed and the printing units (lines, blocks or bytes) may be changed. The following example shows the last 20 lines of filename:</p>
+<pre class="programlisting">$ tail -n 20 filename</pre>
+<p id="ch11Section_5_c0"></a>This example shows the last 15 bytes of all files starting with <span class="emphasis"><em>foo</em></span>:</p>
+<pre class="programlisting">$ tail -c 15 foo*</pre>
+<p id="ch11Section_5_c1"></a>This example shows all lines of filename from the second line onwards:</p>
+<pre class="programlisting">$ tail -n +2 filename</pre>
+<p id="ch11Section_5_c2"></a>Using an older syntax (still used in Sun Solaris as the -n option is not supported), the last 20 lines and the last 50 bytes of filename can be shown with the following command:</p>
+<pre class="programlisting">$ tail -20 filename
+$ tail -50c filename</pre>
+<p id="ch11Section_5_c3"></a>However this syntax is now obsolete and does not conform with the POSIX 1003.1-2001 standard. Even if still supported in current versions, when used with other options (like -f, see below), these switches could not work at all.</p>
+<div class="section" title="7.2.1. File monitoring">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2505578"></a>7.2.1. File monitoring</h4></div></div></div>
+<p id="ch11Section_5_c4"></a><span class="emphasis"><em>tail</em></span> has a special command line option <span class="emphasis"><em>-f</em></span> (follow) that allows a file to be monitored. Instead of displaying the last few lines and exiting, tail displays the lines and then monitors the file. As new lines are added to the file by another process, tail updates the display. This is particularly useful for monitoring log files. The following command will display the last 10 lines of messages and append new lines to the display as new lines are added to messages:</p>
+<pre class="programlisting">$ tail -f /var/adm/messages</pre>
+<p id="ch11Section_5_c5"></a>To interrupt tail while it is monitoring, break-in with <span class="emphasis"><em>Ctrl+C</em></span>. This command can be run "in the background" with &amp;, see job control.</p>
+<p id="ch11Section_5_c6"></a>If you have a command's result to monitor, you can use the <span class="emphasis"><em>watch</em></span> command.</p>
+</div>
+</div>
+<div class="section" title="7.3. cut">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505634"></a>7.3. cut</h3></div></div></div>
+<p id="ch11Section_5_c7"></a>In computing, <span class="emphasis"><em>cut</em></span> is a Unix command line utility which is used to extract sections from each line of input — usually from a file.</p>
+<p id="ch11Section_5_c8"></a>Extraction of line segments can typically be done by <span class="emphasis"><em>bytes (-b), characters (-c)</em></span>, or <span class="emphasis"><em>fields (-f)</em></span> separated by a <span class="emphasis"><em>delimiter (-d — the tab character by default)</em></span>. A range must be provided in each case which consists of one of N, N-M, N- (N to the end of the line), or -M (beginning of the line to M), where N and M are counted from 1 (there is no zeroth value). Since version 6, an error is thrown if you include a zeroth value. Prior to this the value was ignored and assumed to be 1.</p>
+<p id="ch11Section_5_c9"></a>Assuming a file named file containing the lines:</p>
+<pre class="programlisting">foo:bar:baz:qux:quux
+one:two:three:four:five:six:seven
+alpha:beta:gamma:delta:epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+<p id="ch11Section_5_ca"></a>To output the fourth through tenth characters of each line:</p>
+<pre class="programlisting">$ cut -c 4-10 file</pre>
+<p id="ch11Section_5_cb"></a>This gives the output:</p>
+<pre class="programlisting">:bar:ba
+:two:th
+ha:beta</pre>
+<p id="ch11Section_5_cc"></a>To output the fifth field through the end of the line of each line using the colon character as the field delimiter:</p>
+<pre class="programlisting">$ cut -d : -f 5- file</pre>
+<p id="ch11Section_5_cd"></a>This gives the output:</p>
+<pre class="programlisting">quux
+five:six:seven
+epsilon:zeta:eta:teta:iota:kappa:lambda:mu</pre>
+</div>
+<div class="section" title="7.4. paste">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505719"></a>7.4. paste</h3></div></div></div>
+<p id="ch11Section_5_ce"></a><span class="emphasis"><em>paste</em></span> is a Unix command line utility which is used to join files horizontally (parallel merging) by outputting lines consisting of the sequentially corresponding lines of each file specified, separated by tabs, to the standard output. It is effectively the horizontal equivalent to the utility <span class="emphasis"><em>cat</em></span> command which operates on the vertical plane of two or more files.</p>
+<p id="ch11Section_5_cf"></a>To paste several columns of data together into the file <span class="emphasis"><em>www</em></span> from files <span class="emphasis"><em>who</em></span>, <span class="emphasis"><em>where</em></span>, and <span class="emphasis"><em>when</em></span>:</p>
+<pre class="programlisting">$ paste who where when &gt; www</pre>
+<p id="ch11Section_5_d0"></a>If the files contain:</p>
+<table summary="paste" border="1"><colgroup>
+<col width="11">
+<col width="12">
+<col width="12">
+</colgroup></table>
+<p id="ch11Section_5_dd"></a>This creates the file named <span class="emphasis"><em>www</em></span> containing:</p>
+<pre class="programlisting">Batman            GothamCity       January 3
+Trillian          Andromeda        February 4
+Jeeves            London           March 19</pre>
+</div>
+</div>
+<div class="section" title="8. Shell Meta Characters">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2505852"></a>8. Shell Meta Characters</h2></div></div></div>
+<p id="ch11Section_5_de"></a>Unix recognizes certain special characters, called "meta characters," as command directives. The shell meta characters are recognized anywhere they appear in the command line, even if they are not surrounded by blank space. For that reason, it is safest to only use the characters A-Z, a-z, 0-9, and the period, dash, and underscore characters when naming files and directories on Unix. If your file or directory has a shell meta character in the name, you will find it difficult to use the name in a shell command.</p>
+<p id="ch11Section_5_df"></a>The shell meta characters include:</p>
+<p id="ch11Section_5_e0"></a>/ &lt; &gt; ! $ % ^ &amp; * | { } [ ] " ' ` ~ ;</p>
+<p id="ch11Section_5_e1"></a>Different shells may differ in the meta characters recognized.</p>
+<p id="ch11Section_5_e2"></a>As an example,</p>
+<pre class="programlisting">$ ls file.*</pre>
+<p id="ch11Section_5_e3"></a>run on a directory containing the files file, file.c, file.lst, and myfile would list the files file.c and file.lst. However,:</p>
+<pre class="programlisting">$ ls file.?</pre>
+<p id="ch11Section_5_e4"></a>run on the same directory would only list file.c because the ? only matches one character, no more, no less. This can save you a great deal of typing time. For example, if there is a file called california_cornish_hens_with_wild_rice and no other files whose names begin with 'c', you could view the file without typing the whole name by typing this:</p>
+<pre class="programlisting">$ more c*</pre>
+<p id="ch11Section_5_e5"></a>because the c* matches that long file name.</p>
+<p id="ch11Section_5_e6"></a>Filenames containing metacharacters can pose many problems and should never be intentionally created. If you do find that you've created a file with metacharacters, and you would like to remove it, you have three options. You may use wildcards to match metacharacter, use the  to directly enter the filename, or put the command in double quotes (except in the case of double quotes within the file name, these must be captured with one of the first two methods). For example, deleting a file named <span style="color: red">&lt;title_reference&gt;"``*`|more&lt;/title_reference&gt;</span>"` can be accomplished with:</p>
+<pre class="programlisting">$ rm ??more</pre>
+<p id="ch11Section_5_e7"></a>or:</p>
+<pre class="programlisting">$ rm $\backslash$*$\backslash$|more</pre>
+<p id="ch11Section_5_e8"></a>or:</p>
+<pre class="programlisting">$ rm ''*|more''</pre>
+</div>
+<div class="section" title="9. Looking At Files">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2505959"></a>9. Looking At Files</h2></div></div></div>
+<div class="section" title="9.1. cat">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2505967"></a>9.1. cat</h3></div></div></div>
+<p id="ch11Section_5_e9"></a>The <span class="emphasis"><em>cat</em></span> command is a standard Unix program used to concatenate and display files. The name is from "catenate", a synonym of <span class="emphasis"><em>concatenate</em></span>.</p>
+<p id="ch11Section_5_ea"></a>The Single Unix Specification specifies the behavior that the contents of each of the files given in sequence as arguments will be written to the standard output in the same sequence, and mandates one option, -u, where each byte is printed as it is read.</p>
+<p id="ch11Section_5_eb"></a>If the filename is specified as -, then <span class="emphasis"><em>cat</em></span> will read from standard input at that point in the sequence. If no files are specified, <span class="emphasis"><em>cat</em></span> will read from standard input entered.</p>
+<div class="section" title="9.1.1. Jargon File Definition">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506010"></a>9.1.1. Jargon File Definition</h4></div></div></div>
+<p id="ch11Section_5_ec"></a>The Jargon File version 4.4.7 lists this as the definition of <span class="emphasis"><em>cat</em></span>:</p>
+<pre class="programlisting">1. To spew an entire file to the screen or some other output sink without
+     pause (syn. blast).
+
+2. By extension, to dump large amounts of data at an unprepared target or
+     with no intention of browsing it carefully. Usage: considered silly.
+     Rare outside Unix sites. See also dd, BLT.
+
+     Among Unix fans, *cat(1)* is considered an excellent example of
+     user-interface design, because it delivers the file contents without
+     such verbosity as spacing or headers between the files, and because
+     it does not require the files to consist of lines of text, but works
+     with any sort of data.
+
+     Among Unix critics, *cat(1)* is considered the canonical example of
+     bad user-interface design, because of its woefully unobvious name.
+     It is far more often used to blast a single file to standard output
+     than to concatenate two or more files. The name cat for the former
+     operation is just as unintuitive as, say, LISP's cdr.
+
+     Of such oppositions are holy wars made...</pre>
+</div>
+<div class="section" title="9.1.2. Useless Use of 'cat'">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506066"></a>9.1.2. Useless Use of 'cat'</h4></div></div></div>
+<p id="ch11Section_5_ed"></a>UUOC (from comp.unix.shell on Usenet) stands for “Useless Use of cat”. As it is observed on <span class="emphasis"><em>comp.unix.shell</em></span>, “The purpose of cat is to concatenate (or 'catenate') files. If it's only one file, concatenating it with nothing at all is a waste of time, and costs you a process.”</p>
+<p id="ch11Section_5_ee"></a>Nevertheless one sees people doing:</p>
+<pre class="programlisting">$ cat file | some_command and its args ...</pre>
+<p id="ch11Section_5_ef"></a>instead of the equivalent and cheaper:</p>
+<pre class="programlisting">&lt;file some_command and its args ...</pre>
+<p id="ch11Section_5_f0"></a>or (equivalently and more classically):</p>
+<pre class="programlisting">some_command and its args ... &lt;file</pre>
+<p id="ch11Section_5_f1"></a>Since 1995, occasional awards for UUOC have been given out. The activity of fixing instances of UUOC is sometimes called 'demoggification'.</p>
+<p id="ch11Section_5_f2"></a>Amongst many, it is still considered safer to use <span class="emphasis"><em>cat</em></span> for such cases given that the &lt; and &gt; keys are next to each other in many popular keyboard mappings. While the risk might be low, the impact of using &gt; instead of &lt; can be high and prohibitive.</p>
+</div>
+<div class="section" title="9.1.3. zcat">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506137"></a>9.1.3. zcat</h4></div></div></div>
+<p id="ch11Section_5_f3"></a><span class="emphasis"><em>zcat</em></span> is a Unix program similar to <span class="emphasis"><em>cat</em></span>, that decompresses individual files and concatenates them to standard output. Traditionally <span class="emphasis"><em>zcat</em></span> operated on files compressed by compress but today it is usually able to operate on <span class="emphasis"><em>gzip</em></span> or even <span class="emphasis"><em>bzip2</em></span> archives. On such systems, it is equivalent to <span class="emphasis"><em>gunzip -c</em></span></p>
+</div>
+</div>
+<div class="section" title="9.2. more">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2506170"></a>9.2. more</h3></div></div></div>
+<p id="ch11Section_5_f4"></a>In computing, <span class="emphasis"><em>more</em></span> is a command to view (but not modify) the contents of a text file one screen at a time (terminal pager). It is available on Unix and Unix-like systems, DOS, OS/2 and Microsoft Windows. Programs of this sort are called pagers.</p>
+<div class="section" title="9.2.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506190"></a>9.2.1. Usage</h4></div></div></div>
+<p id="ch11Section_5_f5"></a>The command-syntax is:</p>
+<pre class="programlisting">$ more [options] [file_name]</pre>
+<p id="ch11Section_5_f6"></a>If no file name is provided, <span class="emphasis"><em>more</em></span> looks for input from stdin.</p>
+<p id="ch11Section_5_f7"></a>Once <span class="emphasis"><em>more</em></span> has obtained input, it displays as much as can fit on the current screen and waits for user input to advance, with the exception that a form feed (^L) will also cause <span class="emphasis"><em>more</em></span> to wait at that line, regardless of the amount of text on the screen. In the lower-left corner of the screen is displayed the text "--More--" and a percentage, representing the percent of the file that <span class="emphasis"><em>more</em></span> has paged through. (This percentage includes the text displayed on the current screen.) When <span class="emphasis"><em>more</em></span> reaches the end of a file (100%) it exits. The most common methods of navigating through a file are <span class="emphasis"><em>Enter</em></span>, which advances the output by one line, and <span class="emphasis"><em>Space</em></span>, which advances the output by one screen.</p>
+<p id="ch11Section_5_f8"></a>There are also other commands that can be used while navigating through the document; consult <span class="emphasis"><em>more</em></span>'s <span class="emphasis"><em>man</em></span> page for more details.</p>
+<p id="ch11Section_5_f9"></a><span class="emphasis"><em>Options</em></span> are typically entered before the file name, but can also be entered in the environment variable <span class="emphasis"><em>$MORE</em></span>. Options entered in the actual command line will override those entered in the <span class="emphasis"><em>$MORE</em></span> environment variable. Available options may vary between Unix systems.</p>
+</div>
+</div>
+<div class="section" title="9.3. less">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2506281"></a>9.3. less</h3></div></div></div>
+<p id="ch11Section_5_fa"></a><span class="emphasis"><em>less</em></span> is a terminal pager program on Unix, Windows and Unix-like systems used to view (but not change) the contents of a text file one screen at a time. It is similar to <span class="emphasis"><em>more</em></span>, but has the extended capability of allowing both forward and backward navigation through the file. Unlike most Unix text editors/viewers, <span class="emphasis"><em>less</em></span> does not need to read the entire file before starting, resulting in faster load times with large files.</p>
+<div class="section" title="9.3.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506310"></a>9.3.1. Usage</h4></div></div></div>
+<p id="ch11Section_5_fb"></a><span class="emphasis"><em>less</em></span> can be invoked with options to change its behaviour, for example, the number of lines to display on the screen. A few options vary depending on the operating system. While <span class="emphasis"><em>less</em></span> is displaying the file, various commands can be used to navigate through the file. These commands are based on those used by both <span class="emphasis"><em>more</em></span> and <span class="emphasis"><em>vi</em></span>. It is also possible to search for character patterns in the file.</p>
+<p id="ch11Section_5_fc"></a>By default, <span class="emphasis"><em>less</em></span> displays the contents of the file to the standard output (one screen at a time). If the file name argument is omitted, it displays the contents from standard input (usually the output of another command through a pipe). If the output is redirected to anything other than a terminal, for example a pipe to another command, less behaves like cat.</p>
+<p id="ch11Section_5_fd"></a>The command-syntax is:</p>
+<pre class="programlisting">$ less [options] file_name</pre>
+</div>
+<div class="section" title="9.3.2. Frequently Used Options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506364"></a>9.3.2. Frequently Used Options</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_fe"></a>-g: Highlights just the current match of any searched string.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_ff"></a>-I: Case-insensitive searches.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_100"></a>-M: Shows more detailed prompt, including file position.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_101"></a>-N: Shows line numbers (useful for source code viewing).</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_102"></a>-S: Disables line wrap ("chop long lines"). Long lines can be seen by side scrolling.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_103"></a>-?: Shows help.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.3. Frequently Used Commands">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506416"></a>9.3.3. Frequently Used Commands</h4></div></div></div>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_104"></a>[Arrows]/[Page Up]/[Page Down]/[Home]/[End]: Navigation.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_105"></a>[Space bar]: Next page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_106"></a>b: Previous page.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_107"></a>ng: Jump to line number n. Default is the start of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_108"></a>nG: Jump to line number n. Default is the end of the file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_109"></a>/pattern: Search for pattern. Regular expressions can be used.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10a"></a>'^ or g: Go to start of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10b"></a>'$ or G: Go to end of file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10c"></a>s: Save current content (got from another program like grep) in a file.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10d"></a>=: File information.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10e"></a>h: Help.</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_10f"></a>q: Quit.</p></li>
+</ul></div>&lt;/block_quote&gt;</span>
+</div>
+<div class="section" title="9.3.4. Examples">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506506"></a>9.3.4. Examples</h4></div></div></div>
+<pre class="programlisting">$ less -M readme.txt                     #Read "readme.txt."
+$ less +F /var/log/mail.log              #Follow mode for log
+$ file * | less                          #Easier file analysis.
+$ grep -i void *.c | less -I -p void     #Case insensitive search                                                         for "void" in all .c files</pre>
+</div>
+</div>
+</div>
+<div class="section" title="10. Directory Structure">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2506521"></a>10. Directory Structure</h2></div></div></div>
+<p id="ch11Section_5_110"></a>In the File Hierarchy Standard (FHS) all files and directories appear under the root directory "/", even if they are stored on different physical devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.</p>
+<p id="ch11Section_5_111"></a>The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.</p>
+<table summary="Directory Structure" border="1"><colgroup>
+<col width="15">
+<col width="48">
+</colgroup></table>
+<div class="section" title="10.1. man hier">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2506791"></a>10.1. man hier</h3></div></div></div>
+<p id="ch11Section_5_136"></a>This is the manual page on the UNIX filesystem. The syntax for this is:</p>
+<pre class="programlisting">$ man hier</pre>
+</div>
+<div class="section" title="10.2. ls -l">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2506807"></a>10.2. ls -l</h3></div></div></div>
+<p id="ch11Section_5_137"></a>Shows you huge amounts of information (permissions, owners, size, and when last modified) for folders and files. The syntax is</p>
+<pre class="programlisting">$ ls -l</pre>
+<p id="ch11Section_5_138"></a>This can be done after entering the required directory.</p>
+</div>
+</div>
+<div class="section" title="11. Permissions and Ownership">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2506830"></a>11. Permissions and Ownership</h2></div></div></div>
+<div class="section" title="11.1. chmod">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2506838"></a>11.1. chmod</h3></div></div></div>
+<p id="ch11Section_5_139"></a>The <span class="emphasis"><em>chmod</em></span> command (abbreviated from 'change mode') is a shell command and C language function in Unix and Unix-like environments. When executed, it can change file system modes of files and directories. The modes include permissions and special modes.A chmod command first appeared in AT&amp;T Unix version 1, and is still used today on Unix-like machines.</p>
+<div class="section" title="11.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506864"></a>11.1.1. Usage</h4></div></div></div>
+<p id="ch11Section_5_13a"></a>The <span class="emphasis"><em>chmod</em></span> command options are specified like this:</p>
+<pre class="programlisting">$ chmod [options] mode[,mode] file1 [file2 ...]</pre>
+<p id="ch11Section_5_13b"></a>To view what the permissions currently are, type:</p>
+<pre class="programlisting">$ ls -l file</pre>
+</div>
+<div class="section" title="11.1.2. Command line options">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2506892"></a>11.1.2. Command line options</h4></div></div></div>
+<p id="ch11Section_5_13c"></a>The <span class="emphasis"><em>chmod</em></span> command has a number of command line options that affect its behavior. The most common options are:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="itemizedlist"><ul class="itemizedlist" type="*">
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_13d"></a>-R: Changes the modes of directories and files recursively</p></li>
+<li class="listitem" style="list-style-type: *"><p id="ch11Section_5_13e"></a>-v: Verbose mode; lists all files as they are being processed</p></li>
+</ul></div>&lt;/block_quote&gt;</span><div class="section" title="11.1.2.1. Symbolic modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2506929"></a>11.1.2.1. Symbolic modes</h5></div></div></div>
+<p id="ch11Section_5_13f"></a>To the <span class="emphasis"><em>chmod</em></span> utility, all permissions and special modes are represented by its mode parameter. One way to adjust the mode of files or directories is to specify a symbolic mode. The symbolic mode is composed of three components, which are combined to form a single string of text:</p>
+<pre class="programlisting">$ chmod [references][operator][modes] file1 ...</pre>
+<p id="ch11Section_5_140"></a>The references (or classes) are used to distinguish the users to whom the permissions apply. If no references are specified it defaults to “all” but modifies only the permissions allowed by the umask. The references are represented by one or more of the following letters:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="8">
+<col width="45">
+</colgroup></table>
+<p id="ch11Section_5_150"></a>The <span class="emphasis"><em>chmod</em></span> program uses an operator to specify how the modes of a file should be adjusted. The following operators are accepted:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="14">
+<col width="54">
+</colgroup></table>
+<p id="ch11Section_5_157"></a>The modes indicate which permissions are to be granted or taken away from the specified classes. There are three basic modes which correspond to the basic permissions:</p>
+<table summary="Symbolic modes" border="1"><colgroup>
+<col width="5">
+<col width="14">
+<col width="48">
+</colgroup></table>
+<p id="ch11Section_5_16d"></a>The combination of these three components produces a string that is understood by the chmod command. Multiple changes can be specified by separating multiple symbolic modes with commas.</p>
+</div>
+<div class="section" title="11.1.2.2. Symbolic examples">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2507475"></a>11.1.2.2. Symbolic examples</h5></div></div></div>
+<p id="ch11Section_5_16e"></a>Add the 'read' and 'write' permissions to the 'user' and 'group' classes of a directory:</p>
+<pre class="programlisting">$ chmod ug+rw mydir
+$ ls -ld mydir
+drw-rw----   2 starwars  yoda  96 Dec 8 12:53 mydir</pre>
+<p id="ch11Section_5_16f"></a>For a file, remove <span class="emphasis"><em>write</em></span> permissions for all classes:</p>
+<pre class="programlisting">$ chmod a-w myfile
+$ ls -l myfile
+-r-xr-xr-x   2 starwars  yoda 96 Dec 8 12:53 myfile</pre>
+<p id="ch11Section_5_170"></a>Set the permissions for the <span class="emphasis"><em>u*ser and the *g*roup to read and execute only (no write permission) on *mydir</em></span>.</p>
+<pre class="programlisting">$ chmod ug=rx mydir
+$ ls -ld mydir
+dr-xr-x---   2 starwars  yoda 96 Dec 8 12:53 mydir</pre>
+</div>
+<div class="section" title="11.1.2.3. Octal numbers">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2507516"></a>11.1.2.3. Octal numbers</h5></div></div></div>
+<p id="ch11Section_5_171"></a>The <span class="emphasis"><em>chmod</em></span> command also accepts three and four-digit octal numbers representing modes. Using a three-digit octal number to set the modes of a file named myfile :</p>
+<pre class="programlisting">$ chmod 664 myfile
+$ ls -l myfile
+-rw-rw-r--  1   57 Jul  3 10:13  myfile</pre>
+<p id="ch11Section_5_172"></a>Since the <span class="emphasis"><em>setuid</em></span>, <span class="emphasis"><em>setgid</em></span> and <span class="emphasis"><em>sticky</em></span> bits are not set, this is equivalent to:</p>
+<pre class="programlisting">$ chmod 0664 myfile</pre>
+</div>
+<div class="section" title="11.1.2.4. Special modes">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2507555"></a>11.1.2.4. Special modes</h5></div></div></div>
+<p id="ch11Section_5_173"></a>The <span class="emphasis"><em>chmod</em></span> command is also capable of changing the additional permissions or special modes of a file or directory. The symbolic modes use <span class="strong"><strong>s</strong></span> to represent the <span class="emphasis"><em>setuid</em></span> and <span class="emphasis"><em>setgid</em></span> modes, and <span class="strong"><strong>t</strong></span> to represent the sticky mode. The modes are only applied to the appropriate classes, regardless of whether or not other classes are specified.</p>
+<p id="ch11Section_5_174"></a>Most operating systems support the specification of special modes using octal modes, but some do not. On these systems, only the symbolic modes can be used.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="section" title="12. Redirection and Piping">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2507603"></a>12. Redirection and Piping</h2></div></div></div>
+<p id="ch11Section_5_175"></a>In computing, <span class="emphasis"><em>redirection</em></span> is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations.</p>
+<p id="ch11Section_5_176"></a>Programs do redirection with the <span class="emphasis"><em>dup2(2)</em></span> system call, or its less-flexible but higher-level stdio analogues, <span class="emphasis"><em>freopen(3)</em></span> and <span class="emphasis"><em>popen(3)</em></span>.</p>
+<div class="section" title="12.1. Redirecting standard input and standard output">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2507640"></a>12.1. Redirecting standard input and standard output</h3></div></div></div>
+<p id="ch11Section_5_177"></a>Redirection is usually implemented by placing certain characters between commands. Typically, the syntax of these characters is as follows:</p>
+<pre class="programlisting">$ command1 &gt; file1</pre>
+<p id="ch11Section_5_178"></a>executes <span class="emphasis"><em>command1</em></span>, placing the output in file1. Note that this will truncate any existing data in <span class="emphasis"><em>file1</em></span>. To append output to the end of the file, use the &gt;&gt; operator.:</p>
+<pre class="programlisting">$ command1 &lt; file1</pre>
+<p id="ch11Section_5_179"></a>executes <span class="emphasis"><em>command1</em></span>, using <span class="emphasis"><em>file1</em></span> as the source of input (as opposed to the keyboard).:</p>
+<pre class="programlisting">$ command1 &lt; infile &gt; outfile</pre>
+<p id="ch11Section_5_17a"></a>combines the two capabilities: <span class="emphasis"><em>command1</em></span> reads from <span class="emphasis"><em>infile</em></span> and writes to <span class="emphasis"><em>outfile</em></span></p>
+</div>
+<div class="section" title="12.2. Piping">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2507709"></a>12.2. Piping</h3></div></div></div>
+<p id="ch11Section_5_17b"></a>Programs can be run together such that one program reads the output from another with no need for an explicit intermediate file:
+A pipeline of three programs run on a text terminal:</p>
+<pre class="programlisting">$ command1 | command2</pre>
+<p id="ch11Section_5_17c"></a>executes <span class="emphasis"><em>command1</em></span>, using its output as the input for <span class="emphasis"><em>command2</em></span> (commonly called piping, since the "|" character is known as a "pipe").</p>
+<p id="ch11Section_5_17d"></a>This is equivalent to using two redirects and a temporary file:</p>
+<pre class="programlisting">$ command1 &gt; tempfile
+$ command2 &lt; tempfile
+$ rm tempfile</pre>
+<p id="ch11Section_5_17e"></a>A good example for command piping is combining <span class="emphasis"><em>echo</em></span> with another command to achieve something interactive in a non-interactive shell, e.g.:</p>
+<pre class="programlisting">$ echo -e "user\npass" | ftp localhost</pre>
+<p id="ch11Section_5_17f"></a>This runs the ftp client with input user, press return, then pass.</p>
+</div>
+<div class="section" title="12.3. Redirecting to and from the standard file handles">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2507770"></a>12.3. Redirecting to and from the standard file handles</h3></div></div></div>
+<p id="ch11Section_5_180"></a>In Unix shells derived from the original Bourne shell, the first two actions can be further modified by placing a number (the file descriptor) immediately before the character; this will affect which stream is used for the redirection. The Unix standard I/O streams are:</p>
+<table summary="Redirecting to and from the standard file handles" border="1"><colgroup>
+<col width="12">
+<col width="13">
+<col width="24">
+</colgroup></table>
+<p id="ch11Section_5_18d"></a>For example:</p>
+<pre class="programlisting">$ command1 2&gt; file1</pre>
+<p id="ch11Section_5_18e"></a>executes <span class="emphasis"><em>command1</em></span>, directing the standard error stream to <span class="emphasis"><em>file1</em></span>.</p>
+<p id="ch11Section_5_18f"></a>In shells derived from <span class="emphasis"><em>csh</em></span> (the C shell), the syntax instead appends the &amp; character to the redirect characters, thus achieving a similar result.</p>
+<p id="ch11Section_5_190"></a>Another useful capability is to redirect one standard file handle to another. The most popular variation is to merge standard error into standard output so error messages can be processed together with (or alternately to) the usual output. Example:</p>
+<pre class="programlisting">$ find / -name .profile &gt; results 2&gt;&amp;1</pre>
+<p id="ch11Section_5_191"></a>will try to find all files named <span class="emphasis"><em>.profile</em></span>. Executed without redirection, it will output hits to <span class="emphasis"><em>stdout</em></span> and errors (e.g. for lack of privilege to traverse protected directories) to <span class="emphasis"><em>stderr</em></span>. If standard output is directed to file results, error messages appear on the console. To see both hits and error messages in file results, merge <span class="emphasis"><em>stderr</em></span> (handle 2) into <span class="emphasis"><em>stdout</em></span> (handle 1) using 2&gt;&amp;1 .</p>
+<p id="ch11Section_5_192"></a>It's possible use 2&gt;&amp;1 before "&gt;" but it doesn't work. In fact, when the interpreter reads 2&gt;&amp;1, it doesn't know yet where standard output is redirected and then standard error isn't merged.</p>
+<p id="ch11Section_5_193"></a>If the merged output is to be piped into another program, the file merge sequence 2&gt;&amp;1 must precede the pipe symbol, thus:</p>
+<pre class="programlisting">$ find / -name .profile 2&gt;&amp;1 | less</pre>
+<p id="ch11Section_5_194"></a>A simplified form of the command:</p>
+<pre class="programlisting">$ command &gt; file 2&gt;&amp;1</pre>
+<p id="ch11Section_5_195"></a>is:</p>
+<pre class="programlisting">$ command &amp;&gt;file</pre>
+<p id="ch11Section_5_196"></a>or:</p>
+<pre class="programlisting">$command &gt;&amp;file</pre>
+</div>
+<div class="section" title="12.4. Chained pipelines">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2507974"></a>12.4. Chained pipelines</h3></div></div></div>
+<p id="ch11Section_5_197"></a>The redirection and piping tokens can be chained together to create complex commands. For example:</p>
+<pre class="programlisting">$ ls | grep '\.sh' | sort &gt; shlist</pre>
+<p id="ch11Section_5_198"></a>lists the contents of the current directory, where this output is filtered to only contain lines which contain <span class="emphasis"><em>.sh</em></span>, sort this resultant output lexicographically, and place the final output in <span class="emphasis"><em>shlist</em></span>. This type of construction is used very commonly in shell scripts and batch files.</p>
+</div>
+<div class="section" title="12.5. Redirect to multiple outputs">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2508008"></a>12.5. Redirect to multiple outputs</h3></div></div></div>
+<p id="ch11Section_5_199"></a>The standard command <span class="emphasis"><em>tee</em></span> can redirect output from a command to several destinations.</p>
+<pre class="programlisting">$ ls -lrt | tee xyz</pre>
+<p id="ch11Section_5_19a"></a>This directs the file list output to both standard output as well as to the file <span class="emphasis"><em>xyz</em></span>.</p>
+</div>
+</div>
+<div class="section" title="13. More Text Processing">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2508039"></a>13. More Text Processing</h2></div></div></div>
+<div class="section" title="13.1. grep">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2508048"></a>13.1. grep</h3></div></div></div>
+<p id="ch11Section_5_19b"></a><span class="emphasis"><em>grep</em></span> is a command line text search utility originally written for Unix. The name is taken from the first letters in <span class="emphasis"><em>global / regular expression / print</em></span>, a series of instructions for the <span class="emphasis"><em>ed</em></span> text editor. The <span class="emphasis"><em>grep</em></span> command searches files or standard input globally for lines matching a given regular expression, and prints them to the program's standard output.</p>
+<div class="section" title="13.1.1. Usage">
+<div class="titlepage"><div><div><h4 class="title">
+<a name="id2508079"></a>13.1.1. Usage</h4></div></div></div>
+<p id="ch11Section_5_19c"></a>This is an example of a common <span class="emphasis"><em>grep</em></span> usage:</p>
+<pre class="programlisting">$ grep apple fruitlist.txt</pre>
+<p id="ch11Section_5_19d"></a>In this case, <span class="emphasis"><em>grep</em></span> prints all lines containing 'apple' from the file <span class="emphasis"><em>fruitlist.txt</em></span>, regardless of word boundaries; therefore lines containing 'pineapple' or 'apples' are also printed. The <span class="emphasis"><em>grep</em></span> command is case sensitive by default, so this example's output does not include lines containing 'Apple' (with a capital A) unless they also contain 'apple'.</p>
+<p id="ch11Section_5_19e"></a>Like most Unix commands, <span class="emphasis"><em>grep</em></span> accepts command line arguments to change this and many other behaviors. For example:</p>
+<pre class="programlisting">$ grep -i apple fruitlist.txt</pre>
+<p id="ch11Section_5_19f"></a>This prints all lines containing 'apple' regardless of capitalization. The '-i' argument tells <span class="emphasis"><em>grep</em></span> to be case insensitive, or to ignore case.</p>
+<p id="ch11Section_5_1a0"></a>To print all lines containing 'apple' as a word ('pineapple' and 'apples' will not match):</p>
+<pre class="programlisting">$ grep -w apple fruitlist.txt</pre>
+<p id="ch11Section_5_1a1"></a>Regular expressions can be used to match more complicated queries.</p>
+<div class="section" title="13.1.1.1. Variations">
+<div class="titlepage"><div><div><h5 class="title">
+<a name="id2508157"></a>13.1.1.1. Variations</h5></div></div></div>
+<p id="ch11Section_5_1a2"></a>There are countless implementations and derivatives of <span class="emphasis"><em>grep</em></span> available for many operating systems. Early variants of <span class="emphasis"><em>grep</em></span> included <span class="emphasis"><em>egrep</em></span> and <span class="emphasis"><em>fgrep</em></span>. The former applies an extended regular expression syntax that was added to Unix after Ken Thompson's original regular expression implementation. The latter searches for any of a list of 'fixed' strings using the Aho-Corasick algorithm. These variants are embodied in most modern <span class="emphasis"><em>grep</em></span> implementations as command-line switches (and standardized as -E and -F in POSIX). In such combined implementations, <span class="emphasis"><em>grep</em></span> may also behave differently depending on the name by which it is invoked, allowing <span class="emphasis"><em>fgrep</em></span>, <span class="emphasis"><em>egrep</em></span>, and <span class="emphasis"><em>grep</em></span> to be links to the same program.</p>
+<p id="ch11Section_5_1a3"></a><span class="emphasis"><em>pcregrep</em></span> is an implementation of <span class="emphasis"><em>grep</em></span> that uses Perl regular expression syntax.</p>
+<p id="ch11Section_5_1a4"></a>Other commands contain the word 'grep' to indicate that they search (usually for regular expression matches). The <span class="emphasis"><em>pgrep</em></span> utility, for instance, displays the processes whose names match a given regular expression.</p>
+</div>
+</div>
+</div>
+<div class="section" title="13.2. tr">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2508237"></a>13.2. tr</h3></div></div></div>
+<p id="ch11Section_5_1a5"></a><span class="emphasis"><em>tr</em></span> (abbreviated from <span class="emphasis"><em>translate</em></span> or <span class="emphasis"><em>transliterate</em></span>) is a command in Unix-like operating systems.</p>
+<p id="ch11Section_5_1a6"></a>When executed, the program reads from the standard input and writes to the standard output. It takes as parameters two sets of characters, and replaces occurrences of the characters in the first set with the corresponding elements from the other set. For example,</p>
+<pre class="programlisting">$ tr 'abcd' 'jkmn'</pre>
+<p id="ch11Section_5_1a7"></a>maps 'a' to 'j', 'b' to 'k', 'c' to 'm', and 'd' to 'n'.</p>
+<p id="ch11Section_5_1a8"></a>Sets of characters may be abbreviated by using character ranges. The previous example could be written:</p>
+<pre class="programlisting">$ tr 'a-d' 'jkmn'</pre>
+<p id="ch11Section_5_1a9"></a>In POSIX compliant versions of <span class="emphasis"><em>tr</em></span> the set represented by a character range depends on the locale's collating order, so it is safer to avoid character ranges in scripts that might be executed in a locale different from that in which they were written. Ranges can often be replaced with POSIX character sets such as [:alpha:].</p>
+<p id="ch11Section_5_1aa"></a>The <span class="emphasis"><em>-c</em></span> flag complements the first set of characters.</p>
+<pre class="programlisting">$ tr -cd '[:alnum:]'</pre>
+<p id="ch11Section_5_1ab"></a>therefore removes all non-alphanumeric characters.</p>
+<p id="ch11Section_5_1ac"></a>The <span class="emphasis"><em>-s</em></span> flag causes tr to compress sequences of identical adjacent characters in its output to a single token. For example,</p>
+<pre class="programlisting">$ tr -s '\n' '\n'</pre>
+<p id="ch11Section_5_1ad"></a>replaces sequences of one or more newline characters with a single newline.</p>
+<p id="ch11Section_5_1ae"></a>The <span class="emphasis"><em>-d</em></span> flag causes tr to delete all tokens of the specified set of characters from its input. In this case, only a single character set argument is used. The following command removes carriage return characters, thereby converting a file in DOS/Windows format to one in Unix format.</p>
+<pre class="programlisting">$ tr -d '\r'</pre>
+<p id="ch11Section_5_1af"></a>Most versions of <span class="emphasis"><em>tr</em></span>, including GNU <span class="emphasis"><em>tr</em></span> and classic Unix <span class="emphasis"><em>tr</em></span>, operate on single byte characters and are not Unicode compliant. An exception is the Heirloom Toolchest implementation, which provides basic Unicode support.</p>
+<p id="ch11Section_5_1b0"></a>Ruby and Perl also have an internal <span class="emphasis"><em>tr</em></span> operator, which operates analogously. Tcl's <span class="emphasis"><em>string map</em></span> command is more general in that it maps strings to strings while <span class="emphasis"><em>tr</em></span> maps characters to characters.</p>
+</div>
+</div>
+<div class="section" title="14. Elementary Regex">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2508386"></a>14. Elementary Regex</h2></div></div></div>
+<p id="ch11Section_5_1b1"></a>In computing, regular expressions provide a concise and flexible means for identifying strings of text of interest, such as particular characters, words, or patterns of characters. A regular expression (often shortened to regex or regexp) is written in a formal language that can be interpreted by a regular expression processor, a program that either serves as a parser generator or examines text and identifies parts that match the provided specification.</p>
+<p id="ch11Section_5_1b2"></a>Regular expressions are used by many text editors, utilities, and programming languages to search and manipulate text based on patterns. For example, Perl, Ruby and Tcl have a powerful regular expression engine built directly into their syntax. Several utilities provided by Unix distributions—including the editor <span class="emphasis"><em>ed</em></span> and the filter <span class="emphasis"><em>grep</em></span> — were the first to popularize the concept of regular expressions.</p>
+<p id="ch11Section_5_1b3"></a>Traditional Unix regular expression syntax followed common conventions but often differed from tool to tool. The IEEE POSIX <span class="emphasis"><em>Basic Regular Expressions</em></span> (BRE) standard (released alongside an alternative flavor called Extended Regular Expressions or ERE) was designed mostly for backward compatibility with the traditional (Simple Regular Expression) syntax but provided a common standard which has since been adopted as the default syntax of many Unix regular expression tools, though there is often some variation or additional features. Many such tools also provide support for ERE syntax with command line arguments.</p>
+<p id="ch11Section_5_1b4"></a>In the BRE syntax, most characters are treated as literals — they match only themselves (i.e., a matches "a"). The exceptions, listed below, are called metacharacters or metasequences.</p>
+<table summary="Elementary Regex" border="1"><colgroup>
+<col width="13">
+<col width="60">
+</colgroup></table>
+<div class="section" title="14.1. Lazy quantification">
+<div class="titlepage"><div><div><h3 class="title">
+<a name="id2508599"></a>14.1. Lazy quantification</h3></div></div></div>
+<p id="ch11Section_5_1c9"></a>The standard quantifiers in regular expressions are greedy, meaning they match as much as they can, only giving back as necessary to match the remainder of the regex. For example, someone new to regexes wishing to find the first instance of an item between &lt; and &gt; symbols in this example:</p>
+<pre class="programlisting">Another whale explosion occurred on &lt;January 26&gt;, &lt;2004&gt;.</pre>
+<p id="ch11Section_5_1ca"></a>...would likely come up with the pattern &lt;.*&gt;, or similar. However, this pattern will actually return "&lt;January 26&gt;, &lt;2004&gt;" instead of the "&lt;January 26&gt;" which might be expected, because the <span style="color: red">&lt;title_reference&gt;*&lt;/title_reference&gt;</span> quantifier is greedy — it will consume as many characters as possible from the input, and "January 26&gt;, &lt;2004" has more characters than "January 26".</p>
+<p id="ch11Section_5_1cb"></a>Though this problem can be avoided in a number of ways (e.g., by specifying the text that is not to be matched: &lt;[^&gt;]*&gt;), modern regular expression tools allow a quantifier to be specified as <span class="emphasis"><em>lazy</em></span> (also known as non-greedy, reluctant, minimal, or ungreedy) by putting a question mark after the quantifier (e.g., &lt;.*?&gt;), or by using a modifier which reverses the greediness of quantifiers (though changing the meaning of the standard quantifiers can be confusing). By using a lazy quantifier, the expression tries the minimal match first. Though in the previous example lazy matching is used to select one of many matching results, in some cases it can also be used to improve performance when greedy matching would require more backtracking.</p>
+</div>
+</div>
+<div class="section" title="15. One Liners">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="id2508675"></a>15. One Liners</h2></div></div></div>
+<p id="ch11Section_5_1cc"></a>A <span class="emphasis"><em>one-liner</em></span> is textual input to the command-line of an operating system shell that performs some function in just one line of input.</p>
+<p id="ch11Section_5_1cd"></a>The one liner can be</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem"><p id="ch11Section_5_1ce"></a>An expression written in the language of the shell.</p></li>
+<li class="listitem"><p id="ch11Section_5_1cf"></a>The invocation of an interpreter together with program source for the interpreter to run.</p></li>
+<li class="listitem"><p id="ch11Section_5_1d0"></a>The invocation of a compiler together with source to compile and
+instructions for executing the compiled program.</p></li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_1d1"></a>Certain dynamic scripting languages such as AWK, sed, and perl have traditionally been adept at expressing one-liners. Specialist shell interpreters such as these Unix shells or the Windows PowerShell, allow for the construction of powerful one-liners.</p>
+<p id="ch11Section_5_1d2"></a>The use of the phrase one-liner has been widened to also include program-source for any language that does something useful in one line.</p>
+<p id="ch11Section_5_1d3"></a>The word <span class="emphasis"><em>One-liner</em></span> has two references in the index of the book <span class="emphasis"><em>The AWK Programming Language</em></span> (the book is often referred to by the abbreviation TAPL). It explains the programming language AWK, which is part of the Unix operating system. The authors explain the birth of the One-liner paradigm with their daily work on early Unix machines:</p>
+<pre class="programlisting">“The 1977 version had only a few built-in variables and predefined functions. It was designed for writing short programs [...] Our model was that an invocation would be one or two lines long, typed in and used immediately. Defaults were chosen to match this style [...] We, being the authors, knew how the language was supposed to be used, and so we only wrote one-liners.”</pre>
+<p id="ch11Section_5_1d4"></a>Notice that this original definition of a One-liner implies immediate execution of the program without any compilation. So, in a strict sense, only source code for interpreted languages qualifies as a One-liner. But this strict understanding of a One-liner was broadened in 1985 when the IOCCC introduced the category of Best One Liner for C, which is a compiled language.</p>
+<p id="ch11Section_5_1d5"></a>The TAPL book contains 20 examples of One-liners (A Handful of Useful awk One-Liners) at the end of the book's first chapter.</p>
+<p id="ch11Section_5_1d6"></a>Here are the first few of them:</p>
+<span style="color: red">&lt;block_quote&gt;<div class="orderedlist"><ol class="orderedlist" type="1">
+<li class="listitem">
+<p id="ch11Section_5_1d7"></a>Print the total number of input lines:</p>
+<p id="ch11Section_5_1d8"></a>END { print NR }</p>
+</li>
+<li class="listitem">
+<p id="ch11Section_5_1d9"></a>Print the tenth input line:</p>
+<p id="ch11Section_5_1da"></a>NR == 10</p>
+</li>
+<li class="listitem">
+<p id="ch11Section_5_1db"></a>Print the last field of every input line:</p>
+<p id="ch11Section_5_1dc"></a>{ print $NF }</p>
+</li>
+</ol></div>&lt;/block_quote&gt;</span><p id="ch11Section_5_1dd"></a>One-liners are also used to show off the differential expressive power of programming languages. Frequently, one-liners are used to demonstrate programming ability. Contests are often held to see who can create the most exceptional one-liner.</p>
+<p id="ch11Section_5_1de"></a>The following example is a C program (a winning entry in the "Best one-liner" category of the IOCCC, here split to two lines for presentation).:</p>
+<pre class="programlisting">main(int c,char**v){return!m(v[1],v[2]);}m(char*s,char*t){return
+*t-42?*s?63==*t|*s==*t&amp;&amp;m(s+1,t+1):!*t:m(s,t+1)||*s&amp;&amp;m(s+1,t);}</pre>
+<p id="ch11Section_5_1df"></a>This one-liner program is a <span class="emphasis"><em>glob pattern matcher</em></span>. It understands the glob characters '*' meaning 'zero or more characters' and '?' meaning exactly one character, just like most Unix shells.</p>
+<p id="ch11Section_5_1e0"></a>Run it with two args, the string and the glob pattern. The exit status is 0 (shell true) when the pattern matches, 1 otherwise. The glob pattern must match the whole string, so you may want to use * at the beginning and end of the pattern if you are looking for something in the middle. Examples:</p>
+<pre class="programlisting">$ prog foo 'f??'; echo $?
+
+$ prog 'best short program' '??st*o**p?*'; echo $?</pre>
+<p id="ch11Section_5_1e1"></a>Here is a one line shell script to show directories:</p>
+<pre class="programlisting">$ ls -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/   /' -e 's/-/|/'</pre>
+</div>
+</div>
+</div></body>
+</html>
--- a/web/html/func.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,254 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title></title>
-<link rel="stylesheet" href="hgbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><span style="color: red">&lt;html&gt;<span style="color: red">&lt;body&gt;<span style="color: red">&lt;document&gt;<span style="color: red">&lt;title&gt;Functional Approach&lt;/title&gt;</span><span style="color: red">&lt;paragraph&gt;<span class="emphasis"><em>Functions</em></span> allow us to enclose a set of statements and call the function again
-and again instead of repeating the group of statements everytime. Functions also
-allow us to isolate a piece of code from all the other code and provides the
-convenience of not polluting the global variables.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;<span class="emphasis"><em>Function</em></span> in python is defined with the keyword <span style="color: red">&lt;strong&gt;def&lt;/strong&gt;</span> followed by the name
-of the function, in turn followed by a pair of parenthesis which encloses the
-list of parameters to the function. The definition line ends with a ':'. The
-definition line is followed by the body of the function intended by one block.
-The <span class="emphasis"><em>Function</em></span> must return a value:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def factorial(n):
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The code snippet above defines a function with the name factorial, takes the
-number for which the factorial must be computed, computes the factorial and
-returns the value.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;A <span class="emphasis"><em>Function</em></span> once defined can be used or called anywhere else in the program. We
-call a fucntion with its name followed by a pair of parenthesis which encloses
-the arguments to the function.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;The value that function returns can be assigned to a variable. Let's call the
-above function and store the factorial in a variable:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;fact5 = factorial(5)&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The value of fact5 will now be 120, which is the factorial of 5. Note that we
-passed 5 as the argument to the function.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;It may be necessary to document what the function does, for each of the function
-to help the person who reads our code to understand it better. In order to do
-this Python allows the first line of the function body to be a string. This
-string is called as <span class="emphasis"><em>Documentation String</em></span> or <span class="emphasis"><em>docstring</em></span>. <span class="emphasis"><em>docstrings</em></span> prove
-to be very handy since there are number of tools which can pull out all the
-docstrings from Python functions and generate the documentation automatically
-from it. <span class="emphasis"><em>docstrings</em></span> for functions can be written as follows:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def factorial(n):
-  'Returns the factorial for the number n.'
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;An important point to note at this point is that, a function can return any
-Python value or a Python object, which also includes a <span class="emphasis"><em>Tuple</em></span>. A <span class="emphasis"><em>Tuple</em></span> is
-just a collection of values and those values themselves can be of any other
-valid Python datatypes, including <span class="emphasis"><em>Lists</em></span>, <span class="emphasis"><em>Tuples</em></span>, <span class="emphasis"><em>Dictionaries</em></span> among other
-things. So effectively, if a function can return a tuple, it can return any
-number of values through a tuple&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;Let us write a small function to swap two values:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def swap(a, b):
-  return b, a
-
-c, d = swap(a, b)&lt;/literal_block&gt;</span><div class="section" title="1. Function scope">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2981898"></a>1. Function scope</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;The variables used inside the function are confined to the function's scope
-and doesn't pollute the variables of the same name outside the scope of the
-function. Also the arguments passed to the function are passed by-value if
-it is of basic Python data type:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def cant_change(n):
-  n = 10
-
-n = 5
-cant_change(n)&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;Upon running this code, what do you think would have happened to value of n
-which was assigned 5 before the function call? If you have already tried out
-that snippet on the interpreter you already know that the value of n is not
-changed. This is true of any immutable types of Python like <span class="emphasis"><em>Numbers</em></span>, <span class="emphasis"><em>Strings</em></span>
-and <span class="emphasis"><em>Tuples</em></span>. But when you pass mutable objects like <span class="emphasis"><em>Lists</em></span> and <span class="emphasis"><em>Dictionaries</em></span>
-the values are manipulated even outside the function:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;&gt;&gt;&gt; def can_change(n):
-...   n[1] = James
-...
-
-&gt;&gt;&gt; name = ['Mr.', 'Steve', 'Gosling']
-&gt;&gt;&gt; can_change(name)
-&gt;&gt;&gt; name
-['Mr.', 'James', 'Gosling']&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;If nothing is returned by the function explicitly, Python takes care to return
-None when the funnction is called.&lt;/paragraph&gt;</span>
-</div>
-<div class="section" title="2. Default Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2981970"></a>2. Default Arguments</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;There may be situations where we need to allow the functions to take the
-arguments optionally. Python allows us to define function this way by providing
-a facility called <span class="emphasis"><em>Default Arguments</em></span>. For example, we need to write a function
-that returns a list of fibonacci numbers. Since our function cannot generate an
-infinite list of fibonacci numbers, we need to specify the number of elements
-that the fibonacci sequence must contain. Suppose, additionally, we want to the
-function to return 10 numbers in the sequence if no option is specified we can
-define the function as follows:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def fib(n=10):
-  fib_list = [0, 1]
-  for i in range(n - 2):
-    next = fib_list[-2] + fib_list[-1]
-    fib_list.append(next)
-  return fib_list&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;When we call this function, we can optionally specify the value for the
-parameter n, during the call as an argument. Calling with no argument and
-argument with n=5 returns the following fibonacci sequences:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;fib()
-[0, 1, 1, 2, 3, 5, 8, 13, 21, 34]
-fib(5)
-[0, 1, 1, 2, 3]&lt;/literal_block&gt;</span>
-</div>
-<div class="section" title="3. Keyword Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2981995"></a>3. Keyword Arguments</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;When a function takes a large number of arguments, it may be difficult to
-remember the order of the parameters in the function definition or it may
-be necessary to pass values to only certain parameters since others take
-the default value. In either of these cases, Python provides the facility
-of passing arguments by specifying the name of the parameter as defined in
-the function definition. This is known as <span class="emphasis"><em>Keyword Arguments</em></span>.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;In a function call, <span class="emphasis"><em>Keyword arguments</em></span> can be used for each argument, in the
-following fashion:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;argument_name=argument_value
-Also denoted as: keyword=argument
-
-def wish(name='World', greetings='Hello'):
-  print "%s, %s!" % (greetings, name)&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;This function can be called in one of the following ways. It is important to
-note that no restriction is imposed in the order in which <span class="emphasis"><em>Keyword arguments</em></span>
-can be specified. Also note, that we have combined <span class="emphasis"><em>Keyword arguments</em></span> with
-<span class="emphasis"><em>Default arguments</em></span> in this example, however it is not necessary:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;wish(name='Guido', greetings='Hey')
-wish(greetings='Hey', name='Guido')&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;Calling functions by specifying arguments in the order of parameters specified
-in the function definition is called as <span class="emphasis"><em>Positional arguments</em></span>, as opposed to
-<span class="emphasis"><em>Keyword arguments</em></span>. It is possible to use both <span class="emphasis"><em>Positional arguments</em></span> and
-<span class="emphasis"><em>Keyword arguments</em></span> in a single function call. But Python doesn't allow us to
-bungle up both of them. The arguments to the function, in the call, must always
-start with <span class="emphasis"><em>Positional arguments</em></span> which is in turn followed by <span class="emphasis"><em>Keyword
-arguments</em></span>:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def my_func(x, y, z, u, v, w):
-  # initialize variables.
-  ...
-  # do some stuff
-  ...
-  # return the value&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;It is valid to call the above functions in the following ways:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;my_func(10, 20, 30, u=1.0, v=2.0, w=3.0)
-my_func(10, 20, 30, 1.0, 2.0, w=3.0)
-my_func(10, 20, z=30, u=1.0, v=2.0, w=3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, w=3.0)&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;Following lists some of the invalid calls:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;my_func(10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, 3.0)&lt;/literal_block&gt;</span>
-</div>
-<div class="section" title="4. Parameter Packing and Unpacking">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2982116"></a>4. Parameter Packing and Unpacking</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;The positional arguments passed to a function can be collected in a tuple
-parameter and keyword arguments can be collected in a dictionary. Since keyword
-arguments must always be the last set of arguments passed to a function, the
-keyword dictionary parameter must be the last parameter. The function definition
-must include a list explicit parameters, followed by tuple paramter collecting
-parameter, whose name is preceded by a <span style="color: red">&lt;strong&gt;*&lt;/strong&gt;</span>, for collecting positional
-parameters, in turn followed by the dictionary collecting parameter, whose name
-is preceded by a <span style="color: red">&lt;strong&gt;**&lt;/strong&gt;</span>&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def print_report(title, *args, **name):
-  """Structure of *args*
-  (age, email-id)
-  Structure of *name*
-  {
-      'first': First Name
-      'middle': Middle Name
-      'last': Last Name
-  }
-  """
-
-  print "Title: %s" % (title)
-  print "Full name: %(first)s %(middle)s %(last)s" % name
-  print "Age: %d\nEmail-ID: %s" % args&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The above function can be called as. Note, the order of keyword parameters can
-be interchanged:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;&gt;&gt;&gt; print_report('Employee Report', 29, 'johny@example.com', first='Johny',
-                 last='Charles', middle='Douglas')
-Title: Employee Report
-Full name: Johny Douglas Charles
-Age: 29
-Email-ID: johny@example.com&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The reverse of this can also be achieved by using a very identical syntax while
-calling the function. A tuple or a dictionary can be passed as arguments in
-place of a list of <span class="emphasis"><em>Positional arguments</em></span> or <span class="emphasis"><em>Keyword arguments</em></span> respectively
-using <span style="color: red">&lt;strong&gt;*&lt;/strong&gt;</span> or <span style="color: red">&lt;strong&gt;**&lt;/strong&gt;</span>&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def print_report(title, age, email, first, middle, last):
-  print "Title: %s" % (title)
-  print "Full name: %s %s %s" % (first, middle, last)
-  print "Age: %d\nEmail-ID: %s" % (age, email)
-
-&gt;&gt;&gt; args = (29, 'johny@example.com')
-&gt;&gt;&gt; name = {
-        'first': 'Johny',
-        'middle': 'Charles',
-        'last': 'Douglas'
-        }
-&gt;&gt;&gt; print_report('Employee Report', *args, **name)
-Title: Employee Report
-Full name: Johny Charles Douglas
-Age: 29
-Email-ID: johny@example.com&lt;/literal_block&gt;</span>
-</div>
-<div class="section" title="5. Nested Functions and Scopes">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2982188"></a>5. Nested Functions and Scopes</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;Python allows nesting one function inside another. This style of programming
-turns out to be extremely flexible and powerful features when we use <span class="emphasis"><em>Python
-decorators</em></span>. We will not talk about decorators is beyond the scope of this
-course. If you are interested in knowing more about <span class="emphasis"><em>decorator programming</em></span> in
-Python you are suggested to read:&lt;/paragraph&gt;</span><span style="color: red">&lt;line_block&gt;<span style="color: red">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://avinashv.net/2008/04/python-decorators-syntactic-sugar/</div>&lt;/line&gt;</span><span style="color: red">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://personalpages.tds.net/~kent37/kk/00001.html</div>&lt;/line&gt;</span>&lt;/line_block&gt;</span><span style="color: red">&lt;paragraph&gt;However, the following is an example for nested functions in Python:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def outer():
-  print "Outer..."
-  def inner():
-    print "Inner..."
-  print "Outer..."
-  inner()
-
-&gt;&gt;&gt; outer()&lt;/literal_block&gt;</span>
-</div>
-<div class="section" title="6. map, reduce and filter functions">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2982258"></a>6. map, reduce and filter functions</h2></div></div></div>
-<span style="color: red">&lt;paragraph&gt;Python provides several built-in functions for convenience. The <span style="color: red">&lt;strong&gt;map()&lt;/strong&gt;</span>,
-<span style="color: red">&lt;strong&gt;reduce()&lt;/strong&gt;</span> and <span style="color: red">&lt;strong&gt;filter()&lt;/strong&gt;</span> functions prove to be very useful with sequences like
-<span class="emphasis"><em>Lists</em></span>.&lt;/paragraph&gt;</span><span style="color: red">&lt;paragraph&gt;The <span style="color: red">&lt;strong&gt;map&lt;/strong&gt;</span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments: <span class="emphasis"><em>function</em></span>
-and a <span class="emphasis"><em>sequence</em></span> argument. The <span class="emphasis"><em>function</em></span> argument must be the name of the
-function which in turn takes a single argument, the individual element of the
-<span class="emphasis"><em>sequence</em></span>. The <span style="color: red">&lt;strong&gt;map&lt;/strong&gt;</span> function calls <span class="emphasis"><em>function(item)</em></span>, for each item in the
-sequence and returns a list of values, where each value is the value returned
-by each call to <span class="emphasis"><em>function(item)</em></span>. <span style="color: red">&lt;strong&gt;map()&lt;/strong&gt;</span> function allows to pass more than
-one sequence. In this case, the first argument, <span class="emphasis"><em>function</em></span> must take as many
-arguments as the number of sequences passed. This function is called with each
-corresponding element in the each of the sequences, or <span style="color: red">&lt;strong&gt;None&lt;/strong&gt;</span> if one of the
-sequence is exhausted:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def square(x):
-  return x*x
-
-&gt;&gt;&gt; map(square, [1, 2, 3, 4])
-[1, 4, 9, 16]
-
-def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; map(mul, [1, 2, 3, 4], [6, 7, 8, 9])&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The <span style="color: red">&lt;strong&gt;filter&lt;/strong&gt;</span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-the <span style="color: red">&lt;strong&gt;map()&lt;/strong&gt;</span> function. The <span style="color: red">&lt;strong&gt;filter&lt;/strong&gt;</span> function calls <span class="emphasis"><em>function(item)</em></span>, for each
-item in the sequence and returns all the elements in the sequence for which
-<span class="emphasis"><em>function(item)</em></span> returned True:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def even(x):
-  if x % 2:
-    return True
-  else:
-    return False
-
-&gt;&gt;&gt; filter(even, range(1, 10))
-[1, 3, 5, 7, 9]&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The <span style="color: red">&lt;strong&gt;reduce&lt;/strong&gt;</span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-<span style="color: red">&lt;strong&gt;map&lt;/strong&gt;</span> function, however multiple sequences are not allowed. The <span style="color: red">&lt;strong&gt;reduce&lt;/strong&gt;</span>
-function calls <span class="emphasis"><em>function</em></span> with first two consecutive elements in the sequence,
-obtains the result, calls <span class="emphasis"><em>function</em></span> with the result and the subsequent element
-in the sequence and so on until the end of the list and returns the final result:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; reduce(mul, [1, 2, 3, 4])
-24&lt;/literal_block&gt;</span><div class="section" title="6.1. List Comprehensions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2982429"></a>6.1. List Comprehensions</h3></div></div></div>
-<span style="color: red">&lt;paragraph&gt;List Comprehension is a convenvience utility provided by Python. It is a
-syntatic sugar to create <span class="emphasis"><em>Lists</em></span>. Using <span class="emphasis"><em>List Comprehensions</em></span> one can create
-<span class="emphasis"><em>Lists</em></span> from other type of sequential data structures or other <span class="emphasis"><em>Lists</em></span> itself.
-The syntax of <span class="emphasis"><em>List Comprehensions</em></span> consists of a square brackets to indicate
-the result is a <span class="emphasis"><em>List</em></span> within which we include at least one <span style="color: red">&lt;strong&gt;for&lt;/strong&gt;</span> clause and
-multiple <span style="color: red">&lt;strong&gt;if&lt;/strong&gt;</span> clauses. It will be more clear with an example:&lt;/paragraph&gt;</span><span style="color: red">&lt;literal_block&gt;&gt;&gt;&gt; num = [1, 2, 3]
-&gt;&gt;&gt; sq = [x*x for x in num]
-&gt;&gt;&gt; sq
-[1, 4, 9]
-&gt;&gt;&gt; all_num = [1, 2, 3, 4, 5, 6, 7, 8, 9]
-&gt;&gt;&gt; even = [x for x in all_num if x%2 == 0]&lt;/literal_block&gt;</span><span style="color: red">&lt;paragraph&gt;The syntax used here is very clear from the way it is written. It can be
-translated into english as, "for each element x in the list all_num,
-if remainder of x divided by 2 is 0, add x to the list."&lt;/paragraph&gt;</span>
-</div>
-</div>&lt;/document&gt;</span>&lt;/body&gt;</span>&lt;/html&gt;</span></body>
-</html>
--- a/web/html/paragraphlist.py~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,7 +0,0 @@
-f=open('abc.html','r')
-pid_list=[]
-for i in f.readlines():
-    if i.startswith('<p id=') : 
-        list_tmp=i.split('"')[1]
-        pid_list.append(list_tmp)
-print pid_list
--- a/web/html/test.html~	Mon Jan 25 18:56:45 2010 +0530
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,337 +0,0 @@
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>Chapter 1. </title>
-<link rel="stylesheet" href="hgbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.75.1">
-</head>
-<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" title="Chapter 1. ">
-<div class="titlepage"></div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="article"><a href="#id2872631">Functional Approach</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="#id2923650">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2923702">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2923738">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2923841">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2923935">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2923984">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2924165">6.1. List Comprehensions</a></span></dt></dl></dd>
-</dl></dd>
-</dl>
-</div>
-<div class="article" title="Functional Approach">
-<div class="titlepage">
-<div><div><h2 class="title">
-<a name="id2872631"></a>Functional Approach</h2></div></div>
-<hr>
-</div>
-<div class="toc">
-<p><b>Table of Contents</b></p>
-<dl>
-<dt><span class="section"><a href="#id2923650">1. Function scope</a></span></dt>
-<dt><span class="section"><a href="#id2923702">2. Default Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2923738">3. Keyword Arguments</a></span></dt>
-<dt><span class="section"><a href="#id2923841">4. Parameter Packing and Unpacking</a></span></dt>
-<dt><span class="section"><a href="#id2923935">5. Nested Functions and Scopes</a></span></dt>
-<dt><span class="section"><a href="#id2923984">6. map, reduce and filter functions</a></span></dt>
-<dd><dl><dt><span class="section"><a href="#id2924165">6.1. List Comprehensions</a></span></dt></dl></dd>
-</dl>
-</div>
-<p><span class="emphasis"><em>Functions</em></span> allow us to enclose a set of statements and call the function again
-and again instead of repeating the group of statements everytime. Functions also
-allow us to isolate a piece of code from all the other code and provides the
-convenience of not polluting the global variables.</p>
-<p><span class="emphasis"><em>Function</em></span> in python is defined with the keyword <span class="strong"><strong>def</strong></span> followed by the name
-of the function, in turn followed by a pair of parenthesis which encloses the
-list of parameters to the function. The definition line ends with a ':'. The
-definition line is followed by the body of the function intended by one block.
-The <span class="emphasis"><em>Function</em></span> must return a value:</p>
-<pre class="programlisting"> def factorial(n):
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p>The code snippet above defines a function with the name factorial, takes the
-number for which the factorial must be computed, computes the factorial and
-returns the value.</p>
-<p>A <span class="emphasis"><em>Function</em></span> once defined can be used or called anywhere else in the program. We
-call a fucntion with its name followed by a pair of parenthesis which encloses
-the arguments to the function.</p>
-<p>The value that function returns can be assigned to a variable. Let's call the
-above function and store the factorial in a variable:</p>
-<pre class="programlisting"> fact5 = factorial(5)</pre>
-<p>The value of fact5 will now be 120, which is the factorial of 5. Note that we
-passed 5 as the argument to the function.</p>
-<p>It may be necessary to document what the function does, for each of the function
-to help the person who reads our code to understand it better. In order to do
-this Python allows the first line of the function body to be a string. This
-string is called as <span class="emphasis"><em>Documentation String</em></span> or <span class="emphasis"><em>docstring</em></span>. <span class="emphasis"><em>docstrings</em></span> prove
-to be very handy since there are number of tools which can pull out all the
-docstrings from Python functions and generate the documentation automatically
-from it. <span class="emphasis"><em>docstrings</em></span> for functions can be written as follows:</p>
-<pre class="programlisting"> def factorial(n):
-  'Returns the factorial for the number n.'
-  fact = 1
-  for i in range(2, n):
-    fact *= i
-
-  return fact</pre>
-<p>An important point to note at this point is that, a function can return any
-Python value or a Python object, which also includes a <span class="emphasis"><em>Tuple</em></span>. A <span class="emphasis"><em>Tuple</em></span> is
-just a collection of values and those values themselves can be of any other
-valid Python datatypes, including <span class="emphasis"><em>Lists</em></span>, <span class="emphasis"><em>Tuples</em></span>, <span class="emphasis"><em>Dictionaries</em></span> among other
-things. So effectively, if a function can return a tuple, it can return any
-number of values through a tuple</p>
-<p>Let us write a small function to swap two values:</p>
-<pre class="programlisting"> def swap(a, b):
-  return b, a
-
-c, d = swap(a, b)</pre>
-<div class="section" title="1. Function scope">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923650"></a>1. Function scope</h2></div></div></div>
-<p>The variables used inside the function are confined to the function's scope
-and doesn't pollute the variables of the same name outside the scope of the
-function. Also the arguments passed to the function are passed by-value if
-it is of basic Python data type:</p>
-<pre class="programlisting"> def cant_change(n):
-  n = 10
-
-n = 5
-cant_change(n)</pre>
-<p>Upon running this code, what do you think would have happened to value of n
-which was assigned 5 before the function call? If you have already tried out
-that snippet on the interpreter you already know that the value of n is not
-changed. This is true of any immutable types of Python like <span class="emphasis"><em>Numbers</em></span>, <span class="emphasis"><em>Strings</em></span>
-and <span class="emphasis"><em>Tuples</em></span>. But when you pass mutable objects like <span class="emphasis"><em>Lists</em></span> and <span class="emphasis"><em>Dictionaries</em></span>
-the values are manipulated even outside the function:</p>
-<pre class="programlisting"> &gt;&gt;&gt; def can_change(n):
-...   n[1] = James
-...
-
-&gt;&gt;&gt; name = ['Mr.', 'Steve', 'Gosling']
-&gt;&gt;&gt; can_change(name)
-&gt;&gt;&gt; name
-['Mr.', 'James', 'Gosling']</pre>
-<p>If nothing is returned by the function explicitly, Python takes care to return
-None when the funnction is called.</p>
-</div>
-<div class="section" title="2. Default Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923702"></a>2. Default Arguments</h2></div></div></div>
-<p>There may be situations where we need to allow the functions to take the
-arguments optionally. Python allows us to define function this way by providing
-a facility called <span class="emphasis"><em>Default Arguments</em></span>. For example, we need to write a function
-that returns a list of fibonacci numbers. Since our function cannot generate an
-infinite list of fibonacci numbers, we need to specify the number of elements
-that the fibonacci sequence must contain. Suppose, additionally, we want to the
-function to return 10 numbers in the sequence if no option is specified we can
-define the function as follows:</p>
-<pre class="programlisting"> def fib(n=10):
-  fib_list = [0, 1]
-  for i in range(n - 2):
-    next = fib_list[-2] + fib_list[-1]
-    fib_list.append(next)
-  return fib_list</pre>
-<p>When we call this function, we can optionally specify the value for the
-parameter n, during the call as an argument. Calling with no argument and
-argument with n=5 returns the following fibonacci sequences:</p>
-<pre class="programlisting"> fib()
-[0, 1, 1, 2, 3, 5, 8, 13, 21, 34]
-fib(5)
-[0, 1, 1, 2, 3]</pre>
-</div>
-<div class="section" title="3. Keyword Arguments">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923738"></a>3. Keyword Arguments</h2></div></div></div>
-<p>When a function takes a large number of arguments, it may be difficult to
-remember the order of the parameters in the function definition or it may
-be necessary to pass values to only certain parameters since others take
-the default value. In either of these cases, Python provides the facility
-of passing arguments by specifying the name of the parameter as defined in
-the function definition. This is known as <span class="emphasis"><em>Keyword Arguments</em></span>.</p>
-<p>In a function call, <span class="emphasis"><em>Keyword arguments</em></span> can be used for each argument, in the
-following fashion:</p>
-<pre class="programlisting"> argument_name=argument_value
-Also denoted as: keyword=argument
-
-def wish(name='World', greetings='Hello'):
-  print "%s, %s!" % (greetings, name)</pre>
-<p>This function can be called in one of the following ways. It is important to
-note that no restriction is imposed in the order in which <span class="emphasis"><em>Keyword arguments</em></span>
-can be specified. Also note, that we have combined <span class="emphasis"><em>Keyword arguments</em></span> with
-<span class="emphasis"><em>Default arguments</em></span> in this example, however it is not necessary:</p>
-<pre class="programlisting"> wish(name='Guido', greetings='Hey')
-wish(greetings='Hey', name='Guido')</pre>
-<p>Calling functions by specifying arguments in the order of parameters specified
-in the function definition is called as <span class="emphasis"><em>Positional arguments</em></span>, as opposed to
-<span class="emphasis"><em>Keyword arguments</em></span>. It is possible to use both <span class="emphasis"><em>Positional arguments</em></span> and
-<span class="emphasis"><em>Keyword arguments</em></span> in a single function call. But Python doesn't allow us to
-bungle up both of them. The arguments to the function, in the call, must always
-start with <span class="emphasis"><em>Positional arguments</em></span> which is in turn followed by <span class="emphasis"><em>Keyword
-arguments</em></span>:</p>
-<pre class="programlisting"> def my_func(x, y, z, u, v, w):
-  # initialize variables.
-  ...
-  # do some stuff
-  ...
-  # return the value</pre>
-<p>It is valid to call the above functions in the following ways:</p>
-<pre class="programlisting"> my_func(10, 20, 30, u=1.0, v=2.0, w=3.0)
-my_func(10, 20, 30, 1.0, 2.0, w=3.0)
-my_func(10, 20, z=30, u=1.0, v=2.0, w=3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, w=3.0)</pre>
-<p>Following lists some of the invalid calls:</p>
-<pre class="programlisting"> my_func(10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, 20, z=30, 1.0, 2.0, 3.0)
-my_func(x=10, y=20, z=30, u=1.0, v=2.0, 3.0)</pre>
-</div>
-<div class="section" title="4. Parameter Packing and Unpacking">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923841"></a>4. Parameter Packing and Unpacking</h2></div></div></div>
-<p>The positional arguments passed to a function can be collected in a tuple
-parameter and keyword arguments can be collected in a dictionary. Since keyword
-arguments must always be the last set of arguments passed to a function, the
-keyword dictionary parameter must be the last parameter. The function definition
-must include a list explicit parameters, followed by tuple paramter collecting
-parameter, whose name is preceded by a <span class="strong"><strong>*</strong></span>, for collecting positional
-parameters, in turn followed by the dictionary collecting parameter, whose name
-is preceded by a <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, *args, **name):
-  """Structure of *args*
-  (age, email-id)
-  Structure of *name*
-  {
-      'first': First Name
-      'middle': Middle Name
-      'last': Last Name
-  }
-  """
-
-  print "Title: %s" % (title)
-  print "Full name: %(first)s %(middle)s %(last)s" % name
-  print "Age: %d\nEmail-ID: %s" % args</pre>
-<p>The above function can be called as. Note, the order of keyword parameters can
-be interchanged:</p>
-<pre class="programlisting"> &gt;&gt;&gt; print_report('Employee Report', 29, 'johny@example.com', first='Johny',
-                 last='Charles', middle='Douglas')
-Title: Employee Report
-Full name: Johny Douglas Charles
-Age: 29
-Email-ID: johny@example.com</pre>
-<p>The reverse of this can also be achieved by using a very identical syntax while
-calling the function. A tuple or a dictionary can be passed as arguments in
-place of a list of <span class="emphasis"><em>Positional arguments</em></span> or <span class="emphasis"><em>Keyword arguments</em></span> respectively
-using <span class="strong"><strong>*</strong></span> or <span class="strong"><strong>**</strong></span></p>
-<pre class="programlisting"> def print_report(title, age, email, first, middle, last):
-  print "Title: %s" % (title)
-  print "Full name: %s %s %s" % (first, middle, last)
-  print "Age: %d\nEmail-ID: %s" % (age, email)
-
-&gt;&gt;&gt; args = (29, 'johny@example.com')
-&gt;&gt;&gt; name = {
-        'first': 'Johny',
-        'middle': 'Charles',
-        'last': 'Douglas'
-        }
-&gt;&gt;&gt; print_report('Employee Report', *args, **name)
-Title: Employee Report
-Full name: Johny Charles Douglas
-Age: 29
-Email-ID: johny@example.com</pre>
-</div>
-<div class="section" title="5. Nested Functions and Scopes">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923935"></a>5. Nested Functions and Scopes</h2></div></div></div>
-<p>Python allows nesting one function inside another. This style of programming
-turns out to be extremely flexible and powerful features when we use <span class="emphasis"><em>Python
-decorators</em></span>. We will not talk about decorators is beyond the scope of this
-course. If you are interested in knowing more about <span class="emphasis"><em>decorator programming</em></span> in
-Python you are suggested to read:</p>
-<span style="color: red">&lt;line_block&gt;<span style="color: red">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://avinashv.net/2008/04/python-decorators-syntactic-sugar/</div>&lt;/line&gt;</span><span style="color: red">&lt;line&gt;<div class="reference">
-<div class="titlepage"><hr></div>http://personalpages.tds.net/~kent37/kk/00001.html</div>&lt;/line&gt;</span>&lt;/line_block&gt;</span><p>However, the following is an example for nested functions in Python:</p>
-<pre class="programlisting"> def outer():
-  print "Outer..."
-  def inner():
-    print "Inner..."
-  print "Outer..."
-  inner()
-
-&gt;&gt;&gt; outer()</pre>
-</div>
-<div class="section" title="6. map, reduce and filter functions">
-<div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id2923984"></a>6. map, reduce and filter functions</h2></div></div></div>
-<p>Python provides several built-in functions for convenience. The <span class="strong"><strong>map()</strong></span>,
-<span class="strong"><strong>reduce()</strong></span> and <span class="strong"><strong>filter()</strong></span> functions prove to be very useful with sequences like
-<span class="emphasis"><em>Lists</em></span>.</p>
-<p>The <span class="strong"><strong>map</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments: <span class="emphasis"><em>function</em></span>
-and a <span class="emphasis"><em>sequence</em></span> argument. The <span class="emphasis"><em>function</em></span> argument must be the name of the
-function which in turn takes a single argument, the individual element of the
-<span class="emphasis"><em>sequence</em></span>. The <span class="strong"><strong>map</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each item in the
-sequence and returns a list of values, where each value is the value returned
-by each call to <span class="emphasis"><em>function(item)</em></span>. <span class="strong"><strong>map()</strong></span> function allows to pass more than
-one sequence. In this case, the first argument, <span class="emphasis"><em>function</em></span> must take as many
-arguments as the number of sequences passed. This function is called with each
-corresponding element in the each of the sequences, or <span class="strong"><strong>None</strong></span> if one of the
-sequence is exhausted:</p>
-<pre class="programlisting"> def square(x):
-  return x*x
-
-&gt;&gt;&gt; map(square, [1, 2, 3, 4])
-[1, 4, 9, 16]
-
-def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; map(mul, [1, 2, 3, 4], [6, 7, 8, 9])</pre>
-<p>The <span class="strong"><strong>filter</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-the <span class="strong"><strong>map()</strong></span> function. The <span class="strong"><strong>filter</strong></span> function calls <span class="emphasis"><em>function(item)</em></span>, for each
-item in the sequence and returns all the elements in the sequence for which
-<span class="emphasis"><em>function(item)</em></span> returned True:</p>
-<pre class="programlisting"> def even(x):
-  if x % 2:
-    return True
-  else:
-    return False
-
-&gt;&gt;&gt; filter(even, range(1, 10))
-[1, 3, 5, 7, 9]</pre>
-<p>The <span class="strong"><strong>reduce</strong></span> (<span class="emphasis"><em>function</em></span>, <span class="emphasis"><em>sequence</em></span>) function takes two arguments, similar to
-<span class="strong"><strong>map</strong></span> function, however multiple sequences are not allowed. The <span class="strong"><strong>reduce</strong></span>
-function calls <span class="emphasis"><em>function</em></span> with first two consecutive elements in the sequence,
-obtains the result, calls <span class="emphasis"><em>function</em></span> with the result and the subsequent element
-in the sequence and so on until the end of the list and returns the final result:</p>
-<pre class="programlisting"> def mul(x, y):
-  return x*y
-
-&gt;&gt;&gt; reduce(mul, [1, 2, 3, 4])
-24</pre>
-<div class="section" title="6.1. List Comprehensions">
-<div class="titlepage"><div><div><h3 class="title">
-<a name="id2924165"></a>6.1. List Comprehensions</h3></div></div></div>
-<p>List Comprehension is a convenvience utility provided by Python. It is a
-syntatic sugar to create <span class="emphasis"><em>Lists</em></span>. Using <span class="emphasis"><em>List Comprehensions</em></span> one can create
-<span class="emphasis"><em>Lists</em></span> from other type of sequential data structures or other <span class="emphasis"><em>Lists</em></span> itself.
-The syntax of <span class="emphasis"><em>List Comprehensions</em></span> consists of a square brackets to indicate
-the result is a <span class="emphasis"><em>List</em></span> within which we include at least one <span class="strong"><strong>for</strong></span> clause and
-multiple <span class="strong"><strong>if</strong></span> clauses. It will be more clear with an example:</p>
-<pre class="programlisting"> &gt;&gt;&gt; num = [1, 2, 3]
-&gt;&gt;&gt; sq = [x*x for x in num]
-&gt;&gt;&gt; sq
-[1, 4, 9]
-&gt;&gt;&gt; all_num = [1, 2, 3, 4, 5, 6, 7, 8, 9]
-&gt;&gt;&gt; even = [x for x in all_num if x%2 == 0]</pre>
-<p>The syntax used here is very clear from the way it is written. It can be
-translated into english as, "for each element x in the list all_num,
-if remainder of x divided by 2 is 0, add x to the list."</p>
-</div>
-</div>
-</div>
-</div></body>
-</html>