diff options
Diffstat (limited to 'doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml')
-rw-r--r-- | doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml | 101 |
1 files changed, 101 insertions, 0 deletions
diff --git a/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml b/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml new file mode 100644 index 0000000..2215ba8 --- /dev/null +++ b/doc/book-enea-linux-user-guide/doc/prerequisites_and_requirements.xml | |||
@@ -0,0 +1,101 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | ||
2 | <chapter id="prereq_reqs"> | ||
3 | <title>Prerequisites and Requirements</title> | ||
4 | |||
5 | <para>Building Enea Linux or compiling applications requires that your git | ||
6 | environment be setup properly and for certain packages to be installed on | ||
7 | your Linux development host. The following chapter details the | ||
8 | configurations needed on the build environment in order to properly use Enea | ||
9 | Linux.</para> | ||
10 | |||
11 | <section id="gitconfig"> | ||
12 | <title>Git Configuration</title> | ||
13 | |||
14 | <para>If you intend to get Enea Linux sources and build Enea Linux | ||
15 | yourself, you will need Git installed in your build environemtn. Please | ||
16 | refer to <ulink | ||
17 | url="https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup">Getting | ||
18 | Started - First-Time Git Setup</ulink>, for more details on how to set up | ||
19 | your git environment correctly, including how to set your identity using | ||
20 | the following commands:</para> | ||
21 | |||
22 | <programlisting>$ git config --global user.name "John Doe" | ||
23 | $ git config --global user.email johndoe@example.com</programlisting> | ||
24 | </section> | ||
25 | |||
26 | <section id="hostpackages"> | ||
27 | <title>Host Packages</title> | ||
28 | |||
29 | <para>In order to work with Enea Linux, you need a set of tools installed | ||
30 | on the build machine, depending on the scenario you use. The following | ||
31 | chapters will describe what tools to install on the build machine.</para> | ||
32 | |||
33 | <section id="prebuiltprereq"> | ||
34 | <title>Using Pre-Build Binaries</title> | ||
35 | |||
36 | <para>Using the pre-built binaries, you can get up and running more | ||
37 | quickly. Since building is not required, there are not a lot of packaes | ||
38 | and tools that need to be installed but a few are still required:</para> | ||
39 | |||
40 | <itemizedlist> | ||
41 | <listitem> | ||
42 | <para>wget - for downloading the Enea Linux binaries</para> | ||
43 | </listitem> | ||
44 | |||
45 | <listitem> | ||
46 | <para>tar - for decompressing the Enea Linux release</para> | ||
47 | </listitem> | ||
48 | |||
49 | <listitem> | ||
50 | <para>tftpboot server - for deploying Enea Linux on target</para> | ||
51 | </listitem> | ||
52 | |||
53 | <listitem> | ||
54 | <para>NFS server - in case you want to mount the root file system | ||
55 | over NFS</para> | ||
56 | </listitem> | ||
57 | </itemizedlist> | ||
58 | </section> | ||
59 | |||
60 | <section id="hostprereqpackages"> | ||
61 | <title>Required Packages for the Host Development System</title> | ||
62 | |||
63 | <para>Building Enea Linux requires a set of packages to be installed on | ||
64 | your Linux development host. The list of required packages is described | ||
65 | in the <ulink | ||
66 | url="https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#required-packages-for-the-host-development-system">Yocto | ||
67 | Project reference manual</ulink>.</para> | ||
68 | </section> | ||
69 | </section> | ||
70 | |||
71 | <section id="sysshell_config"> | ||
72 | <title>Default Shell Configuration</title> | ||
73 | |||
74 | <para>Before installing Enea Linux, make sure that | ||
75 | <filename>bash</filename> is the default shell.</para> | ||
76 | |||
77 | <para><emphasis role="bold">To verify the default system | ||
78 | shell</emphasis></para> | ||
79 | |||
80 | <itemizedlist> | ||
81 | <listitem> | ||
82 | <para>If your system runs Ubuntu, use list to verify if | ||
83 | <filename>/usr/bin</filename> is a symbolic link to <emphasis | ||
84 | role="bold">bash</emphasis>:</para> | ||
85 | |||
86 | <programlisting># ls -l /bin/sh | ||
87 | lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -> bash</programlisting> | ||
88 | </listitem> | ||
89 | |||
90 | <listitem> | ||
91 | <para>Optionally, in case the link points to <literal>dash</literal>, | ||
92 | change it through the following steps:</para> | ||
93 | |||
94 | <programlisting># ls -l /bin/sh | ||
95 | lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -> dash | ||
96 | # sudo dpkg-reconfigure dash | ||
97 | Use dash as the default system shell (/bin/sh)? No</programlisting> | ||
98 | </listitem> | ||
99 | </itemizedlist> | ||
100 | </section> | ||
101 | </chapter> | ||