The Buildroot User Manual I

Total Page:16

File Type:pdf, Size:1020Kb

The Buildroot User Manual I The Buildroot user manual i The Buildroot user manual The Buildroot user manual ii Contents I Getting started 1 1 About Buildroot 2 2 System requirements 3 2.1 Mandatory packages.................................................3 2.2 Optional packages...................................................4 3 Getting Buildroot 5 4 Buildroot quick start 6 5 Community resources 8 II User guide 9 6 Buildroot configuration 10 6.1 Cross-compilation toolchain............................................. 10 6.1.1 Internal toolchain backend.......................................... 11 6.1.2 External toolchain backend.......................................... 11 6.1.2.1 External toolchain wrapper.................................... 12 6.2 /dev management................................................... 13 6.3 init system....................................................... 13 7 Configuration of other components 15 8 General Buildroot usage 16 8.1 make tips....................................................... 16 8.2 Understanding when a full rebuild is necessary................................... 17 8.3 Understanding how to rebuild packages....................................... 18 8.4 Offline builds..................................................... 18 8.5 Building out-of-tree.................................................. 18 The Buildroot user manual iii 8.6 Environment variables................................................ 19 8.7 Dealing efficiently with filesystem images...................................... 19 8.8 Graphing the dependencies between packages.................................... 20 8.9 Graphing the build duration.............................................. 21 8.10 Graphing the filesystem size contribution of packages................................ 21 8.11 Integration with Eclipse................................................ 22 8.12 Advanced usage.................................................... 22 8.12.1 Using the generated toolchain outside Buildroot............................... 22 8.12.2 Using gdb in Buildroot........................................... 22 8.12.3 Using ccache in Buildroot......................................... 23 8.12.4 Location of downloaded packages...................................... 23 8.12.5 Package-specific make targets........................................ 24 8.12.6 Using Buildroot during development..................................... 24 9 Project-specific customization 26 9.1 Recommended directory structure.......................................... 26 9.1.1 Implementing layered customizations.................................... 27 9.2 Keeping customizations outside of Buildroot..................................... 28 9.3 Storing the Buildroot configuration.......................................... 29 9.4 Storing the configuration of other components.................................... 29 9.5 Customizing the generated target filesystem..................................... 30 9.5.1 Setting file permissions and ownership and adding custom devices nodes................. 31 9.6 Adding custom user accounts............................................. 32 9.7 Customization after the images have been created.................................. 32 9.8 Adding project-specific patches............................................ 32 9.9 Adding project-specific packages........................................... 33 9.10 Quick guide to storing your project-specific customizations............................. 34 10 Frequently Asked Questions & Troubleshooting 36 10.1 The boot hangs after Starting network. ....................................... 36 10.2 Why is there no compiler on the target?....................................... 36 10.3 Why are there no development files on the target?.................................. 37 10.4 Why is there no documentation on the target?.................................... 37 10.5 Why are some packages not visible in the Buildroot config menu?......................... 37 10.6 Why not use the target directory as a chroot directory?............................... 37 10.7 Why doesn’t Buildroot generate binary packages (.deb, .ipkg. )?......................... 37 10.8 How to speed-up the build process?......................................... 38 11 Known issues 40 The Buildroot user manual iv 12 Legal notice and licensing 41 12.1 Complying with open source licenses........................................ 41 12.2 License abbreviations................................................. 42 12.3 Complying with the Buildroot license........................................ 42 12.3.1 Patches to packages.............................................. 43 13 Beyond Buildroot 44 13.1 Boot the generated images.............................................. 44 13.1.1 NFS boot................................................... 44 13.1.2 Live CD.................................................... 44 13.2 Chroot......................................................... 44 III Developer guide 45 14 How Buildroot works 46 15 Coding style 47 15.1 Config.in file................................................... 47 15.2 The .mk file...................................................... 47 15.3 The documentation.................................................. 49 16 Adding support for a particular board 50 17 Adding new packages to Buildroot 51 17.1 Package directory................................................... 51 17.2 Config files...................................................... 51 17.2.1 Config.in file............................................... 51 17.2.2 Config.in.host file........................................... 52 17.2.3 Choosing depends on or select .................................... 52 17.2.4 Dependencies on target and toolchain options................................ 54 17.2.5 Dependencies on a Linux kernel built by buildroot............................. 56 17.2.6 Dependencies on udev /dev management.................................. 56 17.2.7 Dependencies on features provided by virtual packages........................... 56 17.3 The .mk file...................................................... 56 17.4 The .hash file.................................................... 57 17.5 Infrastructure for packages with specific build systems............................... 58 17.5.1 generic-package tutorial........................................ 58 17.5.2 generic-package reference....................................... 60 17.6 Infrastructure for autotools-based packages..................................... 64 17.6.1 autotools-package tutorial...................................... 64 17.6.2 autotools-package reference..................................... 65 The Buildroot user manual v 17.7 Infrastructure for CMake-based packages...................................... 66 17.7.1 cmake-package tutorial.......................................... 66 17.7.2 cmake-package reference........................................ 67 17.8 Infrastructure for Python packages.......................................... 68 17.8.1 python-package tutorial......................................... 68 17.8.2 python-package reference........................................ 69 17.8.3 Generating a python-package from a PyPI repository......................... 70 17.8.4 python-package CFFI backend..................................... 70 17.9 Infrastructure for LuaRocks-based packages..................................... 71 17.9.1 luarocks-package tutorial....................................... 71 17.9.2 luarocks-package reference...................................... 71 17.10Infrastructure for Perl/CPAN packages........................................ 72 17.10.1 perl-package tutorial.......................................... 72 17.10.2 perl-package reference......................................... 73 17.11Infrastructure for virtual packages.......................................... 73 17.11.1 virtual-package tutorial........................................ 73 17.11.2 Virtual package’s Config.in file..................................... 74 17.11.3 Virtual package’s .mk file.......................................... 74 17.11.4 Provider’s Config.in file......................................... 74 17.11.5 Provider’s .mk file.............................................. 74 17.11.6 Notes on depending on a virtual package.................................. 75 17.11.7 Notes on depending on a specific provider.................................. 75 17.12Infrastructure for packages using kconfig for configuration files........................... 75 17.13Infrastructure for rebar-based packages........................................ 76 17.13.1 rebar-package tutorial.......................................... 76 17.13.2 rebar-package reference........................................ 77 17.14Infrastructure for packages building kernel modules................................. 77 17.14.1 kernel-module tutorial.......................................... 77 17.14.2 kernel-module reference........................................ 78 17.15Infrastructure for asciidoc documents........................................ 79 17.15.1 asciidoc-document tutorial...................................... 80 17.15.2 asciidoc-document reference..................................... 80 17.16Infrastructure specific to the Linux kernel package.................................. 81 17.16.1 linux-kernel-tools............................................... 81 17.16.2 linux-kernel-extensions............................................ 82 17.17Hooks available in the various
Recommended publications
  • Enchant 1300
    ENCHANT 1300 Quick Start Guide For more information, please visit harmankardon.com / 1. WHAT’S IN THE BOX Soundbar Remote Control VOL Power Cables* HDMI Cable AUX cable Optical Cable (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) (4ft, 1200mm) Wall-Mount Brackets Product Information & Wall-mounted guide * Power cable quantities vary by region / 2. PLACE YOUR SOUNDBAR 2a. Place the soundbar on the table TV 2B. Wall mount the soundbar Use tape to stick the wall-mounted paper guide on the wall, push a pen tip through the center to mark the wall-mounted bracket location and remove the paper. 1 TV WALLMOUNTED PAPER GUIDE Using the appropriate anchors, screw the wall mount brackets on the pen mark; Fix the screws at the back of soundbar; then hook the soundbar on the wall. 3 2 x3 4 TV / 3. CONNECT YOUR SOUNDBAR 3a. Connect to your TV Option 1 (Best): HDMI TV HDMI OUT HDMI (ARC) (TV ARC) Option 2: OPTICAL TV OPTICAL OUT OPTICAL IN 3b. Connect to other devices HDMI 1 HDMI 2 HDMI 3 HDMI OUT / 4. POWER YOUR SYSTEM 1 2 3 After the power cord is plugged in, the soundbar will take about 30 seconds to start up and then will enter standby mode, ready to use. / 5. CONNECT TO WI-FI 1 2 3 HK ENCHANT 1300 Once the soundbar connects to the internet for the first time, it may detect a software update to improve performance. This update may take a few minutes to complete. / 6. CONTROL YOUR SOUNDBAR 6a. Top Panel Volume Volume Power Down Up Source Display 6b.
    [Show full text]
  • PV204: Disk Encryption Lab
    PV204: Disk encryption lab May 12, 2016, Milan Broz <[email protected]> Introduction Encryption can provide confidentiality and authenticity of user data. It can be implemented on several different layes, including application, file system or storage device. Application encryption examples are PGP or ZIP compression with password. Encryption of files (inside filesystem or through independent layer like Linux eCryptfs) provides more generic solution. Yet some parts (like filesystem metadata) are still unencrypted. However this solution provides encrypted data with private key per user. (Every user can have own directory encrypted by own key.) Encryption of the low-level storage (disk) is called Full Disk Encryption (FDE). It is completely transparent to the user (no need to choose what to encrypt – the whole disk is encrypted). The encrypted disk behaves as the same as a disk without encryption. The major disadvantage is that everyone who knows the password can read the whole disk. Often we combine FDE with another encryption layer. The primary use of FDE is to provide data confidentiality in power-down mode (stolen laptop does not leak user data). Once the disk is unlocked, the main encryption key remains in system, usually directly in system RAM. Exercise II will show how easy is to get this key from memory image of system. Another disadvantage of FDE is that it usually cannot guarantee integrity of data. Encryption is fully transparent and length-preserving, the ciphertext and plaintext device are of the same size. There is no space to store any integrity information. This allows attacks by direct modification of ciphertext.
    [Show full text]
  • Empire News Spring 2009 (PDF 5733Kb)
    STATE UNIVERSITY OF NEW YORK Empire State College ALUMNI AND STUDENT NEWS VOLUME 34 • NUMBER 2 • SPRING 2009 Green Matters Cleansing Global Waters Marine Conservation in Alaska Energy in the Sunshine State Learners First Campaign Highlights Please recycle after reading Empire State College ALUMNI AND STUDENT NEWS C o n t e n t s VOLUME 34 • NUMBER 2 • SPRING 2009 Alan R. Davis President Mary Caroline Powers FEATURES Associate Vice President for Communications and Upfront . 1 Government Relations Publisher A Clear Initiative . 2 Maureen Winney Director of Alumni and Student Relations Water Woman . 3 Managing Editor Hope Ferguson Empire State College’s Adirondack Residency . 4 Community Relations Associate Editor A Planetary View from Alaska . 6 Gael Fischer Director of Publications/Designer Green Makeover: Home Edition . 8 Debra Park Secretary, Office of Communications and Recycling Electronics Could Create “Green Collar” Jobs. 10 Government Relations Alison’s Art . 11 Alumni News and Copy Editor Helping Haiti While So Far from Home . 12 CONTRIBUTORS Hugh Hammett The Jolly Green Garbage Man . 13 Vice President for External Affairs Evelyn Buchanan ‘99 Can a Mother’s Cause Have an Effect? . 15 Executive Director of the Foundation Diane Thompson Empire State College Going Green . 16 Director of Annual Giving Alta Schallehn Director of Gift Planning David Regan White ‘05 AROUND EMPIRE STATE COLLEGE Coordinator of Alumni Services Rebecca Smith LaVallee College News . 17 Assistant Director of Alumni and Student Relations Alumni News . 18 WRITERS Back to You . 21 William Ehmann, Rick Iuli, Day at the Races . 24 Liz W. Armtun, Kathryn Gallien, Kirk Starczewski, Tom Dimopoulos, Marie Morrison ‘06, Barbara Fischkin PHOTOGRAPHY On the cover Cover: Lake George and The Narrows from First Peak, Adirondacks N.Y.
    [Show full text]
  • Mcafee Foundstone Fsl Update
    2016-AUG-18 FSL version 7.5.841 MCAFEE FOUNDSTONE FSL UPDATE To better protect your environment McAfee has created this FSL check update for the Foundstone Product Suite. The following is a detailed summary of the new and updated checks included with this release. NEW CHECKS 20369 - Splunk Enterprise Multiple Vulnerabilities (SP-CAAAPQM) Category: General Vulnerability Assessment -> NonIntrusive -> Web Server Risk Level: High CVE: CVE-2013-0211, CVE-2015-2304, CVE-2016-1541, CVE-2016-2105, CVE-2016-2106, CVE-2016-2107, CVE-2016-2108, CVE- 2016-2109, CVE-2016-2176 Description Multiple vulnerabilities are present in some versions of Splunk Enterprise. Observation Splunk Enterprise is an operational intelligence solution Multiple vulnerabilities are present in some versions of Splunk Enterprise. The flaws lie in multiple components. Successful exploitation by a remote attacker could lead to the information disclosure of sensitive information, cause denial of service or execute arbitrary code. 20428 - (HT206899) Apple iCloud Multiple Vulnerabilities Prior To 5.2.1 Category: Windows Host Assessment -> Miscellaneous (CATEGORY REQUIRES CREDENTIALS) Risk Level: High CVE: CVE-2016-1684, CVE-2016-1836, CVE-2016-4447, CVE-2016-4448, CVE-2016-4449, CVE-2016-4483, CVE-2016-4607, CVE- 2016-4608, CVE-2016-4609, CVE-2016-4610, CVE-2016-4612, CVE-2016-4614, CVE-2016-4615, CVE-2016-4616, CVE-2016-4619 Description Multiple vulnerabilities are present in some versions of Apple iCloud. Observation Apple iCloud is a manager for the Apple's could based storage service. Multiple vulnerabilities are present in some versions of Apple iCloud. The flaws lie in several components. Successful exploitation could allow an attacker to retrieve sensitive data, cause a denial of service condition or have other unspecified impact on the target system.
    [Show full text]
  • OM-Cube Project
    OM-Cube project V. Hiribarren, N. Marchand, N. Talfer [email protected] - [email protected] - [email protected] Abstract. The OM-Cube project is composed of several components like a minimal operating system, a multi- media player, a LCD display and an infra-red controller. They should be chosen to fit the hardware of an em- bedded system. Several other similar projects can provide information on the software that can be chosen. This paper aims to examine the different available tools to build the OM-Multimedia machine. The main purpose is to explore different ways to build an embedded system that fits the hardware and fulfills the project. 1 A Minimal Operating System The operating system is the core of the embedded system, and therefore should be chosen with care. Because of its popu- larity, a Linux based system seems the best choice, but other open systems exist and should be considered. After having elected a system, all unnecessary components may be removed to get a minimal operating system. 1.1 A Linux Operating System Using a Linux kernel has several advantages. As it’s a popular kernel, many drivers and documentation are available. Linux is an open source kernel; therefore it enables anyone to modify its sources and to recompile it. Using Linux in an embedded system requires adapting the kernel to the hardware and to the system needs. A simple method for building a Linux embed- ded system is to create a partition on a development host and to mount it on a temporary mount point. This partition is filled as one goes along and then, the final distribution is put on the target host [Fich02] [LFS].
    [Show full text]
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • Load Balancing for Heterogeneous Web Servers
    Load Balancing for Heterogeneous Web Servers Adam Pi´orkowski1, Aleksander Kempny2, Adrian Hajduk1, and Jacek Strzelczyk1 1 Department of Geoinfomatics and Applied Computer Science, AGH University of Science and Technology, Cracow, Poland {adam.piorkowski,jacek.strzelczyk}@agh.edu.pl http://www.agh.edu.pl 2 Adult Congenital and Valvular Heart Disease Center University of Muenster, Muenster, Germany [email protected] http://www.ukmuenster.de Abstract. A load balancing issue for heterogeneous web servers is de- scribed in this article. The review of algorithms and solutions is shown. The selected Internet service for on-line echocardiography training is presented. The independence of simultaneous requests for this server is proved. Results of experimental tests are presented3. Key words: load balancing, scalability, web server, minimum response time, throughput, on-line simulator 1 Introduction Modern web servers can handle millions of queries, although the performance of a single node is limited. Performance can be continuously increased, if the services are designed so that they can be scaled. The concept of scalability is closely related to load balancing. This technique has been used since the beginning of the first distributed systems, including rich client architecture. Most of the complex web systems use load balancing to improve performance, availability and security [1{4]. 2 Load Balancing in Cluster of web servers Clustering of web servers is a method of constructing scalable Internet services. The basic idea behind the construction of such a service is to set the relay server 3 This is the accepted version of: Piorkowski, A., Kempny, A., Hajduk, A., Strzelczyk, J.: Load Balancing for Heterogeneous Web Servers.
    [Show full text]
  • Environmental Protection Commission[567]
    IAC 5/19/21 Environmental Protection[567] Analysis, p.1 ENVIRONMENTAL PROTECTION COMMISSION[567] Former Water, Air and Waste Management[900], renamed by 1986 Iowa Acts, chapter 1245, Environmental Protection Commission under the “umbrella” of the Department of Natural Resources. TITLE I GENERAL CHAPTER 1 OPERATION OF ENVIRONMENTAL PROTECTION COMMISSION 1.1(17A,455A) Scope 1.2(17A,455A) Time of meetings 1.3(17A,455A) Place of meetings 1.4(17A,455A) Notification of meetings 1.5(17A,455A) Attendance and participation by the public 1.6(17A,455A) Quorum and voting requirements 1.7(17A,455A) Conduct of meeting 1.8(17A,455A) Minutes, transcripts, and recordings of meetings 1.9(17A,455A) Officers and duties 1.10(17A,455A) Election and succession of officers 1.11(68B) Sales of goods and services CHAPTER 2 PUBLIC RECORDS AND FAIR INFORMATION PRACTICES (Uniform Rules) 2.1(17A,22) Adoption by reference CHAPTER 3 SUBMISSION OF INFORMATION AND COMPLAINTS—INVESTIGATIONS 3.1(17A,455B) Adoption by reference CHAPTER 4 AGENCY PROCEDURE FOR RULE MAKING 4.1(17A) Adoption by reference CHAPTER 5 PETITIONS FOR RULE MAKING 5.1(17A) Adoption by reference CHAPTER 6 DECLARATORY ORDERS 6.1(17A) Adoption by reference CHAPTER 7 RULES OF PRACTICE IN CONTESTED CASES 7.1(17A) Adoption by reference CHAPTER 8 CONTRACTS FOR PUBLIC IMPROVEMENTS AND PROFESSIONAL SERVICES 8.1(17A) Adoption by reference CHAPTER 9 DELEGATION OF CONSTRUCTION PERMITTING AUTHORITY 9.1(455B) Scope 9.2(455B,17A) Forms 9.3(455B) Procedures 9.4(455B) Criteria for permitting authority at local public
    [Show full text]
  • MPLAYER-10 Mplayer-1.0Pre7-Copyright
    MPLAYER-10 MPlayer-1.0pre7-Copyright MPlayer was originally written by Árpád Gereöffy and has been extended and worked on by many more since then, see the AUTHORS file for an (incomplete) list. You are free to use it under the terms of the GNU General Public License, as described in the LICENSE file. MPlayer as a whole is copyrighted by the MPlayer team. Individual copyright notices can be found in the file headers. Furthermore, MPlayer includes code from several external sources: Name: FFmpeg Version: CVS snapshot Homepage: http://www.ffmpeg.org Directory: libavcodec, libavformat License: GNU Lesser General Public License, some parts GNU General Public License, GNU General Public License when combined Name: FAAD2 Version: 2.1 beta (20040712 CVS snapshot) + portability patches Homepage: http://www.audiocoding.com Directory: libfaad2 License: GNU General Public License Name: GSM 06.10 library Version: patchlevel 10 Homepage: http://kbs.cs.tu-berlin.de/~jutta/toast.html Directory: libmpcodecs/native/ License: permissive, see libmpcodecs/native/xa_gsm.c Name: liba52 Version: 0.7.1b + patches Homepage: http://liba52.sourceforge.net/ Directory: liba52 License: GNU General Public License Name: libdvdcss Version: 1.2.8 + patches Homepage: http://developers.videolan.org/libdvdcss/ Directory: libmpdvdkit2 License: GNU General Public License Name: libdvdread Version: 0.9.3 + patches Homepage: http://www.dtek.chalmers.se/groups/dvd/development.shtml Directory: libmpdvdkit2 License: GNU General Public License Name: libmpeg2 Version: 0.4.0b + patches
    [Show full text]
  • Institutionen För Datavetenskap Department of Computer and Information Science
    Institutionen för datavetenskap Department of Computer and Information Science Final thesis Simulation of Set-top box Components on an X86 Architecture by Implementing a Hardware Abstraction Layer by Faruk Emre Sahin Muhammad Salman Khan LITH-IDA-EX—10/050--SE 2010-12-25 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Linköping University Department of Computer and Information Science Final Thesis Simulation of Set-top box Components on an X86 Architecture by Implementing a Hardware Abstraction Layer by Faruk Emre Sahin Muhammad Salman Khan LITH-IDA-EX—10/050—SE 2010-12-25 Supervisors: Fredrik Hallenberg, Tomas Taleus R&D at Motorola (Linköping) Examiner: Prof. Dr. Christoph Kessler Dept. Of Computer and Information Science at Linköpings universitet Abstract The KreaTV Application Development Kit (ADK) product of Motorola en- ables application developers to create high level applications and browser plugins for the IPSTB system. As a result, customers will reduce develop- ment time, cost and supplier dependency. The main goal of this thesis was to port this platform to a standard Linux PC to make it easy to trace the bugs and debug the code. This work has been done by implementing a hardware abstraction layer(HAL)for Linux Operating System. HAL encapsulates the hardware dependent code and HAL APIs provide an abstraction of underlying architecture to the oper- ating system and to application software. So, the embedded platform can be emulated on a standard Linux PC by implementing a HAL for it. We have successfully built the basic building blocks of HAL with some performance degradation.
    [Show full text]
  • ٢ SQL Server ﻣﺎﯾ ﺮوﺳﺎﻓﺖ ﺑﺎ ﻫﻤ ﺎری Sybase ﭘﺎﯾ ﺎه داده اﻧﺤﺼﺎری ﺧﻮد را اراﺋﻪ داده اﺳﺖ
    داﻧﺸ ﺎه ﺷﻬﯿﺪ ﺑﻬﺸﺘ داﻧﺸ ﺪه ﻣﻬﻨﺪﺳ ﺑﺮق و ﮐﺎﻣﭙﯿﻮﺗﺮ ﭘﺮوژهی ﮐﺎرﺷﻨﺎﺳ ﻣﻬﻨﺪﺳ ﮐﺎﻣﭙﯿﻮﺗﺮ ﮔﺮاﯾﺶ ﻧﺮم اﻓﺰار ﻣﻮﺿﻮع ﭘﺮوژه: ﭼﻬﺎرﭼﻮب ﺗﻮﺳﻌﻪ وب اﻣﻦ اﺳﺘﺎد راﻫﻨﻤﺎ: ﺟﻨﺎب آﻗﺎی دﮐﺘﺮ ذاﮐﺮاﻟﺤﺴﯿﻨ ﮔﺮدآوردﻧﺪه: ﻋﺒﺎس ﻧﺎدری اﻓﻮﺷﺘﻪ [email protected] ﺑﻬﺎر ١٣٩١ ﭼ ﯿﺪه: وب ﺑﻪ ﻋﻨﻮان ﻣﻬﻤﺘﺮﯾﻦ ﺑﺴﺘﺮ اراﺋﻪ ﻧﺮماﻓﺰار و ﺳﺮوﯾﺲ، ﺗﺎ ﺟﺎﯾﯽ ﺟﻠﻮ رﻓﺘﻪ ﮐﻪ اﻣﺮوزه ﻣﺤﯿﻂﻫﺎی ﻪﻣﺎﻧﺮﺑﺳﺎزی و ﺣﺘ ﺳﯿﺴﺘﻢﻫﺎی ﻋﺎﻣﻞ ﺗﺤﺖ وب ﻗﺮار ﮔﺮﻓﺘﻪاﻧﺪ.وب ﯾ ﺑﺴﺘﺮ و ﭘﺮوﺗﮑﻞ ﺑﺴﯿﺎر ﺳﺎده اﺳﺖ ﮐﻪ ﺑﺎ اﻫﺪاف دﯾ ﺮی ﻃﺮاﺣ ﺷﺪه ﺑﻮده و ﺑﻪ ﺻﻮرت اﻧﻔﺠﺎری ﮔﺴﺘﺮش ﯾﺎﻓﺘﻪ اﺳﺖ، ﺑﻪ ﻫﻤﯿﻦ دﻟﯿﻞ ﺗﻮﻟﯿﺪ ﻧﺮم- اﻓﺰارﻫﺎی ﻣﺒﺘﻨ ﺑﺮ وب ﻧﯿﺎزﻣﻨﺪ ﭼﻬﺎرﭼﻮبﻫﺎی ﮔﺴﺘﺮده و ﻗﺪرﺗﻤﻨﺪی ﻫﺴﺘﻨﺪ. اﯾﻦ ﭼﻬﺎرﭼﻮبﻫﺎی ﻣﻌﻤﻮﻻ در اﻧﺠﻤﻦﻫﺎی ﻣﺘﻦﺑﺎز ﺷ ﻞ ﮔﺮﻓﺘﻪاﻧﺪ و ﻧﻘﺎط ﺿﻌﻒ اﻣﻨﯿﺘ دارﻧﺪ. در اﯾﻦ ﺳﻨﺪ ﭼﻬﺎرﭼﻮب ﺗﻮﺳﻌﻪ وب اﻣﻦ، ﺑﺎ اﺗﮑﺎ ﺑﻪ دو ﭼﻬﺎرﭼﻮب ﺗﻮﻟﯿﺪ ﺷﺪه ﺑﺎ ﺗﻮﺟﻪ ﺑﻪ اﻣﻨﯿﺖ وب ﻣﻄﺮح ﺷﺪهاﻧﺪ. اﺑﺘﺪا ﻣﻔﺎﻫﯿﻢ و ﺳﺎﺧﺘﺎر وب ﺑﻪ ﺗﻔﺼﯿﻞ ﺑﺤﺚ ﺷﺪه ﺗﺎ ﺧﻮاﻧﻨﺪه ﺑﺘﻮاﻧﺪ ﻧﯿﺎز و ﭘﺎﺳ را ﺑﻪ ﺧﻮﺑﯽ درک ﮐﻨﺪ. ﺳﭙﺲ ﻣﺨﺎﻃﺮات ﻣﻮﺟﻮد در اﻣﻨﯿﺖ وب ﻣﻄﺮح و ﺑﺮرﺳ ﺷﺪهاﻧﺪ و در ﺑﺨﺶ اﻧﺘﻬﺎﯾﯽ راﻫ ﺎرﻫﺎی ﻣﻘﺎﺑﻠﻪ ﺑﺎ اﯾﻦ ﻣﺨﺎﻃﺮات اراﺋﻪ ﺷﺪهاﻧﺪ. ﻣﻔﺎﻫﯿﻤ ﻣﺎﻧﻨﺪ ﻣﻌﻤﺎری وب، ﭘﺮوﺗﮑﻞﻫﺎی ﻣﺠﻮد در وب، ﺗﮑﻨﻮﻟﻮژیﻫﺎی ﻣﻮرد اﺳﺘﻔﺎده در وب، ﮐﺎوﺷ ﺮﻫﺎی وب، اﻣﻨﯿﺖ ﻋﻤﻮﻣ وب، اﻣﻨﯿﺖ ﻧﺮماﻓﺰار، MVC، ﭼﻬﺎرﭼﻮبﻫﺎی ﺗﻮﺳﻌﻪ وب و ﻧﯿﺎزﻣﻨﺪیﻫﺎی آﻧﺎن، ﻣﻌﻀﻼت ﻣﺨﺘﻠﻒ وب، ﺗﻌﺎرﯾﻒ اﻣﻨﯿﺖ اﻃﻼﻋﺎت، راﻫ ﺎرﻫﺎی ﺗﻔﺼﯿﻠ و ﻓﻨ ﻣﻘﺎﺑﻠﻪ ﺑﺎ ﻣﻌﻀﻼت اﻣﻨﯿﺘ و دﯾﺪﮔﺎه درﺳﺖ ﺑﻪ اﻣﻨﯿﺖ وب، ﺑﺮﺧ از ﻣﻄﺎﻟﺐ ﭘﻮﺷﺶ داده ﺷﺪه در اﯾﻦ ﺳﻨﺪ ﻣ ﺪﻨﺷﺎﺑ. ﮐﻠﻤﺎت ﮐﻠﯿﺪی: وب، اﻣﻨﯿﺖ، اﻣﻨﯿﺖ ﻧﺮماﻓﺰار، ﭼﻬﺎرﭼﻮب، ﻧﻔﻮذﮔﺮی، ﺗﻮﺳﻌﻪ ﻧﺮماﻓﺰار، ﻣﻬﻨﺪﺳ ﻧﺮماﻓﺰار ﺐﻟﺎﻄﻣ ﺖﺳﺮﻬﻓ 1 ﻪﻣﺪﻘﻣ .............................................................................١ 2 ﻓﺮﻌﻣ ......................................................................٣ 2.1 اﻣﻨﯿﺖ ﻧﺮم اﻓﺰار ..............................................................
    [Show full text]
  • Fedora Core Works--Without the Fluff That Bogs Down Other Books and Help/How-To Web Sites
    Fedora Linux By Chris Tyler ............................................... Publisher: O'Reilly Pub Date: October 01, 2006 ISBN-10: 0-596-52682-2 ISBN-13: 978-0-596-52682-5 Pages: 504 Table of Contents | Index "Neither a "Starting Linux" book nor a dry reference manual, this book has a lot to offer to those coming to Fedora from other operating systems or distros." -- Behdad Esfahbod, Fedora developer This book will get you up to speed quickly on Fedora Linux, a securely-designed Linux distribution that includes a massive selection of free software packages. Fedora is hardened out-of-the-box, it's easy to install, and extensively customizable - and this book shows you how to make Fedora work for you. Fedora Linux: A Complete Guide to Red Hat's Community Distribution will take you deep into essential Fedora tasks and activities by presenting them in easy-to-learn modules. From installation and configuration through advanced topics such as administration, security, and virtualization, this book captures the important details of how Fedora Core works--without the fluff that bogs down other books and help/how-to web sites. Instead, you can learn from a concise task-based approach to using Fedora as both a desktop and server operating system. In this book, you'll learn how to: Install Fedora and perform basic administrative tasks Configure the KDE and GNOME desktops Get power management working on your notebook computer and hop on a wired or wireless network Find, install, and update any of the thousands of packages available for Fedora Perform backups, increase reliability with RAID, and manage your disks with logical volumes Set up a server with file sharing, DNS, DHCP, email, a Web server, and more Work with Fedora's security features including SELinux, PAM, and Access Control Lists (ACLs) Whether you are running the stable version of Fedora Core or bleeding-edge Rawhide releases, this book has something for every level of user.
    [Show full text]