diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/adding-packages-directory.txt | 4 | ||||
| -rw-r--r-- | docs/prerequisite.txt | 12 | ||||
| -rw-r--r-- | docs/running-openadk.txt | 30 |
3 files changed, 19 insertions, 27 deletions
diff --git a/docs/adding-packages-directory.txt b/docs/adding-packages-directory.txt index 227107a89..2f87b7c3e 100644 --- a/docs/adding-packages-directory.txt +++ b/docs/adding-packages-directory.txt @@ -45,10 +45,6 @@ are space separated and can be negated with ! as a prefix. ** variable used PKG_LIBC_DEPENDS ** allowed values are: uclibc-ng glibc musl -* Host system -** variable used PKG_HOST_DEPENDS -** allowed values are: linux darwin cygwin freebsd netbsd openbsd - * Special support needed (Toolchain with Threads, Realtime or C++ enabled) ** variable used PKG_NEEDS ** allowed values are: threads rt c++ diff --git a/docs/prerequisite.txt b/docs/prerequisite.txt index 342592414..32fb77a75 100644 --- a/docs/prerequisite.txt +++ b/docs/prerequisite.txt @@ -5,16 +5,11 @@ System requirements ------------------- -OpenADK is designed to run on Linux systems. But there is support to run on -MacOS X, Windows with Cygwin, OpenBSD, MirBSD, NetBSD and FreeBSD. Main -development happens on Debian/GNU Linux and MacOS X. The other host platforms -are occasionally tested. OpenADK detects the host system and displays only the -software packages, which are known to be cross-compilable on the used host. -For example OpenJDK7 is only cross-compilable on a Linux host. - +OpenADK is designed to run on Linux systems. +Main development happens on Debian/GNU Linux. OpenADK needs some software to be already installed on the host system; here is the list of the mandatory packages, -package names may vary between host systems. +package names may vary between Linux systems. * Build tools: @@ -28,6 +23,7 @@ package names may vary between host systems. ** +git+ ** +strings+ ** +curl or wget+ +** +xz+ ** +ncurses development files+ ** +zlib development files+ ** +libc development files+ diff --git a/docs/running-openadk.txt b/docs/running-openadk.txt index a0676bbce..205b0d292 100644 --- a/docs/running-openadk.txt +++ b/docs/running-openadk.txt @@ -60,8 +60,6 @@ OpenADK is generated while producing the +base-files+ package. The main job the default inittab does is to start the +/etc/init.d/rcS+ shell script, and start one or more +getty+ programs (which provides a login prompt). -Support for systemd and s6 is very experimental at the moment. - /dev management ~~~~~~~~~~~~~~~ @@ -73,19 +71,21 @@ hardware devices, even if they are properly recognized by the Linux kernel. In OpenADK you can choose between different types of device managements. -OpenADK defaults to *dynamic device nodes using devtmpfs and mdev*. This method -relies on the _devtmpfs_ virtual filesystem in the kernel, which is enabled by -default for all OpenADK generated kernels, and adds the +mdev+ userspace -utility on top of it. +mdev+ is a program part of Busybox that the kernel will -call every time a device is added or removed. Thanks to the +/etc/mdev.conf+ -configuration file, +mdev+ can be configured to for example, set specific -permissions or ownership on a device file, call a script or application -whenever a device appears or disappear, etc. Basically, it allows _userspace_ -to react on device addition and removal events. +mdev+ is also important if you -have devices that require a firmware, as it will be responsible for pushing the -firmware contents to the kernel. +mdev+ is a lightweight implementation (with -fewer features) of +udev+. For more details about +mdev+ and the syntax of its -configuration file, see http://git.busybox.net/busybox/tree/docs/mdev.txt. +OpenADK defaults to *static device nodes using devtmpfs*. That is the simplest +way available. Most users might like to change it to *dynamic device nodes +using devtmpfs and mdev*. This method relies on the _devtmpfs_ virtual +filesystem in the kernel, which is enabled by default for all OpenADK generated +kernels, and adds the +mdev+ userspace utility on top of it. +mdev+ is a +program part of Busybox that the kernel will call every time a device is added +or removed. Thanks to the +/etc/mdev.conf+ configuration file, +mdev+ can be +configured to for example, set specific permissions or ownership on a device +file, call a script or application whenever a device appears or disappear, etc. +Basically, it allows _userspace_ to react on device addition and removal +events. +mdev+ is also important if you have devices that require a firmware, +as it will be responsible for pushing the firmware contents to the kernel. ++mdev+ is a lightweight implementation (with fewer features) of +udev+. For +more details about +mdev+ and the syntax of its configuration file, see +http://git.busybox.net/busybox/tree/docs/mdev.txt. initscripts ~~~~~~~~~~~ |