From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@openembedded.org
Subject: Re: getting started - docbook
Date: Wed, 31 Oct 2007 13:26:35 +0100 [thread overview]
Message-ID: <4728747B.6020805@vollmann.ch> (raw)
In-Reply-To: <20071027153928.GA6118@lenovo>
David Farning wrote:
> 1.1. Linux ................................................
> 1.1.1. Linux Overview ...................
> 1.1.2. Linux Arctoture ...................
> 1.1.3. Linux Development Model..
> 1.1.4. Linux Open Source..............
> 1.2. Embedded Device ............................
> 1.2.1. Device Architure..................
> 1.2.2. Processor..............................
> 1.2.3. Storage.................................
> 1.2.4. Device..................................
> 1.3. Linux Distribution............................
> 1.3.1. Kernel ..................................
> 1.3.2. Userspace.............................
> 1.3.3. File System ..........................
> 1.3.4. Updating ..............................
> 1.4. System startup ..................................
> ...
> 1.5. Host/Target .......................................
> ...
> 1.6. Overview ..........................................
> 1.7. History..............................................
This looks like a (more or less general) introduction to
"Embedded Linux".
No problems with that, but make sure not to confuse this with
documentation on how to use OpenEmbedded.
I think there are two different targets for documentation:
1 - How to use OpenEmbedded
2 - What to build with OpenEmbedded
There's always a need for both, but I think it's helpful
to keep them separate (but probably reference each other).
Your TOC for an introduction looks like documentation for 2.
Detlef
next prev parent reply other threads:[~2007-10-31 16:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 22:05 getting started - docbook Filippo Basso
2007-10-25 0:19 ` David Farning
2007-10-25 7:37 ` Koen Kooi
2007-10-25 12:11 ` David Farning
2007-10-25 17:34 ` Cliff Brake
2007-10-26 13:45 ` David Farning
2007-10-27 11:06 ` Tobias Pflug
2007-10-27 15:39 ` David Farning
2007-10-27 17:27 ` Koen Kooi
2007-10-27 21:26 ` David Farning
2007-10-27 22:09 ` Tobias Pflug
2007-10-28 8:06 ` Stelios Koroneos
2007-10-28 8:42 ` Koen Kooi
2007-10-31 12:26 ` Detlef Vollmann [this message]
2007-10-31 18:43 ` Tobias Pflug
2007-10-31 20:12 ` David Farning
2007-10-31 21:30 ` Filippo Basso
2007-10-31 12:34 ` Detlef Vollmann
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 3:38 David Farning
2007-10-22 7:14 ` Koen Kooi
2007-10-22 8:35 ` Koen Kooi
2007-10-23 5:01 ` David Farning
2007-10-23 7:01 ` Koen Kooi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4728747B.6020805@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.